Launchpad Help > Blueprint
Blueprint is a lightweight way to manage releases of your software and to track the progress of features and ideas, from initial concept to implementation. Using Blueprint, you can encourage contributions from right across your project's community, while targeting the best ideas to future releases.
With very little administrative overhead, Blueprint helps you to create a roadmap for your project and shepherd individual features through to release.
To enable Blueprint for your project, follow the Change details link on your project overview page and select the This project uses Blueprint option.
What is a blueprint?
A blueprint is a simple specification. It describes an idea - such as a feature or process - and tracks enough metadata to show its implementation status and who's involved.
Let's take a look at what information makes up a blueprint:
Title and summary: some ideas are simple enough to express fully in the summary.
Link to further information: this can be any URL and is usually a wiki page where the idea or feature is fully explored. Launchpad doesn't provide a wiki facility.
People: who's working on this blueprint? You can optionally track the person drafting the blueprint, the assignee and the reviewer.
Drafting status: how well has this been discussed? Is it still just an idea or is it ready to code?
Related bugs: link to any bug reports tracked in Launchpad that will be fixed or otherwise affected by this feature.
Code branches: while you're working on the implementation, you can upload/register branches your code branches in Launchpad and link to them from the blueprint.
Subscribers: people can subscribe to receive email updates when the blueprint changes.
Dependencies: which other blueprints must be implemented before this one?
Launchpad Blueprint leaves you to manage your project in the way that you want. It imposes no project management structure but instead makes it easy for you, and your project's community, to suggest, develop and implement ideas and features.
People: roles and responsibilities
We saw above that there are certain roles associated with each blueprint. Anyone can take any of these roles and anyone can set who is in any of those roles for a particular blueprint. That makes it very easy for members of your community to suggest new features and track their progress for everyone else to see, without requiring special permission.
However, to allow projects to plan future releases, Launchpad restricts who can prioritise and target blueprints and bugs. As you'd expect, the project-group and project owner have these permissions but Launchpad also allows owners to grant them to other individuals and teams. They take role that, in effect, is a release manager and that Launchpad calls the "driver".
Drivers come in three flavours:
- project group
- project/distribution series.
Each driver's permission to target and prioritise trickles down the hierarchy, so, for example, project-group drivers also have driver permissions for each project within the group and each series in each of those projects.
As a project-group, project or distribution owner, you can set drivers by following the Appoint driver link on the relevant project-group, project, distribution or series overview page.
Launchpad Blueprint helps you to plan future release with two tools:
milestones: points in time, such as a future release or development sprint
series goals: a statement of intention to work on the blueprint for a particular series.
Although only drivers can target blueprints to milestones and set them as series goals, anyone can propose a blueprint as a series goal. As a driver or owner, you can review proposed goals by following the Set goals link on your project's Blueprint overview page.
Your project roadmap
As we saw earlier, you can tell Launchpad which other blueprints must be implemented before the blueprint you're working on.
Launchpad uses this information to recommend the order in which you might implement your project's blueprints. Take a look at the Ubuntu roadmap for an example.
Subscribing to blueprints
By following the Subscribe yourself link on a blueprint page, you can ask Launchpad to send you email notification of any changes to the blueprint. In most cases, you'll receive notification only of changes made to the blueprint itself in Launchpad and not to any further information, such as in an external wiki.
However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.
If you're a blueprint owner and want Launchpad to know about updates to the related wiki page, ask the wiki admin how to send email notifications. Notifications should go to email@example.com.
Many free software projects find that face to face meetings are a useful opportunity to make plans. They're also usually a great way to get to know your fellow project members.
Launchpad helps you plan development sprints by:
allowing you to register and publicise the meeting
- track who's attending and allow people to register their intention to attend
- mark specific blueprints for discussion at a meeting, thereby creating an agenda.
As a meeting organiser, you can download a file of all the attendees. When subscribing to a blueprint, individuals can request that they're listed as an attendee of any meeting at which that blueprint is discussed by selecting the Participation essential option.
Go see the current list of all sprints tracked in Launchpad.