Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
Pierre
To give you an idea: HyperKitty for scm-commits: https://lists.fedoraproject.org/archives/list/scm-commits@lists.fedoraprojec...
I'd say that sounds good, we're probably a team of people that will understand any resulting issues and can file them to the responsible people.
With kind regards, Patrick Uiterwijk Fedora Infra
----- Original Message -----
Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
Pierre
To give you an idea: HyperKitty for scm-commits: https://lists.fedoraproject.org/archives/list/scm-commits@lists.fedoraprojec...
infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
On 8/5/15, Pierre-Yves Chibon pingou@pingoured.fr wrote:
On Wed, Aug 05, 2015 at 05:46:26AM -0400, Christopher Meng wrote:
Any chances for test list?A
At the end, everything will be migrated, but we need to start somewhere :)
Kk, subscribed to infra already. ;)
On Wed, Aug 5, 2015 at 10:45 AM Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
+1
On Wed, Aug 05, 2015 at 10:45:21AM +0200, Pierre-Yves Chibon wrote:
Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
+1 for same reasons already stated by Patrick and others.
On Wed, 5 Aug 2015 10:45:21 +0200 Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
I'm fine with the idea.
The only possible issue would be that we use this list for freeze break requests, but we have a small team that also really talks a lot on IRC, so if the list wasn't working I'm sure people could still get reviews, acks...
so +1 from me.
kevin
On 5 August 2015 at 12:35, Kevin Fenzi kevin@scrye.com wrote:
On Wed, 5 Aug 2015 10:45:21 +0200 Pierre-Yves Chibon pingou@pingoured.fr wrote:
Good morning everyone,
As you may know, mailman3 has been released and with it the new archiver bridging mailing lists and forums: HyperKitty.
Some of the automated mailing list have been already migrated to mailman3, but we still need to migrate 'live' mailing list (ie: having user actually discussing, not just bot sending emails). There has been thoughts to use the infrastructure list as a potential first list to migrate.
Thoughts on this?
I'm fine with the idea.
The only possible issue would be that we use this list for freeze break requests, but we have a small team that also really talks a lot on IRC, so if the list wasn't working I'm sure people could still get reviews, acks...
so +1 from me.
I would say that we have a SOP that if the list is down we use IRC and sysadmin-main@fedoraproject.org to get emergency review and then a published post-facto review on list.
kevin
infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
OK people, thanks for your enthusiasm, I'll migrate infra in the next hours :-) I'll be online this weekend to fix things if they break, and there's an easy way to rollback if it's unfixable.
The only distrubing thing that I've seen is mail delivery being stopped sometimes when an ansible playbook is run on the servers (but not always of course, that would be too easy). But no mail is lost, a simple restart of mailman gets it rolling again.
I'll send an email in this thread when the migration is done.
Aurélien
On Fri, Aug 07, 2015 at 06:16:32PM +0200, Aurelien Bompard wrote:
OK people, thanks for your enthusiasm, I'll migrate infra in the next hours :-) I'll be online this weekend to fix things if they break, and there's an easy way to rollback if it's unfixable.
The only distrubing thing that I've seen is mail delivery being stopped sometimes when an ansible playbook is run on the servers (but not always of course, that would be too easy). But no mail is lost, a simple restart of mailman gets it rolling again.
I'll send an email in this thread when the migration is done.
Might be an idea to send one when you start the migration as well :] Just that we are not surprised or that we watch if one of our email doesn't land on the list.
Pierre
Might be an idea to send one when you start the migration as well :] Just that we are not surprised or that we watch if one of our email doesn't land on the list.
Yeah, that would have been a good idea, but it's too late: your message was processed by Mailman3 already ;-) https://lists.fedoraproject.org/archives/list/infrastructure%40lists.fedorap...
I'm currently checking for bugs & regressions, feel free to ping me :-)
Aurélien
On Fri, Aug 07, 2015 at 07:37:22PM +0200, Aurelien Bompard wrote:
Might be an idea to send one when you start the migration as well :] Just that we are not surprised or that we watch if one of our email doesn't land on the list.
Yeah, that would have been a good idea, but it's too late: your message was processed by Mailman3 already ;-) https://lists.fedoraproject.org/archives/list/infrastructure%40lists.fedorap...
\ó/
On 08/07/2015 12:37 PM, Aurelien Bompard wrote:
Might be an idea to send one when you start the migration as well :] Just that we are not surprised or that we watch if one of our email doesn't land on the list.
Yeah, that would have been a good idea, but it's too late: your message was processed by Mailman3 already ;-) https://lists.fedoraproject.org/archives/list/infrastructure%40lists.fedorap...
I'm currently checking for bugs & regressions, feel free to ping me :-)
Aurélien
Did you use an old subscription list? I have not been subscribed to @infra for about a month and today I start receiving these from you guys.
Performing the unsubscribe process again does not send me a confirmation e-mail.
Did you use an old subscription list? I have not been subscribed to @infra for about a month and today I start receiving these from you guys.
Ah, yes, sorry, I did get an updated subscription list but it only added new entries.
Performing the unsubscribe process again does not send me a confirmation e-mail.
I'll check if it worked
Ooh, can we switch from gravatar to libravatar?
diff --git a/roles/mailman/templates/settings.py.j2 b/roles/mailman/templates/settings.py.j2 index 237bbbc..93d0111 100644 --- a/roles/mailman/templates/settings.py.j2 +++ b/roles/mailman/templates/settings.py.j2 @@ -253,17 +253,17 @@ SOCIAL_AUTH_PIPELINE = ( # https://github.com/twaddington/django-gravatar # # Gravatar base url. -#GRAVATAR_URL = 'http://cdn.libravatar.org/' +GRAVATAR_URL = 'http://cdn.libravatar.org/' # Gravatar base secure https url. -#GRAVATAR_SECURE_URL = 'https://seccdn.libravatar.org/' +GRAVATAR_SECURE_URL = 'https://seccdn.libravatar.org/' # Gravatar size in pixels. #GRAVATAR_DEFAULT_SIZE = '80' # An image url or one of the following: 'mm', 'identicon', 'monsterid', 'wavatar', 'retro'. -#GRAVATAR_DEFAULT_IMAGE = 'mm' +GRAVATAR_DEFAULT_IMAGE = 'retro' # One of the following: 'g', 'pg', 'r', 'x'. #GRAVATAR_DEFAULT_RATING = 'g' # True to use https by default, False for plain http. -#GRAVATAR_DEFAULT_SECURE = True +GRAVATAR_DEFAULT_SECURE = True
# # django-compressor
Will do, thanks :-)
A.
This is so cool!
Can I request migrating the fedora-join mailing list next? It'll make it so much easier for newbies to use it. :D
Thanks, Ankur Sinha "FranciscoD" http://fedoraproject.org/wiki/User:Ankursinha
Hey guys, I'm currently demoingo Hyperkitty with this list !
Say Hi!
A.
On Fri, Aug 07, 2015 at 06:16:32PM +0200, Aurelien Bompard wrote:
OK people, thanks for your enthusiasm, I'll migrate infra in the next hours :-) I'll be online this weekend to fix things if they break, and there's an easy way to rollback if it's unfixable.
Wooh, and now my filters work on List-Post instead of X-Been-There :)
infrastructure@lists.fedoraproject.org
-
Ankur Sinha -
Aurelien Bompard -
Aurelien Bompard -
Christopher Meng -
Kevin Fenzi -
Matthew Miller -
Michael Cronenworth -
Máirín Duffy -
Patrick Uiterwijk -
Paul W. Frields -
Pierre-Yves Chibon -
Ralph Bean -
Ralph Bean -
Stephen John Smoogen -
Xavier Lamien