| 1 |
On 07/18/2010 06:03 PM, Jorge Manuel B. S. Vicetto wrote: |
| 2 |
> On 18-07-2010 20:26, Petteri Räty wrote: |
| 3 |
>> I propose we add a statement to our list FAQ to ban cross posting the |
| 4 |
>> reason being that it leads to fragmentation of the thread when some |
| 5 |
>> people reply on one list and some on the other (and they aren't required |
| 6 |
>> to be subscribed to both). |
| 7 |
|
| 8 |
++ |
| 9 |
|
| 10 |
> |
| 11 |
> I can live with the cross-posting, in particular if it makes easier to |
| 12 |
> find an old thread - if the council meeting threads were sent to both |
| 13 |
> gentoo-council and gentoo-dev, it would certainly be easier to find it |
| 14 |
> on gentoo-council archives than gentoo-dev's. |
| 15 |
|
| 16 |
Why not just post it on gentoo-council? Anybody interested in the |
| 17 |
discussion could participate there. The first message in the thread |
| 18 |
could of course be posted to -dev-announce with follow-ups to the proper |
| 19 |
list. |
| 20 |
|
| 21 |
I've been reading this discussion now in three different lists, |
| 22 |
illustrating the fragmentation problem. |
| 23 |
|
| 24 |
For those who suggest a better mail reader - I'm all ears. My |
| 25 |
requirements apparently are: |
| 26 |
|
| 27 |
1. GUI - one that works with a mouse. |
| 28 |
2. Basic editing functionality (spell check, re-wrapping, etc), with |
| 29 |
all functions accessible via the GUI. |
| 30 |
3. Handles threads split across two different lists with not all |
| 31 |
replies being cross-posted to all lists, turning them into a cohesive |
| 32 |
discussion. |
| 33 |
4. Otherwise, doesn't mix up stuff from multiple lists. |
| 34 |
5. Does all of this in spite of the fact that procmail is set to |
| 35 |
mercilessly destroy anything with a duplicate message ID before the mail |
| 36 |
client even sees it. Alternatively, mail client must handle when I get |
| 37 |
the same email 5 times via 5 different email addresses that were all |
| 38 |
CC'ed so that procmail doesn't have to take care of it. |
| 39 |
|
| 40 |
Of course, not cross-posting like mad lets me cross off #3 and #5, |
| 41 |
meaning that just about anything out there works. |
| 42 |
|
| 43 |
I'm not aware of a mail reader that meets these requirements... Frankly |
| 44 |
I'd be happy to just follow the discussion on gmane except that even |
| 45 |
most news readers can't handle this sort of mess. |
| 46 |
|
| 47 |
If devs want to follow what the council is doing, they should subscribe |
| 48 |
to -council. If devs want to have input on big policy changes that |
| 49 |
aren't strictly coding related they can follow -project. Of course, no |
| 50 |
matter what lists they follow the important stuff can go on |
| 51 |
-dev-announce first. |
| 52 |
|
| 53 |
Just my two cents... Obviously I've been putting up with this sort of |
| 54 |
thing for years, so this is hardly going to be the thing that drives me |
| 55 |
over the edge... :) |
| 56 |
|
| 57 |
Rich |
Archives