Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
Stewards/Coding/CommunityManager: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Community Manager, Coding | 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 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: | Responsibilities: | ||
* | * Collaborate with development teams to provide an effective on-ramp process for new contributors | ||
* Coordinate | * 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 | |||
Requirements: | Requirements: | ||
* Proven track record of volunteer/open source community management experience | * Proven track record of volunteer/open source community management experience | ||
* Strong communication skills and desire to plan, discuss, and solicit feedback in the open | * Strong communication skills and desire to plan, discuss, and solicit feedback in the open | ||
* Ability to think, plan and execute resourcefully, with minimal supervision | * Ability to think, plan and execute resourcefully, with minimal supervision | ||
* Strong knowledge and passion about Mozilla and open source | * Strong knowledge and passion about Mozilla and open source | ||
* Knowledge of a | * Knowledge of infrastructure/web languages a plus (Python, JavaScript, HTML, CSS) | ||
==Notes from Stewards== | |||
jdm's thoughts on responsibilities and requirements: | jdm's thoughts on responsibilities and requirements: | ||