NPO-Accounting/houdini
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify the CCS requirements

Browse source
This commit is contained in:
Eric Schultz 2018-06-07 11:06:25 -05:00 committed by GitHub
parent 323680f183
commit 5e8b366087
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -160,15 +160,15 @@ This generator creates a basic Typescript module along with a test file.
**Note: This is not legal advice and provides a suggestion which may be compliant. You should talk with your legal counsel if you have
questions or concerns with how to comply with the various licenses of Houdini**
Providing the complete, corresponding source code (CCS) of your project to comply with the license of Houdini. There are two methods for doing so right now:
Providing the complete, corresponding source code (CCS) of your project is a requirement of some of the licensed used by Houdini. There are two methods for doing so right now:
1. Providing a tarball of the current running code
2. Providing a link to Github where the code is pulled from
The easiest method is to provide a tarball. Houdini automatically provides a link on the Terms & Privacy page.
The easiest method is to provide a tarball. Houdini automatically provides a link on the Terms & Privacy page which generates a tarball for the current running code at runtime.
For this to work though, the following characteristics must be true:
* Your have to have any changes you made to the project in `HEAD` in your git repository
* Your have to have committed any changes you made to the project in `HEAD` in your git repository
* The `.git` folder for your repository must be a direct subfolder of your `$RAILS_ROOT`
* Your web server must be able to run `git archive`.