Contribute/What makes a pathway: Difference between revisions

Jump to navigation Jump to search
Line 105: Line 105:
#*'''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)
== B. Project Communication and Documentation ==
== B. Project Communication and Documentation ==
# Task tracking and communication. Identify and document the following:
# Identify communication channels:
* Where are tasks tracked?  
#* irc
* Can contributors access this?  
#* mailinglist
* How do contributors pick up tasks from this system and submit their work?
#* vidyo
* How are tasks categorized such that contributors can easily find tasks that matches their skills and available resources?
#* skype
#* regular meeting times
#* project leads, mentors
#* bug tracker details
#* project files (e.g. source code)
# '''Task tracking and communication.''' Identify and document the following:
#* Where are tasks tracked?  
#* Can contributors access this?  
#* How do contributors pick up tasks from this system and submit their work?
# '''Categorize tasks.''' Identify those tasks that differ from the minimum viable contribution in terms of required skills, knowledge and/or access. For each grouping of these tasks, identify and document:
#** what is the prerequisite Mozilla project experience?
#** what are the prerequisite skills?
#** what are the prerequisite tasks?
#** what are the required materials?
#** in that documentation, identify and address any roadblocks (e.g. requires access to staff-only resources or require a high-level of undocumented knowledge)


== C. Supporting & Scaling ==
== C. Supporting & Scaling ==
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,698

edits

Navigation menu