TYPO3.org Team Summit
See also the mailing-list and the newsgroup and all relating pages for the improvements
Here you find a Map with the homes of the Typo3.org Team Members: http://quikmaps.com/full/20595 (Last Update: o4.Jan.2oo7, 1o:3o)
- It is not finished jet, i don't have more adress data. >> PLZ mail me > email@example.com
See also the DATE-column in the table Current Project Members
Why we wanna do it
The target is "making typo3.org a good example of a modern community website" (quote Robert Lemke)
The TYPO3 Association has been thinking about its priorities and believes TYPO3.org is a key service to provide for the community and that it should serve to "enabling people to participate". (quote Kasper Skårhøj)
We need a long term strategy that doesn't rely on a mailing list "team" as it has been currently. Mailing lists are good to gather broad opinions and sometimes other things, but to end the frustrations with the TYPO3.org website we need a team with responsibility to make it happen. (quote Kasper Skårhøj)
We need to build the team (quote Erik Svendsen)
See the table Current_Project_Members - and please update it, if you see that something has changed.
Daniel Hinderink and Kasper thought about how to take this to the next level. The idea was to set up a team and meet in real life to kick it off. From such a meeting these should be the results:
|Main feature areas|
(including TER stability, karma points, team platform, social mobility, ratings)
|Plan for implementation||Plan for process management|
Daniel H. and Kasper would lead and participate in that meeting to help reach these results, but the clear goal is that when the meeting is over the responsibility for TYPO3.org has been outsourced to someone else and both need not think about it again.
Building the team are most important, because this will be the foundation for the future work in the team. Most of the team building can be done through practical work with problems, ideas and solutions for TYPO3.org, but some time has to be used on team-specific problems.
Important in building the team are:
- Get to know each other. Hobbies, family, interests, life experience.
- The team goal. The team goal is both the goal for the task in hand, but also a goal for other outcomes from the team
- Communication rules (both outside and internal), and which technology to use.
- How to work, - processes.
- Teamnorms and roles.
- Decision rules.
- Knowledge sharing
- Conflictsolving rules
- Team identity
-- Erik Svendsen