You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have three different project communication channels identified:
Google Groups: intended for use, not yet purchased; gated by domain transfer from IBM and ensuring we comply with Red Hat IT guidelines as needed - @cybette is on this with help from @jasonbrooks
We need to document how each of these communication channels will be used for the project in the project FAQ.
Here is my proposal for how each communication channel should be used:
mailing lists (e.g. Google Groups) good for async discussion
Slack for real-time discussion including private coordination where required amongst maintainers
GitHub discussions are useful for things like writing up a big bad bug report that's under investigation with up to the minute details, easy to point folks to in Slack or on mailing lists
Note that just using GitHub discussions is not great because it doesn't allow folks to discuss things with the project who are less familiar with GitHub (and, for example, perhaps working in regulated industries where GitHub is hard - e.g. tons of banks don't let employees access GitHub, but they can use an email list); need to be conscious about using GitHub discussions with care.
The text was updated successfully, but these errors were encountered:
Noting that we are not pursuing the paid version of Slack as it is cost prohibitive at this time. Planning to ensure that any discussion that needs to be preserved from a project history perspective moves to the mailing lists.
These are currently tracking to be set up next week, still pending domain transfer.
We currently have three different project communication channels identified:
We need to document how each of these communication channels will be used for the project in the project FAQ.
Here is my proposal for how each communication channel should be used:
Note that just using GitHub discussions is not great because it doesn't allow folks to discuss things with the project who are less familiar with GitHub (and, for example, perhaps working in regulated industries where GitHub is hard - e.g. tons of banks don't let employees access GitHub, but they can use an email list); need to be conscious about using GitHub discussions with care.
The text was updated successfully, but these errors were encountered: