Public-facing e-mail for packaging/crates.io provenance

[connorkuehl]

One of Harald's comments on a PR has me wondering if we could get a mailing list for packaging-type purposes.

Then our crates could have something like this in their manifests:

authors = ["Enarx Developers <enarx-devel@enarx.dev>"]

This isn't pressing, but perhaps something to think about when we get closer to publishing crates.

[MikeCamel]

We've generally resisted email lists for Enarx. What sorts of use cases do you have in mind?

[npmccallum]

Just some thoughts, in no particular order:

1. I like consistent naming. In fact, we can test for this (@mbestavros).

2. We don't currently have a contributors section in the README.md. So this is currently the only place where individual contributors are named. We should fix this.

3. This becomes a high target for spam. I don't like that. Almost all the spam that reaches my inbox comes through mailing lists.

[axelsimon]

2\. We don't currently have a contributors section in the `README.md`. So this is currently the only place where individual contributors are named. We should fix this.

The README currently lists this page as the list of contributors to the project, which is currently mostly correct, but could be less and less as people contribute skills that aren't reflected in code on via pull requests.

Regarding the email address itself, i suggest we add it when we transfer enarx.io ot the Linux Foundation (issue enarx/enarx#291).

[axelsimon]

We are now running on/with LF IT, adding an email alias is very easy and quick.

I didn't request this email alias to be created during transfer, but if / when you want to do this, just let me know. All we need is alias (we have that, enarx-devel@) and addresses to redirect to.

[npmccallum]

@axelsimon Do I dare suggest that emails to enarx-devel@ automatically open github issues?

[axelsimon]

I'm not sure we should do that: we may get emails that contain either private material that shouldn't be made public without prior discussion, or just stuff that isn't useful enough to warrant an issue (i'd expect to get some invitations to events for instance, after a while).

Another question: should we make this address @enarx.io or at @enarx.dev?

[connorkuehl]

Another question: should we make this address @enarx.io or at @enarx.dev?

Just for posterity: this question came up in the standup meeting and the answer was that it should use @enarx.dev as we are transitioning away from @enarx.io

[axelsimon]

Request has been made to have enarx-devel@ on the enarx.dev domain, and make that a mailing list.

[axelsimon]

Trying to sort this out with the Linux Foundation, i have a called planned next Tuesday (2020-09-08), i'll report then!

[axelsimon]

Current status: waiting on the LF, who are looking for a solution long term, to have a proper mailing list behind that email address. In the meantime, we'll just use that address as an alias.

[axelsimon]

Current status: the reason we didn't already set up an alias was that there were some delivery issues between Mailgun, the LF's email provider, and Red Hat. Investigating this with RH IT support currently.

[axelsimon]

We finally have a groups.io subscription live at https://lists.enarx.dev, courtesy of the Confidential Computing Consortium. From there, we should be able to create said alias and have it redirect to the right people. Trying to figure the thing's admin, but we are almost there!

[axelsimon]

I realise i hadn't updated this issue: as mentioned, we currently have a groups.io subscription for lists.enarx.dev, which means we (/i) can create enarx-devel@lists.enarx.dev. This isn't quite the @enarx.dev initially requested, but it might suffice. @connorkuehl what do you think?

[connorkuehl]

@axelsimon I think it's great! lists.enarx.dev is more self-describing as a mailing list too, so it's kind of a silver lining.