19 lines
909 B
Markdown
19 lines
909 B
Markdown
|
# Introduction
|
||
|
|
|
||
|
|
Unprotocols RFC is a repository for universal, cross-project protocols used in
|
||
|
|
software development, ranging from workflow to technical ones.
|
||
|
|
|
||
|
|
It has started as a new home for C4 and COSS protocols to elevate their prominence and articulate their usefulness outside of the original projects'
|
||
|
|
boundaries. More protocols are welcome to join this project.
|
||
|
|
|
||
|
|
You can start contributing by sending a pull request to https://github.com/unprotocols/rfc on GitHub.
|
||
|
|
|
||
|
|
|
||
|
|
## Guidelines
|
||
|
|
|
||
|
|
* A specification SHOULD be created and modified by pull requests according to [RFC 1/C4](1/README.md)
|
||
|
|
* Specification lifecycle SHOULD follow the lifecycle defined in [RFC 2/COSS](2/README.md)
|
||
|
|
* Specification SHOULD use GPL v3 or a later version of the license
|
||
|
|
* Specification SHOULD use [RFC 2119](http://tools.ietf.org/html/rfc2119) key words.
|
||
|
|
* Non-cosmetic changes are allowed only on Raw and Draft specifications.
|