Tanya Lattner via llvm-dev
2022-Jan-08 07:19 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
LLVM Community, I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. https://llvm.org/docs/DiscourseMigrationGuide.html If you have any questions about the plan, please let me know. Thanks, Tanya
Tobias Hieta via llvm-dev
2022-Jan-08 15:54 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
Hi, I am sure there will be quite a bit of push-back for this. But I just wanted to chime in and say that I so glad to move away from email. Thanks to the IWG for their work! -- Tobias. On Sat, 8 Jan 2022 at 08:19, Tanya Lattner via llvm-dev < llvm-dev at lists.llvm.org> wrote:> LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists > and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work > together as a community to resolve any potential issues or help each other > navigate this change. I have put the migration to discourse guide that was > drafted by the Infrastructure Working Group in LLVM Docs, and encourage > people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know. > > Thanks, > Tanya > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-- Tobias Hieta http://about.me/thieta -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20220108/5f0a0e0c/attachment.html>
James Henderson via llvm-dev
2022-Jan-10 09:47 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
Hi, I personally don't really have any particular opinion on moving to Discourse, versus staying on mailing lists (if pushed, my naturally conservative mindset would say stay/use mailman 3 as discussed before, but I'd probably adapt to a switch quickly enough). However, I do have some related concerns to do with the process in particular: 1) Regarding this paragraph in the blog: "The majority of the community was in favor of the move when the move to Discourse was discussed extensively on the LLVM mailing lists. This provides the features mentioned above in addition to a more modern communication. We did hear of one feature some would miss compared to Mailman: the ability to reply to someone directly through email. However, while it may not be ideal for some, we feel this is a worthwhile tradeoff to gain the other benefits, e.g. better safety for LLVM developers and users in general." I skimmed the most recent thread on this topic from the middle of last year, and the distinct impression I got was that the majority opinion, or at least about half of those posting were actually against any move to Discourse, with several raised concerns that I never saw addressed (topics about accessibility and disagreements from existing moderators to the point about moderation being a problem on mailman being two examples). I haven't gone over the thread which originally introduced Discourse back in 2019, so I can't say what happened there. Was this majority reached in the 2019 thread, because my memory of it was that there was no clear consensus in either direction? 2) Also from the above paragraph: who is "we" in "we feel this is a worthwhile tradeoff"? If referring to a specific subgroup (e.g. the IWG/the board), were these concerns actually discussed with the people who raised the concerns? If not, this seems to me like a case of "others don't agree with us, but we're going to ignore their concerns and go ahead with what we (i.e. the IWG/the board etc) want to do" which isn't how community consensus works... 3) The category structure: "January 7-9 - Re-configure the existing LLVM Discourse to the new category/subcategory structure (see below)" When was this structure discussed? Note that the mailing list announcement came AFTER this point of time had started, meaning there was zero opportunity for people like myself who have concerns with the category breakdown to raise them and suggest improvements. Contrast this with the Github Issues migration, where I was able to get additional categories added to the list of labels, to reflect the pre-existing bugzilla breakdown, and how I used this. Three particular categories of topics that aren't reflected in the breakdown are a) debug information, b) LLVM tools like llvm-readelf, llvm-objdump, yaml2obj etc, c) testing infrastructure, i.e. lit, FileCheck etc. 4) The timeline: "January 10-20 (sometime during these 2 weeks) - The LLVM mailing list archives are migrated to Discourse and it is sanity checked by volunteers of the LLVM community. This sanity check can take a week or more." and "We encourage all LLVM community members to start using Discourse on Jan 10th to minimize any disruption once the mailing lists become read only and the final messages are merged to Discourse" Given that this timeline starts today, and was only announced over the weekend (my time), there is zero opportunity for anybody to raise concerns or points, made worse by the fact that many community members might be off for a couple of weeks without any idea this is going on. This timeline should have been at a minimum 2-3 weeks after announcing it before it even begins. Again, contrast this with the recent bugzilla migration, where there were plenty of opportunities for others to raise feedback, and time to address them, before the migration even started. The 1st of February is the earliest any of this should have been starting, in my opinion, not the final cut-off! James On Sat, 8 Jan 2022 at 07:19, Tanya Lattner via llvm-dev < llvm-dev at lists.llvm.org> wrote:> LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists > and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work > together as a community to resolve any potential issues or help each other > navigate this change. I have put the migration to discourse guide that was > drafted by the Infrastructure Working Group in LLVM Docs, and encourage > people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know. > > Thanks, > Tanya > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20220110/8621009e/attachment.html>
Alex Bradbury via llvm-dev
2022-Jan-10 10:23 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
On Sat, 8 Jan 2022 at 07:19, Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:> > LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know.One quick question about the new categories/subcategories - where do you think it would be most appropriate to post issues of LLVM Weekly? Thanks, Alex
Hans Wennborg via llvm-dev
2022-Jan-10 15:58 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
On Sat, Jan 8, 2022 at 8:19 AM Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:> > LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know.My only real concern was this part of the blog post: "The mailman archives on the LLVM server may eventually be removed, but there is no final decision or deadline on this yet." I hope that doesn't happen, as it would break a lot of links into the archives, and I think preserving the history of the project is important. Since it would just be static content at that point, hopefully hosting it is worth the effort. - Hans
Johannes Doerfert via llvm-dev
2022-Jan-10 16:05 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
From the blog post: "Fully supported Email interface - Discourse supports the ability to interact through email if you do not like to use the web or app interfaces." From the Migration Guide: "*TODO:* Creating new topics via email is supported <https://meta.discourse.org/t/start-a-new-topic-via-email/62977> but not configured at the moment. We would need to set up an email address per category and give Discourse POP3 access to that email account. This sounds like a solvable issue." Seeing those two, which relate to the question I asked in June last year [0], I was wondering if this means I cannot actually stay with email if I ever want to start a thread/topic. Maybe the information above is outdated but as we are "moving now" it might be good to actually have that ability for the few of us that are not yet tired of email. Thanks, Johannes [0] https://llvm.discourse.group/t/discourse-as-mailing-list-replacement-some-questions/3713 On 1/8/22 01:19, Tanya Lattner via llvm-dev wrote:> LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know. > > Thanks, > Tanya > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
Kiran Chandramohan via llvm-dev
2022-Jan-11 09:28 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
Hello all, Having used discourse for interacting with the MLIR community, I find discourse useful and support this transition. I have a couple of points, 1. It is mentioned that the current mailing list contents will be moved to discourse. Is there a plan to match the mails of a person with their account in discourse (assuming the person already has posts in discourse and mails in the mailing list)? 2. The Flang project currently sits under Other Projects in discourse, can it be moved to a top-level project like Clang and MLIR in https://llvm.discourse.group/? 3. Thanks, Kiran ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> Sent: 08 January 2022 07:19 To: llvm-dev <llvm-dev at lists.llvm.org> Subject: [llvm-dev] LLVM Infrastructure Changes - Moving to Discourse LLVM Community, I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. https://llvm.org/docs/DiscourseMigrationGuide.html If you have any questions about the plan, please let me know. Thanks, Tanya _______________________________________________ LLVM Developers mailing list llvm-dev at lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20220111/61d52e13/attachment.html>
Alex Bradbury via llvm-dev
2022-Jan-12 12:32 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
On Sat, 8 Jan 2022 at 07:19, Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote:> > LLVM Community, > > I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know.I'm not sure if others have seen this issue, but I've enabled 'mailing list mode' and found all LLVM Discourse emails are being classified as spam by GMail. The emails passed SPF, DKIM and DMARC checks so it doesn't look like there's anything that can be done on Discourse's side. Just thought I'd flag it as an issue in case others were experiencing it. Best, Alex
Florian Weimer via llvm-dev
2022-Jan-15 21:38 UTC
[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse
* Tanya Lattner via llvm-dev:> I just posted a blog post about the upcoming changes to the mailing lists and LLVM Discourse forums: > https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/ > > I am sure some may be anxious about this change, but I hope we can work together as a community to resolve any potential issues or help each other navigate this change. I have put the migration to discourse guide that was drafted by the Infrastructure Working Group in LLVM Docs, and encourage people to add their tips and tricks to help others migrate over. > https://llvm.org/docs/DiscourseMigrationGuide.html > > If you have any questions about the plan, please let me know.Is it possible to cross-post to Discourse and to some other mailing list? I don't think so. We probably didn't use this functionality (posting to mailing lists across LLVM/non-LLVM projects) as much as we should have in the past, but I tried to reach out for a few things, and we had at least one nice success as a result. The projects I work on are not on Github, so that's no suitable tool for collaboration, either.