[Python-Dev] Re: Switching to Discourse

> This does not solve the problem of engaging actively in a discussion, of course I just submitted a proposal to create a Discourse plugin to improve the accuracy of their inbound email parsing, which is something that several people have complained about in this thread. This would enable two

[Python-Dev] Re: Switching to Discourse

Cameron Simpson writes: > I'm presuming we're talking about ways to bidirectionally mirror between > mailman and a Discourse forum. Yes. > None of that is easy to fix - mailing lists essentially just forward > messages, with some gatewaying of what messages they allow inbound >

[Python-Dev] Re: Switching to Discourse

Baptiste Carvello writes: > There is a small catch though: unless I'm mistaken, Discourse won't let > you subscribe to just a set of categories, so any filtering has to > happen on the Mailman side. There are two approaches that come to mind. The first is list-per-category, which would most

[Python-Dev] Re: Switching to Discourse

On 12Dec2022 01:05, Abdur-Rahmaan Janhangeer wrote: If only, fellow list colleagues, I could see only the topics I choose on Discourse. You can mute catgeories. I don't. The Discourse feels like python-list, python-dev, python-* combined. I feel cluttered. Aye. But I filter my inbound

[Python-Dev] Re: Switching to Discourse

On 11Dec2022 19:50, Tiziano Zito wrote: On Sat 10 Dec, 17:47 +0100, Baptiste Carvello wrote: There is a small catch though: unless I'm mistaken, Discourse won't let you subscribe to just a set of categories, so any filtering has to happen on the Mailman side. Well, it is actually possible

[Python-Dev] Re: Switching to Discourse

> On 11 Dec 2022, at 21:05, Abdur-Rahmaan Janhangeer > wrote: > > If only, fellow list colleagues, I could see only the topics I choose on > Discourse. Have you tried changing the Preferences for Notifications/Categories? That would appear to give you the control you are asking for? Barry

[Python-Dev] Re: Switching to Discourse

If only, fellow list colleagues, I could see only the topics I choose on Discourse. The Discourse feels like python-list, python-dev, python-* combined. I feel cluttered. If only I could also export the folks using only the mailing list to the Discourse. If only Discourse was as easy to search

[Python-Dev] Re: Switching to Discourse

On Sat 10 Dec, 17:47 +0100, Baptiste Carvello wrote: There is a small catch though: unless I'm mistaken, Discourse won't let you subscribe to just a set of categories, so any filtering has to happen on the Mailman side. Well, it is actually possible to achieve what you want. I have set up

[Python-Dev] Re: Switching to Discourse

Le 10/12/2022 à 22:51, Cameron Simpson a écrit : > > In short: copying the Discourse stuff to mailman could be done by > subscribing the mailman list to the Discourse forum.  Letting > _nonDiscourse_ users reply or post to Discourse is not trivial. IMHO it would already be a nice achievement if

[Python-Dev] Re: Switching to Discourse

I'm presuming we're talking about ways to bidirectionally mirror between mailman and a Discourse forum. On 10Dec2022 21:21, Stephen J. Turnbull wrote: Since Mailman (and its users!) expects messages to arrive asynchronously and handles that using threading information, as far as I can see the

[Python-Dev] Re: Switching to Discourse

Hi, Le 10/12/2022 à 13:21, Stephen J. Turnbull a écrit : > > as far as > I can see the Mailman side is handled as well as it can be now that > Discourse provides threading information, and you just subscribe > Mailman to Discourse. There is a small catch though: unless I'm mistaken, Discourse

[Python-Dev] Re: Switching to Discourse

Ethan Furman writes: > It seems to me the best possible outcome of Discourse vs email is > somebody / some company donating the time and/or funding to improve > Discourse's and Mailman's abilities to interoperate with each > other. There are fundamental differences between email's

[Python-Dev] Re: Switching to Discourse

