Faidon said:
Do we really need this mailing list after all? We still have RT and
we're keeping it IIRC, so the list is just spamming us all...
- Forwarded message from maint-announce-bounces@lists.wikimedia.org -----
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dzahn | T146746 investigate shared inbox options | |||
| Resolved | Dzahn | T143760 deactivate maint-announce |
Event Timeline
Comment Actions
root@fermium:/var/lib/mailman/bin# ./remove_members -a maint-announce
root@fermium:/usr/local/sbin# ./disable_list maint-announce
maint-announce disabled. Archives should be available at current location, all mail should be moderated and the list should not be on the listinfo page.
@faidon mailing list deactivated, members unsubscribed
Comment Actions
removed the part of the exim alias that forwards it to lists, in private repo commit f4465ebd308e9538b3ab940
it used to forward to both RT and mailman, now just RT again
Comment Actions
I am reopening this.
Why are we using RT for maint-announce? The plan overall was to kill all mail relays into RT, and rely on the mailing list.
The mailing list is what I used for my triaging of clinic duty two weeks ago.
I'd propose we kill the RT link, and reopen this list. The list archive thread page was more than enough for each clinic duty person to update the tracking calendar. Doing so via that means we can downgrade RT to a wholly historic service, with no mail links.
Comment Actions
@faidon @RobH I don't have much of a personal preference here, Activating and deactivating the list are both easy and not much work. I also once thought it would be possible to kill RT by doing this but at the time i thought this was the last thing left on RT and then it turned out we are also keeping it anyways for procurement and Mark asked me to keep it, so i upgraded it to jessie and moved it to a VM.
I could re-create it but only the people subscribe who want to opt-in? dunno...
Comment Actions
- Using mailman:
- pros:
- we already maintain mailman, any outage is noticed
- archive view sorted by date allows on clinic to easily add items to calendar as they were received
- cons:
- typically have to approve/whitelist most new vendors first few emails to list
- have to check calendar against list to determine if an item has been processed
- pros:
- using rt
- pros:
- can maintain old system/process
- can update each ticket to note when its been added to gcal
- cons:
- have to maintain rt mail links
- closed user base, outages may go unnoticed (including mail relay breaks)
- pros:
Since RT is historical data only, except for maint-announce, this would allow it to be fully historical data only (throughout.)
I think we should use mailman's maint-announce list archive for ops clinic duty adding items to gcal and tracking maint-announcements. I'd be interested to hear feedback from others who have processed clinic duty in both mailman and rt.
Comment Actions
As discussed during ops offsite, we'll keep using RT for now and also investigate the possibilty of a shared inbox, but won't go back to the mailing list.