This is my first ever github pull request. I hope I'm doing this right.
I have added links to the new 'clever-stack' Google Group on the main documentation page.
I think the best way to handle user communication needs is for a discussion to begin in the Google Group. If it's just a matter of someone needing instructions, then it can end there. If there's a bona fide bug, then someone can make a github issue out of it in the appropriate repository and include a link to the Google Group thread in the issue.
Rationale:
Discussions are permanent. Chatroom conversations are not.
Google Group discussions are easier to find with a search engine than github issue discussions.
There will be only one Google Group for all of Cleverstack even though there are multiple Cleverstack repositories. This means people will only need to look in one place to find answers to all Cleverstack questions and not have to decide, possibly badly, which repository is the best place to put their question.
People are not used to the idea of using github issues for questions and discussions. I have many times been reprimanded for doing that and had my question abruptly "closed"
Questions as github issues require one of the contributors to label them as such. This is extra work and something that can possibly be forgotten to do.
Users can easily control their subscription to the Google Group to get as many notifications as they want
This is my first ever github pull request. I hope I'm doing this right.
I have added links to the new 'clever-stack' Google Group on the main documentation page.
I think the best way to handle user communication needs is for a discussion to begin in the Google Group. If it's just a matter of someone needing instructions, then it can end there. If there's a bona fide bug, then someone can make a github issue out of it in the appropriate repository and include a link to the Google Group thread in the issue.
Rationale: