RFCs and organisation View as Markdown

Hi there,

First off I'd like to apologise for being a generally useless and overly
reactive poster on this list. I'm going to exercise more self-constraint
now after noticing I made more posts on this list this month than anyone
else, this month.

Anyway, onto the subject of this email, in which I will try to be at least
somewhat helpful.

I notice that the RFCs page (http://wiki.php.net/rfc) doesn't seem to
have any clear instructions on how to create an RFC. I think someone
(perhaps me) should write an RFC on how to write an RFC, and also the
procedure involved, e.g. how to get wiki karma, voting process.

Secondly, I noticed that Python's PEPs are numbered, unlike PHP's RFCs.
Whilst they aren't quite the same thing, I wonder if this would be useful,
particularly since it provides a simple and unambiguous way to refer to
one, e.g. RFC 123 instead of "RFC on how to write an RFC". Plus it would
provide for an obvious way to sort RFCs in a list, by number. At the moment
I'm not really sure if there's an sort of sorting on the RFCs page,
although RFCs certainly seem to be categorised.

Thoughts?

Apologies again,
Andrew Faulds

http://ajf.me/

--

I think what you're looking for is this:

https://wiki.php.net/rfc/voting

As far as formatting goes, I'd just copy what other RFCs have done. I've
raised the idea of clarifying the voting process with a new RFC awhile ago
but nobody seemed interested one way or another so nothing ever came of it.

Regarding sorting, IMHO it really doesn't matter. My preference would be
to put the most recent ones on top, but so long as they're listed under the
right status categories then I really don't think it matters all that much.

--Kris

Andrew Faulds wrote:

Secondly, I noticed that Python's PEPs are numbered, unlike PHP's
RFCs. Whilst they aren't quite the same thing, I wonder if this would
be useful, particularly since it provides a simple and unambiguous way
to refer to one, e.g. RFC 123 instead of "RFC on how to write an RFC".

If we do that, we should call them PHP RFCs (PRFCs?) instead, to avoid
confusion with IETF RFCs, otherwise it may get confusing.

--
Ryan McCue
<http://ryanmccue.info/

Hi Andrew:

I think someone (perhaps me) should write an RFC on how to write an RFC

Note that a new page create on the wiki in the RFC namespace comes with a template that gives some guidance on how to write an RFC.

Lukas based it on my original Traits RFC, since that one was considered to be a nice example. At least it was kind of complete with regard to the essential parts of an RFC:

• intro
• motivation
• full description (up-to-date following the discussions) of the proposed feature
  • with examples and use cases
• summary of semantics
• a patch
  And then based on discussion:
• FAQ or common misconceptions
• alternative proposals
• rejected features
• change log

Best regards
Stefan

--
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax: +32 2 629 3525