Community Management - Ben van 't Ende
The Community Manager makes sure that the communication between the teams (TYPO3 version 4, TYPO3 version 5, FLOW3, Ext-Base, workspaces, design and all other 'official' TYPO3 teams) is happening in a smooth and pleasant way. He has an overview of the overall status (The Big Picture). He activates and re-activates teams if there is a need. He contributes actively to the community and works closely with the committees and teams to ensure the success of the TYPO3 project.
The Community Manager guides teams and individuals that are dedicated to developing for TYPO3. This extends from facilitating information or assistance that helps a project in any way to publishing information on a certain topic to raise awareness within the community or towards the general public.
The Community Manager communicates with all areas of the community working with the committees and teams. He will also serve as the internal and external evangelist for TYPO3, occasionally working with key users.
The Community Manager will report every first working day of the month with the exception of holidays.
Driving solutions and information gathering across teams.
Serve as a coach and public representative for TYPO3 towards community members, end-users and companies.
Analyze and report community success
Organise TYPO3 related presentations and coaching events at conferences
Acting as an interface with the open source community
Prepare articles and presentations
Grow the community
Get more involvement
The goals of growing the community and getting more people involved can be achieved by providing better information on the current TYPO3 platforms like typo3.org. In general we still sport a nerdy approach. On typo3.org there should be quidance in clearly written terms on how to participate and how the teams and community function.
Metrics should show the livelihood of the community. I am aiming to have a clearly separated output for team activity and thus community health next year by getting that data out of Forge, Gerrit and the mailinglists in the form of a dashboard. This will be in the form of a community project staffed by one or more persons.
Local initiatives are all around us and need to be better supported. I plan to visit as many local initiatives as possible and assist the local groups with getting together local meetings.
We are still a very white male dominated project. Intend to get some attention on getting more womoen into the TYPO3 project and teams. I will come to the teams and also the boards with recommendations or serious guidelines on how to achive that.
RE: Community Management - Added by Steffen Ritter about 7 years ago
Could you please tell how much you actually invoiced for this year until now?
Did you need your budget - or better did you work in fulltime this year, too?
If the Budget application is just "do the sime like this year", I'm in favor of not investing that much money for community management. The money could be invested with a higher outcome (e.g. professional PR).
I will explain my thought behind that to the EAB and Ben in Person if wanted, but I think this does not belong here...
RE: Community Management - Added by Steffen Gebert about 7 years ago
Steffen, IMHO you should think about a bit more about your words, seriously. Criticism is fine, but you should first tell the people and afterwards throw out statements like that.
RE: Community Management - Added by Olivier Dobberkau about 7 years ago
Ben will present his Budget Application on Friday at TYPO3 Conference T3A Budget discussion 17:30-19:00.
If you are interested come by. Not Conference Ticket needed!
RE: Community Management - Added by Manuela Heuing about 7 years ago
Hmm... - the comment of Steffen Ritter is interesting for me. It upsets me to think about the hole budget discussion process. General it´s difficult for me when people ask questions and then be stopped immediately. Exactly such opinions like Steffen Ritters could enter us more deeply into the budget applications and create more understanding and awareness.
I have some questions, too. And I need these informations before I could going into the discussion at all:
- How long has this position been?
- Is the Community Manager elected or appointed?
- On which board has the position to report?
- For which period is the position set?
- Which areas of responsibility has this position?
- How much time are going into which tasks per month (rough estimate)?
- Are there any changes / improvements planned compared to the previous period?
- Are the 66.000 € really for only one person for a 30h-per-Week-Job?
If I know these things I could start discussions about the meaningfulness of budget requests and only then could I help to collect some ideas for saving budget. We can´t finally pay all applications fully.
RE: Community Management - Added by Ben van 't Ende about 7 years ago
Great to see you get involved. I am just preparing some stats for my budget presentation for what I did over the past three quarters of this year. In general I would say no large community can do without a community manager or rather enabler. The function was first started because there was the need for a person that had an overview over the project, which we did not have some years ago after Kasper retreated more and more from his function. The function of community manager is hard to measure as you do not produce a product. I will however show how the number of contributors to the core doubled over the last two years, code-sprints rose from 1 in 2009 to about 7 this year and barcamps also from 1 years back to 7 now. Now I did not organise all these events, but it does show the health of the community, which i manage. I also have a session at the con about the community, which i would really like to be an open discussion about what we can do to activate the community.
- How long has this position been? Since April 2010 and started on partial budget from the Phoenix team to help them out in the team and with communication.
- Is the Community Manager elected or appointed? I request a budget. When granted I can do my job.
- On which board has the position to report? I report to the Expert Advisory Board and to the community. I write the monthly community report
- For which period is the position set? For the budget year
- Which areas of responsibility has this position? I would like to describe it as encouraging people to join and participate, reducing bottlenecks and other areas. It covers a wide area. I also participate in a lot of teams to be able to connect the dots. A lot of what I do is to make sure there is communication about the projects to make sure the community knows what is going on. A lot of the articles on typo3.org are not written by me but initiated by me. I also make sure the relevant teams stay active or get new members.
- How much time are going into which tasks per month (rough estimate)? Community communication: 400 hours, events, conferences: 130, typo3.org relaunch: 40, articles and presentations and a lot smaller tasks
- Are there any changes / improvements planned compared to the previous period? Planned is to get more women into the community, to support the national committees/initiatives, a product board is planned, a community counsel, more support for the TYPO3 camps
- Are the 66.000 € really for only one person for a 30h-per-Week-Job? The hourly rate is 55 euro's.
RE: Community Management - Added by Wolfangel Cyril about 7 years ago
Just a short input coming from my experience as French speaking committee manager:
we would have done close to nothing without Ben, if you want TYPO3 to keep growing in other countries we absolutly need a community manager.
Also hos actions are bringing money for the association, for example the french event call T3UNI is giving all it's profit to the association, and i'm just talking about what happenend in France.
I think theses actions are a lot more profitable for TYPO3 that pure code developpement, this is exaclty what TYPO3 need !
RE: Community Management - Added by Patrick Lobacher about 7 years ago
Wow - this is a lot of money. But - from my inner feeling - it's worth every cent. Much more than "some" technical issue paid or one or another codesprint. Communication is the most important part (more than code development) within a growing community and from my point of view - Ben did a great job and will in the next period.
RE: Community Management - Added by Manuela Heuing about 7 years ago
Thanks for the answers and how you´re handling the questions, Ben.
I think community management is a good idea and we need it. Of course. I'm just generally not a fan of fulltime positions in associations or parties. Too often I´ve made the experience, these areas are developed into kingdoms and the dealing with it is very difficult. From a purely democratic perspective, I think it would be better if there are two or three people, they share this position. Even if it´s more work.
In general - not only in relation to this position - I would appreciate it, if we pay not more than max. half-time-jobs in the association. And if everything is paid fairly, it´s totally ok for me.
RE: Community Management - Added by Felix Oertel about 7 years ago
For me it's hard to judge about this budget as well. Some kind of voting at the outcome of this year's work would be great. Probably every team should be asked about how they benefitted.
I like Ben, he's a nice guy, and I know, he did a hole butload full of work with the typo3.org relaunch. But I think in the extbase team, we did not profit too much. Our codesprints rose from 0 to five (or six) this year, but for completely different reasons. Also we hat to manage (or try to manage) to set our communication (regular skype meetings, news articles for releases, website (which is not online yet, I know ;) ) our self.
I like the idea of an enabler, but for this sum and 30 hrs/week there should be some pretty neat outcome. Probably it exists ... I can not say.
RE: Community Management - Added by Andreas Otto † about 7 years ago
I think community management is a good idea and we need it. Of course. I'm just generally not a fan of fulltime positions in associations or parties. Too often I´ve made the experience, these areas are developed into kingdoms and the dealing with it is very difficult.
That is exactly what I thought as well.
I would rather have a situation where the association defines the role of the community manager (responsibilities, targets, etc. ) and defines the budget. Interested people can then apply for the position of the community manager and the association will then appoint the community manager. The community manager will be appointed for a period of three years. Half a year before the three year period ends the association will make an announcement that interested people can hand in their applications.
RE: Community Management - Added by Gina Steiner about 7 years ago
atm the typo3 association is not able to employ people outside of switzerland. we already checked out the possibility. we asked our official statutory auditors bdo because we where in need of a solution for sandra but they said if we want to employ sandra in germany we have to build up a branch association in germany. this for sure is too much overhead, we have international members an can not set up branches in every country. in addition it is not possible to sign a contract over 3 years, since the budget cycle of the association is one year. we also had this problem when the certification asked us to set up a 3-years contract with a company. in this case we got in contact with the company and convinced them of a one-year contract which will be extended from year to year. so: good idea, not possible with our current association.
RE: Community Management - Added by Felix Oertel almost 7 years ago
i think andreas' idea is good and we should do it like this. apply for a wildcard budget, wait for it to be allocated, have a four week hand-in-period, appoint a manager who gets the budget.
we could then either repeat this every year or just renew the position after the following budget has been granted. (of course she / he has to know, that the budget is only given for one year, not three)