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

Putting a list of outreach channels and document it #17

Open
realslimshanky opened this issue Mar 5, 2021 · 6 comments
Open

Putting a list of outreach channels and document it #17

realslimshanky opened this issue Mar 5, 2021 · 6 comments
Assignees

Comments

@realslimshanky
Copy link
Member

The goal is to put all the mailing lists and other channels where news and announcements about the conference can be posted. CC @raukadah

@realslimshanky
Copy link
Member Author

@raukadah Let's start this async and meet on a call whenever possible.
I've created a google sheet to list down all the mailing lists and also new columns can be used to manage post sent to the lists.

@realslimshanky
Copy link
Member Author

@raukadah I've updated the sheet with instructions about how to use it,

Guidelines to use:
--
1. Whenever there's a new email to send please add a new column and write the email URL/subject in row 1
2. Write your name in the row of the mailing list if you're taking responsibility for sending out the email to that mailing list
3. Once sent, replace your name with 'SENT'

@satyaakam
Copy link
Member

I see mails being sent to different mailing list as cross post , can we just put all the mailing addresses in BCC ?

@sayanchowdhury
Copy link
Member

I agree with @satyaakam. Rather than sending a separate email please cc, or bcc the mailing addresses. Though I would suggest to send a separate email to inpycon mailing list.

gist:

  • main email to inpycon
  • second email with all emails in cc and with [X-POST] in subject to the mailing list
  • chair can send the email to PSF related mailing lists if needed.

@anistark
Copy link
Member

Can we document these somewhere and close this issue?

@realslimshanky @abhishekmishragithub

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

5 participants