[Typo3-dev] The future of the TYPO3 platform

[Daniel Hinderink [TYPO3]]

> Kasper Skårhøj wrote:
> 
>> True. It turns out to be hard to recruit people into this since there
>> are extremely high expectations to the quality of their contributions.
>> We are doing our best extend the team - but not at the cost of our
>> "unique" quality/stability!
>> 
>> 
>>> - There should be a better management for the available manpower (people
>>> managing e.g. CVS, release maintainers, feature plans, plugin
>>> coordinators, website updates (maybe blog?), documentation, i18n)
>> 
>> 
>> Did you look at the project/teams page. What is wrong with this? There
>> are plenty of ways for people to engage themselves.
> 
> If you mean http://typo3.org/1477.0.html I'd like to say that it is more
> or less just a list of teams with it members.

And?
 
> If I may do a suggestion? It would to be a benefit to have a developer
> subdomain, and for the bigger projects a own subdomain.

TYPO3.org is that domain.
 
> I do some translations for KDE and now some stuff about how it is organized.
> 
> I.e. there is http://developer.kde.org/ which addresses interessted people.
> 
> There is http://bugs.kde.org/ for quering and reportuing bugs
> 
> http://i18n.kde.org/ is for the translator teams.
> 
> Typo3 is not that huge as KDE is, but typo3 is complex, and there are a
> lot of documents, projects etc around the website.
> 
> For me (I'm not (yet) that kind of specialist, it is hard to find the
> right information that I need.

I understand, but putting things on many domains will make maintenance even
harder and we are heavily understaffed in that respect.

Cheers

Daniel


> 
> [..]
> 
>>> i18n
>> 
>> 
>> Team members are working on this. Do you see any problems? And for
>> translation of the system we have a kick-ass system!
> 
> Where can I read about it?
> 
> [..]
> 
>>> I have been using TYPO3 since v. 3.5.0-rc1. What will happen to the
>>> 3.5.0 release anyway? Will there be bugfixes and/or backports for the
>>> 3.5.x branch?
>> 
>> 
>> Of course there will be no backports.
>> One of our (apparently) unique features is that (unless otherwise
>> stated) you upgrade to the next version with full backwards
>> compatibility and only some 4-5 buttons to press to synchronize things.
>> And why wouldn't you? To avoid having the copyright notice of 3.5.0
>> shown in the login screen?
>> 
>> Martin K. suggested to add branches / tags in CVS for future releases. I
>> think that is a good idea though.
> 
> Yes indeed. Maintaining CVS branches is simple.
> 
> I'm against backports of new 3.6 features, but bugfixes (most important
> if there are some security related ones) is a must.
> 
> [..]
> 
>> Since we don't have time to analyse all these projects or experience
>> their communities first-hand, maybe you can give some actual suggestions
>> to what can be done with TYPO3's community?
>> I'm actually pretty sure that if you really want to shape TYPO3s
>> community to the better we are ready to allow you a shot at it.
> 
> See above...
> 
>> 
>> 
>>> Conclusion: Things just seem a little unstuctured. I believe Kasper
>>> should concentrate on what he does best: code :-)
>> 
>> 
>> Thats what I do all the time.
>> Oh no, not true. I do actually write a lot in manuals! Guess why? Seems
>> to be the *least* interesting job to do for other volunteers! Hence I
>> *have to*!
> 
> I wrote to HOWTOS for the TLDP. Why? because I'm a lazy guy and my weak
> memory. I'm sure with the right promotion this can (hopefully) be changed.
> 
> Thanks a lot
> 
> rgds
> 
> Luc
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> 

-- 

Daniel Hinderink
TYPO3 - get.content.right
Innovation, Marketing, PR
http://www.typo3.com

-- 
Fashion is a form of ugliness so intolerable that we have to alter it every
six months.
Oscar Wilde