[TYPO3-dev] Experience from usergroup meeting about core development

Steffen Gebert steffen.gebert at typo3.org
Mon Feb 13 18:44:56 CET 2012


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

> The common opinion was that there is no direction of development which
> is then followed by the whole core team. Everybody does the features
> which are nice for himself but nobody checks the requirements of an
> enterprise cms or from the competitors.

I think the idea came from Benni some time ago: Ask the Platinum + Gold
sponsors, what features they are missing most in TYPO3. Taking this as a
starting point, we could also ask the broad community for their votings.

I think, when such a wish-list exists, some developers will take care of
these issues - at least most of them (it's motivating to implement *the*
most-wished killer feature, isn't it? ;)).

Other than that, I hope that more developments happens in teams.
One-man-shows turn out to fail or to get merged untested, because of
nobody is able to review everything.

I'm clearly against presenting a roadmap of the great features of the
next version, from which maybe one or two are really implemented. I'm
happy that we stopped this since 4.5 (?).
Instead, I would like to see more teams being formed, especially for
bigger features. Present an idea at the devdays or a new-version-kickoff
and ask for co-authors.

On the other hand, what information about TYPO3's direction do people
expect? "TYPO3v4 will die in favor of Phoenix" or "The next version will
focus on this and that"? I'd say, it's not possible to make everybody
focus on a single topic per release (and makes no sense IMHO), instead -
as said - I'd like to see several people joining forces. Sometimes this
works very well and - like for FAL - will hopefully be crowned with big
success.

And for the general "feeling responsible" thing: I really hope that Ben
has his suggestions for "Team rules" finished until the DevDays. I think
that's really overdue, to have some guide lines, how an official TYPO3
team has to operate (frequent meetings, public protocols, regular team
reports (2-4x per year), etc.).

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 v4 Core Team Member
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPOUwYAAoJEIskG/rSlyw4d8MH/RCZb3No2xf0Utg7xGwXX7RQ
eeRNeRZO3GlWa6BoOrDArmnAihto759XjMtR5zYRcmppzbUNvs6b3o8f0S/20UT2
ZNrfw5Sdf2QjJ4fSnyYucl3xB/fMWxU3G0pUowsFS1+9ULin9pm7UiuhSNCbcno6
5RG6QOgRO9Oa+5CLE8YMzCWLq8hbOulhdEyN9koWTVD/W3QcpTvmeyQKCUEaA7d/
C5k6Ja6XdN2UgutDxV3uGnQIyts9MEN5HrnijXt2Jf/2WMhqQFpAd5pABcYEKHGo
Qyx8wHG3RRp6Vm8spooDjd++I+Ed4i8DWXOPgSOqzKq+GxzbvUVrxLMkXD4dIYs=
=MZjf
-----END PGP SIGNATURE-----



More information about the TYPO3-dev mailing list