[TYPO3-content-rendering] RFC: Improving content-rendering -- core - Workflow

[Sebastian Kurfuerst]

Hi,

this is the right place to discuss how to make the workflow between the
content-rendering group and the core group more effective.
As always, any comments are welcome. My suggestions follow now:

I think it makes sense if you (=the CRG people) fix the CRG issues, as
you are experts in this area, the core team might not be.
For further discussion of open issues, I suggest we create a new BT
category, named "Content Rendering"... Or, do you think it makes sense
to use the CSS styled content category for it, maybe even rename it?

We should have a "Review team" inside the CRG as well, consisting of
maybe 4 people: 2 programmers, and 2 others who test the output. Of
course this could be changed, but as Content Rendering is so important,
we definitely have to look at backwards compatibility and upgrade paths.

I think these reviewers can get the "updater" role in the bugtracker.

Then, wenn a bug arrives (whoever reports them), everybody can post a
fix, and the CRG review team can review it then. When everything is
approved, a core team member (for example myself, Rupert, whoever) can
take care of getting it into the core.
I suggest a following structure for the core information: (Which can be
pasted directly into the core list!)
 - Problem Description
 - Solution
 - possible side-effects
 - backwards-compatibility
 - changes in rendering?
 - Who has approved the patch, being the responsible person for it?
(That person is contacted then when there are problems => I'd suggest
the reviewers).


Please tell me what you think, and what you are willing to do, then I
could set up the necessary things in the bugtracker.

Greets from Dresden,
Sebastian