[Python-Dev] Re: Moving to Discourse

2022-09-22 Thread Brett Cannon
On Thu, Sep 22, 2022 at 12:41 AM Baptiste Carvello <
devel2...@baptiste-carvello.net> wrote:

> Hello,
>
> Le 21/09/2022 à 13:14, Petr Viktorin a écrit :
> > On 21. 09. 22 10:17, Baptiste Carvello wrote:
> >>
> >> * mailing-list mode: there needs to be a *standardized* set of filters
> >> to access Core-Dev + PEPs (and only that).
> >> [...]
>
> > Do you have a proposal we could standardize?
> > Open a PR on the devguide. You shouldn't need an official hat-wearer
> > around, unless there's a disagreement.
>
> I believe indeed that the devguide should provide complete guidance
> towards getting a python-dev equivalent using mailing-list mode, to
> avoid many users having to reinvent the wheel. I don't have enough
> experience to give such advice myself (yet).
>
> > But I don't think the goal is to make sure all people using the mailing
> > list get the same set of posts. Different people have different
> interests.
>
> That's exaggerated: often many people share common interests, and thus
> want to follow a common set of discussions.


... which is expected to take place on Discourse. A key point here is we
are trying to consolidate after having this split approach for a few years
that people found annoying. We also acknowledge we can't stop people from
talking wherever they want on the internet.


> This is what makes up a
> discussion forum. Python-dev has served well its hundreds (or is it
> thousands) of users over all those years, so its perimeter must be
> sensible enough.
>

But the mailing list has also not served others well either (and people
have explicitly told us the mailing list didn't serve them, so this isn't a
hypothesis), so I don't think it "must be sensible enough" that what
python-dev does is always best/right/sensible. There is no perfect
solution, hence why we had this lengthy discussion to begin with.


>
> > Only mirroring/archiving Core-Dev + PEPs also seems pretty arbitrary.
>
> According to the devguide, "these are the Discourse equivalents to the
> python-dev mailing list". I believe many people want just that. This is
> also the perimeter that makes most sense for long term external
> archival, as it is likely to contain all major design discussions.
>
> >> * RSS: the shortcomings I described in my august post [2] are still
> >> there. At the very least, the PSF needs to make sure that the age /
> >> length limits of the RSS files (both core-dev.rss and posts.rss) are
> >> *much* increased.
>
> > I'm not sure what the PSF can do here -- this sounds like it should be a
> > feature request to Discourse.
>
> Discourse could indeed make their RSS interface much friendlier. Alas,
> as I say in my previous message, a very useful feature request
> (per-category post feeds) has been lingering for 6 years. So I won't
> hold my breath.
>
> In the meantime, I suppose Discourse must have some instance
> configuration knobs, and it would make sense that the length of the RSS
> files can be changed there (being a very arbitrary limit). The PSF could
> then choose a more appropriate length just for their own instance (the
> current 25-post limit represents less than 24 hours; a few days instead
> would be nice).
>

If you can find the setting then we can look at tweaking it, but a quick
glance at the admin interface didn't turn up anything obvious.

-Brett


>
> > I guess the mailing list mode is a better option if you don't want to
> > miss anything. Is it lacking something that RSS provides, besides easier
> > filtering?
>
> There is room between not missing anything and having less than 24 hours
> of history available.
>
> Since you asked (but not a major point): RSS is accessible without
> registering an account.
>
> Cheers,
> Baptiste
>
> >> [2]
> >>
> https://mail.python.org/archives/list/python-dev@python.org/message/UZJ27G57F7QJJ2LYBDGZQ5BIXLH7OXWJ/
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/MBARP67IL4X3LUWQGEELTMFPJCLUXBTI/
> Code of Conduct: http://python.org/psf/codeofconduct/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/ZD27KIII3TVMKZJSTRBYAKBS3BU43JUZ/
Code of Conduct: http://python.org/psf/codeofconduct/


[Python-Dev] Re: Moving to Discourse

2022-09-22 Thread Baptiste Carvello
Hello,

Le 21/09/2022 à 13:14, Petr Viktorin a écrit :
> On 21. 09. 22 10:17, Baptiste Carvello wrote:
>>
>> * mailing-list mode: there needs to be a *standardized* set of filters
>> to access Core-Dev + PEPs (and only that).
>> [...]

> Do you have a proposal we could standardize?
> Open a PR on the devguide. You shouldn't need an official hat-wearer
> around, unless there's a disagreement.

I believe indeed that the devguide should provide complete guidance
towards getting a python-dev equivalent using mailing-list mode, to
avoid many users having to reinvent the wheel. I don't have enough
experience to give such advice myself (yet).

> But I don't think the goal is to make sure all people using the mailing
> list get the same set of posts. Different people have different interests.

That's exaggerated: often many people share common interests, and thus
want to follow a common set of discussions. This is what makes up a
discussion forum. Python-dev has served well its hundreds (or is it
thousands) of users over all those years, so its perimeter must be
sensible enough.

> Only mirroring/archiving Core-Dev + PEPs also seems pretty arbitrary.

According to the devguide, "these are the Discourse equivalents to the
python-dev mailing list". I believe many people want just that. This is
also the perimeter that makes most sense for long term external
archival, as it is likely to contain all major design discussions.

>> * RSS: the shortcomings I described in my august post [2] are still
>> there. At the very least, the PSF needs to make sure that the age /
>> length limits of the RSS files (both core-dev.rss and posts.rss) are
>> *much* increased.

> I'm not sure what the PSF can do here -- this sounds like it should be a
> feature request to Discourse.

Discourse could indeed make their RSS interface much friendlier. Alas,
as I say in my previous message, a very useful feature request
(per-category post feeds) has been lingering for 6 years. So I won't
hold my breath.

In the meantime, I suppose Discourse must have some instance
configuration knobs, and it would make sense that the length of the RSS
files can be changed there (being a very arbitrary limit). The PSF could
then choose a more appropriate length just for their own instance (the
current 25-post limit represents less than 24 hours; a few days instead
would be nice).

> I guess the mailing list mode is a better option if you don't want to
> miss anything. Is it lacking something that RSS provides, besides easier
> filtering?

There is room between not missing anything and having less than 24 hours
of history available.

Since you asked (but not a major point): RSS is accessible without
registering an account.

Cheers,
Baptiste

>> [2]
>> https://mail.python.org/archives/list/python-dev@python.org/message/UZJ27G57F7QJJ2LYBDGZQ5BIXLH7OXWJ/
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/MBARP67IL4X3LUWQGEELTMFPJCLUXBTI/
Code of Conduct: http://python.org/psf/codeofconduct/