Synchronized build

Author: lektor-bot

contributing-code/index.html

@@ -8,7 +8,10 @@
 <meta property="og:title" content="Contribution Guidelines" />
 
 
-<meta property="og:description" content="We do all of our development on GitHub. If you are not familiar with GitHub or pull requests, here is an excellent guide to get started." />
+<meta property="og:description" content="We do all of our development on
+GitHub. If you are not familiar with
+GitHub or pull requests, here is an excellent guide to get
+started." />
 
 <meta property="og:url" content="/contributing-code/" />
 <meta property="og:type" content="article" />
@@ -29,7 +32,10 @@
 
 <meta name="twitter:card" content="summary_large_image" />
 <meta name="twitter:title" content="Contribution Guidelines">
-<meta name="twitter:description" content="We do all of our development on GitHub. If you are not familiar with GitHub or pull requests, here is an excellent guide to get started.">
+<meta name="twitter:description" content="We do all of our development on
+GitHub. If you are not familiar with
+GitHub or pull requests, here is an excellent guide to get
+started.">
 
 <meta name="twitter:site" content="@creativecommons">
 <meta name="twitter:creator" content="@creativecommons">
@@ -210,7 +216,10 @@
       <div class="container is-paddingless">
         <h1>Contribution Guidelines</h1>
         <div class="description column is-9 is-paddingless">
-          <p>We do all of our development <a href="https://github.com/creativecommons/">on GitHub</a>. If you are not familiar with GitHub or pull requests, <a href="https://guides.github.com/activities/hello-world/">here is an excellent guide to get started</a>.</p>
+          <p>We do all of our development <a href="https://github.com/creativecommons/">on
+GitHub</a>. If you are not familiar with
+GitHub or pull requests, <a href="https://guides.github.com/activities/hello-world/">here is an excellent guide to get
+started</a>.</p>
 
         </div>
       </div>
@@ -293,73 +302,122 @@ <h4 class="b-header">On this page</h4>
 
                   </li>
 
+                  <li>
+                    <a class="link" href="#donations">Donations</a>
+                    
+                  </li>
+                
               </ul>
             </aside>
           </div>
         </div>
         <div class="column content is-three-quarters">
-          <h2 id="finding-an-issue">Finding an issue</h2><p>Here's a list of <a href="/projects/">all our current projects</a>. We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.</p>
-<p>We make extensive use of issue labels to designate the priority, status and beginner-friendliness of various issues. We have a standard set of labels across all projects, <a href="/contributing-code/repo-labels/">documented here</a>. Here are some of the ones that are most relevant to finding a good issue to work on:</p>
+          <h2 id="finding-an-issue">Finding an issue</h2><p>Here's a list of <a href="/projects/">all our current projects</a>. We use GitHub issues
+associated with each project to track the work associated with that project.
+That's where you can find things to work on.</p>
+<p>We make extensive use of issue labels to designate the priority, status and
+beginner-friendliness of various issues. We have a standard set of labels
+across all projects, <a href="/contributing-code/repo-labels/">documented here</a>. Here
+are some of the ones that are most relevant to finding a good issue to work on:</p>
 <ul>
 <li><strong>Issues available for community contribution:</strong><ul>
 <li>The following tags mark issues that are open for community contribution:<ul>
-<li><span class="gh-label friendliness">help wanted</span> : Open to participation from the community but not necessarily beginner-friendly</li>
-<li><span class="gh-label friendliness">good first issue</span> : Open to participation from the community and friendly towards new contributors</li>
+<li><span class="gh-label friendliness">help wanted</span>: Open to
+participation from the community but not necessarily beginner-friendly</li>
+<li><span class="gh-label friendliness">good first issue</span>: Open to
+participation from the community and friendly towards new contributors</li>
 </ul>
 </li>
 <li>You do not need our permission to work on one of these issues.</li>
-<li>You may work on an issue labeled <span class="gh-label friendliness">good first issue</span> even if it's not your first issue.</li>
+<li>You may work on an issue labeled <span class="gh-label friendliness">good
+first issue</span> even if it's not your first issue.</li>
 </ul>
 </li>
 <li><strong>Issues not available for community contribution:</strong><ul>
-<li>The following tags mark issues that are <em>not</em> open for community contribution:<ul>
-<li><span class="gh-label friendliness">🔒 staff only</span> : Requires infrastructure access or institutional knowledge that would be impractical to provide to the community</li>
+<li>The following tags mark issues that are <em>not</em> open for community
+contribution:<ul>
+<li><span class="gh-label friendliness">🔒 staff only</span>: Requires
+infrastructure access or institutional knowledge that would be
+impractical to provide to the community</li>
 </ul>
 </li>
 <li>Do not work on these.</li>
 </ul>
 </li>
 <li><strong>Issues not ready for work:</strong><ul>
-<li>The following tags mark issues that are <em>not</em> open for community contribution:<ul>
-<li><span class="gh-label status-neutral">🚧 status: blocked</span>: Blocked by other work that needs to be done first</li>
-<li><span class="gh-label status-dark">🧹 status: ticket work required </span>: Needs additional work before it is ready to be taken up</li>
-<li><span class="gh-label status-darker">🚦 status: awaiting triage</span>: Has not been triaged by a maintainer</li>
+<li>The following tags mark issues that are <em>not</em> open for community
+contribution:<ul>
+<li><span class="gh-label status-neutral">🚧 status: blocked</span>: Blocked
+by other work that needs to be done first</li>
+<li><span class="gh-label status-dark">🧹 status: ticket work required
+</span>: Needs additional work before it is ready to be taken up</li>
+<li><span class="gh-label status-darker">🚦 status: awaiting triage</span>:
+Has not been triaged by a maintainer</li>
 </ul>
 </li>
 <li>Do not work on these.</li>
 </ul>
 </li>
 <li><strong>Issues without any of the above labels:</strong><ul>
 <li>These issues <em>may</em> (or may not) be open for contribution.</li>
