-
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f509c4b
commit decade1
Showing
1 changed file
with
38 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# Contributing | ||
|
||
Crypto needs adoption and the goal of this tool is to help other developers build faster! If you find any bugs / issues or have suggestions, please consider collaborating. It would be greatly appreciated. | ||
|
||
When contributing to this repository, please first discuss the change you wish to make via issue, | ||
email, or any other method with the owners of this repository before making a change. | ||
|
||
Please note we have a [code of conduct](CODE-OF-CONDUCT.md), please follow it in all your interactions with the project. | ||
|
||
## Pull Request Process | ||
|
||
If you consider that: | ||
|
||
* You have added some new featuree with which you add value so that more people reuse it, | ||
* You have made the tool more versatile to be compatible with new updates, | ||
* You have fixed an existing issue, | ||
* Or you have simply improved the user interface or its documentation | ||
|
||
Then we encourage you to return the progress made to the repository. | ||
|
||
Follow the steps below to make a contribution to the digital tool: | ||
|
||
1. Fork the Project | ||
2. Develop your awesom feature to add value to this tool | ||
3. Ensure any install or build dependencies are removed before the end of the layer when doing a | ||
build. | ||
4. Update the README.md with details of changes to the interface, this includes new environment | ||
variables, exposed ports, useful file locations and container parameters. | ||
5. Increase the version numbers in any examples files and the README.md to the new version that this | ||
Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). | ||
6. You may merge the Pull Request in once you have the sign-off of two other developers, or if you | ||
do not have permission to do that, you may request the second reviewer to merge it for you. | ||
|
||
If you have not contributed to this repo, but thhe tool has been useful for you, we would love to read your experience. Tell us about it openiing an issue or throug admin@unizend.com | ||
|
||
## Code of Conduct | ||
|
||
Remember this project has a [code of conduct](CODE-OF-CONDUCT.md). We hope everyone taking part of this project, agree with our code of conduct. Read it to know what we exxpect from the contributors. |