Difference between revisions of "OIP"
m (2 revisions imported) |
(typo) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Byteball Improvement | + | Obyte Improvement Proposal (formerly Byteball Improvement Proposal) |
| − | == | + | == OIPs == |
| − | + | An Obyte Improvement Proposal (OIP) is a design document providing information to the Obyte community, or describing a new feature for Obyte or its processes or [[platform|environment]]. The OIP should provide a concise technical specification of the feature and a rationale for the feature. | |
| − | We intend | + | We intend OIPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Obyte. The OIP author is responsible for building consensus within the community and documenting dissenting opinions. |
| − | Because the | + | Because the OIPs are maintained as text files in a versioned repository<ref>https://github.com/byteball/OIPs</ref>, their revision history is the historical record of the feature proposal. |
=== BBIP 1 === | === BBIP 1 === | ||
| Line 14: | Line 14: | ||
Comments-Summary: No comments yet.<br /> | Comments-Summary: No comments yet.<br /> | ||
Comments-URI: https://github.com/byteball/bbips/wiki/Comments:BBIP-0001<br /> | Comments-URI: https://github.com/byteball/bbips/wiki/Comments:BBIP-0001<br /> | ||
| − | Status: | + | Status: Active<br /> |
Type: Process<br /> | Type: Process<br /> | ||
Created: 2017-07-20<br /> | Created: 2017-07-20<br /> | ||
License: BSD-2-Clause, OPL<br /> | License: BSD-2-Clause, OPL<br /> | ||
| − | < | + | === OIP 2 === |
| + | OIP: 0002<br /> | ||
| + | Title: Consensus Timestamps<br /> | ||
| + | Author: Tony Churyumoff @tonych<br /> | ||
| + | Discussions-To: Discord #tech<br /> | ||
| + | Comments-Summary: No comments yet<br /> | ||
| + | Comments-URI: https://github.com/byteball/OIPs/issues/5<br /> | ||
| + | Status: Draft<br /> | ||
| + | Type: Standards Track<br /> | ||
| + | Created: 2019-02-22<br /> | ||
| + | License: BSD-2-Clause and CC0-1.0<br /> | ||
==References== | ==References== | ||
Latest revision as of 13:17, 7 March 2019
Obyte Improvement Proposal (formerly Byteball Improvement Proposal)
Contents
OIPs
An Obyte Improvement Proposal (OIP) is a design document providing information to the Obyte community, or describing a new feature for Obyte or its processes or environment. The OIP should provide a concise technical specification of the feature and a rationale for the feature.
We intend OIPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into Obyte. The OIP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the OIPs are maintained as text files in a versioned repository[1], their revision history is the historical record of the feature proposal.
BBIP 1
BBIP: 1
Title: BBIP Purpose and Guidelines
Author: Peter Miklos @pmiklos
Comments-Summary: No comments yet.
Comments-URI: https://github.com/byteball/bbips/wiki/Comments:BBIP-0001
Status: Active
Type: Process
Created: 2017-07-20
License: BSD-2-Clause, OPL
OIP 2
OIP: 0002
Title: Consensus Timestamps
Author: Tony Churyumoff @tonych
Discussions-To: Discord #tech
Comments-Summary: No comments yet
Comments-URI: https://github.com/byteball/OIPs/issues/5
Status: Draft
Type: Standards Track
Created: 2019-02-22
License: BSD-2-Clause and CC0-1.0
