Stewards/Coding/CommunityManager
Community Manager, Coding
While Mozilla has a sizable paid engineering staff, the success of the project depends in large part on unpaid code contributors. In order to ensure that code contribution is as painless as possible, we're looking for a full-time Coding Community Manager.
The Coding Community Manager will aid new and existing contributors, ensuring their work is submitted in the right place and to the right people. They will track contribution patterns, finding gaps in process and documentation, and driving the solutions. The Coding Community Manager will analyze existing tools and processes, looking for opportunities to make contribution easier and more effective.
The Coding Community Manager is a social person who can jump into a bug and connect a contributor with the right engineer to help move a bug fix forward. They can ask in IRC channels to find the right person to review a patch. They can identify contributor un-friendly patterns in systems and blog/discuss improvements with the developer community.
The Coding Community Manager uses Bugzilla like McGyver would use a multitool (if they had those back then). They have enough coding chops to build tools and visualizations that track and aid contributions.
This position is available for remote work in some countries. If you are near one of our offices we're happy to provide a desk and many delicious snacks. Mozilla currently has offices in San Francisco, Mountain View, Portland, London, Paris, Auckland, Toronto, Vancouver and Taipei.
Responsibilities:
- Collaborate with development teams to provide an effective on-ramp process for new contributors
- Track contributions and contributors in Bugzilla, aiding where possible
- Identify contribution roadblocks, drive changes in community process to resolve them
- Coordinate with developers to ensure contributions are handled expeditiously
- Investigate new methods to measure code contributions
- Develop tools and programs to better highlight and reward community contributions and contributors
- Consider and enact new ways of reaching talented programmers who are not yet part of the community
- Encourage contribution in social media and blogs
- Manage contributor reward nominations and the delivery of rewards
Requirements:
- Proven track record of volunteer/open source community management experience
- Strong communication skills and desire to plan, discuss, and solicit feedback in the open
- Ability to think, plan and execute resourcefully, with minimal supervision
- Strong knowledge and passion about Mozilla and open source
- Knowledge of infrastructure/web languages a plus (Python, JavaScript, HTML, CSS)
Notes from Stewards
jdm's thoughts on responsibilities and requirements:
- audit existing contribution paths, prune those that are ineffective, and spruce up the rest to make them more inviting
- collaborate with development teams to provide an effective on-ramping process for new contributors
- work with community members to discover and fix pain points in the existing processes
- investigate new methods to measure code contributions
- develop tools to better highlight community contributions and contributors
- consider (and enact!) new ways of reaching talented programmers who are not yet part of the community
- knowledge of infrastructure/web languages a plus (python, javascript, html/css)
Dietrich: +1 on all of jdm's notes above. some other thoughts (though too specific for the actual job description probably):
- watch for contribution drop-off and engage those contributors
- watch for reward-able contributions, and be a coordination point for core devs who want to reward contributors (send swag, for example. or pro-actively calling out "friends of the tree" at the weekly project meeting.)