Normativa Lectora

Esta normativa lectora representa la manera de que el Fedora Council le gustaría que su misión del Proyecto se convierta en una realidad.

La Visión del Proyecto de Fedora es:

El Proyecto Fedora visualiza un mundo donde cada uno se beneficia desde el software libre y abierto creado por comunidades inclusivas, bienvenidas y pensamiento abierto.

Para llevar a cabo esto, nuestra Misión es:

Fedora crea una plataforma innovadora para hardware, clouds, y contenedores que permite desarrollo de software y miembros de comunidades construyan soluciones a medida para sus usuarios.

Hacemos esto con el contexto de Cuatro Fundamentos: Libertad, Amistad, Características y Primero.

Contexto

The Fedora Council identifies the short-, medium-, and long-term goals necessary to keep the Project on the leading edge of technology. The Fedora.next initiative focused the outputs of the project around use cases. In 2017, we updated the mission statement to reflect changes in the computing landscape. Today, it is too difficult to build new solutions in Fedora.

Nuestra Cercanía

We will make it easy for the community to build solutions, address specific developer problems, and meet their end users’ specific needs. We will do this by encouraging and helping Objectives which make the necessary changes required to ease the process. This accelerates the transformation of Fedora into a community that enables the construction of solutions.

Internamente, Fedora se centra en realizar estas soluciones para que sean llevadas a cabo. Las salidas de Fedora son las Soluciones de nuestros miembros de la comunidad creados. Nuestro enfoque en actividad permite experimentación sin juzgar anterior o control de acceso.

¿Que significa esto?

Teams such as Design, Documentation, Packagers, Release Engineering, and Quality Assurance provide building blocks and offer services to other community members and Teams. Services and building blocks include the following:

  • Infraestructura IC

  • Asesoramiento y orientación para la construcción de comunidades

  • Financiación de eventos

  • Servicios de logotipo

  • RPM u otros paquetes de software

  • Botín

  • Pruebas y validación

  • Asistencia de usuario

  • Diseño XU

Anyone may use building blocks like software packages and artwork to create a Solution. Example solutions include: Fedora Workstation, KDE Plasma, and the Python Classroom Lab. Teams define criteria for services they provide to solution-builders. For example, teams providing press and promotional support may choose to provide additional support to Solutions with larger user bases.

Teams are free to define elements of their Solutions, such as intent, deliverables, and release cadence. Teams can build Solutions from any building block and pick and choose what tools they use. Based on their choices, they get different levels of ability to use the Fedora trademark (i.e. “Fedora Remix” vs “Powered by” vs “Fedora”). Some solutions are the premier showcases that we call Editions; these are used in the gating tests for our releases.

Want to help? Learn how to contribute to Fedora Docs ›