In this mail I sum up the preparations for specifying features for Ubuntu Studio 14.10. Please don't discuss features in response to this mail, as I will follow up with a series of mails on feature specification planning per project, where we can iron out what to do this next cycle. Everyone is welcome to join in those discussions!
// For anyone interested in reading more about the development process of Ubuntu Studio, there's a a very incomplete documentation about that here: https://wiki.ubuntu.com/UbuntuStudio/DevelopmentCycle // # LAUNCHPAD BLUEPRINTS I've put together some blueprints here https://blueprints.launchpad.net/ubuntustudio/+spec/ubuntustudio-topic-u. Before we start filling each blueprint with work items, which are very much in an early drafting stage currently, I would like us to discuss the goals for each project separately - so, *please don't start editing blueprints just yet*. ## what are blueprints for? When we are done with specifying features for 14.10, the blueprints will be where we keep track of what needs to be done, and who is assigned to what task. Each blueprint belongs to a specific project in launchpad, and is to hold work items for that project (A work item is a hands on type of task, and can be coupled with a bug report). Some blueprints are topic blueprints, which depend on a set of other blueprints. The main ubuntustudio-topic-u is at the root of this dependency tree, mostly just to help keeping everything in one place.) Drafters for launchpad blueprints are commonly the launchpad group that acts as the driver for those projects, while the approver will always be the ubuntustudio-core team. On approving blueprints, please see below. # SPECIFICATION PLANNING FOR 14.10 I've put together a sum of things we've set out to do in the past here https://wiki.ubuntu.com/UbuntuStudio/UtopicUnicorn/WhiteBoardSpecs, which I will use as base for starting discussions on feature specs for different projects. Anyone may suggest new features, even new projects. I'm only taking up things I'm aware of, and frankly, things I remember to bring up - so don't be shy in suggesting new things or having opinions about anything. ..on how democracy in this very small community of developers works: * If there are differing opinions about anything, we discuss it within the community. * If a discussion doesn't settle it, the ubuntustudio-core team will decide which way to go. The ubuntustudio-core team will follow a Debian-like philosophy and also, try to implement as much upstream as possible. So: * If a feature suggestion is not specific to Ubuntu Studio, it should be implemented upstream - either in Ubuntu vanilla, Debian, or possible upstream application(s). * If a feature change/addition doesn't break or confuse anything else, there's no reason to disapprove it. * In the case where a feature addition/change WILL break something, and the community can't settle on one thing, ubuntustudio-core team will have to use their best judgment to find the best solution. /Kaj Ailomaa - Ubuntu Studio project leader -- ubuntu-studio-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
