Contributions to Tsugi from all comers are welcome and encouraged.
Please use these guidelines and the information in README.md to assure that your contributions are compatible with our (evolving) workflow and practices.
The Tsugi project participates in the Apereo Welcoming Policy.
Before a code submission will be accepted, you will need to submit a Contributor License Agreement (CLA). This is a one-off process that should only take a few moments to complete. See: https://www.apereo.org/licensing/agreements
To check the status of a CLA, please visit: http://licensing.apereo.org/
Bugs and features against Tsugi are tracked in Github Issues
If you want to suggest a change, generate a GitHub Pull Request and we will review it, and apply it if appropriate.
You will notice that there is a vendor folder. While many suggest that this is bad practice, in order to keep our releases rock solid and out install / upgrade process extremely simple, we keep the vendor folder in the repo. Within that folder you will see that two other Tsugi repos are also included:
https://github.com/tsugiproject/tsugi-php
https://github.com/tsugiproject/koseu-php
You can open issues and submit pull requests to with the main tsugi repo or these other repos. Regardless of where you start the process the branch manager (Chuck) will make sure your modifications are propogated across repositories.