User:Pfrields/Goals

= FPL Goals =

The goals for the Fedora Project Leader are varied and often overlap with the work of other Fedora functionaries such as the Fedora Engineering Manager, the Fedora Program Manager, and Community Architecture. As the face or voice of Fedora, the FPL is accountable for everything that happens in Fedora, but the FPL must have some measurable individual achievements besides simply participating in discussions or rubber-stamping ideas.

FY09/Q1 (and first 90 days)
Link here

Foster a broader audience for Fedora
This is not just boosting the number of users, since Fedora is about enabling contributors. It might mean creating new partnerships between Fedora and corporate entities that enhance our ability to drive the adoption of FOSS in places other than the user desktop.

Lower contributor barriers
It is too hard for collateral contributors to join Fedora, but the nature of the process requires some interaction with complex applications. Automating these processes makes Fedora more attractive for a larger number of contributors.

Clarify roles where needed to improve direction and performance of Fedora
It is not always clear where issues need to be decided in Fedora. The will of the community needs to be maintained, while minimizing the chances for initiatives to stall while waiting for an owner.

Develop key technical and management abilities
The FPL needs to maintain a level of skill and knowledge of Engineering department processes, platform capabilities, and leadership.

Continue personal contribution to Fedora
The FPL maintains a better community standing by participating in one or more parts of the Project as an equal contributor. Although this work should be secondary to achieving the broader project goals, it's important for the FPL to have context for decision-making and to understand contributor barriers.

The Rest of FY09
Link here