“In the Lucid cycle I was keen to track work on this set of
projects in a more effective way. To do this the process worked a
little like this:“1. We first had a series of discussions at both UDS and online
in which we discuss each project, what is involved and what targets
and goals are in scope for the Lucid cycle. Targets beyond the
Lucid cycle were explicitly deferred until the 10.10 cycle.“2. The conclusions generated from these discussions were first
documented as a Roadmap on the Ubuntu wiki. This provides a
high-level set of goals that the project is striving for.“3. We then produced a Blueprint for each project and a set of
actions that are assigned to people. The blueprint is what we use
to track progress on the project. The actions are stored in the
whiteboard on the blueprint (which anyone can edit) and anyone can
subscribe to the blueprint, which makes it great for keeping on
track projects even if you are not involved in them.”
LinuxToday is a trusted, contributor-driven news resource supporting all types of Linux users. Our thriving international community engages with us through social media and frequent content contributions aimed at solving problems ranging from personal computing to enterprise-level IT operations. LinuxToday serves as a home for a community that struggles to find comparable information elsewhere on the web.
Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved
Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.