1. What are the top 3 issues facing Gentoo?

  a.
  b.
  c.

Developer friction: 10
Communication among devs: 8
Poisonous people: 6
Communication with users: 5
Culture: 4
Lack of follow-through: 4
Developer turnover: 2
Lack of unity in dev community: 2
Lack of discipline: 2
Lack of meritocracy: 1
Lack of respect: 1
Taking stuff personally: 1
Being overly emotional: 1
Elitism of devs: 1
Communication with derivatives, enterprises, etc: 1
User participation: 1

Low number of devs: 14
Goals (distro-wide): 11
Leadership (distro-wide): 8
"Unpopular" teams understaffed: 6
Lack of training/educated devs: 3
High barrier to entry: 3
Succession planning: 2
Too much work by too few: 1
More people doing distro-wide projects: 1
Leadership/goals (teams): 1
Too much worrying about management stuff like goals, audience, etc.: 1

Publicity: 12
Perception: 4
Tell people where the value is in using Gentoo: 1
People who run gentoo "because it is cool": 1
Website update: 1

Portage/Ebuilds limit developers (slow innovation): 6
Release frequency low: 3
No sense of exciting innovations: 3
Lack of innovation: 2

USE dependencies: 3
New EAPIs, PMS: 2
New SCM: 2
Portage's long-term viability: 2
Tree complexity: 2

Compile farm: 2
Dev docs/QA hard: 2
New bug tracker: 1
Project management tools: 1
Overly possessive maintainers: 1
Stability: 1
Binpkgs: 1
No orphaned packages: 1
Docs: 1
QA: 1

Foundation: 3
Non-ebuild parts of Gentoo need more attention (pr, docs, etc): 1
Non-technical parts waste time (foundation, CoC/proctors): 2


2. Who is Gentoo's audience (target user)?

3. Why do you work on Gentoo?

4. What are Gentoo's goals?

5. What is Gentoo doing to reach them?

6. What are your personal or team goals? (pick personal/team and say which)

7. What are you doing to reach them?

8. How do Gentoo's goals overlap with your personal goals or team goals?

9. What should Gentoo change? (New projects, new directions, etc.)