[Debian-roadmap] Roadmap -- kick-off

[Mehdi Dogguy]

Hi all,

I apologize for not starting this discussion earlier. I hope you are still
interested by this project and motivated to help putting this in place.

You are receiving this mail today because you have showed an interest in
helping to build a project roadmap. The goal of this thread is to discuss
the way we should follow to get this started and agree on the goals behind
the idea of a roadmap for Debian.

First, please make sure you are subscribed to:
     debian-roadmap at lists.alioth.debian.org
     https://lists.alioth.debian.org/mailman/listinfo/debian-roadmap

1) Context

Our distribution is the main product delivered by our project to the world. I
tend to believe that we don’t only package upstream projects and publish new
releases. Debian offers more than that and has its added value. Release Goals
were one way to show how our distribution is original, relevant and innovating.
Even on a social level, it is important to set some goals in order to continue
to motivate prospective contributors into joining Debian. We, as the Debian
community, should work to publish and maintain a roadmap, and strive to
implement it each cycle. It is not necessary to have it done in time for a
release, but it is more important to follow its progress.

The roadmap we are looking to put in place is not a tool to decide on projects
volunteers will work on. Its main purpose is to document significant changes in
the project and give them more visibility.

A discussion took place with Debian Technical Committee (See #830344). They
discussed how should the TC help with a project roadmap. Even if the TC declined
to manage the roadmap, I believe the thread is an interesting read about the
subject.

2) Roadmap BoF

You can find here the minutes of the meeting held during DebConf16:

   https://gobby.debian.org/export/debconf16/bof/roadmap

For reference, you can also find my slides about the roadmap here:

   https://annex.debconf.org/debconf-share/debconf16/slides/51-bits-from-the-dpl.pdf

3) Quick summary

Below a quick summary of ideas already mentioned and questions still open.
We can use it as an agenda. If you have in mind important questions about
the project and/or the process, do not hesitate

- 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.

  Having consensual goals and proposed by project members also avoids the
  need to make the project vote for project goals like a GR.

  I think this specific item is clear enough. Any further comments? or
  should we consider it approved?

- The DEP process /could/ be the process to manage the roadmap, but it
  is up to this team to decide. It could be left to specific goals which
  match with the spirit of DEPs and not enforce it for each goal.

  Previously, Release Goals used to be maintained on the wiki. The process
  is documented on https://wiki.debian.org/ReleaseGoals/

  I think that the question about the tool should be clarified early
  enough.

  Any ideas? I think that both options are valid but the decision is
  up to the team.

- The roadmap is not a tool to tell people what to work on, but rather
  a tool to help attracting more visibility on their work. If a goal
  has been declined to be part of the roadmap, it doesn't mean that it
  should be stopped, but it has not been judged sufficiently significant
  to be shown in the roadmap.

- The roadmap team could have the following role:

  * 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

  I think it is important to discuss the team's role right now, but the
  actual delegation text (if needed) can wait until we have identified
  a concrete plan for the roadmap.

  For now, do you have any comments on the above listed tasks?

- Publicity period and communication workflow: When should we communicate
  about the roadmap? How should we make a call for ideas? etc...

- AOB?

Regards,

-- 
Mehdi