Hello everyone! I was wondering if we could make a decision about this topic. On the one hand, and as far as I understand, the forum is the preferred channel of communication. On the other hand, having multiple channels of communication can spread important discussions too thin, making it difficult to have productive conversations in one place.
As a newcomer to the contributing community, I can attest that the current situation causes some confusion. IMHO, the same applies to the chat options: there is IRC and the Discord server (though perhaps I should start a new forum topic about that in order to keep decisions separated). In summary, I'm +1 to "move on-mass (all few of us :) over there"! Thank you! Natalia. On Thursday, January 26, 2023 at 10:07:36 AM UTC-3 Alex Krupp wrote: > I just submitted a proposal to create a Discourse plugin to improve the > accuracy of their inbound email parsing. This would enable two things: > > - Folks who prefer to live in their inbox could continue to do so and > contribute by just replying to emails. Discourse currently has > reply-by-email, but it often mangles formatting and/or entirely deletes > text. Once these issues are fixed, folks who like the current experience > would be able to just pretend the forum doesn't exist and continue having > the same experience as they currently have with Google Groups. > - Right now importing the archives from Google Groups into Discourse > isn't realistic for the same reasons; some messages will import correctly, > but others will be mangled or missing text. This would also be made > possible. > > If this is something you care about (positively or negatively), here is > the exploratory proposal: > > > https://meta.discourse.org/t/proposed-plugin-to-improve-reply-by-email-accuracy/252944 > > Any feedback and/or testing would be much appreciated! Right now Discourse > recognizes that this is a problem and is interested in solving it, but > getting it prioritized will require folks to A) speak up saying they want > it done B) test the underlying API to verify that it actually solves the > problem. > > Alex > > On Fri, Jan 20, 2023 at 2:24 AM Carlton Gibson <carlton...@gmail.com> > wrote: > >> OK, I've updated the Trac wiki page to point to the forum too. (We use >> this as a wiki-link in responses to guide folk onwards.) >> >> The docs have a `|django-developers|` shortcut used in quite a few places >> so that needs a moment more to review and adjust. >> (I'll look at it soon-ish... — if no-one beats me to it :) >> >> Thanks. >> C >> >> On Thu, 19 Jan 2023 at 18:15, Andrew Godwin <and...@aeracode.org> wrote: >> >>> We should at least update those Trac and Triage Workflow docs to point >>> to both, maybe with the Forum first? >>> >>> Andrew >>> >>> On Thu, Jan 19, 2023, at 12:30 AM, Carlton Gibson wrote: >>> >>> I'm trying to begin new conversations there where I can. >>> >>> The main issue is that we're still pointing people here from Trac and >>> the Triage Workflow docs — so if there's a rough "Yeah, let's do it" we can >>> adjust practice there. >>> >>> I expect there will always be the "How do I start?" posts. The Forum at >>> least has a pinned post for that. ... >>> >>> On Thu, 19 Jan 2023 at 01:04, 'Kye Russell' via Django developers >>> (Contributions to Django itself) <django-d...@googlegroups.com> wrote: >>> >>> Hi all, >>> >>> I find that the signal-to-noise ratio on this mailing list is (by my >>> determination) quite bad around this time of year. >>> >>> Is a move to the forum still on the cards? >>> >>> Kye >>> On 6 Dec 2022 at 7:16 AM +0800, Andrew Godwin <and...@aeracode.org>, >>> wrote: >>> >>> I did some investigation of moving django-users and django-developers to >>> the Forum right after DjangoCon; I wanted to see if we could import all the >>> old posts too, which we probably could, but I'm not entirely sure of the >>> utility of that. >>> >>> I will say that the forum is a lot easier to moderate - the ability to >>> moderate after a post has gone out, rather than gating all posts behind >>> approval if they're untrusted, is a big step in itself, not to mention the >>> ability to remove sensitive or offensive content once it's posted. >>> >>> Andrew >>> >>> On Monday, November 28, 2022 at 10:01:17 PM UTC-7 m...@kye.id.au wrote: >>> >>> IMO django-announce and django-updates serve a very different purpose >>> and I would be against moving them if it were suggested. >>> >>> I am incredibly strongly in favour of moving django-developers and >>> django-users to the forums. IMO being able to more easily trap people >>> misusing this list as a tech support channel is itself reason enough to >>> move. Beyond that, I’d argue that the plentiful UX issues with Google >>> Groups, and mailing lists in general, certainly don’t do the community any >>> favours in terms of getting more people on board. >>> >>> Kye >>> >>> On 28 Nov 2022 at 11:40 PM +0800, 'Tobias McNulty' via Django developers >>> (Contributions to Django itself) <django-d...@googlegroups.com>, wrote: >>> >>> As someone who only just joined the forum -- I'm +1: >>> >>> - The forum has seen great adoption from what I can tell (nearly >>> half the number of posts as django-developers during the same time >>> period, >>> not bad given the mailing list's head start in subscribers). >>> - It seems beneficial to house future conversations in a single >>> place, e.g., so members don't need to subscribe to both the mailing list >>> and forum to get the full picture of current active development, set up >>> two >>> different sets of mail filters to tag things appropriately, etc... >>> >>> Would the plan be to switch django-users as well? I think similar >>> arguments could be made for consolidating those... >>> >>> (On the other hand, I see little value in switching django-announce and >>> django-updates, but I'm not necessarily opposed to it either, especially if >>> there's a way to import the subscribers to those lists...) >>> >>> Cheers, >>> >>> >>> *Tobias McNulty*Chief Executive Officer >>> >>> tob...@caktusgroup.com >>> www.caktusgroup.com >>> >>> >>> >>> On Mon, Nov 28, 2022 at 9:05 AM Carlton Gibson <carlton...@gmail.com> >>> wrote: >>> >>> Hey Roger, >>> >>> Indeed it does. You can set up Email Mode (that may not be the actual >>> name) and it’ll work just like a mailing list. >>> >>> You can also subscribe to just a particular category, so the Internals >>> one would map to the discussion on this list. >>> >>> >>> >>> On Monday, 28 November 2022, Roger Gammans <rgam...@gammascience.co.uk> >>> wrote: >>> >>> Hi >>> >>> I can't speak for others, but I personally STRONGLY value the fact that >>> this discussion happens in my inbox, not on yet another website. >>> >>> But perhaps the forum still supports this reading mode? >>> >>> On Mon, 2022-11-28 at 05:38 -0800, Carlton Gibson wrote: >>> >>> Hi all. >>> >>> Given the issues with Tom's access to the mailing list here, and the >>> fact that the Forum has been active for a few years now, and is a great >>> success, I'd like to revisit whether we can move on-mass (all few of us :) >>> over there? >>> >>> We'd enjoy the benefits of a much nicer system. We'd not have issues >>> such as the current, and we'd be one less item in the pocket of a >>> mega-corp. (You can rank those as you will :) >>> >>> Initially when this can up (a long time ago) Andrew and Tom discussed >>> whether we could import the history here into the forum. I think that's >>> unnecessary. We can still access the history here (until such a day as >>> Google takes it away) at worst -- but, rather, if we can get an archive we >>> could import it into read-only Datasette instance[0] — and that would >>> likely be good enough. >>> >>> Can we move now? >>> >>> Thanks. >>> >>> Kind Regards, >>> >>> Carlton >>> >>> >>> [0]: I'd happily do this. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/101f4e6d-9b83-47ab-bb1b-b571402e037dn%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/django-developers/101f4e6d-9b83-47ab-bb1b-b571402e037dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/4a329eadd5606c2f94aa5638e079800f1914d0d7.camel%40gammascience.co.uk >>> >>> <https://groups.google.com/d/msgid/django-developers/4a329eadd5606c2f94aa5638e079800f1914d0d7.camel%40gammascience.co.uk?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/CAJwKpyTSfF51C6ejog0xMd_6s-DofOUT4yaTeWmoc5SEiTY8jQ%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/django-developers/CAJwKpyTSfF51C6ejog0xMd_6s-DofOUT4yaTeWmoc5SEiTY8jQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/CAMGFDKSKe7ZDDwiaBpKtsU0z582K482PFsSpNfTLSvb2B-L95A%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/django-developers/CAMGFDKSKe7ZDDwiaBpKtsU0z582K482PFsSpNfTLSvb2B-L95A%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/60a05b93-e297-48ee-9bb1-4dcf54d76c64n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/django-developers/60a05b93-e297-48ee-9bb1-4dcf54d76c64n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/dfe142b6-c535-458e-8eeb-b65c0fad951c%40Spark >>> >>> <https://groups.google.com/d/msgid/django-developers/dfe142b6-c535-458e-8eeb-b65c0fad951c%40Spark?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/CAJwKpySNRUkhxN1N80LxQaf49HJacLUf6EO16akeH2bNQr6q6g%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/django-developers/CAJwKpySNRUkhxN1N80LxQaf49HJacLUf6EO16akeH2bNQr6q6g%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-develop...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/57abfafd-2cc8-4453-bb67-8673bb882ee6%40app.fastmail.com >>> >>> <https://groups.google.com/d/msgid/django-developers/57abfafd-2cc8-4453-bb67-8673bb882ee6%40app.fastmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAJwKpySDiaDx0tJDWO0YZwuG0MTzTGfxY9t9m1druBVkpvd70A%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/django-developers/CAJwKpySDiaDx0tJDWO0YZwuG0MTzTGfxY9t9m1druBVkpvd70A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > > Alex Krupp > Cell: (607) 351 2671 <(607)%20351-2671> > > Read my Email: www.fwdeveryone.com/u/alex3917 > Subscribe to my blog: https://alexkrupp.typepad.com/ > My homepage: www.alexkrupp.com > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/aecb0c5f-b191-466e-844d-63a2217f3a7bn%40googlegroups.com.
