How does the Discourse project work?

[dontdieych (YCH)]

@downey

Actually many people here on meta are also contributors to Discourse, which is a collective work created not only by the small “core team” (for lack of a better term) of volunteers paid to work on Discourse, but also by the ideas, discussion, and code from hundreds (at least 215) of others of volunteers. While clearly some have contributed more than others, they are all co-creators and co-builders of Discourse.

I believe those 215 people’s contributions give more power to core team. Those contributions didn’t take power from them.

I’m afraid of you would accept ‘power’ as ‘dirty politics’. Please accept it as ‘trust’ and ‘believe’

All of us, Discourse user, especially 215 contributors are continuously giving them trust. So it would be quite rude if anyone saying “OK, you guys well done. But, from now on, you must show me exactly what is going on here. What is next plan? Give me briefing right now.”

@downey

Agreed that the listening is good here, but most large open source projects do not use (or at least try to avoid) a two-class system of contributors as it relates to communication and development. There are many more examples you might want to study.

I don’t believe there is two-class contributors. There is one development unit and others. Think Discourse team as one unit. Why? Because they build this thing as one unit at first. The unit is communicating with us quite well. I don’t think we should look at their every single brainstorming. If we do, we would be looks like …