| domain | shortname | name | status | editor |
|---|---|---|---|---|
rfc.pumpkindb.org |
0/RFC |
Request For Comments |
raw |
Yurii Rashkovskii <[email protected]> |
Request For Comments outlines guidelines for creating and maintaining PumpkinDB RFCs.
Copyright (c) 2017 The Editor and Contributors
This Specification is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This Specification is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see http://www.gnu.org/licenses.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
- To provide guidelines for creating PumpkinDB RFCs
- To provide a reasonable minimalistic template
- A specification SHOULD be created and modified by pull requests according to C4
- Specification lifecycle SHOULD follow the lifecycle defined in COSS - Consensus Oriented Specification System
- 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.