The goal of this BOF is to brainstorm about Debian: What are the big challenges for our future? What should we focus on? What should Debian be in 10 years?
People allergic to SWOT analysis are welcomed, but should ensure they took proper medication as there's a high risk of being exposed. (see https://en.wikipedia.org/wiki/SWOT_analysis )
Quick review of DebConf16 organization. The goal is to be able to quickly identify what went good/bad, what was a good/bad idea... and how this could help DebConf17 team.
How to help DebConf17 team to get started?
- What are the first steps?
- Who's interested to help?
With Debian LTS, we are now offering something that users expected for a long time and we are keeping users that we lost to Ubuntu in the past. Debian LTS would not exist without the work of paid contributors and the financial support of its sponsors.
Can we learn what we got right in Debian LTS and try to see how we could use money to improve other parts of Debian? In this BoF, we will make some propositions and expect the audience to react to them, highlighting what is good and what is problematic, making suggestions on how to fix/improve the propositions. The Debian Project Leader is a central role in the way Debian spends his money. He will thus take an active role in this discussion.
The project used to have Release Goals which, to some extent, defined global goals for the project. Such goals were proposed at the beginning of a release cycle and decided by the Release Team. The RT later stated  that "whilst release goals have been useful in the past to introduce archive-wide changes, [RT] should review whether this remains the case and whether the release team is really the right place to determine them."
Still, Debian members need to produce a list of common goals and projects. Those goals should not necessarily bound to a release. The roadmap will greatly help us to promote our vision and priorities.
State of the project, ongoing activities and planned changes