vacp2p
/
unprotocols-rfc
mirror of https://github.com/vacp2p/unprotocols-rfc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Unprotocols RFC http://rfc.unprotocols.org
43 Commits 1 Branch 0 Tags 300 KiB
JavaScript 100%
Go to file
Yurii Rashkovskii 21725647e5 Problem: no way to discard a specification without drawbacks 
Simply deleting specification is problematic in two ways:

1. Confusion over specification number: should we reuse it?
2. Loss of potentially valuable ideas or findings.

Solution: re-introduce Deleted state
 		2016-09-11 08:30:33 -07:00
1 Problem: RFCs metainformation can't be extracted programmatically 2016-06-06 10:17:09 +07:00
2 Problem: no way to discard a specification without drawbacks 2016-09-11 08:30:33 -07:00
.gitignore Initial specifications import 2016-05-17 23:50:07 -07:00
README.md Minor README update 2016-05-18 11:50:55 -07:00
SUMMARY.md Problem: COSS lifecycle is outdated 2016-05-30 11:40:31 -07:00
book.js Problem: hard to find the latest version of a given spec 2016-06-19 20:36:46 +07:00

README.md

Unprotocols RFC

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
  • Specification lifecycle SHOULD follow the lifecycle defined in RFC 2/COSS
  • Specification SHOULD use GPL v3 or a later version of the license
  • Specification SHOULD use RFC 2119 key words.
  • Non-cosmetic changes are allowed only on Raw and Draft specifications.