Hi, I appreciate the discussion! Even if this doesn’t happen, I’m so grateful that the idea is taken seriously.
@codinghorror, here’s an example: if I didn’t follow meta, I might not know that the composer was about to change! That’s a big deal. For peace of mind, knowing that’s about to hit my community is important. I might want to announce it or be prepared to field questions - even simple ones like, “Why is this different?” Vs. getting a question from someone and saying, “oh, I hadn’t logged on yet, I didn’t realize they had changed that feature.”
Edit: Another nice feature - the Christmas hats theme! So much fun. That’s a “small” new feature, not official, but it is interesting and unique. Pushing that out to everyone, at least as a one sentence line of “something new in Discourse”, adds value by making it easier to realize what’s new and valuable about the product.
The “problem” is:
- Discourse is improving rapidly (from a baseline of awesome).
- Dozens of changes are considered each week in meta. Some of them jump from “we’ll think about it” to “pr-welcome” to “here you go” to “merged into core” quite fast. Or they are bugs that are fixed that change functionality or solve problems I (or a community member) might have had.
- The Discourse updates, as far as I can tell, are about Discourse’s core - but not the plugins. The plugins make Discourse even more awesome, and seem to be an integral part of the open source nature of the project. Right now they are kind of left to fend on their own? As a non-technical CM, that pushes those off the table for me, at least at this stage. If Discourse told me, “this plugin is now official” or “people are raving about this plugin, check it out” that would help.
In terms of the solution side:
- Discourse can win the game on technical merits. But it can also win the game on customer service. Double plus good.
- A single source of truth aligns everyone.
If you help us look awesome to our colleagues and our communities when talking about the upgrades to the product, we’ll be even happier than we are now. I’m saying, every week, I’d love to be more excited about what you’re doing.
It is also an opportunity to clarify what feedback is most valuable to the team. E.g., maybe poll customers on, “hey, in meta we’ve had requests for five possible development projects, what’s most important to you?” Or, “we’re actively testing these two features, please let us know if you want to weigh in on them and how that might affect your community.”