On 09Dec2022 14:58, Simon Cross wrote: I can now pull from Discourse or GH when it’s convenient for me. It’s also much easier to disengage for a few days and catch up later. I have a question about how you handle multiple communities. I'm subscribed to ~30 python-dev style mailing lists

[Python-Dev] Re: Switching to Discourse

On 12/9/22 09:20, Barry Warsaw wrote: > The whole shift away from email leaves me calmer and better engaged. There are definitely advantages to the different methods of staying engaged, and which is the best fit definitely depends on the individual. It seems to me the best possible outcome

[Python-Dev] Re: Switching to Discourse

It’s possible, but here’s the way I look at it. I’m *already* engaged with dozens of communities, within Python but also others. So every morning I’d wake up to many hundreds of emails, which is just incredibly stress inducing. So it’s a tension between guarding my time better and FOMO.

[Python-Dev] Re: Switching to Discourse

> > I have a question about how you handle multiple communities. I'm > subscribed to ~30 python-dev style mailing lists across different > projects. There is no way I can open up 30 Discourse sites each day. > Mail brings everything into one place for me, and I have things setup > so that new mail

[Python-Dev] Re: Switching to Discourse

Barry Warsaw writes: > I absolutely love not having to slog through hundreds of emails > before my first shots of caffeine, and I can now pull from > Discourse or GH when it’s convenient for me. It’s also much easier > to disengage for a few days and catch up later. I absolutely cannot

[Python-Dev] Re: Switching to Discourse

> I can now pull from Discourse or GH when it’s convenient for me. It’s also > much easier to disengage for a few days and catch up later. I have a question about how you handle multiple communities. I'm subscribed to ~30 python-dev style mailing lists across different projects. There is no way

[Python-Dev] Re: Switching to Discourse

On Dec 7, 2022, at 02:57, Petr Viktorin wrote: > > I'd like to point out that the SC decision was *reactive*, after most > discussions moved to Discourse without SC pushing. > > I liked the list myself! But as soon as most of the posts were mandatory PEP > and release notices, it stopped

[Python-Dev] Re: Switching to Discourse

I am a new community member and extremely eager to contribute. I am just adding my two cents here. Apart from the core-mentorship list, I have not found any other list useful. Discourse is impactful and has a quite low turnaround time. I have been answering questions in the forum and from what I

[Python-Dev] Re: Switching to Discourse

Le 07/12/2022 à 11:57, Petr Viktorin a écrit : > > I'd like to point out that the SC decision was *reactive*, after most > discussions moved to Discourse without SC pushing. > > I liked the list myself! But as soon as most of the posts were mandatory > PEP and release notices, it stopped being

[Python-Dev] Re: Switching to Discourse

Le 07/12/2022 à 16:11, John Ehresman a écrit : > I’ve found that using mailing list mode to lurk on discuss.python.org works > well. I’ve set up rules on my local mail client to archive what I don’t want > in my inbox; I have 4 rules in place now, though I’m interested in a bit more > than what

[Python-Dev] Re: Switching to Discourse

I’ve found that using mailing list mode to lurk on discuss.python.org works well. I’ve set up rules on my local mail client to archive what I don’t want in my inbox; I have 4 rules in place now, though I’m interested in a bit more than what was typically on python-dev. Cheers, John > On Dec

[Python-Dev] Re: Switching to Discourse

On 06. 12. 22 11:16, Baptiste Carvello wrote: Hi, Le 05/12/2022 à 14:50, Stephen J. Turnbull a écrit : I'd be sad, but I get the feeling that the only people left reading it are "here for the community", not to develop code, … I think this is indeed true, but that's nothing to be sad

[Python-Dev] Re: Switching to Discourse

Baptiste Carvello writes: > Le 05/12/2022 à 14:50, Stephen J. Turnbull a écrit : > > > > I'd be sad, but I get the feeling that the only people left > > reading it are "here for the community", not to develop code, … > I think this is indeed true, but that's nothing to be sad about: I'm

