[TYPO3-dev] RFC as tool to concept branch 5.x -- WAS: TYPO3 5 mailing list?

[Elmar Hinz]

dan frost wrote:
> 4. I think that all contributions to the V5
> discussion should be in RFCs which are thoroughly
> thought out, contain code examples, list the
> impacts on TYPO3, and list the advantages/reasons
> for doing it. These RFCs should be published on a
> mailing list or in a special part of typo3.org.
> Anyone should be able to comment on them. The RFCs
> would be more general and wide-ranging than the
> applications for funding.
> 
> We probably need some way of choosing the RFCs
> which are feasible, worth doing and that the
> community likes - how this could happen, I'm not sure.
> 

Hello,

RFC could be a very good tool for the conceptial work on version 5.0. If
someone is really interested to propose a matter he should work it out in
detail. It is an appropriate base to discuss it publicly before
implementation. More people have the chance to point out the weak points
ahead of.

I think, that every RFC should have a responsible author (or a group of
authors). The author could publish them like every other documentation via
TER. If the author wants to modify the RFC in consecution of public
discussion we have the versioning feature of TER2. Older versions are
allways at hand.

Every RFC (in fact every extension) should have a direct link to an
associated  WIKI page where people can comment the RFC and make proposals.
The discussion could be accompanied in a newsgroup for RFCs or 5.x branch.

I imagine that there is a public list in the wiki, which RFCs are needed
and wich are already written. If we get concurrent RFCs with different
solutions for a topic that is a good base for a deeper discussion and
comparism of both solutions.

Regards

Elmar