-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The first deliverable that the Fedora Server Working Group was tasked
with was the production of a Product Requirements Document. This
document is intended to provide a high-level view of the goals and
primary deliverables of the Fedora Server distribution. A great deal
of discussion has gone on during the weekly Working Group meetings as
well as on the mailing list.

At this time, the deadline for the delivery of the PRD is rapidly
approaching. Originally it was due to be delivered for ratification on
Monday, January 13th, but at the FESCo meeting on Wednesday, it was
agreed to delay this deadline by a single week. The primary reason for
this delay was so that the Fedora Cloud and Fedora Server groups could
have some last discussions about overlap and respective areas of
responsibility.

This past Tuesday, we had an all-day PRD hackfest in IRC and have come
up with a fairly strong draft[1]. It is not yet complete (notably,
there remains a FIXME under "Misc. Concerns" and some ambiguity around
the Use Cases), but I believe that it is close enough to its final
form (as envisioned by those people that have contributed to it), that
we should expose this document to the wider world and ask for input
before submitting it to the Fedora Engineering Steering Committee and
Fedora Advisory Board a week from Monday.

Please read through the PRD draft and provide feedback of any sort. If
you see that we have missed or misrepresented any of our statements,
we would very much like to hear this soon.

[1]
https://fedoraproject.org/w/index.php?title=Server/Product_Requirements_Document_Draft
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLQUp4ACgkQeiVVYja6o6O8IwCcCIaNJEr919QgyB3XJC+2Ynqf
6PcAoJ2BpgMwi1NzdG2XBZ0nyEzlh9XZ
=DINq
-----END PGP SIGNATURE-----
_______________________________________________
devel-announce mailing list
devel-announce@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel-announce

Reply via email to