UDS Intrepid Community Report

[:UDS-Intrepid/Report:back to the reports index page]

Plans for 8.10

Place in this section bullet points of specific intended outcomes for the 8.10 development cycle.

• Outcome
• Outcome

Sessions

Brainstorm and UDS

• Next UDS have tagging support in brainstorm.
• Tag all current ideas as 8.10 ideas. Always tag version numbers, over animal names.
• Shortly before UDS scheduling, encourage the community to re-tag existing ideas or add new ideas to Brainstorm.
• Gather developer feedback for the top 50 brainstorm ideas. Use this feedback to assess ideas for UDS scheduling.

Gobby doc: community-brainstorm Spec: foo

Ubuntu $(language) Development Teams

• There will be best-practise documentation on how to drive Ubuntu $(language) Teams.
• The aim is to help people who are interested in development but don't speak English very well slowly get involved into the general Ubuntu development world.
• The most important goal is to make sure that every discussion, every fix and every item that is worked on lands in Ubuntu itself.
• Translation, localised Documentation and liaison with ubuntu-dev are efforts that those teams concentrate on.

Gobby doc: community-ubuntu-(lang)-dev

Universe QA

• The developers will revisit the [:Bugs/Importance:use of the "Critical" bug importance] together with the BugSquad to make it possible to indicate broken packages in Universe easier.

• They will also revisit their policy about removing Universe packages from the archive if they don't meet quality requirements. There was a general agreement that this possibility is not used enough.
• Ideas on how to programmatically find out if a package is "in a bad state" where discussed.
• A collation of "opportunities" is necessary and ideas for input into were discussed.
• We need a howto on how to get patches from other distributions.
• More Universe Bug Days should happen.
• Another session is going to happen this week.

Gobby doc: community-universe-qa