ManagingBlueprints
622
Comment:
|
2883
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
* Creating a topic (done by a Ubuntu Developer) * Creating blueprints (done by the Ubuntu Studio developer in charge of blueprints) * Creating workitems (done by any Ubuntu Studio developer) * Managing workitems (DONE, POSTPONED, etc) |
<<Include(UbuntuStudio/Navigation/Header)>> <<Include(UbuntuStudio/Navigation/CoreSideBar)>> |
Line 6: | Line 4: |
== Managing Workitems == | <<TableOfContents>> |
Line 8: | Line 6: |
View every workitem as a suggestion? View each change to the source as reversable? How to process each workitem (suggestion): |
= Registering a blueprint for a Ubuntu Studio project = |
Line 11: | Line 8: |
* Create a workitem, based on a bug or a feature request * Research the effects of implementing the work item, and publish on mail list * If there are no objections, or improvements to the work item, implement it |
A blueprint could be for anything, but it always needs to be registered within a project of some sort. Things to keep in mind before registering: * Register the blueprint within the project it is for. For example, blueprints for [[https://launchpad.net/linux-lowlatency|linux-lowlatency]] go [[https://blueprints.launchpad.net/linux-lowlatency|here]] * Is it going to be targeted for a specific release of [[https://launchpad.net/ubuntustudio|Ubuntu Studio]]? If yes, Add it as a dependency to the correct topic blueprint in the [[https://blueprints.launchpad.net/ubuntustudio|ubuntustudio launchpad project]]. See the [[UbuntuStudio/ManagingBlueprints#Dependency_structure_for_Ubuntu_Studio_topics|next section]] about the dependency structure for Ubuntu Studio topics. = Dependency structure for Ubuntu Studio topics = '''Example of a release targeted blueprints tree for Ubuntu Studio 14.04:''' https://blueprints.launchpad.net/ubuntustudio/+spec/topic-ubuntustudio-flavor-t Structure for the [[https://blueprints.launchpad.net/ubuntustudio|ubuntustudio project blueprint]] topics * '''ubuntustudio-?''' (main topic) * '''core-?''' (subtopic) * '''applications-?''' (subtopic) * '''art-?''' (subtopic) * '''documentation-?''' (subtopic) * '''website-social-?''' (subtopic) Each subtopic will have dependencies to blueprints from other Ubuntu Studio projects. Next is a table that shows the structure of those dependencies: || '''Subtopic name''' || '''Dependecy LP Projects''' || || core-? || [[https://launchpad.net/linux-lowlatency|linux-lowlatency]], [[https://launchpad.net/linux-rt|linux-rt]], [[https://launchpad.net/ubuntustudio-meta|ubuntustudio-meta]], [[https://launchpad.net/ubuntustudio-default-settings|ubuntustudio-default-settings]], [[https://launchpad.net/ubuntustudio-live|ubuntustudio-live]] || || applications-? || [[https://launchpad.net/ubuntustudio-controls|ubuntustudio-controls]], [[https://launchpad.net/ubuntustudio-menu|ubuntustudio-menu]], [[https://launchpad.net/ubuntustudio-installer|ubuntustudio-installer]] || || art-? || [[https://launchpad.net/ubuntustudio-icon-theme|ubuntustudio-icon-theme]], [[https://launchpad.net/ubuntustudio-look|ubuntustudio-look]], [[https://launchpad.net/ubuntustudio-lightdm-theme|ubuntustudio-lightdm-theme]], [[https://launchpad.net/usplash-theme-ubuntustudio|usplash-theme-ubuntustudio]] || || documentation-? || -- || || website-social-? || [[https://launchpad.net/ubuntustudio-website|ubuntustudio-website]] || ---- [[UbuntuStudio/BlueprintsTemplate|Release Blueprints Template]] - used when planning for next release ---- CategoryUbuntuStudioPlanning CategoryUbuntuStudio |
Contents
Registering a blueprint for a Ubuntu Studio project
A blueprint could be for anything, but it always needs to be registered within a project of some sort.
Things to keep in mind before registering:
Register the blueprint within the project it is for. For example, blueprints for linux-lowlatency go here
Is it going to be targeted for a specific release of Ubuntu Studio? If yes, Add it as a dependency to the correct topic blueprint in the ubuntustudio launchpad project. See the next section about the dependency structure for Ubuntu Studio topics.
Dependency structure for Ubuntu Studio topics
Example of a release targeted blueprints tree for Ubuntu Studio 14.04: https://blueprints.launchpad.net/ubuntustudio/+spec/topic-ubuntustudio-flavor-t
Structure for the ubuntustudio project blueprint topics
ubuntustudio-? (main topic)
core-? (subtopic)
applications-? (subtopic)
art-? (subtopic)
documentation-? (subtopic)
website-social-? (subtopic)
Each subtopic will have dependencies to blueprints from other Ubuntu Studio projects. Next is a table that shows the structure of those dependencies:
Subtopic name |
Dependecy LP Projects |
core-? |
linux-lowlatency, linux-rt, ubuntustudio-meta, ubuntustudio-default-settings, ubuntustudio-live |
applications-? |
ubuntustudio-controls, ubuntustudio-menu, ubuntustudio-installer |
art-? |
ubuntustudio-icon-theme, ubuntustudio-look, ubuntustudio-lightdm-theme, usplash-theme-ubuntustudio |
documentation-? |
-- |
website-social-? |
Release Blueprints Template - used when planning for next release
UbuntuStudio/ManagingBlueprints (last edited 2015-04-26 16:27:35 by h-141-65)