-<li>Please add a comment asking one of the maintainers to triage the issue and label it as appropriate.</li>
+<li>Please add a comment asking one of the maintainers to triage the issue and
+label it as appropriate.</li>
 </ul>
 </li>
 </ul>
-<p>You can use our <a href="/contributing-code/issue-finder/">Issue Finder tool</a> to find a good issue that matches your skills and familiarity with our software and community.</p>
+<p>You can use our <a href="/contributing-code/issue-finder/">Issue Finder tool</a> to find a
+good issue that matches your skills and familiarity with our software and
+community.</p>
 <p>Some helpful saved searches on GitHub than can assist with finding an issue:</p>
 <ul>
-<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+-linked%3Apr">issues labeled <span class="gh-label friendliness">good first issue</span></a></li>
-<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+-linked%3Apr">issues labeled <span class="gh-label friendliness">help wanted</span></a></li>
-<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Apr+is%3Aopen+label%3A%22help+wanted%22">PRs labeled <span class="gh-label friendliness">help wanted</span></a></li>
+<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+-linked%3Apr">issues labeled <span class="gh-label friendliness">good first
+issue</span></a></li>
+<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+-linked%3Apr">issues labeled <span class="gh-label friendliness">help
+wanted</span></a></li>
+<li><a href="https://github.com/search?q=org%3Acreativecommons+is%3Apr+is%3Aopen+label%3A%22help+wanted%22">PRs labeled <span class="gh-label friendliness">help
+wanted</span></a></li>
 </ul>
-<p>Check the issue comments/labels to see whether someone else has indicated that they are working on it. If someone is already working on it and there has been activity within the last 7 days, you may want to find a different issue to work on.</p>
-<h2 id="contribution-process">Contribution process</h2><p>Once you've found an issue you'd like to work on, please follow these steps to make your contribution:</p>
+<p>Check the issue comments/labels to see whether someone else has indicated that
+they are working on it. If someone is already working on it and there has been
+activity within the last 7 days, you may want to find a different issue to work
+on.</p>
+<h2 id="contribution-process">Contribution process</h2><p>Once you've found an issue you'd like to work on, please follow these steps to
+make your contribution:</p>
 <ol>
-<li>Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue.</li>
-<li>Write your code and submit your pull request. Be sure to read and follow our <strong><a href="/contributing-code/pr-guidelines/">pull request guidelines</a></strong>!</li>
+<li>Comment on it and say you're working on that issue. This is to avoid
+conflicts with others also working on the issue. If you've followed the
+guidelines above, you don't need to ask permission to start work on an
+issue.</li>
+<li>Write your code and submit your pull request. Be sure to read and follow our
+<strong><a href="/contributing-code/pr-guidelines/">pull request guidelines</a>!</strong></li>
 <li>Wait for code review and address any issues raised as soon as you can.</li>
 </ol>
-<p><strong>A note on collaboration:</strong> We encourage people to collaborate as much as possible. We especially appreciate contributors reviewing each others pull requests, as long as you are <a href="https://medium.com/@otarutunde/comments-during-code-reviews-2cb7791e1ac7">kind and constructive</a> when you do so.</p>
+<p><strong>A note on collaboration:</strong> We encourage people to collaborate as much as
+possible. We especially appreciate contributors reviewing each others pull
+requests, as long as you are <a href="https://medium.com/@otarutunde/comments-during-code-reviews-2cb7791e1ac7">kind and constructive</a> when you
+do so.</p>
 <h2 id="proposing-a-new-issue">Proposing a new issue</h2><p>If you want to work on something that there is no GitHub issue for, follow these steps:</p>
 <ol>
-<li>Create a a new GitHub issue associated with the relevant repository and propose your change there. Be sure to include implementation details and the rationale for the proposed change.<ul>
-<li>We are very reluctant to accept random pull requests without a related issue created first.</li>
+<li>Create a new GitHub issue associated with the relevant repository and
+propose your change there. Be sure to include implementation details and the
+rationale for the proposed change.<ul>
+<li>We are very reluctant to accept random pull requests without a related
+issue created first.</li>
 </ul>
 </li>
-<li>The issue will automatically have the <span class="gh-label status-darker">🚦 status: awaiting triage</span> label applied. Wait for a project maintainer to evaluate your issue and decide whether it's something that we will accept a pull request for.</li>
-<li>Once the project maintainer has approved the issue and removed the <span class="gh-label status-darker">🚦 status: awaiting triage</span> label, you may start work on code as described in the "Contribution process" section above.</li>
+<li>The issue will automatically have the <span class="gh-label
+status-darker">🚦 status: awaiting triage</span> label applied. Wait for a
+project maintainer to evaluate your issue and decide whether it's something
+that we will accept a pull request for.</li>
+<li>Once the project maintainer has approved the issue and removed the <span
+class="gh-label status-darker">🚦 status: awaiting triage</span> label, you
+may start work on code as described in the "Contribution process" section
+above.</li>
 </ol>
 <p>When in doubt, ask a question on <a href="/community/">one of our community forums</a>.</p>
+<h2 id="donations">Donations</h2><p>Recurring donations to Creative Commons Open Source can be made via <a href="https://github.com/sponsors/creativecommons">Sponsor
+@creativecommons on GitHub
+Sponsors</a>.</p>
 
         </div>
       </div>