Alternative to adding a code.blender.org blog
This blueprint was created to see if the Launchpad Blueprint capability would be a good mechanism for tracking "small new features: that are being proposed for Blender. Blueprints would be an alternative to the proposed approach of creating a blog for that purpose. Blueprints are limited to a simple text description of a feature. This can be a good thing. The description is a succinct summary of the idea, not an elaborate plan for implementation. The blueprint includes a link to a URL (a wiki page is suggested) where the elaborate specification would reside. This blueprint points to Ton's email about starting a blog as an example. Blueprints provide a mechanism for classifying status of ideas, assigning the idea to an the person responsible for the implementation. The status tag allow easy sorting of ideas.
Blueprint information
Whiteboard
The whiteboard provides a mechanism for comments to be made about the idea.
It has limitations. Only one comment message is available and anyone with write permission can erase the comments.
The blueprints cannot be deleted, but when they are marked as "Obsolete" they are hidden from the list of blueprints.
I assigned this blueprint to Kevin Roy just to demonstrate how assignment are made. He is a member of the blender-committer team on launchpad. Membership of this team could be restricted to only launchpad members with Blender svn-write access.
The blueprint design isn't laid out like the blog described by Ton. A sidebar with the latest commits isn't included, but the latest commits can be viewed by clicking on the "Code" link at the top of the page. The "Bugs" button is lined to the Blender bug tracker. (Which would be a great replacement for the current Blender bug tracker.)
