Fedora.Next draft for trifold.

Gabriele Trombini (mailga) mailga at fedoraonline.it
Fri Aug 1 16:43:34 UTC 2014


I've created a draft explaining fedora.next to be includde in a trifold for 
mktg use.

Can someone, take a look to the attached text and rectify what 
seems wrong/incomplete?

I'll study a layout afterwards, when the text will be decided.

-------------- next part --------------

-Mission: lead the advancement of free and open source software and content as a collaborative community: 
  - always striving to lead, not follow;
  - consistently seeking to create, improve, and spread free/libre code and content;
  - succeeding through shared action on the part of many people throughout our community. 

“Freedom, Friends, Features, First”

The four foundations are the core values of the Fedora community.


  - give a positive voice for people with diverse requirements;
  - invite contributions even when they're not perfect, allowing software into Fedora even with rough edges, and improving from there;
  - focusing more on packages where it really matters that they’re packaged well, making them as useful as possible to people;
  - moving fast while still keeping a handle on the direction we’re going, balancing innovation with change management;
  - making easier to have projects that work on Fedora without necessarily being in the distribution proper.


"Fedora.Next" is the word which sets the next plannings of the Fedora project. This consists in shipping "bricks" for general purposes, without gluing together. People can build other things and/or re-assemble the ones shipped into something else, although it should be clear, if done, that it's no longer the official set.
People can share creations and maybe even make new sets.
This is performed by the working groups that also manage many of the technical decisions, making them set up for growth.


- Base:

This is the common base on which the Fedora OS products will be built. Language stacks and environments will be able to assume that this is available and consistent across all of Fedora, and that change will be carefully managed.

The Fedora.next proposal suggests that this should exist, but leaves open exactly what it will look like. This group will create a reference document that answers that question, and work on the practical infrastructure for building this as a subset of Fedora. 

- Environment & Software Stacks

These are also policies development for software. New guidelines for how software may be included under the Fedora umbrella without necessarily conforming. 
Fedora.Next allows disruptive innovation without disrupting what works in Fedora now. At first, work will be concerned with more conservative approaches like the first generation Software Collections (which may fit in with only minor exceptions to the current packaging guidelines), this is also the place to explore and solve issues like container composition and updates. 

- Product Working Groups
The first responsibility of each working group will be to establish a governance charter.Then, the first required deliverable for each group will be a Product Requirements Document. This will include a statement of target audience and the role the product is intended to fill in the Fedora ecosystem. This document will be presented to the Board for ratification.The second deliverable should be a list of necessary changes from existing Fedora procedures needed to release the product. This should be ordered to show what things depend on other changes and at which point the changes will mean that we can no longer produce the current type of Fedora. This will allow us to identify the resources needed by what teams in order to implement the plan and at what point we may need to have a longer than normal release cycle to do tooling work. The last deliverable is to actually start producing the Fedora Products listed below. 

- Base Design Working Group
- Environments & Software Stacks Working Group 

- Product Working Groups
  - Fedora Workstation (aims: create a reliable, user-friendly and powerful operating system for laptops and PC hardware. The system will primarily be aimed at providing a platform for development of server side and client applications that is attractive to a range of developers - from hobbyists and students to developers working in corporate environments); 
  - Fedora Server (aims: common base platform with 'featured application stacks' built on top of it. It commits to produce, test, and distribute these application stacks);
  - Fedora Cloud (aims: responsible for initial and ongoing development of the Product Requirements Document, and for coordinating production of the Fedora Cloud operating system);

Automation everywhere: 
  - automated testing;
  - agile release engineering;
  - improving communications across platforms and areas;
  - making available in a easier way the documentation simplifying its access;

More information about the marketing mailing list