OSE Developers: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 11: Line 11:
Development teams should have 12-24 people to show clear and visible development velocity. An interdisciplinary team is needed because many projects include elements of mechanics, electronics, hydraulics, sensors, software, etc. In addition, graphics, media, marketing, and business development skills are used in taking products to full releases as [[Distributive Enterprise]]. An effective team works on projects taken from the perspective of module-based design - where each project is broken down into modules that can be developed in parallel according to the task breakdown of the [[Development Template]]. Modularity applies not only to techical, but also to organizational, business, and marketing areas. Development cycles are run on a quarterly basis (the 90 day period), with the intended outcome being a product release.  If OSE Developers are required to contribute 10 hours per week, then the 12 person team is effectively a 3-person full time equivalent. This is the minimum required for visible progress. Once a well-performing team is established, new teams may form. The minimum number of Developers for starting a new development team is 12. Our goal is to create 12 teams of 12 by end of 2017.
Development teams should have 12-24 people to show clear and visible development velocity. An interdisciplinary team is needed because many projects include elements of mechanics, electronics, hydraulics, sensors, software, etc. In addition, graphics, media, marketing, and business development skills are used in taking products to full releases as [[Distributive Enterprise]]. An effective team works on projects taken from the perspective of module-based design - where each project is broken down into modules that can be developed in parallel according to the task breakdown of the [[Development Template]]. Modularity applies not only to techical, but also to organizational, business, and marketing areas. Development cycles are run on a quarterly basis (the 90 day period), with the intended outcome being a product release.  If OSE Developers are required to contribute 10 hours per week, then the 12 person team is effectively a 3-person full time equivalent. This is the minimum required for visible progress. Once a well-performing team is established, new teams may form. The minimum number of Developers for starting a new development team is 12. Our goal is to create 12 teams of 12 by end of 2017.


The project teams work together on current [[Development Priorities]] as the official development pathway. Tasks not on the Development Priorities
The project teams work together on current [[Development Priorities]] and only on the official tasks at the [[Critical Path]] and consistent with the 20 year [[OSE Roadmap]]. Other projects may be taken up independently by contributing to the OSE Wiki, but core resources of OSE Developers will be allocated only to the Critical Path.


'''To apply, please go to [[OSE_Developer_Initial_Application]].
'''To apply, please go to [[OSE_Developer_Initial_Application]].''' Fill it out, and then we can set up a first interview at your earliest convenience.

Revision as of 18:49, 31 January 2017


HintLightbulb.png Hint: Last Updated 1/17

OSE Developers are the official members of the OSE Engineering or Documentation Teams. This is a globally distributed volunteer team of designers, documenters, and prototypers. OSE developers commit a minimum of 10 hours per week to a coordinated development process on key OSE priorities, for a 3 month or longer duration. After the 3 month mark, OSE Developers have an option to continue.

The title of volunteer still has formal requirements of collaboration on active working teams, and is not to be taken lightly. The expectations are similar to the requirements in a 'regular job,' with timelines, project plans and team responsibilities. OSE Developers are selected for participation based on successful completion of the application process - up to a basic proficiency test in open source computer aided design (CAD) - the OSE FreeCAD Test. The application process is maintained by the HR Team, and the on-boarding process is shown at the OSE Developer Initial Application page.

The OSE Developer is the highest status of OSE development collaboration. The title of OSE Developer marks the official development team that is working actively on the OSE Roadmap. Otherwise, ad-hoc contributors are welcome to contribute to the OSE Wiki, the official development platform of the OSE project.

Development Teams must include a Heavyweight Product Manager, a Product Owner, and a Process Manager to steward a Concurrent Engineering process. Member requirements are an open mind - as any of the technical skills, such as FreeCAD 101, can be learned with a few hours of practice. We are looking for a mindset of avid learning across different disciplines as the primary requirement. We are position this opportunity as a chance to learn diverse technical skills.

Development teams should have 12-24 people to show clear and visible development velocity. An interdisciplinary team is needed because many projects include elements of mechanics, electronics, hydraulics, sensors, software, etc. In addition, graphics, media, marketing, and business development skills are used in taking products to full releases as Distributive Enterprise. An effective team works on projects taken from the perspective of module-based design - where each project is broken down into modules that can be developed in parallel according to the task breakdown of the Development Template. Modularity applies not only to techical, but also to organizational, business, and marketing areas. Development cycles are run on a quarterly basis (the 90 day period), with the intended outcome being a product release. If OSE Developers are required to contribute 10 hours per week, then the 12 person team is effectively a 3-person full time equivalent. This is the minimum required for visible progress. Once a well-performing team is established, new teams may form. The minimum number of Developers for starting a new development team is 12. Our goal is to create 12 teams of 12 by end of 2017.

The project teams work together on current Development Priorities and only on the official tasks at the Critical Path and consistent with the 20 year OSE Roadmap. Other projects may be taken up independently by contributing to the OSE Wiki, but core resources of OSE Developers will be allocated only to the Critical Path.

To apply, please go to OSE_Developer_Initial_Application. Fill it out, and then we can set up a first interview at your earliest convenience.