On 03/09/2015 10:40 AM, Laszlo Ersek wrote:
> On 03/06/15 23:29, Peterson, Joe wrote:
>> Hello all,
>>
>> The current host for our EDK2 mailing list has had a few technical
>> issues lately- primarily that some mails have been significantly
>> delayed or not delivered at all. We are investigating other options
>> for this hosting. I know there has been some discussion about
>> splitting the mailing list as well, but I would like to split off a
>> discussion about what we need from the mailing list host separate
>> from the discussion on how we use it.
>
>> 1) Do you think we should move the archives? It will take a
>> little effort to do so. Is it going to be worth it? We can point
>> people to the older (current) archive.
>
> The sourceforge mail archive is practically unusable.
>
> The best mailing list archive solution I've ever seen is GMANE. (Much
> better than mailman, for example.)
>
> GMANE's records of edk2-devel may not be complete at this point (as
> others have pointed out). I'd prefer if the full timeline were imported
> into GMANE, and GMANE were promoted to official archive status.
Agreed.
>> 2) I would like to recommend we use a plain text only list.
>> There are a lot of reasons including: plain text is handled by all
>> mail clients and spam filters are less likely to reject plain text
>> messages. Are there objections to plain text? Support?
>
> I strongly support plaintext-only.
Agreed.
> I also support David's recommendations: dropping the [edk2] subject
> prefix, and (especially!) the obnoxious Reply-To header, exactly for the
> reasons David named.
Personally, I like the Reply-To header. With it, using Thunderbird,
replies go to the list automatically. Without it, I need to "reply all"
then edit the "To:" header if I want to reply only to the list. If I
just "reply", it only goes to the original sender. I find I reply to
the list far more often than to an individual, so the Reply-To is handy
for me.
>> 3) We can automatically subscribe current subscribers to the new
>> list. I would think this is desirable, but there is some merit to
>> starting with a fresh list. Thoughts? (Even if we split the list,
>> there is likely to be a "general" list that would make sense for
>> almost everyone to subscribe to.)
>
> I'd prefer if the "system" auto-subscribed me to the new list, yes.
Ditto.
>> 4) When we switch, should we do so after we settle on if we are
>> going to split the list or do it now to get past the technical issue,
>> and then deal with the process change?
>
> I disagree that edk2-devel should be splintered into several "topical"
> lists in the first place.
>
> edk2-devel is one of the quietest mailing lists I've encountered. For me
> personally it's quite easy to ignore threads I'm not interested in. On
> the other hand I very much appreciate when people "unexpectedly" chime
> in in a patch review thread (or some other discussion).
Ditto.
--
Brian
--------------------------------------------------------------------
... He say, "One and one and one is one. The one thing I can tell
you is debug till it runs" ...
If the Beatles had studied computer science
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
