[DotGNU]RFC 1: Organizing RFC's

[Peter Minten]

RFC Number: 1
Title: Organizing RFC's
Maintainers: Peter Minten <address@hidden>
Date of entrance: 20-oct-2002
Date of decision: -
Area: DotGNU Working Group
Status: Being considered
Version: 1
Description: 

This RFC discussed how to build a standard system of RFC documents documents and
how to display them properly on the DotGNU Website.

Full text:

This RFC discussed how to build a standard system of RFC documents and how to
display them properly on the DotGNU Website.

On the Perl 6 developers website (http://dev.perl.org/perl6) they have invented
a great system for keeping track of plans. They make a document out of every
idea, a so called RFC document. The RFC document contains all the data of the
plan:
* RFC Number (assigned by librarian, see 'RFC 4: The librarian subcommittee')
* Title
* Maintainers (who maintains it, both real people and subcommittees (see 'RFC 3:
  Subcommittees' for more info on this))
* Date of entrance (when was the RFC send in)
* Date of decision (when was the RFC rejected/accepted, this is useful to search
  for the edition of the DotGNU Gazette (RFC 5) that contains explanation about
  the decision.
* Area (under which WG the RFC falls)
* Status (Being considered, Rejected or Accepted)
* Version number (starting with 1)
* Short description
* Full text of the RFC

All info's except the full text should be put on a summary page. The full text
should be on a separate webpage to which the summary page should link. Each RFC
summary should have a background color indicating it's status. This is green for
accepted, yellow for being considered and red for rejected.

The Working Groups are expected to review RFC's. The results of those reviews
should be published once in a set period of time in a message to the DotGNU
Developers Mailing List. This message is described in 'RFC 5: The DotGNU
Gazette'. New RFC's should also be put into the Gazette.

End of RFC