planet miro and watching progress

, Will Kahn-Greene | share this (mastodon)
Note: This is an old post in a blog with a lot of posts over a long span of time. The world has changed, technologies have changed, and I've changed. It's likely this is out of date, the code doesn't work, the ideas haven't aged well, or the ideas were terrible to begin with. Let me know if you think this is something that needs updating.

I threw together a Planet using Venus for Miro-related blogs (and other feeds). Like other Miro-related sites, the configuration and templates are stored in SVN. It's currently set to update every 8 hours, but we can change that if need be.

The mission of these dev blogs and planet miro is to keep everyone in the loop on progress of Miro. Previously if you wanted to track progress, you could hang out on IRC (#miro-hackers on irc.freenode.net), follow the Trac timeline, and/or watch bugs change status in Bugzilla through searches. These methods are good, but they don't follow the progress of a person or groups of people, they're following the status changes of development artifacts--the two things aren't necessarily the same. When I started in July, I mentioned starting development blogs and a planet because I think this has been wildly successful for other projects, but then ... I never really got around to implementing the dream. Kudos to Dean for getting the devblogs set up!

As a side note, when putting together the planet, I skimmed the Miro Testing blog and I thought the entry from the 26th on how do we grow the community was both poignant and important. It's worth reading if you haven't already.

Updates:

9/29/2007: Upon Dean's request, I changed the frequency of planet miro updates to once an hour.

Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.