Steering Committee Structure » History » Revision 24
h1. Steering Committee Structure Current members (january 2010): * Robert Lemke * Karsten Dambekalns * Ingmar Schlecht * Dominic Brander * Michael Stucki * Mark Stephenson * Christian Jul Jensen * Ben van 't Ende * Jürgen Egeling * Adrian Zimmermann * Kasper Skårhøj h2. Suggested New SC Structure (12/01/2010) Robert Lemke compiled a document (NewTYPO3AssociationCommitteeStructure-2010112.pdf) on the new TYPO3 association structure. This part about the Steering Committee is from this document. You can find the document attached to this page. # The Steering Committee sets the strategic goals for the TYPO3 project in the scope of the TYPO3 Association during regular meetings. # The Steering Committee represents the community and acts likewise. It consists of key community members. Members should already have proven their dedication for the TYPO3 project in other areas as well as bringing the maturity and responsibility for the position with them. A Steering Committee member should have the competence to make decisions for the TYPO3 Association even if they are not in accordance with individual or company interests. # The Steering Committee consists of a minimum of 7 to a maximum of 10 people. # New Steering Committee members can be suggested by any Association member. The existing Steering Committee members decide on the invitation of new committee members. # Only one person per company at a time is allowed to be member of the Steering Committee. # After each General Assembly the members of the Steering Committee elect a chairman of the committee by simple majority. The Steering Committee Chairman is responsible for accomplishing decisions on strategic goals through meetings and online discussions. # A member of the Board cannot be a Steering Committee member. # The Steering Committee accepts applications for funding of projects by leaders of the TYPO3 teams. Based on these applications and the general strategy the Steering Committee gathers a budget proposal for submission to the Finance Committee. # There are 4 CoS-CoB (Combined Steering Committee and Board) meetings a year. One of the meetings is the General Assembly. During the meetings the Steering Committee and board work separately or together, depending on the actual topics. It is obligatory to take part in at least 3 of these meetings. Absence is only allowed for important reasons. Travel expenses and lodging will be reimbursed. _Please mark if you agree with the contents of the Steering Committee Structure. If you do not agree please write about it on the internal mailinglist. All votes should be done by Saturday 23rd of January_ [X] Robert Lemke [X] Karsten Dambekalns [X] Ingmar Schlecht [X] Dominic Brander [X] Michael Stucki [X] Mark Stephenson (although it is not practical for me to attend 3 meetings per year in person) [ ] Christian Jul Jensen [X] Ben van 't Ende [X] Jürgen Egeling (ben voted for Jürgen - login problems, login solved, accepted, juergen) problems) [X] Adrian Zimmermann [?] Kasper Skårhøj (votes blank, because he is not involved that much that he feels he can decide) h2. Potential New Steering Committee Members [juergen] the question is what we wanted to achive with the new members. With each member, we give a new direction. What we need, is IMHO some people that find a general strategy for TYPO3, that we can follow. What we do nto need are countless ideas, where we pick and jump ini how others do things. Most other open source projects in our area have one big company behind. They can act totally different. It is in the interest of the company to market the project. So we first need a strategy what to do in marketing, and _THAN_ tools (ideas) how we could follow them. I want to suggest the following prodecures for new members: # tell them we consider them as a new member # give them a task # see if the task is fullfilled # if fullfilled: Take him/her IMHO we have enough idea givers, that show up random ideas, but "do not have the time" to fullfill and work on getting the ideas done. # Jochen Rau # Benjamin Mack - [ben] Benni is release manager for TYPO3 4.4 and very active in getting this version released in time. He is a good speaker and someone who thinks carefully about things. - [ingmar] I fully agree with Ben's points. Also, Benni has a positive spirit when communicating, is visionary and IMHO clearly a good one to have on the steering committee. # Daniel Brün - [robert] Daniel is one of the few long term TYPO3 guys who is very fit technically, also outside TYPO3 topics, and knows who to market it and lead a successful company in a friendly style. Time might be an issue though # Eike Diestelkamp: Have a look at http://www.hdnet.de/ Diestelkamp # François Suter - [dominic]: I do not know him very good but I have the impression that he is really doing things AND he is a representive of the French speaking part of our community. # Kian Gould - [ben] Kian is Owner and managing director of AOE media. He has been very active in the community. Like DKD his company has sponsored countless events. A good reason to let him into the SC is to have some more company influence in there. This will also give of a good sign to companies that want to sponsor TYPO3 or become a member of the TYPO3 association. - [juergen] I am really uncertain with Kian. He promised importand thinks like new person for getting new members, but I only see him delivering "short term stuff" and "ideas". - [dominic]: Generally I strongly suggest to 1. have more people from outside of Germany and 2. less developers. - [juergen]: ack + marketing person # Oliver Hader - [ingmar] As (new) core team leader, it will be good for him to be in the steering committee. He has a passion for TYPO3 and his time spent on TYPO3 doesn't stop with the working hours. # [juergen] $anyone_non_programmer. Reason: IMHO the technical ideas are done in the core team. SC should do strategical desicions that _effect_ the technical things, but this can be covered by the already existing majority of technical people in the SC. IMHO a good marketing person that _delivers_ would be a good idea.