Re: [Mailman-Developers] bugs on launchpad
My idea as a user would be to be able to select from my web configuration page an option: send_public_url_in_mail_footers: [ disabled, gmane_url, mailmanweb_url ] And maybe it would be cool (if possible I have no idea) to add a mail command that when I send subject: public $mailing_list $id I get back an email with this url. Because maybe from one mailing list I'm normally not interested in the url and I also want it in some cases. Not sure I anyone else in the world would like this feature though :D ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On 3/22/2012 5:48 PM, Stephen J. Turnbull wrote: On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw ba...@list.org wrote: If we add something like $archive_url to the decoration interpolation dictionary, what happens when we have multiple archivers that support permalink() enabled? Do we chose one at random (these are unordered)? -1 I agree so -2. I thinking is if you list administrator/owner has not defined an order, make it simple and impose a known order in that case - alphabetize/sort the order and pick the first one. Do we add a configuration variable to select a primary archiver for this? +1 +2 This would allow the list administrator/owner to define and pick the primary archiver. For any other archivers, people can go to the Archived-At header(s). If there's *no* archiver configuration variable, we don't know where to point to anyway for Gmane-like archivers (yes, I know, catering to Gmane will give Brad hives, but some people like Gmane). The local archive, if it exists, may seem TOOWTDI, but it might not be the preferred one even if it's the only one configured in Mailman (although that seems a lot less likely than the case where somebody just grandfathers an existing Gmane subscription as the archive URL of choice). Do we allow something like $archive_url.prototype as an interpolation variable to select e.g. the 'prototype' archiver? -1 Too complex. If people want alternative archives, they can go to the list FAQ or the Archived-At headers. If we go this way, we'd better have a *really* good comment and a pre-existing entry in the FAQ to save Mark some time. :-) I agree with Stephen. Too complex and can be confusing without it being well documented with a number of examples. ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On Mar 16, 2012, at 06:05 PM, Andrea Crotti wrote: https://bugs.launchpad.net/mailman/+bug/956889 This one got duped to 266684. We have (almost) all the basics to make this work in message headers/footers, but it's not plumbed through yet. One complication is this: If we add something like $archive_url to the decoration interpolation dictionary, what happens when we have multiple archivers that support permalink() enabled? Do we chose one at random (these are unordered)? Do we add a configuration variable to select a primary archiver for this? Do we allow something like $archive_url.prototype as an interpolation variable to select e.g. the 'prototype' archiver? This isn't much of a problem for the RFC 822 headers, because we can just add multiple Archived-At headers. https://bugs.launchpad.net/mailman/+bug/956384 +1. I followed up on the tracker issue. Don't forget to tag Mailman 3 issues with the 'mailman3' tag! PS. ironically today they asked me for the first time in my life to check why Mailman was not working on a Linux server. The problem was that /var was full, but well knowing more about Mailman certainly helped :D Yay! -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On Mar 18, 2012, at 04:36 PM, Stephen J. Turnbull wrote: On Sat, Mar 17, 2012 at 3:05 AM, Andrea Crotti andrea.crott...@gmail.com wrote: Hi everyone, I filed in two bugs today: https://bugs.launchpad.net/mailman/+bug/956889 https://bugs.launchpad.net/mailman/+bug/956384 These are both policy issues, I think they should be posted to the list as well as filed on Launchpad, or instead of in the case of continuous integration. Once it's decided what to do about them, a specific issue should filed to track progress. IMO YMMV etc -- I don't pretend to channel Barry on this. But you didn't do so badly! :) -Barry ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw ba...@list.org wrote: If we add something like $archive_url to the decoration interpolation dictionary, what happens when we have multiple archivers that support permalink() enabled? Do we chose one at random (these are unordered)? -1 Do we add a configuration variable to select a primary archiver for this? +1 If there's *no* archiver configuration variable, we don't know where to point to anyway for Gmane-like archivers (yes, I know, catering to Gmane will give Brad hives, but some people like Gmane). The local archive, if it exists, may seem TOOWTDI, but it might not be the preferred one even if it's the only one configured in Mailman (although that seems a lot less likely than the case where somebody just grandfathers an existing Gmane subscription as the archive URL of choice). Do we allow something like $archive_url.prototype as an interpolation variable to select e.g. the 'prototype' archiver? -1 Too complex. If people want alternative archives, they can go to the list FAQ or the Archived-At headers. If we go this way, we'd better have a *really* good comment and a pre-existing entry in the FAQ to save Mark some time. :-) ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Developers] bugs on launchpad
On Sat, Mar 17, 2012 at 3:05 AM, Andrea Crotti andrea.crott...@gmail.com wrote: Hi everyone, I filed in two bugs today: https://bugs.launchpad.net/mailman/+bug/956889 https://bugs.launchpad.net/mailman/+bug/956384 These are both policy issues, I think they should be posted to the list as well as filed on Launchpad, or instead of in the case of continuous integration. Once it's decided what to do about them, a specific issue should filed to track progress. IMO YMMV etc -- I don't pretend to channel Barry on this. ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Developers] bugs on launchpad
Hi everyone, I filed in two bugs today: https://bugs.launchpad.net/mailman/+bug/956889 https://bugs.launchpad.net/mailman/+bug/956384 because I thought we could have a discussion there about these topics. But now I was wondering if it is a good idea, is it maybe better to write on the mailing list for these kind of things?? PS. ironically today they asked me for the first time in my life to check why Mailman was not working on a Linux server. The problem was that /var was full, but well knowing more about Mailman certainly helped :D ___ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
