-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Configured CLA and added documentation #issue-54
- Loading branch information
Showing
7 changed files
with
88 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,3 +14,4 @@ | |
- [Micronaut HTTP Client documentation](https://docs.micronaut.io/latest/guide/index.html#httpClient) | ||
|
||
|
||
|
83 changes: 83 additions & 0 deletions
83
micronautpi4j-utils/src/docs/asciidoc/contributingToLibrary.adoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
== Contribute to the Pi4Micronaut Library | ||
|
||
*Get Familiar with the Library* | ||
|
||
Before making contributions,understand the purpose and functionality of the Pi4Micronaut library. Review the library documentation, any related articles, or tutorials. | ||
|
||
*Set Up Your Development Environment* | ||
|
||
Fork the library's repository from the GitHub. | ||
Clone your fork locally. | ||
Follow setup instructions provided in the repository's README or ADOC files. | ||
|
||
*Understand the Contribution Process* | ||
|
||
Familiarize yourself with the library's contribution guidelines. | ||
Understand the community guidelines. | ||
Find out the preferred method of communication (e.g., issues, mailing list, discord). | ||
|
||
*Identify a Way to Contribute* | ||
|
||
Bug fixes: Look for open issues tagged as 'bug' or report new ones. | ||
|
||
New features: Discuss new ideas before implementing, to gauge interest and get guidance. | ||
|
||
Documentation: Contribute to the README, ADOC or other documentation. | ||
|
||
Testing: Improve or expand the test suite. | ||
|
||
Refactoring: Optimize existing code or improve its readability. | ||
|
||
*Making Changes* | ||
|
||
Always create a new branch for your changes. | ||
Follow the library's coding style and standards. | ||
Write clean, well-documented code. | ||
Add or update tests for your changes, if necessary. | ||
Commit frequently with meaningful commit messages. | ||
|
||
*Test Your Changes* | ||
|
||
Ensure that all tests pass. | ||
Manually test your changes for unforeseen issues. | ||
Ensure your changes do not introduce regressions. | ||
Use your own hardware to test the new component integration. | ||
|
||
Note: A test suite will be developed in future to test the components without the use of external hardware | ||
|
||
*Signing the Contributor License Agreement* | ||
|
||
While creating a pull request, you'll be prompted to sign a Contributor License Agreement. Please do so by logging in with your GitHub account. | ||
|
||
*Submit a Pull Request (PR)* | ||
|
||
Push your changes to your forked repository. | ||
Create a pull request from your branch to the main library's master or main branch. | ||
In the PR description, explain your changes, motivations, and any decisions made. | ||
Link to any related issues or discussions. | ||
|
||
*Respond to Feedback* | ||
|
||
Maintainers or other contributors might provide feedback. | ||
Be open to suggestions and make necessary revisions. | ||
Engage in a constructive dialogue to ensure the quality of the contribution. | ||
|
||
*Stay Updated* | ||
|
||
Keep your fork synchronized with the main repository to ease future contributions. | ||
Regularly check for updates or changes in the library's contribution guidelines. | ||
|
||
*Engage with the Community* | ||
|
||
Attend community meetings or join chat groups. | ||
Help other contributors or users when you can. | ||
|
||
Note: While your contribution is highly valued, there's no guarantee that all pull requests will be merged. It depends on the library's direction, quality of the contribution, and decisions of the maintainers. | ||
|
||
Thanks for considering a contribution to the Pi4Micronaut library! Your involvement helps make the project better for everyone. | ||
|
||
|
||
|
||
|
||
|
||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters