Open Leadership and Events/Working Open: Difference between revisions
Jump to navigation
Jump to search
(Created page and added textual content) |
(Added links in sections 1-3) |
||
| Line 5: | Line 5: | ||
=== Step 1 - DESIGN === | === Step 1 - DESIGN === | ||
To figure out what you’re doing and why, you can: | To figure out what you’re doing and why, you can: | ||
* Write a POP (Purpose-Outcomes-Process) to help you clarify your aims and plans for your work. (worksheet) | * '''Write a POP''' ([https://rockwoodleadership.org/pop-everything-tbt/ Purpose-Outcomes-Process]) to help you clarify your aims and plans for your work. ([https://www.rjweanfdn.org/wp-content/uploads/2015/09/Leading-Powerful-and-Vision-Driven-Meetings-POP-Handout-Noden-Kirk.pdf worksheet]) | ||
* Fill out an Open Canvas to define and share your project goals, community strategy, and needs for resources. (canvas) | * '''Fill out an [https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/develop-an-open-project-strategy-with-open-canvas/ Open Canvas]''' to define and share your project goals, community strategy, and needs for resources. ([http://mzl.la/open-canvas canvas]) | ||
* Write a vision to describe your project’s big idea in a super short form that you can share with everyone and anyone. | * '''[https://mozilla.github.io/open-leadership-training-series/articles/introduction-to-open-leadership/stating-your-project-vision/ Write a vision]''' to describe your project’s big idea in a super short form that you can share with everyone and anyone. | ||
=== Step 2 - BUILD === | === Step 2 - BUILD === | ||
To let people know how to join, you can: | To let people know how to join, you can: | ||
* Create a short text document called a “README” file, to welcome newcomers to your project | * '''Create a short text document called [https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/write-a-great-project-readme/ a “README” file]''', to welcome newcomers to your project | ||
* Create Personas and Pathways for your project, a tool to help you plan and test how you'll interact with new contributors. | * '''Create [https://mozilla.github.io/open-leadership-training-series/articles/building-communities-of-contributors/bring-on-contributors-using-personas-and-pathways/ Personas and Pathways]''' for your project, a tool to help you plan and test how you'll interact with new contributors. | ||
* Write or choose a Code of Conduct, to establish guidelines for how members of your community interact with each other. | * '''Write or choose a [https://mozilla.github.io/open-leadership-training-series/articles/building-communities-of-contributors/write-a-code-of-conduct/ Code of Conduct]''', to establish guidelines for how members of your community interact with each other. | ||
* Write Contributing Guidelines, a set of instructions that explain how new contributors can help out on your project. | * '''Write [https://mozilla.github.io/open-leadership-training-series/articles/building-communities-of-contributors/write-contributor-guidelines/ Contributing Guidelines]''', a set of instructions that explain how new contributors can help out on your project. | ||
* Add an open license to help others understand how they can reuse, remix, and share your work. (choose a license for code or content) | * '''Add an open license''' to help others understand how they can reuse, remix, and share your work. (choose a license for [https://choosealicense.com/ code] or [https://creativecommons.org/choose/ content]) | ||
=== Step 3 - EMPOWER === | === Step 3 - EMPOWER === | ||
To Invite people to collaborate, you can: | To Invite people to collaborate, you can: | ||
* Develop effective communications channels for your project. | * '''Develop [https://mozilla.github.io/open-leadership-training-series/articles/open-communications/ effective communications channels]''' for your project. | ||
* Make personal invitations. People are 4x more likely to contribute if they receive a personal invitation. | * '''Make personal invitations.''' People are 4x more likely to contribute if they receive a personal invitation. | ||
* Mentor new contributors to raise up new leaders in your project. | * '''Mentor [https://docs.google.com/presentation/d/134T7ZebcEmlU-1k84dNr1brXkcf3Cc0erZHucBSwqRA/present?token=AC4w5VgcHOivT2uZfJMJh_XbttZRViJeyg%3A1576523348907&includes_info_params=1&eisi=CLLjxJHvuuYCFYs2ygod3UwGGQ#slide=id.g1088c5b110_0_183 new contributors]''' to raise up new leaders in your project. | ||
=== Step 4 - WORK OPEN === | === Step 4 - WORK OPEN === | ||
| Line 36: | Line 36: | ||
Have questions about where to begin? Drop us a line @MozOpenLeaders or leadopen@mozillafoundation.org. | Have questions about where to begin? Drop us a line @MozOpenLeaders or leadopen@mozillafoundation.org. | ||
=== LICENSE === | |||
https://i.creativecommons.org/l/by/4.0/88x31.png | |||
This work by the Open Leadership & Events Team is licensed under a [http://creativecommons.org/licenses/by/4.0/ Creative Commons Attribution 4.0 International License]. | |||
[[Category:Open Leadership]] | |||
Revision as of 16:57, 9 April 2020
Here at Mozilla, we talk a lot about working openly. The word “open” is even in our team name (Open Leadership & Events). But what does that mean and how does one go about doing that?
There are lots of resources and many ways you can get started on working openly (for example, these great posts by Open Matt). We thought it might be helpful to put together a guide to get you started. Feel free to make a copy of this document and make it your own!
Step 1 - DESIGN
To figure out what you’re doing and why, you can:
- Write a POP (Purpose-Outcomes-Process) to help you clarify your aims and plans for your work. (worksheet)
- Fill out an Open Canvas to define and share your project goals, community strategy, and needs for resources. (canvas)
- Write a vision to describe your project’s big idea in a super short form that you can share with everyone and anyone.
Step 2 - BUILD
To let people know how to join, you can:
- Create a short text document called a “README” file, to welcome newcomers to your project
- Create Personas and Pathways for your project, a tool to help you plan and test how you'll interact with new contributors.
- Write or choose a Code of Conduct, to establish guidelines for how members of your community interact with each other.
- Write Contributing Guidelines, a set of instructions that explain how new contributors can help out on your project.
- Add an open license to help others understand how they can reuse, remix, and share your work. (choose a license for code or content)
Step 3 - EMPOWER
To Invite people to collaborate, you can:
- Develop effective communications channels for your project.
- Make personal invitations. People are 4x more likely to contribute if they receive a personal invitation.
- Mentor new contributors to raise up new leaders in your project.
Step 4 - WORK OPEN
Collaborate & help others be open!
- Join an Open Leaders X cohort.
- Join us for MozFest.
- Share your work on Pulse.
- Keep up with the latest in open programming with our newsletter.
- Explore the Mozilla Wiki for previously developed working open resources.
- Share the open love! Send this list to others who might be interested.
<3 Here’s a sample tweet to get you started:
Want to work more openly but not sure how to start? Check out this Working Open Checklist from @mozilla: https://mzl.la/work-open-checklist #WOLO #workingopen #openleaders
Have questions about where to begin? Drop us a line @MozOpenLeaders or leadopen@mozillafoundation.org.
LICENSE
This work by the Open Leadership & Events Team is licensed under a Creative Commons Attribution 4.0 International License.