Donna Benjamin
The Open Practice Library is a community-driven collection of practices for teams to use in support of working together. A "practice" is a behaviour or "trick" that teams use to improve how they achieve their goals. Sometimes those goals are technical, like programming and IT, but all teams can use help defining their practices. Whether you're a teacher, event planner, salesperson, or artist, the process is important. When you're a team, getting on the same page is vital, and that's what the Open Practice Library can help you do.
The Library draws on the experience of practitioners from a wide range of backgrounds. Some of the practices in the Library may feel familiar if you're an agile practitioner or UX researcher. As a sysadmin, site reliability engineer, or software developer, you may also recognize a few practices from your own toolkit.
To support cross-functional teams building their collaboration skills together, the Open Practice Library is open to all to use, study, share, and even contribute, regardless of their role or job function. Many people who use the Library are surprised to learn they can contribute to it! So, below I'll take a look at seven different ways you can contribute to the Open Practice Library and then explore three reasons why you might want to have a go.
We share our practices on LinkedIn, and LOVE hearing how you're using them out there in the wild. Share your experience using the practice. Did it work for you? Would you change anything? Any tips for others using the practice?
Please help grow the Open Practice Library community by telling other people about it and inviting them to contribute too. Follow us on LinkedIn and check out the podcast.
Are you a practitioner with a tried and true method that the Library hasn't yet covered? It'd be great to share that with the world. Note that the content gets licensed under a creative commons license to make sure it's open for all to use and share with others. Review the Library's Editorial Style Guide to learn more about how to write about a practice for the Library.
Ok, ready?
Select Add a Practice from the menu.
(Donna Benjamin, CC BY-SA 4.0)
That takes you to the login page of the content management system (CMS). The Library uses the open source Netlify CMS for moderating contributions.
Select Login with Netlify Identity.
(Donna Benjamin, CC BY-SA 4.0)
Then click Continue with GitHub account.
(Donna Benjamin, CC BY-SA 4.0)
Next, log in with your GitHub details, or create an account (it's free).
(Donna Benjamin, CC BY-SA 4.0)
Once logged in, select New Practice, which takes you to the form to add a practice to the collection.
(Donna Benjamin, CC BY-SA 4.0)
Once you've drafted the new practice, you also need to add your name and GitHub username to the CMS for display on the Practice page. Select Author from the Quick add menu, or choose Author from the Collections menu, and then select New Author.
(Donna Benjamin, CC BY-SA 4.0)
Click the Improve this Practice button and find the links we love section. Post the URL, add a description, and select the category (for example, Video, blog).
You can search for the practice you want to improve, for example, "Affinity Mapping."
Then click on the practice name to open the edit page.
Click the Improve this Practice button and go right ahead and fix it!
See something that's not quite right? Have a suggestion for a feature? Let the community know.
How: Go to the issues page and log into GitHub to add a new issue.
There's a backlog of issues in GitHub that list where help on the website is needed. If you want to roll up your sleeves and help with fixing bugs or developing new features—you can even contribute code.
We have some small expenses, you can contribute cash to our Open Collective fund
Why contribute? Here are four reasons for you to consider:
Contributing to the Open Practice Library is a fun and easy way to participate in a global, open community of practitioners who are all willing to share their knowledge and trying to improve their own ways of working.
Adapted from the original published on OpenSource.com under a CC-BY-SA licence.