How does the Discourse project work?

[mcwumbly (Dave McClure)]

I have taken the liberty to consolidate some quotes from various threads I’ve seen over the past few days that seem to fall under this general topic.

Overall I’ve been happy with the community and the process to date.

Jeff’s post above is so far the answer worth referencing with regards to the current modus operandi.

However, it does seem like the community is starting to go through some post-v1.0 growing pains for a little while as new people join the community as users, participants on meta and contributors.

I think some people are now airing frustrations they were holding back in the run up to the release.

@haiku

The process is harder and more frustrating than it needs to be due to no clear demarcation between “Team stuff” and “everyone else stuff”.

@erlend_sh

The big questions on my mind are:

Where is my input most wanted right now?
What features are likely to arrive in the next, or the following, stable release?

@mcwumbly

I think it’d be good to follow up each release with a short post that combines the release notes (or a link to them) with what your asking for here in some loose form:

1. Here’s what we shipped in this release
2. Here’s what’s on the top of our list now
3. Here’s where help or input from the community is most wanted

@blake

When archiving a topic on Meta for closing out a bug/feature I think it would be helpful if we linked to the actual commit message on GitHub.

@cpradio

As an aside, this is the sort of stuff I had hoped would quit happening after hitting 1.0. You are stable now, making UI changes out of the blue seems dangerous, especially when unannounced, no discussion, what-so-ever.

@BhaelOchon

I don’t think the team need to stop making changes by any means, but the changes that are made should be well-considered and deliberate and purposeful.

It’s certainly worth considering how the process can evolve and be more explicitly communicated going forward, but this is a process in of itself.