Because much of the developers are already using the github issue and discussion forums, for me it’s the question, if we should enable the “discussion forum” on the hipparchus github projects settings?
I’m not familiar with GitHub discussions.
Having the Hipparchus forum in the same place as the Orekit forum is interesting to benefit from the Orekit visibility.
At the opposite, we always talk about the “Orekit forum”, not the " Orekit/Hipparchus " forum. So, this visibility has the disadvantage of slightly masking the existence of Hippparchus. In fact, Hipparchus and Orekit are two different projects, even if one has a dependency to the other one. I think that the two are usually linked, like for the forum, because a lot of Hipparchus’ developers are also Orekit developers. But in fact, there are no reason to have both forums in the same place.
In summary, I think they are no reason to have Hipparchus discussions in the Orekit forum because it is an independent project. But, as Orekit and Hipparchus share a lot of developers, it is easy for them to have both discussions in the same area
I don’t want my remarks to be a source of inhibition and frustration. It therefore seems useful to clarify my previous comments. As I’m not involved in the project (I’m just the “ops” in charge of the platform and the guy who implemented the CI/CD pipeline of Hipparchus with Github Actions), my opinion doesn’t count. I just wanted to point out that the technical arguments were wrong and that Discourse offers all the features mentioned and many more.
The community must be free to adopt the tools it prefers, even if I personally have a soft spot for free (open source) and self-hosted tools, which offer better guarantees of independence and freedom.