OSE Organization Chart
Jump to navigation
Jump to search
November, 2012
see other models at Organization
Linked from Shuttleworth Project Pitch - Staff
Sequencing Rationale - Up to Mid-2013
- Machine Designers are the core developers. On the core prototyping front - we currently have 2 Machine Designers. We intend to build our team to 6 machine designers by March 2013.
- Product Lead directs machine design effort. When we reach 4 machine designers (Jan. 2013), we will need to recruit a Product Lead to oversee the Machine Designers.
- Documentation Director assures that documentation is produces alongside the development process. This includes video instructionals and technical documentation. Documentation Director develops a production plan for instructionals and progress videos with the Videographer. The Product Lead is responsible for machine documentation until a Documentation Director is recruited. Docmentation Director works with OSHWA on documentation standards and reports to Product Lead.
- Community Manager facilitates remote contributions. To facilitate an increasing number of contributions from remote collaborators, we need the Community Manager to guide remote developers - to complement the work of dedicated Machine Designers. While the Product Lead manages the overall technical development. The Community Manager recruits both high level Technical Advisors for specific projects and leads our hands-on development hackathons, which we call Flash Mobs.
- Operations Manager handles all the moving parts by interfacing between the Executive Director and staff. The Operations Manager coordinates the interplay between machine design, machine builds, remote collaboration, and documentation.
- Production Director leads production and sales to generate earnings - to make the operation financially self-sustaining financially.
Details
- Machine designers follow OSE Specifications in general, and build machines according to Open Source Hardware Modularity Pattern Language, follow GVCS Rollout Sequencing, and follow the GCVCS Module Ecology White Paper - defining the design standards and interfaces for the main modules. See preliminary design of modules in the GVCS Modularity Pattern Language.
June, 2012
https://docs.google.com/drawings/d/1xGbOx8XkmAXcPxZ2-edTvAIlhDFWlOC9RcyzKBAb3CY/edit