For what it's worth, the way NASA cFS teams use github is very unintuitive to me. I tend to think of issues on github as being about low level code changes, so the idea of having discussions like this one on github never crosses my mind (thanks for posting the link to this to the mailing list). If lots of other cFS users are like me, that probably explains why you don't get a lot of people following the repos.

Seems to me the cFS community needs services for:

internal cFS development discussions
usage questions
high level info broadcast from internal devs to users

Right now I'm never sure where to go for any of the above, and end up either posting to the mailing list or trying to see if a question fits as an issue in one of the repos. I've gotten better response rates from the mailing list, so have moved away from making github issues.

I personally would prefer for the services for the three items above to be separate. I notice that I'm less likely to send user-level questions to the mailing list because I perceive it to be mostly for internal dev discussions.

I also think cFS needs a central web page that has way more entry level info in it. I personally get confused about what versions are what, and what works with what, and how to get started. AFAIK, the only place for that info right now is spread out among a bunch of different repos and the mailing list. That makes it super hard to get a new dev up and running with cFS in our org.

If you had a community web page that had entry-level info, you could also put something like @astrogeco's screenshots there. I don't personally have an opinion on slack/discord/whatever. I do think you need to make it easier for people to know whatever decision you pick. I suspect the failure of the slack channel recently is because it was super hard to find if you missed the original emails about it.

I guess my main ask is that there be a single cFS web site where everything else is linked from. Then if I have a question I go there and look around, and eventually find whatever services you decide on.

Community space for Q&A and support #207

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions