Objectives

In other languages: English (en) español (es) português do Brasil (pt-br) 中文（中国大陆） (zh-cn) Ελληνικά (el) [edit]

12-18 Month Community Objectives

The primary role of the Fedora Council is to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them. This section documents the medium-term targets we've highlighted (as explained in the Council charter).

Current

Fedora Editions, Phase 2

Summary: Take the initial Server/Workstation/Cloud split from Fedora 21 from an experiment into solid production. Increase autonomy from FESCo and improve targeted outreach.

Objective Lead: Stephen Gallagher

Timeframe: F22 and F23 releases, ending shortly after Flock 2015.

Details: Objectives/Fedora Editions, Phase 2

University Involvement Initiative

Summary: Increase Fedora's exposure in university environments, particularly engineering universities.

Objective Lead: Remy DeCausemaker

Timeframe: 2015-2016 academic year

Details: Objectives/University_Involvement_Initiative

Fedora Modularization (Requirements Phase)

Summary: Requirements-gathering from stakeholders for "Rings" aspect of Fedora.next

Objective Lead: Langdon White

Timeframe: F23 release - Flock; will be updated with subsequent phase

Details: Objectives/Fedora Modularization, Requirements Phase

About Fedora

Vision statement: Our vision.

Foundations: Our core values.

Overview: Our mission.

Objectives: Our specific objectives.

User base: Our users.

Ongoing Objectives

The following sections describe the overall objectives of the Fedora Project on an ongoing basis.

Note
This section is still valid, but is in the process of being updated as part of the new Fedora Council. See this blog post for background.

Creating a Free (as in Freedom) distribution

• Create a complete, general-purpose operating system built for and by a community. The operating system is an integrated set of software that addresses and balances needs of a wide variety of users and contributors.
• Build the operating system exclusively from free and open source software. Fedora is self-hosting and self-building, and requires no non-free software to create the distribution.
• Emphasize usability and a "just works" philosophy in default configurations and feature designs.
• Include a wide range of packages that fits into the various different needs of the users. This package set is limited, of course, to packages that Fedora can legally provide, and also subject to our packaging guidelines.
• Produce robust time-based releases every six months using a release model that allows the development team the flexibility it needs to ensure quality, while making sure that a release does not slip indefinitely. Our schedule may shift from time to time based on participant needs, but only after consideration and approval by the community governance entities that oversee the Project.
• Ensure that releases will always be available for free download in binary, source packages and as installable images.
• Provide timely updates for releases, throughout the supported lifetime of a release.

Building open source software communities

• The community includes current and potential or future contributors. Our outreach begins with our free distribution, and we constantly develop ways to give collaborators additional on-ramps for participation.
• Do as much of the development work as possible staying close to upstream projects. We promote upstream communities by collaborating on patches, providing the latest upstream versions for our development and testing branches wherever possible, and making sure upstream products work consistently and well in our stable releases.
• Be on the leading edge of free and open source technology, by adopting and helping to develop new features and version upgrades.
• Promote rapid adoption of new releases by allowing for easy upgrades, with minimal disturbances to configuration changes.
• Establish and implement technical standards for packages, ensuring the quality and consistency of the operating system.
• Promote a global perspective by supporting as many languages and geographic locales as possible.

Developing the science and practice of building communities

• Use existing models that work, (re)building on them only as needed in each case.
• Self-identify as a community of practice and keep a balance of domain, community, and practice in the Project.
• Promote a scientific approach to continuous learning through failure and advancement.
• Follow sound and scientific community principles that are derived from eons of humanity's lessons learned and relearned.

Objectives Outside of the Fedora Project

• The Fedora Project is not interested in a slow rate of change between releases, but rather to be innovative. We do not offer a long-term release cycle because it diverts attention away from innovation. For those community members who desire a long-term release cycle, there are derived distributions that satisfy this requirement. For community members who require a business-class support model beyond community maintenance, we recommend Red Hat Enterprise Linux. Our center of innovation and fastest rate of change is in our development branch.
• The Fedora Project is not interested in having its distribution be a platform for proprietary or patent encumbered components. While we do not purposely make installation of such components more difficult, we also do not allow our schedule or processes to be driven by theirs.
• The Fedora Project is not a dumping ground for unmaintained or poorly designed software. Sheer quantity of available software is not a measurement for the quality of a distribution. We do not include free and open source software that interferes with the Project's mission of advancing free and open source software.