[Bug 757543] [SUGGESTION] Add forums.gnome.org, using the awesome Discourse software.

["sysadmin" (GNOME Bugzilla) <bugzilla gnome org>]

Comment # 8 on bug 757543 from trusktr

* Could it replace mailman?
 It has reply-by-email
  https://meta.discourse.org/t/set-up-reply-via-email-support/14003/
  https://meta.discourse.org/t/new-reply-via-email-support/7764

* Can it do topics within a mailing list (commits-list uses this)?
 It has topics. I haven't tried reply-by-email yet though.

* Does it send out sane emails (plain text)?
 Haven't tried it yet. The default is HTML formatted. It can according to
  https://meta.discourse.org/t/plain-text-e-mail-notifications/13895/

* Could you review patches without it messing with the layout?
 Not sure what you mean.

* How does it deal with text that should be shown fixed width?
 The editor uses Markdown, so backticks for code, plus all the other stuff
Markdown offers. You'd write a C++ snippet like this:

 ```cpp
 int main(void) {
   return 0;
 }
 ```

* In the "mailing list" replacement, does it limit who can email?
 I haven't tried it yet. I'm gonna try enabling the mailing list feature for
http://forums.infamous.io

* Can you download an archive of the messages as "mbox"?
 No idea. Why would you need to do that?

* Can it handle threading?
 In what sense? On the server-side? I'm not sure how that's implemented. I just
know the app itself is really pleasant to use for archived discussion.

* Can it handle a 250+ threaded discussion with multiple people talking about
different items? It seems to fail in this.
 Oh, you mean discussion threading, not CPU threading. x] You mean like in the
screenshot that I've attached?

* How does it deal with changed subjects topic1 -> topic2 (was: topic1)
 It seems like when you rename a topic it just changes with no trace of what
the old name was, as far as I can tell from trying it just now. I'm not sure if
there's any setting around this.

* Can it show a proper overview of the thread?
 What's a proper over view?

---

      You are receiving this mail because:

• You are watching the QA Contact of the bug.
• You are watching the assignee of the bug.