TYPO3 V6

Added by Maik Hagenbruch almost 7 years ago

TYPO3 v4/v6 - Oliver Hader

Ongoing development, maintenance and release of TYPO3 CMS (known as „Version 4“ and „Version 6“).
Note: The „Travel Expenses“ which were traditionally part of this budget have been split off in a separate budget request, namely „TYPO3 Active Contributors Meetups (T3DD/T3CON)“
For 2013 we will put more emphasis to the following aspects, which should pave the path to our next LTS release by the end of 2013:

a) 4 planned Code Sprints per Release (thus 8 per year)
b) Lowering work-time of Core Team Leader (Olly Hader, from 10 days to 6 days per month), rising Co-Leader work time (Benni Mack and Helmut Hummel from 2 to 4 days per month)
c) enabling a new worktime for a „Coder / Quality Assurance“ (Christian Kuhn, 4 days per month), which is the „guy“ responsible for all necessary coding tasks that noone volunteerly is wanting to do (clean ups, unit tests, post-reviews, pre-release coding / fixing, etc).

This work-load might also be shared with the Co-Leaders.


Replies (7)

RE: TYPO3 V6 - Added by Ernesto Baschny almost 7 years ago

See also this related budget, which is meant to make sure our team and active TYPO3 Core contributors meet up before and during the main events (T3DD and T3CON):

http://forge.typo3.org/boards/15/topics/13

RE: TYPO3 V6 - Added by Felix Oertel almost 7 years ago

While I would totally support Christian Kuhn as the right call for this job, I don't think it's a good idea to pay someone for coding.

RE: TYPO3 V6 - Added by Philipp Gampe almost 7 years ago

As far as I am informed, this budget must not necessarily be payed to Christian Kuhn.

Paid for should mainly be done for pressing task around the releases and very complicated bugs that hang around for ever.

I do not think that any features should be payed from this budget, because I think that those should be paid by companies.

RE: TYPO3 V6 - Added by Ernesto Baschny almost 7 years ago

Philipp Gampe wrote:

As far as I am informed, this budget must not necessarily be payed to Christian Kuhn.

Paid for should mainly be done for pressing task around the releases and very complicated bugs that hang around for ever.

I do not think that any features should be payed from this budget, because I think that those should be paid by companies.

If you think that with "4 days a month" of coding is enough to implement many features. Considering that the 4 days are about QA, Bug Fixing, Code Reviewing (Gerrit...), Unit Test-Coding, Pre-Release Coding Fixing..

Well, that's exactly what's written in the application. "Wer lesen kann ist klar im Vorteil". :) Please don't spread wrong rumors in this forum, as people get quickly "heated up" by such arguments and it sheds a bad light upon the application (because I guess many just read the comments here in the Forum and NOT the application itself, because of the annoying OpenOffice formats...).

Cheers,
Ernesto

RE: TYPO3 V6 - Added by Ernesto Baschny almost 7 years ago

Please also read this summary I wrote about this application:

http://buzz.typo3.org/people/ernesto-baschny/article/typo3-core-budget-application-2013/

I'll be at the T3CON Stuttgart on Friday on the Budget-Session to answer your potential questions.

RE: TYPO3 V6 - Added by Ernesto Baschny almost 7 years ago

There is a ongoing discussion in the teams.core Mailing list around the need or not of a new LTS for TYPO3 CMS.

We have strong reasons to believe that there will be another LTS released during 2013 and this budget application is already coping with that fact. Quoting the application:

For 2013 we will put more emphasis to the following aspects, which should pave the path to our next LTS release by the end of 2013:

a) 4 planned Code Sprints per Release (thus 8 per year)

b) Lowering work-time of Core Team Leader (Olly Hader, from 10 days to 6 days per month), rising Co-Leader work time (Benni Mack and Helmut Hummel from 2 to 4 days per month)

c) enabling a new worktime for a „Coder / Quality Assurance“ (Christian Kuhn, 4 days per month), which is the „guy“ responsible for all necessary coding tasks that noone volunteerly is wanting to do (clean ups, unit tests, post-reviews, pre-release coding / fixing, etc). This work-load might also be shared with the Co-Leaders.

Thus, we have set up a job description of a "Coder" which in fact could as well be used for backporting bug fixes to maintained releases of TYPO3 CMS, with important focus on the LTS.

    (1-7/7)