What should we build? #1
Description
A lot of us are becoming alarmed at the quality of posts, projects and resources popping up in the AngularJS community. The bottom line is the core team is too swamped to push 'Best Practices' or moderate anymore, and there is no officially documented best practices. It would be nice if there was a way to ensure / improve the quality of posts and projects that arise in the community through a centralized system.
Ideas that have been discussed:
- An official blog
- An official newsletter / internet magazine
- Pro reviewed-quality control
- A directory
- A voting and feedback system (StackOverflow-esque)
- A submission-for-review service
- Democratically run project (no 'you write for me' or 'i write for you' ownership)
Mix and match. We wouldn't want to discourage bloggers, and we know some of the best devs don't have the time to go to each blog and provide feedback (or blog themself).
CakePHP has the 'Bakery' service (although it lacks voting)
I personally have been actively working to provide a 'Best Practices' repository in the AngularJS wiki (instead of blogging) and the new book by @pkozlowski-opensource and @petebacondarwin is probably the closest thing we have now.