Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Communication Channel usage guidelines must be documented #144

Closed
lhawthorn opened this issue Apr 15, 2024 · 3 comments
Closed

Project Communication Channel usage guidelines must be documented #144

lhawthorn opened this issue Apr 15, 2024 · 3 comments
Assignees

Comments

@lhawthorn
Copy link
Member

lhawthorn commented Apr 15, 2024

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:

  • 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.

@lhawthorn lhawthorn self-assigned this Apr 15, 2024
@lhawthorn
Copy link
Member Author

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.

@lhawthorn
Copy link
Member Author

We also now have this stub page to collect all of these details.

https://github.com/instructlab/community/blob/main/Collaboration.md

@lhawthorn
Copy link
Member Author

All of this is now documented on the collaboration page. Closing this issue with great delight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants