Webdev/Web Production/Community/Conversion Points: Difference between revisions
< Webdev | Web Production | Community
Bsternthal (talk | contribs) (Created page with "The following expand upon: https://wiki.mozilla.org/Contribute/Webdev#Conversion_Points #'''Ready to contribute:''' #* Person has found a task and communicated interest. #* P...") |
Bsternthal (talk | contribs) No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Expanding upon: [[Contribute/Webdev#Conversion_Points]] | |||
#'''Ready to contribute:''' | #'''Ready to contribute:''' | ||
#* Person has found a task and communicated interest. | #* Person has found a task and communicated interest. | ||
#* Person has any project pre-reqs completed. | #* Person has any project pre-reqs completed. | ||
#* Person understands the flow of task | #* Person understands the complete flow of work, from task initiation through completion. | ||
#'''First contribution:''' contributor has submitted first contribution successfully | #'''First contribution:''' contributor has submitted first contribution successfully | ||
#'''Active contributor:''' contributor is making regular and/or high-impact contributions | #'''Active contributor:''' contributor is making regular and/or high-impact contributions | ||
#* Person can take bugs in bugzilla. https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html | #* Person can take bugs in bugzilla. https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html | ||
#* Person is granted an account on kanbanery - <span style="color:red">How we grant users this privilege is up for debate. I like having contributors request this and we grant it based on some criteria (like bugzilla).</span> | #* Person is granted an account on kanbanery - <span style="color:red">How we grant users this privilege is up for debate. I like having contributors request this and we grant it based on some criteria (like bugzilla).</span> | ||
#* Invited to be a project guide. | |||
#'''Privileged contributor:''' contributor, through regular, on-going activity, has earned sufficient trust and can now contribute via privileged activities (e.g. approving pull requests) | #'''Privileged contributor:''' contributor, through regular, on-going activity, has earned sufficient trust and can now contribute via privileged activities (e.g. approving pull requests) | ||
#* Invited to meetings | #* Invited to meetings. | ||
#* Allowed to merge pull requests (within their knowledge domain). | |||
#* Can take critical path tasks. | |||
Latest revision as of 22:43, 10 June 2014
Expanding upon: Contribute/Webdev#Conversion_Points
- Ready to contribute:
- Person has found a task and communicated interest.
- Person has any project pre-reqs completed.
- Person understands the complete flow of work, from task initiation through completion.
- First contribution: contributor has submitted first contribution successfully
- Active contributor: contributor is making regular and/or high-impact contributions
- Person can take bugs in bugzilla. https://bugzilla.mozilla.org/page.cgi?id=get_permissions.html
- Person is granted an account on kanbanery - How we grant users this privilege is up for debate. I like having contributors request this and we grant it based on some criteria (like bugzilla).
- Invited to be a project guide.
- Privileged contributor: contributor, through regular, on-going activity, has earned sufficient trust and can now contribute via privileged activities (e.g. approving pull requests)
- Invited to meetings.
- Allowed to merge pull requests (within their knowledge domain).
- Can take critical path tasks.