mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-07 22:11:09 +08:00
163 lines
8.4 KiB
Markdown
163 lines
8.4 KiB
Markdown
|
[#]: subject: "7 ways anyone can contribute to Open Practice Library"
|
|||
|
|
[#]: via: "https://opensource.com/article/21/10/open-practice-library"
|
|||
|
|
[#]: author: "Donna Benjamin https://opensource.com/users/kattekrab"
|
|||
|
|
[#]: collector: "lujun9972"
|
|||
|
|
[#]: translator: " "
|
|||
|
|
[#]: reviewer: " "
|
|||
|
|
[#]: publisher: " "
|
|||
|
|
[#]: url: " "
|
|||
|
|
|
|||
|
|
7 ways anyone can contribute to Open Practice Library
|
|||
|
|
======
|
|||
|
|
Contributing to the Open Practice Library is a fun way to participate in
|
|||
|
|
a global community of practitioners who are all willing to share their
|
|||
|
|
knowledge and improve their own ways of working.
|
|||
|
|
![Stack of books for reading][1]
|
|||
|
|
|
|||
|
|
The [Open Practice Library][2] is a community-driven collection of practices for teams to use in support of working together. A "practice" is a behavior 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.
|
|||
|
|
|
|||
|
|
### 1\. Add a comment.
|
|||
|
|
|
|||
|
|
Share your experience using the practice. Did it work for you? Would you change anything? Any tips for others using the practice? Login to the comment system and start a discussion with the community.
|
|||
|
|
|
|||
|
|
**How:** At the bottom of every practice page is a space for comments.
|
|||
|
|
|
|||
|
|
![Add a comment][3]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
To join the conversation, you must sign up for an account on [Hyvor Talk][5].
|
|||
|
|
|
|||
|
|
### 2\. Spread the word.
|
|||
|
|
|
|||
|
|
Please help grow the Open Practice Library community by telling other people about it and inviting them to contribute too. Find the Library on [Twitter][6], [Instagram][7], and check out the [podcast][8].
|
|||
|
|
|
|||
|
|
### 3\. Add your favorite practice.
|
|||
|
|
|
|||
|
|
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][9] to learn more about how to write about a practice for the Library.
|
|||
|
|
|
|||
|
|
Ok, ready?
|
|||
|
|
|
|||
|
|
Select **Add a Practice** from the menu.
|
|||
|
|
|
|||
|
|
![Add a practice][10]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
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**.
|
|||
|
|
|
|||
|
|
![Login with Netlify Identity][11]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
Then click **Continue with GitHub** account.
|
|||
|
|
|
|||
|
|
![Continue with Github][12]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
Next, log in with your GitHub details, or create an account (it's free).
|
|||
|
|
|
|||
|
|
![Log in with Github details][13]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
Once logged in, select **New Practice**, which takes you to the form to add a practice to the collection.
|
|||
|
|
|
|||
|
|
![Select New Practice][14]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
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**.
|
|||
|
|
|
|||
|
|
![Select New Author][15]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
### 4\. Add a helpful resource or link.
|
|||
|
|
|
|||
|
|
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).
|
|||
|
|
|
|||
|
|
![Improve this Practice button][16]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
You can search for the practice you want to improve, for example, "Affinity Mapping."
|
|||
|
|
|
|||
|
|
![Search for practice][17]
|
|||
|
|
|
|||
|
|
(Donna Benjamin, [CC BY-SA 4.0][4])
|
|||
|
|
|
|||
|
|
Then click on the practice name to open the edit page.
|
|||
|
|
|
|||
|
|
### 5\. See a typo?
|
|||
|
|
|
|||
|
|
Click the **Improve this Practice** button and go right ahead and fix it!
|
|||
|
|
|
|||
|
|
### 6\. Add an issue on GitHub.
|
|||
|
|
|
|||
|
|
See something that's not quite right? Have a suggestion for a feature? Let the community know.
|
|||
|
|
|
|||
|
|
**How:** Go to the [issues page][18] and log into GitHub to add a new issue.
|
|||
|
|
|
|||
|
|
### 7\. Help with the website code.
|
|||
|
|
|
|||
|
|
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][19] or developing new features—you can even contribute code.
|
|||
|
|
|
|||
|
|
### Wrap up
|
|||
|
|
|
|||
|
|
Why contribute? Here are three reasons for you to consider:
|
|||
|
|
|
|||
|
|
1. "**While we teach, we learn**" is an old Roman saying.
|
|||
|
|
You deepen your own understanding of a practice you use by writing it down and sharing it with others. Do some research on the background of where the practice came from, help credit the original source, and find examples of its usage.
|
|||
|
|
2. **Improve your writing skills**.
|
|||
|
|
By following the editorial style guide, you are learning to adapt your natural writing style to fit specific criteria. This is a valuable and fundamental communication skill that you can apply in a range of contexts.
|
|||
|
|
3. **Demonstrate leadership**
|
|||
|
|
By sharing your knowledge and expertise with an open, global community, you can help others grow and learn from your depth of experience.
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
[Contributing to the Open Practice Library][20] 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.
|
|||
|
|
|
|||
|
|
You don't need to be a master coder to contribute to open source. Jade Wang shares 8 ways you can...
|
|||
|
|
|
|||
|
|
--------------------------------------------------------------------------------
|
|||
|
|
|
|||
|
|
via: https://opensource.com/article/21/10/open-practice-library
|
|||
|
|
|
|||
|
|
作者：[Donna Benjamin][a]
|
|||
|
|
选题：[lujun9972][b]
|
|||
|
|
译者：[译者ID](https://github.com/译者ID)
|
|||
|
|
校对：[校对者ID](https://github.com/校对者ID)
|
|||
|
|
|
|||
|
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|||
|
|
|
|||
|
|
[a]: https://opensource.com/users/kattekrab
|
|||
|
|
[b]: https://github.com/lujun9972
|
|||
|
|
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/books_read_list_stack_study.png?itok=GZxb9OAv (Stack of books for reading)
|
|||
|
|
[2]: https://openpracticelibrary.com/learn
|
|||
|
|
[3]: https://opensource.com/sites/default/files/uploads/1_add-comment.png (Add a comment)
|
|||
|
|
[4]: https://creativecommons.org/licenses/by-sa/4.0/
|
|||
|
|
[5]: https://talk.hyvor.com
|
|||
|
|
[6]: https://twitter.com/practicelibrary
|
|||
|
|
[7]: https://www.instagram.com/openpracticelibrary
|
|||
|
|
[8]: https://podcasts.apple.com/us/podcast/open-practice-podcast/id1501715186
|
|||
|
|
[9]: https://openpracticelibrary.com/page/editorial/
|
|||
|
|
[10]: https://opensource.com/sites/default/files/uploads/2_add-practice.gif (Add a practice)
|
|||
|
|
[11]: https://opensource.com/sites/default/files/uploads/2_login-netlify.png (Login with Netlify Identity)
|
|||
|
|
[12]: https://opensource.com/sites/default/files/uploads/3_continue-github.png (Continue with Github)
|
|||
|
|
[13]: https://opensource.com/sites/default/files/uploads/4_github_details.png (Log in with Github details)
|
|||
|
|
[14]: https://opensource.com/sites/default/files/uploads/5_new-practice.gif (Select New Practice)
|
|||
|
|
[15]: https://opensource.com/sites/default/files/uploads/6_select-new-author.gif (select New Author)
|
|||
|
|
[16]: https://opensource.com/sites/default/files/styles/medium/public/uploads/7_improve-this-practice.png?itok=ypFLi0uu (Improve this Practice button)
|
|||
|
|
[17]: https://opensource.com/sites/default/files/styles/medium/public/uploads/8_search-for-practice.png?itok=f81s25N8 (Search for practice)
|
|||
|
|
[18]: https://github.com/openpracticelibrary/openpracticelibrary/issues/new
|
|||
|
|
[19]: https://github.com/openpracticelibrary/openpracticelibrary/issues?q=is%3Aissue+is%3Aopen+label%3ABug
|
|||
|
|
[20]: https://openpracticelibrary.com/page/contribution-guide
|