Hi Dennis, On Tuesday, 2011-08-23 12:25:59 -0700, Dennis E. Hamilton wrote:
> Complete loss of subject heading is a minor annoyance? It happens only if there's something that looks like an email address in the subject, how often does that happen except when discussing about *@ooo mailing lists? > How about the mangling of the To address? When I get one of these, > I cannot use any rules because the To address that my mail client sees > is not that of ooo-dev but some hacked-up pseudo gmane address. There's always the List-Post header containing the list's mailto address, generated by the mailing list software. That's reliable. > I think folks having an NNTP and newsgroup-ish way of reading ooo-dev > is a great thing. It duplicates the archiving, though. I wouldn't consider that as a disadvantage. There are several archives of each mailing list spread across the net anyway. So chances are better that anyone searching for something will find the correct answer. > But more than > that, I would rather it be done well and not in a way that disrupts > the original mailing list. Especially not that. If it worked well, > I would be tempted to use it. It does work well, just not with the special case of a mangled subject if ... see above. > I have a different question. > > According to the information on GMANE, it takes someone who claims to > be an administrator to offer up a mailing list for aggregation there. I haven't seen that. http://gmane.org/faq.php says | If you have any doubts about whether the mailing list wants to be | carried by Gmane, ask the people on the mailing list first. Or at least | the mailing list administrator. Apparently the person who added this list didn't have any doubts.. > Who did that and where was it discussed here? I suspect I may have > seen an off-hand mention but I had no idea what the consequences were > at that point. I don't remember having seen something like that. If there was, I would had said yes, go ahead. > Finally, wholesale harvesting of someone's e-mail list raises serious > netiquette issues far beyond concerns for top posting, CC additions, > etc. I don't see where netiquette should be involved here. This is a public mailing list, not any private mail forwarded or archived. Thousands of public mailing lists, including Apache's, end up in one or more archives. > When did we consider what we expect of that and also what does > it not being on Apache infrastructure raise as a concern? Why should it raise any concern? Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
signature.asc
Description: Digital signature
