[TYPO3-dev] TYPO3 5 mailing list?
Michael Scharkow
mscharkow at gmx.net
Tue May 30 12:36:54 CEST 2006
Hi Kasper,
Kasper Skårhøj wrote:
> First: How can we open up for broad, result producing collaboration on
> the 5.0 architecture?
Invite all interested parties to submit a formalized proposal stating
*what component* (e.g. CSC, TCA format, module X, class Y) they'd like
to work on with *what goal* in mind, *how* it's supposed to be
implemented (to keep things focused on the actual work), *how long* a
working prototype will take, etc.
The R'n'D team should priorize the work so that dependencies are handled
correctly and the overall architecture is structured.
TYPO3 is so modular already that it should be possible to separate the
work into manageable chunks, we only have to take care that the projects
are small enough to be implemented in a reasonable timeframe. The 4.0
projects have IMO been somewhat too large to be handled in time by one
person.
If there are larger components to be done, encourage people to have code
sprints with interested developers, keep the teams small and make sure
no single dev is involved in too many of them.
> Second: What will motivate the best developers in our community to take
> responsibilities for the implementation of that architecture?
A few ideas:
1. A less rigid access to the 5.0 branch in SVN/CVS and less strictness
in code quality. Everyone should get access to new developments as soon
as possible. Until now, most of the projects where rather private and
only hit CVS when they were already quite big.
2. Use project management tools such as basecamp and keep the schedule
tightly monitored.
3. Pressure people to get help or fail early because we cannot lose 2
years on feature X. Have the project leaders report every month, etc.
On a related issue: We should *really* relieve the core devs and others
from being webmasters, editors, bug managers, security team members,
etc. This has been tried many times, but we still have huge dependencies
on Robert or Rupi or you being around to fix simple stuff on typo3.org etc.
Cheers,
Michael
More information about the TYPO3-dev
mailing list