[llvm-dev] LLVM Infrastructure Changes - Moving to Discourse

Tanya Lattner via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 11 13:42:40 PST 2022



> On Jan 11, 2022, at 1:28 AM, Kiran Chandramohan <Kiran.Chandramohan at arm.com> wrote:
> 
> 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,
> 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)?
Good questions! Here is the plan from the Discourse migration team:

Users from the archive will first be imported as users based on their email, and then they will be merged into your current Discourse site also based on their email; their ID and all user fields from our existing Discourse site will prevail.

not mailman user,     Discourse user  --> use Discourse normally
    mailman user,     Discourse user  --> use Discourse normally; they'll see their old emails in their history as if they posted them through Discourse
    mailman user, not Discourse user  --> will have Discourse user records created along with their old email history; reset Discourse password to start using it
> 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/ <https://llvm.discourse.group/>? 

I think the general idea is to make something a top-level category when it has enough traffic and needs sub-categories itself. Flang can always be moved out from under Subprojects when it makes sense. We are trying to limit how many top-level categories we have to make things less visually cluttered. Maybe we can revisit this in a couple months when we see how things go with Flang where it is? 

Thanks,
Tanya

> Thanks,
> Kiran
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org <mailto:llvm-dev-bounces at lists.llvm.org>> on behalf of Tanya Lattner via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>>
> Sent: 08 January 2022 07:19
> To: llvm-dev <llvm-dev at lists.llvm.org <mailto: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/ <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 <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 <mailto:llvm-dev at lists.llvm.org>
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev <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/38d6e741/attachment.html>


More information about the llvm-dev mailing list