First of all, I don't know how Discourse works, but from what I saw on the 
online demo it looked like a forum. Therefore, our main use case would be as a 
place to ask/deposit questions.
I believe that having a mailing list pushing mails down our throats compels 
people to answer: "Oh, I know the answer for that one". I don't imagine people 
going out of their ways to go to a website/forum and search for questions they 
can answer. I have been actively checking StackOverflow's gem5 questions for 
the past year or so, and I can tell you there is close to null community 
engagement - it is basically Ciro - on the answering department.
That being said, the mailing list is indeed harder to work with, and 
StackOverflow is not a forum, so we could have a try at a forum-like approach 
and see how things go.

   Em quarta-feira, 10 de junho de 2020 00:41:20 GMT+2, Jason Lowe-Power via 
gem5-dev <> escreveu:  
 +1 for Discourse :).

Just to give a bit more context: I'm also trying to find a good forum for
community engagement during my online Learning gem5 class this summer. I
would like to find a platform that could be used generally for my class
this summer, future iterations of the class, and general gem5 questions, as
I believe there will be significant overlap between these groups.

Other potential options that IMO have more cons than pros when compared to
- Slack/Teams/etc.
- stackoverflow

That said, we're open to suggestions :). Our goal is to create the most
welcoming and inclusive environment possible. We'll go where our users are!


On Tue, Jun 9, 2020 at 2:45 PM Bobby Bruce via gem5-dev <>

> Dear all,
> In an effort to better support the gem5 community, there has been a
> suggestion that we drop the gem5-users mailing list and replace it with
> Discourse,, a web-based discussion
> platform. I'm writing this email to propose this to the community and ask
> for feedback on the matter.
> We have noticed that using mailing lists as our primary communication
> platform is problematic. Sending an email to a list can be daunting
> experience, requiring an etiquette many are not accustom to. I'm sure I'm
> not the only one who feels like they are unduly bothering a large number of
> people when posting to a list (like I'm doing right now :) ). This is, of
> course, an unfortunate hurdle for many to get over when they encounter
> problems using gem5, particularly those new to the project. I've come to
> believe mailing lists are simply not a very good technology for fostering
> community engagement and helping those who are running into difficulties.
> Mailing lists are also difficult to search, and lack proper formatting
> mechanisms to neatly display attributes such as code and output logs.
> Looking around at alternative technologies available, Discourse appears to
> be a suitable replacement. For those unaware, Discourse is (essentially) a
> revamp of messaging forums. It is an increasingly popular platform for
> users and developers in open source projects to communicate with one
> another (see LLVM's discourse as an example:
> ).
> All-in-all, I think it's a well-designed product and contains all the
> features we'd expect and need to get our work done. I can see no immediate
> downsides to using it, though feedback from the community on the matter
> would be greatly appreciated, particularly from those who have used
> Discourse before. Dissenting opinions on the whole idea of moving away from
> the gem5-user's mailing list are also welcome.
> So, let me know what you think! :)
> Please note, regardless as to any decision made, we will continue the use
> of the gem5-dev mailing list for technical discussions for the foreseeable
> future.
> Kind regards,
> Bobby
> --
> Dr. Bobby R. Bruce
> Room 2235,
> Kemper Hall, UC Davis
> Davis,
> CA, 95616
> web:
> _______________________________________________
> gem5-dev mailing list --
> To unsubscribe send an email to
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
gem5-dev mailing list --
To unsubscribe send an email to
gem5-dev mailing list --
To unsubscribe send an email to

Reply via email to