[python-committers] Can we choose between mailing list and discuss.python.org?

[Nathaniel Smith]

On Thu, Feb 14, 2019, 09:39 Brett Cannon <brett at python.org wrote:

>
>
> On Wed, Feb 13, 2019 at 12:17 PM Paul Moore <p.f.moore at gmail.com> wrote:
>
>> On Wed, 13 Feb 2019 at 19:56, Steve Dower <steve.dower at python.org> wrote:
>> >
>> > On 13Feb2019 1112, Brett Cannon wrote:
>> > >
>> > >
>> > > On Wed, Feb 13, 2019 at 2:55 AM Paul Moore <p.f.moore at gmail.com
>> > > <mailto:p.f.moore at gmail.com>> wrote:
>> > >
>> > >     On Tue, 12 Feb 2019 at 22:00, Antoine Pitrou <antoine at python.org
>> > >     <mailto:antoine at python.org>> wrote:
>> > >      > Here is a 161-message Discourse thread (at the time of this
>> writing):
>> > >      > https://discuss.python.org/t/pep-517-backend-bootstrapping/789
>> > >
>> > >     As someone directly involved in that discussion, with a strong
>> need to
>> > >     understand all of the points being made, that's a great example of
>> > >     both the benefits and the flaws of the discourse model.
>> > >
>> > >
>> > > Can I ask if that entire thread is on topic, or is there a reasonable
>> > > point in that discussion where side conversations could have been
>> broken
>> > > off into a separate topic(s)? When email threads tend to reach that
>> > > length there have been side discussions that could have become their
>> own
>> > > topic if someone thought to change the subject and Discourse allows
>> for
>> > > having an admin break posts off at any point and I'm curious if it
>> would
>> > > have been helpful and people simply didn't think about it (I know I
>> > > don't always think of it immediately yet).
>> >
>> > My feeling (as I followed the entire discussion from the start) is that
>> > the side discussions all tied back, rather than diverging permanently.
>> > So at best it would be "you 2-3 go and discuss this part separately and
>> > come back when you agree", which as we know is often followed up by "you
>> > other 2-3 re-discuss everything they already discussed since you weren't
>> > part of the side discussion".
>>
>> Precisely this. I don't know *how* I would have split off a separate
>> sub-thread in Discourse if needed (it's easy enough in email by
>> changing the subject, I presume it's not much harder in Discourse?)
>>
>
> Nope, it's not hard. The process is:
>
>    1. An admin notices/is asked to split a topic that has diverged
>    2. The admin clicks the wrench icon and chooses to Select Posts
>    3. You select posts either manually, post + all following, or post +
>    all replies
>    4. You then have the option to create a new topic for the selected
>    posts, specifying category, title, labels, etc.
>
> The pro to this compared to subject changing in an ML is it's retroactive.
> The con is an admin needs to to it, but you can always @ mention 'admins'
> -- maybe 'staff' group has the same abilities? -- to bring a thread to
> their attention that needs splitting.
>

Apparently you don't actually need an admin to do this – any user with
"trust level 4" can do it:
https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/

That includes admins and moderators, but we can also promote as many people
as we want to that level, and they don't have to sign up for moderator work
or count against our staff account cap.

-n

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20190214/7fa53e20/attachment-0001.html>