Community structure
From Docs
|
Unity Sponsor
Attained if you donate money to Unity
Privileges: Get your name and logo with a link shown on the sponsors page T-Shirts and other goodies can be decided on later
Unity Member
Duties:
- Contribute: Wiki / Translate / Graphics
- Give support in forums / IRC
- Advocate Unity-Linux (PR stuff)
- Attend community meetings
Privileges
- Sponsor priveliges
- Part of the Member list on wiki (must have own page on wiki)
- a hostmask for IRC
- invitations to developer meetings (no voice)
Must agree with to Unity-Code - Unity-Code will be much like the Ubuntu Code of Conduct or the Code of Conduct. A Community meeting will be held soon to establish the Unity Code of Conduct.
Unity Developer
Duties:
- Administration duties of some kind (web, forum,...)
- Active contributions in docs/pkging/bug fixing/BS and other unity tools
- Attend community meetings & Dev meetings
- Use the bug tracker
Privileges:
- All other levels privileges
- Access to devel server/BS/svn/wp-admin and other needed things
- Developer status
Must agree with to Unity-Code - Unity-Code will be much like the Ubuntu Code of Conduct or the Code of Conduct. A Community meeting will be held soon to establish the Unity Code of Conduct.
How New Developers are Selected
After being nominated and vouched for by 3 devs (must be in a meeting?) the new developer enters into a trial period of (3 months?) to prove himself. After an introduction to the new tools, he will get minimal hand-holding from other developers and let him find his way.
Meetings Developer meetings are to be held quarterly or on ‘special/important’ occasions a developer may call a meeting. Community meetings are to be organised by the community themselves. Recommended is twice a year.
