-
Notifications
You must be signed in to change notification settings - Fork 0
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
Email addresses #6
Comments
We should also have some email addresses for contributions. Like people wishing to send a patch (like bmorel) or a security concern. |
Propsed by @www2000 in Gitter: |
Note: Per #6 (comment) that should be for VS Engine itself; we should have separate ones for the games. |
Note: We already have the emails in the comment above; they were previously established. |
is oke that i close this ticket? |
@www2000 not yet; we need to figure out a proper mailing list solution first. Not sure if we'll host that or use a service targetting open source projects or not. We'll need this at least for the man page stuff, bug reports, security reports, etc. |
Possible Mailing List Host: https://www.freelists.org/
|
I prefer something on our domain. It will make it easier for everyone. |
If we install something, I'd prefer majordomo or mailman; both are actively maintained and high quality listservs and should integrate with postfix/exim easily. |
NOTE: we need to solve the mailing list side of this to help close out vegastrike/Vega-Strike-Engine-Source#96 as we need a mailing list for bug reports. |
I've updated https://github.com/vegastrike/infrastructure and taken it about as far as I can using Vagrant/Ansible locally. I need a few folks to check it out and verify reproducibility; then we can spin up a server in our Digital Ocean account and start deploying. From here on out, let's do PRs against that repository. |
added [email protected] for VS:UtCS. |
Not mailing lists yet; but we have something sufficient for 0.6.x. Retargetting future work to 0.7.x |
we now have: |
Only task now is pushing these into the various parts of documentation to make them known. |
This contributes to the following stories: vegastrike/infrastructure-tracking#1 vegastrike#96 vegastrike/infrastructure-tracking#6
This contributes to the following stories: vegastrike/infrastructure-tracking#1 vegastrike#96 vegastrike/infrastructure-tracking#6
Pushing this out for review when we hit 0.9.x; though I think everything is mostly taken care of right now. |
We need to setup some email addresses as mailing lists to the members of the Infrastructure team for managing our social media presence.
We should have 1 email list for each social media account listed in #1.
Social Email Addresses:
Other:
The text was updated successfully, but these errors were encountered: