Email addresses needed

[jjasghar]

When we get "instructlab.io" email via @jeremyeder

EDIT: updated email addresses to remove prefix -@joesepi

Mailing list	Purpose
announce@instructlab.io	Where we announce releases or other important updates.
dev@instructlab.io	Developer discussions.
maintainers@instructlab.io	Do we need a list for maintainers?  Used for pypi?
users@instructlab.io	User discussions, e.g. “my first PR”.
security@instructlab.io	Security issues and announcements
pypi@instructlab.io	Publishing to pypi (if we decide to break it out per package process)
coc@instructlab.io	Code of conduct reporting or communication.

[joesepi]

Need to determine domain name specifically before we can create email addresses.

[joesepi]

We also need an email address for Code of Conduct reporting that should forward to the Code of Conduct Committee members. (EDIT: I guess this is captured in the coc@domain.com address above)

[jjasghar]

We also need an email address for Code of Conduct reporting that should forward to the Code of Conduct Committee members.

cough coc@instructlab.io cough

[joesepi]

There is this table in a doc that we may want to mirror:

Mailing list	Purpose
instruct-lab-announce	Where we announce releases or other important updates.
instruct-lab-dev	Developer discussions.
instruct-lab-maintainers	Do we need a list for maintainers?  Used for pypi?
instruct-lab-users	User discussions, e.g. “my first PR”.

[jjasghar]

we need a instruct-lab-security list.

[cybette]

Propose to remove the instruct-lab prefix as we have the instructlab.io domain, i.e.

announce@instructlab.io
dev@instructlab.io

etc.

Please :+1: (remove prefix) or :-1: (keep prefix) this comment to indicate your preferences.

[cybette]

we're checking if it's possible to add external domains to our google workspace. If not, we'll use mailman 3.

[cybette]

Since each email list serves a different purpose (announce only, discussions, points of contact for specific topics like coc/security), I've created this access table. Please feel free to edit/comment.

Mailing list	who can join group	who can view posts	who can post to group	who can post as group
announce	anyone	anyone	admins	admins
dev	anyone	anyone	members	noone
maintainers	invite only	members	members	admins
users	anyone	anyone	members	noone
security	invite only	members	anyone	admins
pypi	invite only	members	members	admins
coc	invite only	members	anyone	admins
website	invite only	members	anyone	admins

We'll define the admins (may be different for each list) when they have been created.

[joesepi]

The website team asked about an email specific to the website. I think this may be partly on the admin side (like Google Analytics) but could be good to add something like website@domain.com or something too. @cybette

[lhawthorn]

We continue to wait on transfer of domain instructlab.io to Red Hat to get ourselves set up with email addresses.

[lhawthorn]

We will also need coc-reporting that goes to just the Code of Conduct Committee members.

[lhawthorn]

Make sure to add email addresses to the project FAQ - marked with TODO in doc and with link to this issue https://github.com/instructlab/community/blob/main/FAQ.md

[joesepi]

@luke-inglis brought up a good question in today's triage call asking if there was a place people could give feedback on any aspect of the project. @jjasghar suggested the users@instructlab.io email address as a place for such feedback and comments.

[cybette]

@jjasghar suggested the users@instructlab.io email address as a place for such feedback and comments.

+1 for using users for feedback

also we need to change .io to .ai :)

[lhawthorn]

We are creating the project mailing lists right now via Google Workspace. Here is the list of mailing lists as I understand them today and their purposes. List addresses will be ListPrefix@instructlab.ai

Mailing list	who can join group	who can view posts	who can post to group	who can post as group	purpose
announce	anyone	anyone	admins	admins	Where we announce releases and other project wide updates
community	anyone	anyone	anyone	admins	community discussions, such as sharing a tutorial link or getting help with a meetup talk
dev	anyone	anyone	members	noone	developer discussions, both front and backend
maintainers	invite only	members	members	admins	maintainer only discussions, private & used extremely sparingly
users	anyone	anyone	members	noone	user feedback on project or help getting started, e.g. "my first PR"
security	invite only	members	anyone	admins	reporting alias for vulnerabilities
pypi	invite only	members	members	admins	publishing to PyPI
coc	invite only	members	anyone	admins	code of conduct reporting and communication
website	invite only	members	anyone	admins	website administration and maintenance e.g. analytics

[lhawthorn]

@mscherer is going to create these mailing lists for us, please stay tuned ...

[mscherer]

I created the groups, and I have added the 3 current users as managers (I have not found (yet) how to do it with a group of owner, ironically). I am double checking the permissions, , especially around coc and security.

[mscherer]

I think that's done for the list. Now, someone need to fix the docs around. I will update the old alias to forward to the new one later today (incase we forget some doc somewhere).

[lhawthorn]

I will work on updating the docs, thank you @mscherer

[lhawthorn]

These email addresses have been created and documented at https://github.com/instructlab/community/blob/main/Collaboration.md

Going now to update the reporting email addresses for e.g. security-reporting