[TYPO3-dev] RFC as tool to concept branch 5.x

[dan frost]

Elmar.

Fact: TER is not meant for discussion of ideas

Fact: Making the TER a respository of RFCs will
put non-TYPO3-functionality in it. This will annoy
people. Imagine: download: "new TYPO3 versioning
architecture" and you find it's a PDFs. How
annoying is that.

Fact: the TER is not "normal" for Open Source
projects. They might have similar things, but they
do not have the TER. For TYPO3 to grow, attract
talent and become more of a standard  it must
adopt straight-forward, easily understandable ways
of doing things.

The TER is the wrong tool for this.

Now, let's get on with discussing the process of RFCs.

dan

Elmar Hinz wrote:
> Christopher wrote:
>>>> TER2 doesn't create any PDF at all.
>>> That is a difficult point for now unless the feature is implemented
>>> again.
>> I could be wrong, but I don't think the _TER_ has ever done this. It
>> has _contained_ pdfs of some documents, but I don't think it created
>> them...
>>
>> -Christopher
> 
> Well, they "occured" after some days in TER1. Maybe someone has generated
> them by hand.
> 
> Openoffice is opensource. I guess the engine to transform .sxw to .pdf
> could have been extracted from the editor.
> 
> Regards
> 
> Elmar
> 
> 
> 
> 
> 
> 
> 
> 
> 
>