Slack:

The Slack page should exist for user/collaborator discussion, NOT issue tracking. Slack is not forever nor indexed and we should avoid simple repeat questions and focus on actual chat and discussion. We can have separate channels for each repo as well as other open source projects that use HySDS or a version of it. Issue tracking and specific question/answer should exist somewhere indexable like a google group or stack overflow.

There is also the question of affiliation listings on slack. Should users list their affiliation/interest in HySDS on their slack profile? This could be useful for users to know who they're talking to or what their motivation is for HySDS. The risk here is that there is no way to enforce this rule, so anyone can be “from JPL.” I feel that this could be useful for the community but users (and especially those at JPL) will have to be cautious about authenticity. Personally I think listing affiliation is a good idea, and not a huge risk.

Google Group:

A google group could serve as a less formal question/answer platform akin to stack overflow. This would be easily searchable for new users, and more for documenting the common pitfalls of getting to know HySDS rather than formal issue tracking, which will be done in JIRA.

JIRA:

For formal issue tracking/feature requests/general ticketing. I don’t believe everyone should have access to file tickets as that would likely overload the team with nonsense. Maybe an admin (or two) from each contributor team has ticketing privileges?

GitHub:

Pull requests and version management, but also where we will host the HySDS website with GitHub pages. See Open MCT (https://nasa.github.io/openmct/) for reference. The GitHub website will host version dependent documentation that is unlikely to change. This is the documentation mostly closely tied to the source code. Doing this facilitates better documentation from contributors. Actual HTML and CSS will (hopefully) make this a prettier site than the wiki.

Atlassian wiki:

The wiki will host all the generalized information about HySDS. This is for people who want an overview, to get a general understanding of HySDS and its components. Everything on the wiki is subject to change, it should evolve with HySDS. Things like the contributor guide, style guides, community overview, and generalized architecture documentation will be hosted here. It’s best to keep these pages as easily digestible chunks that the average person can skim without getting overwhelmed. That being said, more detailed information should be available for more advanced readers without having to dig too deep.

Browser not supported