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

Email addresses #6

Open
BenjamenMeyer opened this issue May 11, 2020 · 16 comments
Open

Email addresses #6

BenjamenMeyer opened this issue May 11, 2020 · 16 comments
Milestone

Comments

@BenjamenMeyer
Copy link
Member

BenjamenMeyer commented May 11, 2020

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:

  • Vega Strike Core Engine
  • Under the Coldest Sea Game Play

Other:

  • Contributions
  • Security Reports
@nabaco
Copy link
Member

nabaco commented May 11, 2020

We should also have some email addresses for contributions. Like people wishing to send a patch (like bmorel) or a security concern.

@BenjamenMeyer
Copy link
Member Author

BenjamenMeyer commented May 11, 2020

Propsed by @www2000 in Gitter:

@BenjamenMeyer
Copy link
Member Author

Note: Per #6 (comment) that should be for VS Engine itself; we should have separate ones for the games.

@BenjamenMeyer
Copy link
Member Author

Note: We already have the emails in the comment above; they were previously established.

@www2000
Copy link

www2000 commented May 13, 2020

is oke that i close this ticket?

@BenjamenMeyer
Copy link
Member Author

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

@BenjamenMeyer
Copy link
Member Author

Possible Mailing List Host: https://www.freelists.org/

  • Disadvantage: It's not under our domain
  • Advantage: they provide the infrastructure and probably have a larger set of servers to support it

@nabaco
Copy link
Member

nabaco commented May 14, 2020

I prefer something on our domain. It will make it easier for everyone.
FreeLists uses Ecartis, which looks unmaintained. But if we still want to use it, maybe we should just use Ecartis on our server.

@BenjamenMeyer
Copy link
Member Author

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.

@BenjamenMeyer
Copy link
Member Author

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.

@BenjamenMeyer
Copy link
Member Author

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.

@BenjamenMeyer
Copy link
Member Author

added [email protected] for VS:UtCS.

@BenjamenMeyer
Copy link
Member Author

Not mailing lists yet; but we have something sufficient for 0.6.x. Retargetting future work to 0.7.x

@BenjamenMeyer
Copy link
Member Author

@BenjamenMeyer BenjamenMeyer modified the milestones: 0.6.x, 0.9.x Jan 13, 2021
@BenjamenMeyer
Copy link
Member Author

Only task now is pushing these into the various parts of documentation to make them known.

BenjamenMeyer added a commit to BenjamenMeyer/Vega-Strike-Engine-Source that referenced this issue Feb 11, 2021
@BenjamenMeyer
Copy link
Member Author

Pushing this out for review when we hit 0.9.x; though I think everything is mostly taken care of right now.

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

3 participants