[python-committers] Timeline to vote for a governance PEP
Donald Stufft
donald at stufft.io
Sat Nov 3 13:26:16 EDT 2018
> On Nov 3, 2018, at 1:24 PM, Donald Stufft <donald at stufft.io> wrote:
>
>
>
>> On Nov 3, 2018, at 11:22 AM, Antoine Pitrou <antoine at python.org> wrote:
>>
>>
>> Le 03/11/2018 à 16:19, Stefan Krah a écrit :
>>> On Sat, Nov 03, 2018 at 07:22:21AM -0700, Ethan Furman wrote:
>>>> On 11/03/2018 03:55 AM, Paul Moore wrote:
>>>>
>>>>> Frankly, I feel pretty disenfranchised by the process
>>>>> at the moment.
>>>>
>>>> +1
>>>
>>> I wouldn't go as far as disenfranchised, but just this thread made it clear
>>> to me that taking in information is at least 10x faster if presented on a
>>> mailing list.
>>>
>>> Discourse feels like eating soup with a fork, especially now that the
>>> volume is higher.
>>
>> Indeed. As soon as a discussion is starting to become branchy,
>> Discourse just ruins readability compared to a normal threaded
>> discussion system. The electoral system discussion is an example of that:
>> https://discuss.python.org/t/python-governance-electoral-system/290
>>
>
> Huh, I found the experience exactly the opposite. I was just remarking last night how glad I was that the discussion happened in discourse instead of on the mailing list, because of how poorly I felt the discussion would have gone on a mailing list. The ability to trivially multi quote alone was a drastic improvement, much less the ability to control, on a topic by topic basis, what level of notification I wanted for that topic.
>
Perhaps the difference is in that every mail client I’ve ever used presents mailing list threads (or any thread) as a singular flat stream anyways? To be honest, I find the threaded views on like hyper kitty or piper mail to be abysmal anyways :|
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20181103/9008dd42/attachment-0001.html>
More information about the python-committers
mailing list