Abstract

OSE's social capital warrants Linux.org-scale contribution volume, yet this potential is almost entirely untapped (.1℅ at most). To address this, OSE is developing its HR towards a professional organizational level, without a budget, based on learnings from the Rare Genomics Institute's HR department - who are friends we met at TED. OSE's first step is hiring a recruiting manager, with promotion track to VP of HR. Current recruiting goals include an Engineering Team and the Documentation Team, aimed at recruiting and training people to hold the official title of OSE Developer. To support these projects, Curriculum Development is required for generating training materials for all collaborators on open source culture and tool chains. Also, a documentation team is needed to support the project with Remote Extreme Build documentation, video production, graphics assets, and generation of CAD assets for existing projects. To bind the project with common culture and to build a Distributive Enterprise development community, we are developing a podcast to pump open economic culture through the internet.

Overview

All Engineering and Documentation Team members are required to commit 10 hours of work per week on average
Duration of commitment is 3 months, after which we do a Review
People accepted to the Engineering or Documentation Teams hold the official title of OSE Developer and are awarded a positional email at the opensourceecology domain for the duration of their commitment.
A Product Owner and Process Manager take on leadership of the Engineering Team.
A minimum viable team to make for active development consists of a Process Manager, Product Owner, and rest of the Engineering Team.
For a team to be high performing (rapid development velocity) - there must be no less than 12 active members on the Engineering Team and Documentation Team.
The development team is posted at the OSE Developers wiki page. This page lists active and past developers.
HR maintains the OSE Developer wiki page, and facilitates on- and off-boarding.
People who are not full OSE Devs are marked as OSE Contributors, and may engage in any ad-hoc development tasks as well as on development tasks from the formal OSE Roadmap.