1. Tasks for the delegated team - Reviewing the proposals and ensuring a coherency - Deciding the content of the roadmap (using proposals made by project members) - Periodical review of the roadmap (content, status and progress) - Helping people with ideas to get in touch with the correct persons to turn the idea into a real project that can go on the roadmap Severity of bugs opened for project goals are raised to "important", when they are *not* RC (Only the Release Team decides on RCness of a bug). -> Not really important anymore since the NMU policy is quite liberal and a 15 days delay is quite acceptable. Another possible "bonus" for roadmap items could be faster NEW processing (But new is currently *very* fast! should we have a roadmap entry about keeping it that way? :-)) +1 ;-) (problem is what you said before: somebody need to dedicate time for it) [madduck] In general there seems to be consensus that it's not useful to define goals before there is some work done, or goals for which nobody already feels responsible. Instead, foster roadmap projects/DEPs whatever to be actively worked on and then select those with progress and momentum for inclusion in a release. 2. Which Team? a "let me help you to do what you want" team. - OdyX - buxy - lucas - pabs - moray - realist - madduck - kate - johns - paulproteus - ana 3. Ideas for the roadmap - See https://wiki.debian.org/ReleaseGoals/ about the old process and proposed release goals up to Jessie - a project goal should be: * SMART (Specific, measurable, assignable, realistic, timely) * Have an 'advocate', who can track and keep status of progress. * Be generally consensual Non consensual goals should be debated by developers until a rough consensus is reached or decided by the team in charge of the roadmap - in various areas: ?? TC in the constitution: - §6.1.2 Decide any technical matter where Developers' jurisdictions overlap. - §6.1.3 Make a decision when asked to do so. - §6.1.5 Offer advice. - §6.2.7 Membership is limited in time, by constitution 4. Questions - Overlap with DEP process? Could be the same process. No management of DEPs. No measurement of DEPs. Focussed on technical side. Not obvious to show what are the current things. Could be the way to implement the roadmap. - Delegation needed? - Decide the content of the roadmap - Overlap with other delegations - Voting on goals? like a GR - Release goals - define goal with deadline doesn't work - DEPs with owners and drivers - Telling people what to work on? - Publicity period?