[Python-Dev] Re: Switching to Discourse

Hi, Le 05/12/2022 à 14:50, Stephen J. Turnbull a écrit : > > I'd be sad, but I get the feeling that the only people left > reading it are "here for the community", not to develop code, … I think this is indeed true, but that's nothing to be sad about: "being here for the community" is not wrong

[Python-Dev] Re: Switching to Discourse

Barney Gale writes: > I did; I think it was a mistake to start discourse without a plan for > shutting down this mailing list. "Start"? When it was started it was an experiment. Nobody had a strong take on whether Discourse would really take off or not, or even whether there might be a

[Python-Dev] Re: Switching to Discourse

On Mon, 5 Dec 2022 at 01:00, Steven D'Aprano wrote: > On Sun, Dec 04, 2022 at 08:20:56PM +, Barney Gale wrote: > > > Oh brilliant. I'll unsubscribe from this list then. It sounds like the > only > > people using it will be those folks who think their tooling preferences > are > > more

[Python-Dev] Re: Switching to Discourse

On Fri, 02 Dec 2022 18:41:44 -0500 "Gordon R. Burgess" wrote: > I am a long time lurker here*, a professional and educational user of > the language, a list moderator with practical exeperience managing a > engaged community of a few thousand users over the course of a decade - > and yes, I am

[Python-Dev] Re: Switching to Discourse

On Sun, Dec 04, 2022 at 08:20:56PM +, Barney Gale wrote: > Oh brilliant. I'll unsubscribe from this list then. It sounds like the only > people using it will be those folks who think their tooling preferences are > more important than creating a joined-up Python community; I can survive >

[Python-Dev] Re: Switching to Discourse

Oh brilliant. I'll unsubscribe from this list then. It sounds like the only people using it will be those folks who think their tooling preferences are more important than creating a joined-up Python community; I can survive without their input. On Sun, 4 Dec 2022, 19:53 Baptiste Carvello, <

[Python-Dev] Re: Switching to Discourse

Le 04/12/2022 à 16:55, Barney Gale a écrit : > > I don't want to post to multiple > places in order to reach the devs. Nobody proposed that. In order to reach the devs, you use discourse (or have someone else do it on your behalf). Just let the "second circle" of the community keep their

[Python-Dev] Re: Switching to Discourse

Perspective from a minor Python contributor: The only thing worse than email or Discourse is email AND Discourse. Fragmented communities are a nightmare. I don't want to post to multiple places in order to reach the devs. Its hard enough to build consensus already. The relative strengths of email

[Python-Dev] Re: Switching to Discourse

Le 02/12/2022 à 18:49, Brett Cannon a écrit : > > Since we are promoting/pushing folks to use discuss.python.org Until now I've seen more "pushing" (with sticks) than "promoting" (with carrots). Since august I've been looking for a way to follow the discussions on discourse without using the

[Python-Dev] Re: Switching to Discourse

I am a long time lurker here*, a professional and educational user of the language, a list moderator with practical exeperience managing a engaged community of a few thousand users over the course of a decade - and yes, I am old. I saw what happened when the young developers there insisted that

[Python-Dev] Re: Switching to Discourse

On Fri, Dec 2, 2022 at 8:17 AM Baptiste Carvello < devel2...@baptiste-carvello.net> wrote: > Le 02/12/2022 à 10:09, Gregory P. Smith a écrit : > > > > On Thu, Dec 1, 2022 at 8:37 AM Victor Stinner > > wrote: > > > > > > Should we *close* the python-dev mailing

[Python-Dev] Re: Switching to Discourse

Le 02/12/2022 à 10:09, Gregory P. Smith a écrit : > > On Thu, Dec 1, 2022 at 8:37 AM Victor Stinner > wrote: > > > Should we *close* the python-dev mailing list? > > > I'd be in favor of this. Why? Californian firms won't let their employees use an

