Participation: Difference between revisions
Jump to navigation
Jump to search
Asdofindia (talk | contribs) (Convert markdown to wiki markup on the twitter link) Tag: Mobile edit |
|||
| (28 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
{{Participation}} | {{Participation}} | ||
==Community Development at Mozilla== | |||
== | |||
<div style="display:block;border-radius:10px;background-color:rgb(227, 220, 200);padding:20px;margin-top:20px;"> | <div style="display:block;border-radius:10px;background-color:rgb(227, 220, 200);padding:20px;margin-top:20px;"> | ||
[[Image:Mozilla_Participation.svg|right]] | |||
== Who We Are == | == Who We Are == | ||
| Line 10: | Line 9: | ||
=== Our Mission === | === Our Mission === | ||
The Community Development Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement. | |||
We do this by: | |||
* Designing and implementing specific participation initiatives -- in partnership with teams around Mozilla -- that adapt and advance global best-practice on participation | |||
* Recruiting and investing in core contributors mobilizers/leaders, and developing diverse, local and global communities that make individual contribution more impactful | |||
* Delivering software/systems and practices that increase the impact of participation across Mozilla | |||
=== | === Community Development Team Principles === | ||
These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission. | These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission. | ||
| Line 22: | Line 26: | ||
# Participation must provide value for both Mozilla and Mozillians (participants) | # Participation must provide value for both Mozilla and Mozillians (participants) | ||
</div> | </div> | ||
== What We Do == | == What We Do == | ||
=== Working in the open === | |||
The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals. | The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals. | ||
Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [https://github.com/mozilla/participation-org/issues | Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [https://github.com/mozilla/participation-org/issues]. We welcome feedback on the process and approach. | ||
You can also follow along with what we’re doing on the [https://blog.mozilla.org/community/category/participation/ Blog] and by following [https://twitter.com/mozparticipate @MozParticipate on Twitter]. | You can also follow along with what we’re doing on the [https://blog.mozilla.org/community/category/participation/ Blog] and by following [https://twitter.com/mozparticipate @MozParticipate on Twitter]. | ||
=== | A Github Milestone = [https://github.com/mozilla/participation-org/milestones Heartbeat]. | ||
== Joining the Discussion! == | |||
If you'd like to get regular updates and discussions about Participation at Mozilla we have a [https://discourse.mozilla-community.org/c/participation section at Mozilla’s discourse] that you can use as a mailing list as well as an online forum. In fact, once it’s set up you can respond to threads by emails and it will be publish directly into the topic. | |||
== | === The Team === | ||
==== Head of Community Infrastructure ==== | |||
* [https://mozillians.org/u/geroter/ George Roter], Team Leader | |||
==== Community Development ==== | |||
* [https://mozillians.org/u/lucyeoh/ Lucy Harris] - Lead | |||
* | * [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis] | ||
* | * [https://mozillians.org/u/emmairwin/ Emma Irwin] | ||
* | * [https://mozillians.org/u/nukeador/ Rubén Martín] | ||
* [https://mozillians.org/u/couci/ Konstantina Papadea] | |||
* [https://mozillians.org/en-US/u/kelimutu/ Rizki Kelimutu] | |||
==== [[ParticipationSystems|Participation Systems]] ==== | |||
* [https://mozillians.org/u/hmitsch/ Henrik Mitsch] - Lead | |||
* [https://mozillians.org/u/jgiannelos/ John Giannelos] | |||
* [https://mozillians.org/u/akatsoulas/ Anastasios Katsoulas] | |||
* [https://mozillians.org/u/arielle/ Arielle Kilroy] | |||
* [https://mozillians.org/u/comzeradd/ Nikos Roussos] | |||
* [https://mozillians.org/u/yalam96/ Yousef Alam] | |||
* [https://mozillians.org/u/leo/ Leo McArdle] | |||
* [https://mozillians.org/u/viorelaioia/ Viorela Ioia] | |||
Latest revision as of 19:15, 27 February 2018
Community Development at Mozilla
Who We Are
Our Mission
The Community Development Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement.
We do this by:
- Designing and implementing specific participation initiatives -- in partnership with teams around Mozilla -- that adapt and advance global best-practice on participation
- Recruiting and investing in core contributors mobilizers/leaders, and developing diverse, local and global communities that make individual contribution more impactful
- Delivering software/systems and practices that increase the impact of participation across Mozilla
Community Development Team Principles
These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission.
- Participation is when people can freely contribute their energies, time and ideas to support Mozilla’s mission
- In order to keep the web open and participatory it must be shaped by organizations, like Mozilla, who are equally open and participatory
- Participation is at the core of Mozilla’s history and identity and provides a key advantage for Mozilla as an organization
- Participation cannot exist without a culture of openness that allows contributors the opportunity to shape and build Mozilla’s programs and products at every level
- Participation must provide value for both Mozilla and Mozillians (participants)
What We Do
Working in the open
The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals.
Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [1]. We welcome feedback on the process and approach.
You can also follow along with what we’re doing on the Blog and by following @MozParticipate on Twitter.
A Github Milestone = Heartbeat.
Joining the Discussion!
If you'd like to get regular updates and discussions about Participation at Mozilla we have a section at Mozilla’s discourse that you can use as a mailing list as well as an online forum. In fact, once it’s set up you can respond to threads by emails and it will be publish directly into the topic.
The Team
Head of Community Infrastructure
- George Roter, Team Leader