Email addresses - Githubissues

vegastrike / infrastructure-tracking

Repo for tracking issues, etc for any of our infrastructure

1 stars 0 forks source link

Email addresses #6

Open BenjamenMeyer opened 4 years ago

BenjamenMeyer commented 4 years ago

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 commented 4 years ago

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

BenjamenMeyer commented 4 years ago

Propsed by @www2000 in Gitter:

:laughing: : social@vega-strike.org
:rocket: social_engine@vega-strike.org

BenjamenMeyer commented 4 years ago

Note: Per https://github.com/vegastrike/infrastructure-tracking/issues/6#issuecomment-626933756 that should be for VS Engine itself; we should have separate ones for the games.

BenjamenMeyer commented 4 years ago

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

www2000 commented 4 years ago

is oke that i close this ticket?

BenjamenMeyer commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

NOTE: we need to solve the mailing list side of this to help close out https://github.com/vegastrike/Vega-Strike-Engine-Source/issues/96 as we need a mailing list for bug reports.

BenjamenMeyer commented 3 years ago

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 commented 3 years ago

added vsutcs@vega-strike.org for VS:UtCS.

BenjamenMeyer commented 3 years ago

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

BenjamenMeyer commented 3 years ago

we now have:

users@lists.vega-strike.org
devel@lists.vega-strike.org
security@lists.vega-strike.org

BenjamenMeyer commented 3 years ago

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

BenjamenMeyer commented 3 years ago

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