[Python-Dev] Re: Switching to Discourse

On Thu, Dec 1, 2022 at 8:37 AM Victor Stinner wrote: > > Should we *close* the python-dev mailing list? > I'd be in favor of this. Or at least setting up an auto-responder suggesting people post on discuss.python.org instead. -gps ___ Python-Dev

[Python-Dev] Re: Switching to Discourse

On 01. 12. 22 17:28, Victor Stinner wrote: What happened to this SC decision (move to Discourse)? People started again to write on python-dev. So what's going on? PEPs must be announced on Discourse. For discussions you can use any medium. A list, Discord, IRC, in-person chat... Should I

[Python-Dev] Re: Switching to Discourse

What happened to this SC decision (move to Discourse)? People started again to write on python-dev. So what's going on? Should I reply on python-dev? Ask to move to Discourse? Should we *close* the python-dev mailing list? Victor ___ Python-Dev

[Python-Dev] Re: Switching to Discourse

Oh, I see, thanks. This is for the email interface, not the web interface. -Barry > On Sep 27, 2022, at 13:49, Cameron Simpson wrote: > > On 27Sep2022 11:14, Barry Warsaw wrote: >>> Threading on the Python Discourse should now be working correctly. This is >>> the good work of Martin

[Python-Dev] Re: Switching to Discourse

On 27Sep2022 11:14, Barry Warsaw wrote: Threading on the Python Discourse should now be working correctly. This is the good work of Martin Brennan: https://meta.discourse.org/u/martin I’m not sure what “working correctly” means. Do you have some examples on discuss.python.org where

[Python-Dev] Re: Switching to Discourse

> Threading on the Python Discourse should now be working correctly. This is > the good work of Martin Brennan: https://meta.discourse.org/u/martin I’m not sure what “working correctly” means. Do you have some examples on discuss.python.org where threading is used? Is this something that

[Python-Dev] Re: Switching to Discourse

On 15Jul2022 13:26, Barry Warsaw wrote: To me, that’s the biggest negative of Discourse, and I definitely prefer threaded discussions. Unfortunately though, much like top posting , I think that horse is out of the barn, what with other forums like GitHub being linear. On Jul 15, 2022, at

[Python-Dev] Re: Switching to Discourse

Le 18/07/2022 à 13:45, Baptiste Carvello a écrit : > Le 15/07/2022 à 17:52, Petr Viktorin a écrit : >> >> For everything on Discourse, the RSS feed is at >> https://discuss.python.org/latest.rss >> For a specific categoriy/topic, append .rss to the Web URL. > > [...] > Is there a way to access

[Python-Dev] Re: Switching to Discourse

On 21. 07. 22 9:01, Cameron Simpson wrote: On 21Jul2022 13:25, Stephen J. Turnbull wrote: Cameron Simpson writes: Discourse does not do `In-Reply-To:` very well at all. Here's some headers from the _second_ post in the "Core dev sprint this year" thread: Message-ID: In-Reply-To:

[Python-Dev] Re: Switching to Discourse

On Sat, Jul 23, 2022, 19:33 Steven Barker wrote: > So to give my final takeaway: It might be possible for Discourse to > replace Python-dev, even for those who wish to get their messages by email. > But the user experience of signing up is vastly worse, and will need much > more than a single

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 3:42 PM Steven Barker wrote: > So last night I tried activating mailing list mode [...] > To follow up on my own post, here's an update. I figured out that I'd done something incorrectly the first time I tried muting certain categories of posts on Discourse. I think I

[Python-Dev] Re: Switching to Discourse

