[TYPO3-core] Review system woes

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Francois,

your first suggestion sounds radical to me. I fear it won't help so
much, instead people will just stop doing work for TYPO3. That's the
problem with open source: People do what they like to do. If they aren't
allowed to submit new patches, but only review ones, (at least I expect
that) many will not switch over to doing reviews.

I can't agree more with your second point, the Core Team state. I
understand the frustration by Christian that many "team members" that
simply do nothing are blocking his work + the expectations of other
community members. It was also demotivating for me, when I was active to
see the long list of members.
I expect sth. to happen soon, Olly, Michi, and Benni met few weeks ago
and I heard here at the mountain that their suggestion should be
published these days.
Oh my god.. I fear the next storm.. restructuring of the Core Team
announced at T3BOARD :-)

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

I work for TYPO3 solely in my spare time. If you think that
my work helps you running your business, you are invited to
send me a donation via PayPal to this email address. Thanks

On 2/16/13 12:55 PM, François Suter wrote:
> Hi Olly,
> 
>> Some possible solutions at this time:
>>
>> * Review Days: Benni already started an initiative similar to previous
>>    Bug Days to basically concentrate on reviews instead on bug fixes.
>>    The scheduled date is *Friday,February 22nd 2013*  and open for all
> 
> I propose a far more radical solution: we halt all development until we
> have reached zero pending patches in Gerrit. Anyway the objective of 6.1
> is "improvement". What better way than to have given a final answer
> (merged or abandoned) to every pending patch? What else is more
> important? I'm sure everyone will appreciate a "stabilization" release
> after all the recent rush of changes (just look at the number of
> extensions which are still not compatible with 6.0).
> 
>> * Change in Core Team Structure: Since the community is flexible, the
>>    permissions ("commit/submit karma") needs to be flexible as well, thus
>>    there are plans to restructure the current scenario and as one effect,
>>    give more power to active (long-term) contributors. A detailed draft
>>    on that will follow - but let's do it step-by-step and not all at once
> 
> Yes, yes, yes, bring that on quickly. The recent fight over Christian's
> patch has raised the priority of this to critical IMO. We lack vision,
> we lack strategy, the rather hands-off leadership you exerted has shown
> its limits. We need a smaller, more dedicated, more active Core Team,
> which gives the community and in particular the active contributors a
> sense of where we are heading.
> 
> Let me make a strong statement: I think that the Core Team in its
> current form is as good as dead. There's no vision for the product,
> little or no communication, weak leadership and awfully little
> cooperation between members. Let's restructure it, rebuild it and make
> it shine again, because we have a wonderful group of nice and skillful
> people!
> 
> As a side note I feel a bit bad about saying "we" here, since my recent
> involvement has been with the Doc Team rather than the Core Team. But I
> wanted to express my feelings, because I still care :-)
> 
> Cheers
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJRH5iBAAoJEIskG/rSlyw4encIAMkYU0XqnGztsiRCeJusdbvh
8NVUM3puVFcv+sfmG5OCSr+3wxvoP48Xd9m2Yl6irnBshxEoQhQJQNzQ2o3SXtBh
83NfFmvZg0pWN4Sm9EnF1q0lSUa+bcJucuz1QBYmxkYMmAes2n6zQxngSYSDEm/g
G83QwOIO4z/FXigiavj0xJpPbLkqf/sxMBDIkb8kGwa0TxxQGNChFzt4HnkV6MB7
JpFU7G70Ixy8GJjsEyfuET0RzYBIJoJMxf8lk5IP3moedK4yfQljHQrBqKLQIoK8
WLroiiOyxjLFgTbmL0L3boS2HHafgxfzuYEqY7pIxvwOMomIJFoxuDg/D5J8hAo=
=vkf3
-----END PGP SIGNATURE-----