4 ms·
Interestingly, as an early users of the software, I got mostly the exact opposite feeling. Build it for a real community and try to make it work within that co
by wycats 14y ago
Interestingly, as an early users of the software, I got mostly the exact opposite feeling.
Build it for a real community and try to make it work within that community
Ember used Discourse for the past several months. We provided a ton of feedback and I like to think that our participation served exactly this purpose: building Discourse for a real community.
Make it possible to close threads, write summary for threads, group threads together, explore a topic
I'm not sure how much of this comes across in the pitch, but these specific goals are focuses of the software. For example, Discourse supports a "Best of Thread" view (see https://github.com/discourse/core/blob/master/app/models/post.rb#L163 https://github.com/discourse/core/blob/master/app/models/pos... and https://github.com/discourse/core/blob/master/lib/score_calculator.rb https://github.com/discourse/core/blob/master/lib/score_calc...), which is currently only triggered on a very high threshold. I like this feature a lot. You could easily imagine it being possible for moderators to hand-curate the "Best of" view in the future.
There is also an "aggregated links" view that aggregates all of the outbound links from a thread and shows how many times they have been clicked on.
Discourse has moderator tools for "closing" threads. I would expect that closed threads would work well together with the "Best of" view.
Bring more structure than linear comments, but less complexity than threaded comments.
I think this is one of the team's highest priorities. There is some innovation in the way replies work, but it's also possible to "reply as a new thread", with margin links between the threads. I have found this to be a very good compromise, and something that explicitly attempts to tackle your desire here.
In short, I think there's more depth here than you're seeing at first glance, and the things you want to see from Discourse are things the team is actively thinking about.
- eranation 14y agoFollowing yesterday's discussion on Ember.js / AngularJS (http://news.ycombinator.com/item?id=5168803 http://news.ycombinator.com/item?id=5168803) I think this is one more item in the "why to give Ember a try" side (Just for the mere fact that SE chose it over other alternatives, used it and open sourced it, and had you somehow involved I assume). Were you consulting them on Ember development aspects? Were you involved in the development somehow? do they use version 1.0?
- wycats 14y agoWere you consulting them on Ember development aspects? We worked with Robin and Sam as community members over the past few months as they worked on Discourse. Frankly, they're both rock stars, and managed the entire project with surprisingly little direction from us. Were you involved in the development somehow? I think the largest extent of direct code collaboration between the Ember team and Discourse was Erik Bryn's work on the `group` helper. Other than that, they asked us questions from time to time and we answered them. do they use version 1.0? Yes! I was insanely impressed by Robin's ability to get the (rather large) Discourse codebase ported over to Ember 1.0 pre4 within days of us shipping it. As has been mentioned on other threads, there has been a bunch of churn in the run-up to 1.0, and Robin took it like a champ. The code is largely idiomatic Ember 1.0 code, and reads well to me.