Opened 6 years ago

Closed 5 years ago

#3136 closed enhancement (fixed)

switch to new mailing lists

Reported by: dustin Owned by: dustin
Priority: major Milestone: sys - other
Version: Keywords:
Cc: sean@…

Description (last modified by sa2ajj)

We're already hosting a number of mailing lists on lists.buildbot.net, but only using sysadmin@… and botherders@….

Back in July we were scheming to switch everyone over to the new list. This involved

  • announce@…
  • users@…
  • devel@…

The plan is to take the list of subscribers currently on buildbot-devel@… and move that group to users@… (since it's primarily a Q&A list).

We're also going to import archives. Amar has a way to get the archives from SF and import them.

The timing is a little tricky to work out, though. We need to give folks enough warning to know when they should start to send to the new address, and we need to move the subscribers over and deactivate the old list reasonably quickly. I don't know if the archives need to be imported at exactly that time, or if we can backfill.

Draft email:

---

As part of Amar's great work in setting up Buildbot's dedicated infrastructure, it's time to transition away from SourceForge mailing lists and over to our own hosted lists.

So, as of <<WHEN?>> this list's address will become users@…, and at that time buildbot-devel@… will no longer work. You will receive a subscription email from the new list, and should update your address book appropriately.

We have a bunch of other lists, too, as seen on http://lists.buildbot.net. Buildbot-devel has gotten a bit over-used, both for discussion among users and for development traffic. For folks involved in contributing to or developing Buildbot, I'd point especially to devel@….

Folks not interested in the day-to-day, but interested in announcements about new releases, please subscribe to announce@….

We'll be importing the archives for buildbot-devel to the new users@ list, so they will remain searchable both on http://lists.buildbot.net and on the external mirrors (gmane, etc.).

Change History (19)

comment:1 Changed 6 years ago by sa2ajj

  • Description modified (diff)

comment:2 Changed 6 years ago by verm

I need to request a new pickle from sourceforge so we can cutover the subscriber list.

We also need to take the mbox and sanitise them of the sourceforge advertisements. There are scripts out there to do this.

If we can schedule when this should happen I can handle it. Basically as soon as I get a copy of the pickle (which can take weeks if the last time is any indication) I can do the cutover. I already setup the list months ago.

comment:3 Changed 6 years ago by verm

Announce list is enabled.

In order to post you must be subscribed and add:

Approved: <moderator pass> as the first line in the body of a text message. If it's not text it must be in the header.

The password is in the shared secret list.

comment:4 Changed 6 years ago by verm

sa2ajj noted in #2846:

We could also consider using a newer interface for mailman. Example is available at ​https://lists.stg.fedoraproject.org/archives/

comment:5 Changed 6 years ago by dustin

You pick the day, and as long as it's far enough out to send the email above, I'll be happy with it.

comment:6 Changed 6 years ago by verm

I'll request the pickle from sourceforge and let you know as soon as I have it.

comment:7 Changed 5 years ago by skelly

  • Cc sean@… added

comment:8 Changed 5 years ago by dustin

  • Cc sean@… removed

Per today's meeting (https://supybot.buildbot.net/meetings/buildbot/2015/buildbot.2015-07-21-16.00.html) we're going to split off the archive-migration bit from the switch for users. We can migrate the archives later.

Skelly's going to look into the details:

  • how to migrate the subscriber list
  • how best to configure the SF lists to preserve the archives and correctly send users to the new list
  • how to announce this to everyone on the lists

comment:9 Changed 5 years ago by dustin

  • Cc sean@… added

comment:10 Changed 5 years ago by skelly

Retroactively importing an archive appears to be possible. From https://mail.python.org/pipermail/mailman-users/2009-October/067264.html:

The safest thing is to prepend the majordomo mbox to LISTNAME.mbox/LISTNAME.mbox. Then in the future, you could rebuild the entire archive with

bin/arch --wipe LISTNAME

The alternative is to not combine the two files and to remember that rebuilding the archive is a two step process

bin/arch --wipe LISTNAME /path/to/majordomo_archive_mbox
bin/arch LISTNAME

to initialize the archive from majordomo_archive_mbox and then add the posts from the default LISTNAME.mbox/LISTNAME.mbox.

I recommend the former so you don't need to remember the two step process.

comment:11 follow-up: Changed 5 years ago by dustin

Amar mentioned that the tarball from SF is also the only way to get the list of members in a usable format. So that may hold things up. Amar says he has requested a new tarball from SF.

comment:12 in reply to: ↑ 11 Changed 5 years ago by verm

Replying to dustin:

Amar mentioned that the tarball from SF is also the only way to get the list of members in a usable format. So that may hold things up. Amar says he has requested a new tarball from SF.

I requested this yesterday. We'll see how long it takes as soon as I have it I'll grab the list archives via rsync, send out a notice to the lists and switch.

I'll send 3 blaring notices in a row so noone will be surprised. As soon as I cut over I'll kill the SF lists.

comment:13 Changed 5 years ago by verm

Still no word from Sourceforge, I will try pinging them on IRC. I opened the ticket on 2015-07-21.

comment:14 Changed 5 years ago by dustin

Per IRC conversation, we're going to make the switch without archives or a subscriber list, opting instead to just announce the new lists on the old, probably several times. After that, we'll want to keep the old list around (until we get an archive tarball), but prevent people from posting to it.

comment:15 Changed 5 years ago by verm

I added devel@ and commits@. I also grabbed a copy of the mbox files from 2015-01-11 2:54PM EST.

The lists need to be tested, after this we should send out an email on the Sourceforge list and then disable them. I would give it 30 mins before disabling just in case there is a delay in sending out to list members. Who knows how they have it setup.

comment:16 Changed 5 years ago by verm

Had to do a slew of upgrades to Apache as it was never updated to SSL.

The lists are now under 100% SSL and verified as working:

  • devel@…
  • users@…
  • commits@…

Someone should send out a notice to the old lists saying they should migrate, wait an hour or so then shut down the old lists.

comment:17 Changed 5 years ago by dustin

  • Owner changed from verm to dustin
  • Status changed from new to assigned

comment:18 Changed 5 years ago by dustin

These are now migrated and in use.

I accidentally deleted the old list :(

I attempted to subscribe gmane to the new lists, but haven't verified that that happened yet.

comment:19 Changed 5 years ago by dustin

  • Resolution set to fixed
  • Status changed from assigned to closed

I re-created the old list and set up the autoresponder.

I also got in touch with Lars and the archives are working again, e.g., http://blog.gmane.org/gmane.comp.python.buildbot.devel

Note: See TracTickets for help on using tickets.