Fedora.next PRD refresh
sgallagh at redhat.com
Mon Jun 1 19:03:44 UTC 2015
== Overview ==
Back at the beginning of the Fedora.next initiative when we created the
working groups, we tasked them with creating "Product Requirement
Documents" (PRDs) to guide the development of each of these core
More than a year has passed and the Fedora Council feels that it's a
good time to give another pass at these documents and re-align them,
both with the current reality and the next phase of this process.
Additionally, the Council feels that it would be good to perform such a
re-alignment and update each year.
This year, we have set an admittedly short deadline: the PRDs need to
be updated and ready for review on June 12th (11 days from now). In the
future, this will be scheduled further in advance and with more time to
address it (see below).
== What do we have to do? ==
There are two things that should be done during a PRD refresh exercise
(though their implementation is left as an exercise to the Working
1) Review the PRD for plans that are outdated. Some examples:
* Support for CPU architectures that no longer make sense
* Features that have been de-prioritized or indefinitely deferred
* References to technology that has been replaced or obsoleted
2) Add new plans and requirements for the evolving technology. Some
* Fedora Cloud commits to producing an implementation of the Nulecule
* Fedora Server commits to producing Server Roles that can be
migrated to a Fedora Atomic deployment
* Fedora Workstation integrates seamlessly with a self- or publicly
-hosted ownCloud deployment.
(Optional): The PRD review period may be an excellent time for those
WGs with persistent membership to evaluate whether it is time to
refresh the WG membership as well.
== Future PRD Refreshes ==
Starting at Flock 2016 (yes, *next* calendar year), each working group
will have a workshop scheduled at Flock to go over its PRD and plan for
the following year. Note: because Flock generally falls between Alpha
and Beta of a Fedora release, all PRD planning is presumed to be a
directive for Fedora N+1 and N+2 at that time, not retroactively
applied to the current release.
The workshops are expected to cover the majority of the update, and
then they will be brought back to the respective mailing lists for
further review before being due to the Council one month after Flock
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: This is a digitally signed message part
More information about the server