You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h1>🌍 Community<aclass="headerlink" href="#community" title="Link to this heading"></a></h1>
99
+
<sectionid="submitting-issues-ideas-suggestions">
100
+
<h2>Submitting Issues, Ideas, & Suggestions<aclass="headerlink" href="#submitting-issues-ideas-suggestions" title="Link to this heading"></a></h2>
101
+
<p><em>Have an issue? Seeking Support?</em>
102
+
- <aclass="reference external" href="https://github.com/kylejgillett/sounderpy/issues">Open a GitHub Issue</a>
103
+
- Shoot me an email! (<aclass="reference external" href="mailto:kyle.gillett%40und.edu">kyle<span>.</span>gillett<span>@</span>und<span>.</span>edu</a>)
104
+
- Shoot me a DM on X (@wxkylegillett)</p>
105
+
</section>
106
+
<sectionid="contributing-to-sounderpy">
107
+
<h2>Contributing to SounderPy<aclass="headerlink" href="#contributing-to-sounderpy" title="Link to this heading"></a></h2>
108
+
<p>Contributions to this library are encouraged! Below are a few simple guidelines to follow if you are considering helping out this package.</p>
109
+
<ulclass="simple">
110
+
<li><p><strong>Tackling open issues on Github</strong> – feel free to search through unresolved <aclass="reference external" href="https://github.com/kylejgillett/sounderpy/issues">Github Issues</a> and propose a solution!</p></li>
111
+
<li><p><strong>Contributing your code</strong> – if you have made local modifications to SounderPy, feel free to suggest adding your changes by opening a <aclass="reference external" href="https://github.com/kylejgillett/sounderpy/pulls">GitHub pull request</a>.</p></li>
112
+
<li><p><strong>Adding an entirely new feature</strong> – similarly to above, open a <aclass="reference external" href="https://github.com/kylejgillett/sounderpy/pulls">GitHub pull request</a> with the proposed additions.</p></li>
113
+
<li><p><strong>Creating tutorials</strong> – So much of the code we write is best understood with comprehensive tutorials. I highly encourage anyone to build tutorials that explain the code, explain a specific use/task, or to simply provide more examples. Do so by opening a <aclass="reference external" href="https://github.com/kylejgillett/sounderpy/pulls">GitHub pull request</a>.</p></li>
114
+
</ul>
115
+
<p><strong>To contribute to SounderPy…</strong></p>
116
+
<olclass="arabic">
117
+
<li><p>In GitHub, fork the SounderPy repository (repo) into your profile.</p></li>
118
+
<li><p>Pull down the forked repo to your local machine.</p></li>
119
+
<li><p>After making changes, commit them to your forked repo.</p></li>
120
+
<li><p>Finally, open a Pull Request.</p>
121
+
<blockquote>
122
+
<div><ulclass="simple">
123
+
<li><p>Pull requests, for any contribution, should include a detailed explanation of the code, why it’s needed, and what it fixes/replaces.</p></li>
124
+
<li><p>Ensure that your code is well formatted, clean, commented and easy to read.</p></li>
125
+
<li><p><strong>IMPORTANT</strong>: The goal of SounderPy is to make sounding analysis available to everyone – beginners and experts alike. As such, SounderPy code should be <em>easy to read</em>, not just well-documented. In the case of this library, code that is clean and <em>easy to read</em> is valued more over code that is “fancy”, “too-complex” and harder to read.</p></li>
0 commit comments