161
edits
ParticipationSystems: Difference between revisions
m
I thin I got rid of a blank line. Can't remember. It's been a whole 7 seconds.
m (Commented out template bar thing because it's not working yet.) |
m (I thin I got rid of a blank line. Can't remember. It's been a whole 7 seconds.) |
||
| Line 5: | Line 5: | ||
This program strives to create a Mozilla that is understandable, approachable, collaborative, satisfying to work with, well managed and diverse. | This program strives to create a Mozilla that is understandable, approachable, collaborative, satisfying to work with, well managed and diverse. | ||
If we do this work right | If we do this work right: | ||
* We will have facilitated diversity and inclusion at Mozilla. We will become a benchmark for how to harness the collective intelligence of thousands of people to achieve an ambitious vision | |||
We will have facilitated diversity and inclusion at Mozilla. We will become a benchmark for how to harness the collective intelligence of thousands of people to achieve an ambitious vision | * Community participation will be a core muscle available to all parts of Mozilla. It will be well run and programs will be routinely build in participation because they will provide real value | ||
* High value contributions will result because Mozilla is knowable and understandable, and its pursuits are compelling. People are attracted to the project, see where they can contribute and how to do so | |||
Community participation will be a core muscle available to all parts of Mozilla. It will be well run and programs will be routinely build in participation because they will provide real value | * When interacting with Mozilla, people will naturally locate themselves in the right context and altitude, and they will be able to naturally and appropriately connect with staff | ||
* Their work is enjoyable, they get value out of working on Mozilla projects and they become confident that their efforts are impactful and recognized | |||
High value contributions will result because Mozilla is knowable and understandable, and its pursuits are compelling. People are attracted to the project, see where they can contribute and how to do so | * Mission aligned contributors and leaders will effectively work with us to invent, shape and defend the internet | ||
When interacting with Mozilla, people will naturally locate themselves in the right context and altitude, and they will be able to naturally and appropriately connect with staff | |||
Their work is enjoyable, they get value out of working on Mozilla projects and they become confident that their efforts are impactful and recognized | |||
Mission aligned contributors and leaders will effectively work with us to invent, shape and defend the internet | |||
== Current Challenges == | == Current Challenges == | ||
We have a legacy to clean up: Mozilla is too messy & complicated to engage with all volunteers. | We have a legacy to clean up: Mozilla is too messy & complicated to engage with all volunteers. | ||
Our leadership is unified, but the organization and its “operating system” isn’t yet. We have vestigial walls that need to be taken down, and some new systems that need to get built. | Our leadership is unified, but the organization and its “operating system” isn’t yet. We have vestigial walls that need to be taken down, and some new systems that need to get built. | ||
| Line 48: | Line 43: | ||
#* Identifying legacy systems for participation and migrating them. | #* Identifying legacy systems for participation and migrating them. | ||
#* When: TBD | #* When: TBD | ||
== Program goals == | == Program goals == | ||