A week ago we shipped the new version of drumbeat.org. This was a ground up rewrite and represents a significant change in the direction of the site. Before I go into too many details, or start talking about what’s next, I want to thank everyone who has committed code to the project so far:
- Jaco Joubert - Design
- Ned Schwartz - Front end hacking
- Brian Brennan - Initial markup and css cutup, front end rescue operative
- Cillian O'Ruanaidh - Tester, Django hacker
- Guillermo Movia - Markup and css for those welcome and error messages.
So, What's New?
When we decided to rewrite drumbeat.org in Django, we also decided to revisit our goals for the site. The old site tried to do a lot of things and we’d prefer to do fewer things and do them well. We decided that drumbeat.org is a social web application that should allow a user to link to content all over the web and have their activities (blog posts, wiki edits, github commits) aggregated in one place. With that in mind, we built the new drumbeat.org. There’s a lot of refining to do, but that’s the essence of the new site: find people and projects to follow, create projects, and aggregate activity relevant to your project.
What about my blog posts / pictures / text?
Most data, including user accounts and projects was automatically migrated over. You should even be able to log in with your old password. Some things however, like blog posts, don’t exist on the new site. The old site will be available at old.drumbeat.org until March 15th, 2011. You’ll be able to salvage whatever content you may have on the site before then.
Getting to a point where we were comfortable shipping was the first step. We’ll now be shipping updates as often as we can. See the (constantly in progress) Roadmap for an idea of what we’d like to do over the next couple of quarters. We’re also hiring a full-time front-end dev which will double the number of full-time technical staff we have dedicated to drumbeat.org. As such, I’m planning to start having weekly planning calls that will be open to the community. One week will be dedicated to planning an iteration (deciding on what bugs / features to tackle for a specific iteration) and the next one will serve as a status check-in. 2011 is going to be an exciting time for drumbeat.org. I’m so glad to be out of the building phase and into the shipping phase.
This is really great, but what it's really missing is _____.
I love feedback and I love ideas about what would be useful for drumbeat.org. If you have some feature that you feel is absolutely essential, there are a few things you can do:
- Check the Roadmap. If it's already there, we're planning to add it.
- Check Bugzilla. It's possible someone has already thought of this and decided to file a bug on it.
- Bring it up on the mailing list. This is a good chance to see if other people share your passion for the feature you're thinking of.
- File a bug. If you feel like it's worth lobbying for, file a bug requesting the feature.
It’s important to note that simply requesting a feature will not make it so. It’s entirely possible that a particular feature does not align with the goals of the project and will therefore not be implemented.
I found a bug
Fantastic. This is extremely helpful. If you feel you’ve found a bug, the process is similar to above, only shorter!
- Check Bugzilla. It's possible someone has already filed a bug about the issue you've encountered. If they have, feel free to comment on the bug.
- File a bug. Include a description of what you were doing, as well as steps to reproduce (if possible).
That’s it! Filing bugs is a great way to help the project.