Teams Description
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenERP Community Leaders |
Fix Committed
|
High
|
Unassigned |
Bug Description
Write a sexy slideshow that presents all OpenERP teams:
- community
- commiters
- drivers
- quality
- experts-...
- l10n-...
- community-leaders
We need a clean hierarchy and advantages for contributors to grow in this hierarchy.
For each team:
- introduction
- their role, advantages and responsibilities
- requirements to apply
- their impact on the development flow
This document must allow us to communicate efficiently to the community.
A very quick example: "The Drivers"
Drivers
======
The OpenERP drivers are people from the community that proved to have a strong market knowledge. Their role is to classify and manage priorities on bugs, features and improvements requests. The community report a lot of bugs, whishlist and features requests. Their role is to emphasize what's important/urgent and what's not by planifying on milestones. The R&D team will work on milestones as proposed by the drivers.
This team does not perform developments but provide feedback based on their market knowledge to drive developments. Their role is to design a strong, smart and fast growing product by emphasing godd ideas that come from the community.
Requirements to Apply: you must have published at least 3 customers success stories on the OpenERP planet.
Changed in openerp-community-leaders: | |
importance: | Undecided → High |
Changed in openerp-community-leaders: | |
status: | New → Fix Committed |
Hi Sajid,
Where was this committed? I see no code on this project...