knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Even less pretty.

This commit is contained in:
Evan Anderson 2018-08-03 11:16:11 -07:00
parent 164942f2b3
commit 5de0c6ad9c
1 changed files with 21 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
community/CONTRIBUTING.md
View File

@ -98,8 +98,8 @@ following steps:
note with the design decision and the general execution plan to the
working group's mailing list and on the feature's issue.
* Submit PRs to [knative/serving](https://github.com/knative/serving/pulls) with
your code changes.
* Submit PRs to [knative/serving](https://github.com/knative/serving/pulls)
with your code changes.
* Submit PRs to knative/serving with user documentation for your feature,
including usage examples when possible. Add documentation to
@ -168,7 +168,6 @@ When reporting a bug please include the following key pieces of information:
hundreds of lines long.
## Third-party code
* All third-party code must be placed in `vendor/` or `third_party/` folders.
* `vendor/` folder is managed by [dep](https://github.com/golang/dep) and stores
the source code of third-party Go dependencies. `vendor/` folder should not be
@ -176,16 +175,13 @@ modified manually.
* Other third-party code belongs in `third_party/` folder.
* Third-party code must include licenses.
A non-exclusive list of code that must be places in `vendor/` and
`third_party/`:
A non-exclusive list of code that must be places in `vendor/` and `third_party/`:
* Open source, free software, or commercially-licensed code.
* Tools or libraries or protocols that are open source, free software, or commercially licensed.
* Derivative works of third-party code.
* Excerpts from third-party code.
### Adding a new third-party dependency to `third_party/` folder
* Create a sub-folder under `third_party/` for each component.
* In each sub-folder, make sure there is a file called LICENSE which contains the appropriate
license text for the dependency. If one doesn't exist then create it. More details on this below.
@ -195,7 +191,6 @@ A non-exclusive list of code that must be places in `vendor/` and
* Once the pristine copy is merged into master, you may modify the code.
### LICENSE
The license for the code must be in a file named LICENSE. If it was distributed like that,
you're good. If not, you need to make LICENSE be a file containing the full text of the license.
If there's another file in the distribution with the license in it, rename it to LICENSE