One thing I’ve noticed and found disappointing with discourse is that it seems to lose the markdown formatting in both emails and quoting in replies. It really effects the readability, partly when there’s code that loses its formatting :-( I don’t know that that affects this discussion-/ but

[Python-Dev] Re: Switching to Discourse

Hi Brett, I understand your points. I think the main point of difference is the gap in usability between GitHub discussions and Discourse - I think it's massive, but I understand others will be less enamoured by GitHub and less frustrated by Discourse than me. One correction: but that does make

[Python-Dev] Re: Switching to Discourse

On Fri, Jul 22, 2022 at 3:45 AM Samuel Colvin wrote: > Reading this thread and thinking about discuss.python.org/Discourse - I'm > surprised no one is advocating github discussions > . > I think it's because discuss.python.org is what we decided to try

[Python-Dev] Re: Switching to Discourse

Reading this thread and thinking about discuss.python.org/Discourse - I'm surprised no one is advocating github discussions . In particular organisation discussions would provide an

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 07:06:47PM -0400, Edwin Zimmerman wrote: > Mailing list mode is not what you want.  Instead, turn mailing list mode off > and set your email settings to these: > > > > You can adjust the categories you receive email notifications for by changing > your list of watched

[Python-Dev] Re: Switching to Discourse

Terry Reedy writes: > On 7/21/2022 8:46 PM, Christopher Barker wrote: > > Does anyone else find it very odd to call a communication system “discord”? > For games, most of which involve combat, it seems appropriate. For > CPython development, 'harmony' might be better. Already taken by the

[Python-Dev] Re: Switching to Discourse

On 7/21/2022 8:46 PM, Christopher Barker wrote: OT: Does anyone else find it very odd to call a communication system “discord”? For games, most of which involve combat, it seems appropriate. For CPython development, 'harmony' might be better. -- Terry Jan Reedy

[Python-Dev] Re: Switching to Discourse

Cameron Simpson writes: > On 21Jul2022 17:46, Christopher Barker wrote: > >OT: > >Does anyone else find it very odd to call a communication system > >“discord”? > > I think it is a refreshing level of honesty about what live chat is > like. As in "discordant". I would refine "live

[Python-Dev] Re: Switching to Discourse

On 21Jul2022 17:46, Christopher Barker wrote: >OT: >Does anyone else find it very odd to call a communication system >“discord”? I think it is a refreshing level of honesty about what live chat is like. As in "discordant". Cheers, Cameron Simpson

[Python-Dev] Re: Switching to Discourse

I feel similarly as Steven. I'm even less important to the development of CPython than he is. But like him, switching to Discourse means I simply won't try to follow development. Mailing list are friendly and easily manageable. In the small amount I've used Discourse, it feels unwieldy and less

[Python-Dev] Re: Switching to Discourse

OT: Does anyone else find it very odd to call a communication system “discord”? dis·cord /ˈdiskôrd/ *noun* 1. 1. disagreement between people. "a prosperous family who showed no signs of discord" “Naming things is hard” — but really? -CHB -- Christopher Barker, PhD (Chris)

[Python-Dev] Re: Switching to Discourse

On 21Jul2022 15:42, Steven Barker wrote: >So last night I tried activating mailing list mode, and I'm not >remotely >satisfied with the experience so far. Where mailing lists are concerned, >I'm *only *subscribed to python-dev. Not python-users, not -ideas, not >-packaging (if that's still a

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 6:47 PM Steven Barker wrote: > On Mon, Jul 18, 2022 at 6:28 AM Petr Viktorin wrote: > >> On 16. 07. 22 8:48, Miro Hrončok wrote: >> > On 15. 07. 22 13:18, Petr Viktorin wrote: >> >> - You can use discuss.python.org's “mailing list mode” (which >> >> subscribes you to all

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022, 15:26 Baptiste Carvello < devel2...@baptiste-carvello.net> wrote: > Le 21/07/2022 à 07:59, Stefan Behnel a écrit : > > > > I'm actually reading python-dev, c.l.py etc. through Gmane, and have > > done that ever since I joined. Simply because it's a mailing list of > > which

[Python-Dev] Re: Switching to Discourse

On Mon, Jul 18, 2022 at 6:28 AM Petr Viktorin wrote: > On 16. 07. 22 8:48, Miro Hrončok wrote: > > On 15. 07. 22 13:18, Petr Viktorin wrote: > >> - You can use discuss.python.org's “mailing list mode” (which > >> subscribes you to all new posts), possibly with filtering and/or > >> categorizing

[Python-Dev] Re: Switching to Discourse

Le 21/07/2022 à 07:59, Stefan Behnel a écrit : > > I'm actually reading python-dev, c.l.py etc. through Gmane, and have > done that ever since I joined. Simply because it's a mailing list of > which I don't need a local (content) copy, and wouldn't want one. Gmane > seems to have a complete

[Python-Dev] Re: Switching to Discourse

Le 21/07/2022 à 03:29, Stephen J. Turnbull a écrit : > > I can't speak to 1 and 2, and I can't speak to cost of resource usage > for 3, but it would be possible to have a Mailman list that has no > subscribers, prohibits subscription, and allows only a small number of > authorized posters, one of

[Python-Dev] Re: Switching to Discourse

To demystify why you want to boost (I am in the python discord and other non gaming and gaming chats) it unlocks better features but the core experence of chat still exists . Basically voice chat goes up to 384kbps steams go up to 1080p quality and you get a 100MB upload limit. I know that

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:34 AM Skip Montanaro wrote: > > No, Discord is a different thing; it does text and voice communication > > channels in real-time. If you're familiar with Slack, it's broadly > > similar in purpose. > > Thanks (and to the others who replied). FYI this multiple

[Python-Dev] Re: Switching to Discourse

On 21/07/2022 18:53, Mats Wichmann wrote: On 7/21/22 11:11, Mariatta wrote: On Thu, Jul 21, 2022 at 10:05 AM Skip Montanaro mailto:skip.montan...@gmail.com>> wrote: I have a perhaps stupid question. Is Discord the same as discuss.python.org , just by

[Python-Dev] Re: Switching to Discourse

On 7/21/22 11:16, Skip Montanaro wrote: >> No, Discord is a different thing; it does text and voice communication >> channels in real-time. If you're familiar with Slack, it's broadly >> similar in purpose. > > Thanks (and to the others who replied). It seems like they've tried to > make it a

[Python-Dev] Re: Switching to Discourse

On 7/21/22 11:11, Mariatta wrote: > > > On Thu, Jul 21, 2022 at 10:05 AM Skip Montanaro > mailto:skip.montan...@gmail.com>> wrote: > > I have a perhaps stupid question. Is Discord the same as > discuss.python.org , just by another > name? I find the

[Python-Dev] Re: Switching to Discourse

On Fri, 22 Jul 2022 at 03:17, Skip Montanaro wrote: > > > No, Discord is a different thing; it does text and voice communication > > channels in real-time. If you're familiar with Slack, it's broadly > > similar in purpose. > > Thanks (and to the others who replied). It seems like they've tried

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:20 AM Samuel Colvin wrote: > > If discord is not finalised, we might also consider https://zulip.com/ > which rust uses and would (based on a > very quick look) appear to be more appropriate for python development's use > case? > > >

[Python-Dev] Re: Switching to Discourse

> No, Discord is a different thing; it does text and voice communication > channels in real-time. If you're familiar with Slack, it's broadly > similar in purpose. Thanks (and to the others who replied). It seems like they've tried to make it a game, giving me the "opportunity" to buy boosts (or

[Python-Dev] Re: Switching to Discourse

On Thu, 21 Jul 2022 07:59:46 +0200 Stefan Behnel wrote: > h.vetin...@gmx.com schrieb am 18.07.22 um 18:04: > > One of the comments in the retro was: > >> Searching the archives is much easier and have found me many old threads > >> that I probably would have problem finding before since I

[Python-Dev] Re: Switching to Discourse

Hi, no I think "discord" refers to https://discord.com/ If discord is not finalised, we might also consider https://zulip.com/ which rust uses and would (based on a very quick look) appear to be more appropriate for python development's use case? Samuel --

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:05 AM Skip Montanaro wrote: > I have a perhaps stupid question. Is Discord the same as > discuss.python.org, just by another name? I find the similarity in > names a bit confusing. > > It's not the same. discuss.python.org is an instance of Discourse. Discord is

[Python-Dev] Re: Switching to Discourse

On Fri, 22 Jul 2022 at 03:07, Skip Montanaro wrote: > > I have a perhaps stupid question. Is Discord the same as > discuss.python.org, just by another name? I find the similarity in > names a bit confusing. > No, Discord is a different thing; it does text and voice communication channels in

[Python-Dev] Re: Switching to Discourse

I have a perhaps stupid question. Is Discord the same as discuss.python.org, just by another name? I find the similarity in names a bit confusing. Skip ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 12:19 AM Stefan Behnel wrote: > I'm actually reading python-dev, c.l.py etc. through Gmane, and have done > that ever since I joined. Simply because it's a mailing list of which I > don't need a local (content) copy, and wouldn't want one. Gmane seems to > have a complete

[Python-Dev] Re: Switching to Discourse

On Wed, Jul 20, 2022 at 05:43:26PM -0700, Ethan Furman wrote: > It works, but I wouldn't say "quite well" -- any thread from discourse is > one long linear series of replies, and reading them in chronological order > means jumping around and trying to figure what is a reply to what. Sometimes,

[Python-Dev] Re: Switching to Discourse

On 21Jul2022 13:25, Stephen J. Turnbull wrote: >Cameron Simpson writes: > > Discourse does not do `In-Reply-To:` very well at all. Here's some > > headers from the _second_ post in the "Core dev sprint this year" > > thread: > > > > Message-ID: > > > > In-Reply-To: > > References:

[Python-Dev] Re: Switching to Discourse

h.vetin...@gmx.com schrieb am 18.07.22 um 18:04: One of the comments in the retro was: Searching the archives is much easier and have found me many old threads that I probably would have problem finding before since I haven’t been subscribed for that long. I'm actually reading python-dev,

[Python-Dev] Re: Switching to Discourse

Cameron Simpson writes: > Discourse does not do `In-Reply-To:` very well at all. Here's some > headers from the _second_ post in the "Core dev sprint this year" > thread: > > Message-ID: > > In-Reply-To: > References: I'm tempted to write something uncivil, but instead

[Python-Dev] Re: Switching to Discourse

I'm -1 on moving to the walled garden, but I don't expect this to change anyone's mind. I don't know if I'll move over to Discourse or not. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org

[Python-Dev] Re: Switching to Discourse

On 21Jul2022 10:29, Stephen J. Turnbull wrote: >As long as Discourse provides the In-Reply-To header field, the current >threading algorithm would work reasonably well. Discourse does not do `In-Reply-To:` very well at all. Here's some headers from the _second_ post in the "Core dev sprint this

[Python-Dev] Re: Switching to Discourse

Eric Snow writes: > I consider the ability to search message archives to be essential to > effective contribution[.] +1 > There are relevant three aspects to archival and search that are worth > asking about here: > > 1. search functionality on the [archive] web site > 2. ability to

[Python-Dev] Re: Switching to Discourse

On 7/20/22 17:35, Cameron Simpson wrote: > On 18Jul2022 16:53, Joannah Nanjekye wrote: >> My original stand on preferring email stands though due to stable >> standards. > > Several of us use the email mode in Discourse. It works quite well. For > me, both python-dev and the PDO posts land in

[Python-Dev] Re: Switching to Discourse

On 18Jul2022 16:53, Joannah Nanjekye wrote: >I see I might have misunderstood, thinking a python-dev channel on discuss >was not as active as the mailing list. Understood. > >My original stand on preferring email stands though due to stable >standards. Several of us use the email mode in

[Python-Dev] Re: Switching to Discourse

On Mon, Jul 18, 2022 at 11:48 AM wrote: > LLVM did the same recently (though they imported all previous messages from > the mailinglist, thus making them searchable in discourse) [2 - announcement; > 3 - retro], and by and large, I think it was a success. > > One of the comments in the retro

[Python-Dev] Re: Switching to Discourse

On Fri, Jul 15, 2022 at 5:21 AM Petr Viktorin wrote: > The Steering Council would like to switch from python-dev to > discuss.python.org. This seems like a net win for the community so +1 from me. (For me personally it amounts to disruption with little advantage, so I'd probably be -0).

[Python-Dev] Re: Switching to Discourse

On Fri, Jul 15, 2022 at 12:15 PM Barry Warsaw wrote: > I agree that the experiment has proven successful enough that there’s more > value at this point in consolidating discussions. We've only been running this experiment since 2017(?) so maybe it's too soon to say it's a success? -eric

[Python-Dev] Re: Switching to Discourse

I think it's a great idea! :) [1] LLVM did the same recently (though they imported all previous messages from the mailinglist, thus making them searchable in discourse) [2 - announcement; 3 - retro], and by and large, I think it was a success. One of the comments in the retro was: > Searching

[Python-Dev] Re: Switching to Discourse

> > I don't think I *can* do much more than accept it and move on: > *if python-dev was used by everyone*, rather than almost exclusively by > people who prefer e-mail (and presumably use threading mail clients), > we'd get mangled threading anyway from all the non-threaded clients. > Don't

[Python-Dev] Re: Switching to Discourse

I see I might have misunderstood, thinking a python-dev channel on discuss was not as active as the mailing list. Understood. My original stand on preferring email stands though due to stable standards. On Mon., Jul. 18, 2022, 4:41 p.m. Petr Viktorin, wrote: > On 15. 07. 22 21:13, Joannah

[Python-Dev] Re: Switching to Discourse

On 15. 07. 22 21:13, Joannah Nanjekye wrote: I am -1 for leaving email due to the long history of standardization, for a platform whose future I don't know about. When you say core development is busier, does that mean the experiment with python-dev failed? aka wasn't a success, if so why are

[Python-Dev] Re: Switching to Discourse

On 15. 07. 22 20:59, Ethan Furman wrote: On 7/15/22 08:37, Petr Viktorin wrote: > And that's exactly why I consume Discourse in mailing list mode, with client-side > filtering in Thunderbird. How do you handle threading?  I follow each (sub)thread through to it's end, as it keeps a

[Python-Dev] Re: Switching to Discourse

On 16. 07. 22 8:48, Miro Hrončok wrote: On 15. 07. 22 13:18, Petr Viktorin wrote: - You can use discuss.python.org's “mailing list mode” (which subscribes you to all new posts), possibly with filtering and/or categorizing messages locally. Hello Petr, I suppose this might be the preferred

[Python-Dev] Re: Switching to Discourse

Petr Viktorin schrieb am 15.07.22 um 13:18: The discuss.python.org experiment has been going on for quite a while, and while the platform is not without its issues, we consider it a success. The Core Development category is busier than python-dev. According to staff, discuss.python.org is much

[Python-Dev] Re: Switching to Discourse

On 15. 07. 22 13:18, Petr Viktorin wrote: - You can use discuss.python.org's “mailing list mode” (which subscribes you to all new posts), possibly with filtering and/or categorizing messages locally. Hello Petr, I suppose this might be the preferred way for the old farts like me who prefer

[Python-Dev] Re: Switching to Discourse

On 15Jul2022 11:59, Ethan Furman wrote: >On 7/15/22 08:37, Petr Viktorin wrote: >> And that's exactly why I consume Discourse in mailing list mode, with >> client-side >> filtering in Thunderbird. > >How do you handle threading? I follow each (sub)thread through to >it's end, as it keeps a

  1   2   >