#331 setup email alias for hyperscale SIG members
Closed: Fixed 2 years ago by arrfab. Opened 2 years ago by dcavalca.

I'd like to have an email alias (or a private mailing list if that's easier) for Hyperscale SIG members that we can use when registering accounts on behalf of the SIG. For example, I recently setup a quay.io organization for centoshyperscale, and ended up using one of my personal emails for it, which isn't ideal (both for accountability reasons, and because quay enforces that one email can have only one account). Something like hyperscale-sig@centosproject.org would do for example. Thanks!


That sounds like a good and simple RFE to implement : I had that idea in mind when when added the automatic @centosproject.org alias for every member of a CentOS SIG.
We can easily extend that with a email alias for the group, following the <sig_name>@centosproject.org and so including all members.
Would that suit your needs ? (and so would be applied automatically for all other SIGs)
@rcb ^ opinion ?

Yes, that would be perfect, thanks!

let me also see with @abompard as I think that he said there was a new api endpoint in fasjson to also query in one api call all members and details, instead of parsing list and calling fasjson on every items in the list.

Metadata Update from @arrfab:
- Issue assigned to arrfab
- Issue tagged with: centos-common-infra, feature-request, low-trouble, medium-gain

2 years ago

Yes, having a sig_name@centosproject.org alias would be very helpful for me, as I have to look up SIG membership (in case it's changed) every time I want to contact a SIG, and copy each name over. So definitely +1 from me.

This is already done in Fedora for things like <package>-maintainer@fedoraproject.org, so I imagine a similar process would work for this need to provide <sig>-sig@centosproject.org.

I worked on the simple script that queries fasjson API to extract SIG members to now also construct alias for <sig_name>@centosproject.org and so send mails to all members of the group.
It was pushed in STG through git/ansible and as it was working it's now implement also on real prod env.

in this case, it's so sig-hyperscale@centosproject.org and a test mail was sent.
I'll close this request after feedback, but from maillog I see that mail was correctly distributed

Metadata Update from @arrfab:
- Issue priority set to: Waiting on External (was: Needs Review)

2 years ago

received the sig-hyperscale email fine here.

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1