A real community, however, exists only when its members interact in a meaningful way that deepens their understanding of each other and leads to learning.
If you would like to support this project, have an interesting idea how to improve the operation of this tool, or if you found some errors - fork this, add your fixes, and add a pull request of your branch to the master branch.
The issue tracker is the preferred channel for bug reports, features requests and submitting pull requests, but please respect the following restrictions:
-
Please do not use the issue tracker for personal support requests (use Stack Overflow or IRC)
-
Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others
I would like you to stick to certain standards of writing in bash. I realize that it is not easy and time-consuming if you have certain habits. I do not expect 100% compliance and adherence to good practices, however, I would like you to try to use certain principles.
The following should help:
- http://wiki.bash-hackers.org/
- https://google.github.io/styleguide/shell.xml
- https://github.com/progrium/bashstyle
- http://kvz.io/blog/2013/11/21/bash-best-practices/
One of the requirements before approving your changes is to check them with the shellcheck utility. If the returned errors are not critical (eg. SC2154) you can use the shellcheck disable=SC2154 design.
Moving forward all commits to this project must include a "signed-off-by" line indicating the name and email address of the contributor signing off on the change. To enable signatures add the following lines to .git/hooks/prepare-commit-msg :
SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/- signed-off-by: \1/p')
grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
When creating a pull request, please heed the following:
- Base your code on the latest master branch to avoid manual merges
- Code review may ensue in order to help shape your proposal
- Explain the problem and your proposed solution