I set up this Discourse forum today as a test: does this work well for communication and cooperation among Trustroots volunteers?

We’ve been on Slack since 2015, and it’s quite good for exchanging messages quickly and joking around. Slack is less useful when there’s no daily activity. It’s also not so good at building organisational memory (we can’t even search beyond 10k messages without paying, and we currently don’t have money to spend on this).

The advantages of Discourse:

  • makes it easier to build something more concrete, e.g. posts can become wiki pages
  • it’s probably easier to get an overview, e.g. we can have boards matching teams. Once we have teams. But Discourse may help building actual teams.
  • it’s free software

The disadvantage is that it’s one more thing to maintain and back up. Let’s see how useful and active this forum can become.

One more point: this forum is the meta trustroots forum, it’s not the Trustroots forum. At this point we don’t want it to be used for e.g. organizing events in your town. But on this forum we can figure out what’s the minimum viable forum that we can launch on Trustroots and coordinate efforts to make it happen sooner rather than later.

Happy to read your thoughts.


So if I get the point right we want forums to be as inclusive as possible for community members to enter in development of trustroots. There’s always space for higher level talk and lower level entry than what github issues or slack currently provides.

One thing that comes straight into mind how to make it easier for users to participate is possibilty to log in with trustroots account. Discourse seems to be providing possibility for SSO(single sign on). Ain’t sure does it require some extra work to implement(nonce, external_id?), but looking the bright side, the same trustroots account could also be with existing wikis to lower entry for editing.

To really kick meta going on we should probably add at least hyperlink to and perhaps contruct participate page to join in development without knowing what the heck is API.