Participation/Resources/Designing for participation/Documentation: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 10: Line 10:
*Most importantly, have fun and be open to the unexpected.
*Most importantly, have fun and be open to the unexpected.


=Why Run or Participate in Designing for Participation=
=Purpose & Goals=
 
==what's the goal of this workshop?==
Designing for Participation was created in order to get Mozilla community members to think about how they can structure the work Mozilla does to better enable contributions from anywhere. As such the workshop has three goals:
*impart on participants some best practices about how to design tasks to better enable participation
*foster a conversation where best practices and ideas can be surfaced and critically assessed, particularly around how suggestion may or may not be relevant to areas the participants work on
*provide participants with action items they can take back to where they contribute to Mozilla that will help increase opportunities for participation from community members
*share differing experiences around the possibilities and obstacles to participation between managers, employees, staff, volunteers, newcomers and veteran contributors.
 
==who should participate?==
Almost anyone at Mozilla should feel like this is open to them. "Roles" that might want to participate or lead this workshop include:
*module owners
*newcomers
*veterans
*staff
*volunteers
*managers


There are lots of reasons one might want to run or participate in Designing for Participation. Some of the more common reasons include:
Some of the more common questions participants often have that make them a good fit for the course include:
*We are starting a new product/activity/function and want to think about how we can encourage community participation
*We are starting a new product/activity/function and want to think about how we can encourage community participation
*I've just moved to/been assigned as a manager to a new area and we want to expand how we can encourage community participation
*I've just moved to/been assigned as a manager to a new area and we want to expand how we can encourage community participation
Line 18: Line 34:
*I need to expand the scope of our work without increasing the financial resources I have
*I need to expand the scope of our work without increasing the financial resources I have
*I'm a manager and I'd like some tools for thinking about how to evaluate how effectively those who work for me create space and opportunity for community participation.
*I'm a manager and I'd like some tools for thinking about how to evaluate how effectively those who work for me create space and opportunity for community participation.
 
*I'm a contributor and I'd love to expand how much I contribute or have been trying to explore new parts of the project to contribute to with little success.
=Purpose & Goals=
 
 
- what's the goal of this workshop?
 
- who are some potential audiences?
 
- learning objectives for each audience
 
 
 
Module owners and those creating a project
 
 
 
Managers who want to learn what their employees should be doing to encourage greater participation from community members
 




People who want to contribute more
==assumptions==
It is worth noting that this course is not for everyone. Participants in this course are assumed to know what an open source project is and, at a high level at least, how it works.


=Logistics=


=Syllabus breakdown=


Pull out "Goals" slide (#3)
Pull out "Goals" slide (#3)
Confirmed users
288

edits