[TYPO3-core] Review system woes

[Georg Ringer]

Hi,


Am 08.02.2013 09:12, schrieb Daniel Alder:
> Am 07.02.2013 18:51, schrieb Philipp Gampe:
> 
>> You - as a core team member - could ask other team members to review it.
>> That is what non-core-devs do too. It is a rather effective way to fasten
>> the review of important changes.
> 
> ..i've seen many examples this was not working.
> 
> first:
> it depends on "who do you know?"

every core member knows all the other members and got most of them in
skype, ...

> it depends on "personal attitudes" => do this person think it's a good
> thing (he decides on his own not in "community")

of course the person should do more than just giving a +1 without
thinking/testing ;)

> beside the main problem in the typo3 community there is no "lead".

which is very hard to implement having an open-source project and not
paid coders. People have other important stuff to do too.

> to remember: the basement of typo3 ARE the agencies who making money
> with typo3. so this is why everyone of them is using LTS or switching to
> other systems.

that is just a wrong assumption. Not every agency uses LTS ;)

> another funny side-effect: every big agency is doing there own thing
> (frameworks/APIs/own repositories do patch/fix the cores which never
> will be contributed to the community)
> 
> imagine this big amount of energy would flow back to typo3 community!

+1.

> so i think the review-system isn't the best i've seen on the market. 

so what do other review systems make better?

Georg