<p>We would love for you to contribute to CPL and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow:</p>
<ulclass="simple">
<li><p><aclass="reference external"href="#found-a-bug">Issuses and Bugs</a></p></li>
<p>If you find a bug in the source code, you can help us by <aclass="reference external"href="#submitting-an-issue">submitting an issue</a> to our <aclass="reference external"href="https://git.sh-edraft.de/sh-edraft.de/sh_cpl/">Gitea Repository</a>. Even better, you can <aclass="reference external"href="#submitting-a-pull-request">submit a Pull Request</a> with a fix.</p>
<p>You can request a new feature by submitting an issue to our <aclass="reference external"href="https://git.sh-edraft.de/sh-edraft.de/sh_cpl/">Gitea Repository</a>. If you would like to implement a new feature, please consider the size of the change in order to determine the right steps to proceed:</p>
<p>For a Major Feature, first open an issue and outline your proposal so that it can be discussed. This process allows us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.</p>
<p>Note: Adding a new topic to the documentation, or significantly re-writing a topic, counts as a major feature.</p>
<p>Small Features can be crafted and directly submitted as a <aclass="reference external"href="#submit-pr">Pull Request</a>.</p>
<p>Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.</p>
<p>We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we require that you provide a minimal reproduction. Having a minimal reproducible scenario gives us a wealth of important information without going back and forth to you with additional questions.</p>
<p>A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem) as well as confirm that we are fixing the right problem.</p>
<p>We require a minimal reproduction to save maintainers’ time and ultimately be able to fix more bugs. Often, developers find coding problems themselves while preparing a minimal reproduction. We understand that sometimes it might be hard to extract essential bits of code from a larger codebase but we really need to isolate the problem before we can fix it.</p>
<p>Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don’t hear back from you, we are going to close an issue that doesn’t have enough info to be reproduced.</p>
<p>Before you submit your Pull Request (PR) consider the following guidelines:</p>
<ol>
<li><p>Search the <aclass="reference external"href="https://git.sh-edraft.de/sh-edraft.de/sh_cpl/">repository</a> for an open or closed PR that relates to your submission. You don’t want to duplicate existing efforts.</p></li>
<li><p>Be sure that an issue describes the problem you’re fixing, or documents the design for the feature you’d like to add. Discussing the design upfront helps to ensure that we’re ready to accept your work.</p></li>
<li><p>Fork the sh-edraft.de/sh_cpl repo.</p></li>
<li><p>In your forked repository, make your changes in a new git branch:</p>
<p>Note: the optional commit <codeclass="docutils literal notranslate"><spanclass="pre">-a</span></code> command line option will automatically “add” and “rm” edited files.</p>
</li>
<li><p>Push your branch to the <aclass="reference external"href="https://git.sh-edraft.de/sh-edraft.de/sh_cpl/">repository</a>:</p>
<p>The sh-edraft.de team reserves the right not to accept pull requests from community members who haven’t been good citizens of the community. Such behavior includes not following the CPL <aclass="reference external"href="#coding-rules">coding rules</a> and applies within or outside of CPL managed channels.</p>
