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
<p>Have you built a great new feature or documentation improvement? Drop us a note in the forums or file a feature enhancement request in our issue tracker and let us know about it. We gladly, and regularly accept contributions, and there are a few ways you can participate.</p>
181
+
<p>Have you built a great new feature or documentation improvement? Drop us a note in the forums or file a feature enhancement request in our issue tracker and let us know about it. We gladly, and regularly accept contributions, and there are a serveral ways you can participate.</p>
182
182
183
-
<p>Contributors are given credit for their work, though they must be willing (for licensing purposes) to license and/or assign a copyright of the work. Once you have submitted your contribution we will contact you about providing us with a license or submitting a signed Contributor Agreement. If we request that you assign your copyright of the work to a Terracotta project, you can find the Contributor Agreement document and directions for submission to Terracotta through the link. This document only needs to be filled out once per contributor - not once for each contribution.</p>
183
+
<p>Contributors are given credit for their work, though they must be willing (for licensing purposes) to license and/or assign a copyright of the work.</p>
184
184
185
-
<h3id="contributions-which-do-not-require-full-contributors-license-agreement-cla">Contributions which do not require full Contributor’s License Agreement (CLA)</h3>
<p>A contribution which is an obvious or “drive-by” fix would not require you to sign a CLA rather you will grant us a license to use your contribution. Changes are obvious fixes if they do not introduce any new functionality or creative thinking.</p>
187
+
<p>We follow a DCO / commit-signoff process for accepting contributions.</p>
188
188
189
-
<p>The submissions such as the following would not require you to sign a CLA</p>
189
+
<p>Please review this content here, to be aware of the terms you are agreeing to, and to find the instructions for doing so:</p>
190
190
191
-
<ul>
192
-
<li>Bug fixes that have an obvious simple fix and do not change intended feature functionality;</li>
193
-
<li>Adding logging messages or debugging output;</li>
<p>The following are examples that would still require a signed CLA before your submission would be incorporated into the project:</p>
203
-
204
-
<ul>
205
-
<li>Any code that results in a change in functionality;</li>
206
-
<li>A new feature;</li>
207
-
<li>Feature Enhancement, or anything that alters product behavior;</li>
208
-
<li>A translation; or</li>
209
-
<li>Extensive or creative documentation or comments.</li>
210
-
</ul>
211
-
212
-
<p>If you’re not sure if your fix is obvious you can ask us by sending an email to: tc-oss@wwpdl.vnet.ibm.com.</p>
213
-
214
-
<h4id="agreement-and-grant-of-copyright">Agreement and Grant of Copyright<aname="grant"></a></h4>
215
-
216
-
<p>For those contributions that do not require a CLA: <em>upon submission of Your Contribution you hereby grant IBM and to recipients of the software distributed by IBM a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to install, use, reproduce, prepare derivative works of, publicly display, publicly perform, offer to sell, sell, import, sublicense, transfer, and distribute Your Contribution and any such derivative works.</em></p>
217
-
218
-
<h3id="contributions-which-do-require-a-full-contributors-license-agreement-cla">Contributions which do require a full Contributor’s License Agreement (CLA)</h3>
219
-
220
-
<p>Substantial contributions cannot be accepted at this time as we are currently transitioning to IBM processes and policies.</p>
221
-
222
-
<p>Please check back for updates.</p>
191
+
<p> › › <ahref="https://github.com/ehcache/contributing/blob/main/CONTRIBUTING.md">Instructions for CONTRIBUTING to the Ehcache Project</a></p>
223
192
224
193
<h2id="becoming-an-ehcache-developer">Becoming an Ehcache Developer</h2>
0 commit comments