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
On Sat, Mar 17, 2012 at 3:05 AM, Andrea Crotti andrea.crotti.0@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.
On Mar 16, 2012, at 06:05 PM, Andrea Crotti wrote:
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.
+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
On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw barry@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. :-)
participants (3)
-
Andrea Crotti -
Barry Warsaw -
Stephen J. Turnbull