Hello, I'm afraid you misundertood my message. I'm not discussing the choice of Discourse as a communication medium (which would be futile after the decision has been made), just the thematic perimeter that would make up an equivalent of Python-dev (for those hundreds of us who happened to like it). Le 22/09/2022 à 19:58, Brett Cannon a écrit :
On Thu, Sep 22, 2022 at 12:41 AM Baptiste Carvello <devel2022@baptiste-carvello.net <mailto:devel2022@baptiste-carvello.net>> wrote: Le 21/09/2022 à 13:14, Petr Viktorin a écrit :
> 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. [...]
"Discourse", without further qualification, is a discussion medium, not a discussion forum as I mean it ("a group of people sharing common interests…"). The Python discourse instance is the equivalent of Python-list + Python-dev + Ideas + Typing + Packaging + whatever else. Nobody is expected to read all of that, are they? Thus it makes sense to be interested in a sensible subset of it.
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 [...], so I don't think it "must be sensible enough" that what python-dev does is always best/right/sensible. [...]
My words "sensible enough" only qualified the *thematic perimeter* of Python-dev: design discussions including PEPs, relation to other important projects in the community, sometimes general programming philosophy. This perimeter is a product of experience. There's a reason Python-dev was split from Python-list, then Ideas from Python-dev etc. Let history inform us. In conclusion, the only thing I'm looking for is a fully working way to access this information perimeter from a convenient mail-like interface. Various solutions have been handwaved, but none is ready for prime time.
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.
Sorry to say, but this is yet another sign that Discourse is not mature enough for a community as big as Python. This set-in-stone limit is obviously devised for a very small community. Cheers, Baptiste