agorise/bsips
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

bsip#1/template: added summary for shareholders

Browse source
This commit is contained in:
Fabian Schuh 2015-12-28 09:42:18 +01:00
parent e320862ba6
commit e9066d0f3d
2 changed files with 13 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
BSIPs-Template.md
View file

@ -1,18 +1,19 @@
BSIP: <BSIP number> BSIP: <BSIP number>
Title: <BSIP title> Title: <BSIP title>
Authors: <list of authors' real names and optionally, email addrs> Authors: <list of authors' real names and optionally, email addrs>
Status: [ Draft | Accepted | Final | Withdrawn | Deferred | Rejected | Superseded] Status: [ Draft | Accepted | Final | Withdrawn | Deferred | Rejected | Superseded ]
Type: [ Informational | Protocol ] Type: [ Informational | Protocol ]
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format> Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
Replaces: <BSIP number>
Superseded-By: <BSIP number>
Discussion: <url> Discussion: <url>
Worker: <Id of worker proposal> Replaces: <BSIP number> (optional)
Superseded-By: <BSIP number> (optional)
Worker: <Id of worker proposal> (optional)
# Abstract # Abstract
# Motivation # Motivation
# Rational # Rational
# Specifications # Specifications
# Discussion # Discussion
# Summary for Shareholders
# Copyright # Copyright
# See Also # See Also

9
bsip-0001.md
View file

@ -130,13 +130,20 @@ Each BSIP *should* have the following parts:
* Specification -- The technical specification should describe the syntax and * Specification -- The technical specification should describe the syntax and
semantics of any new feature. The specification should be detailed enough to semantics of any new feature. The specification should be detailed enough to
allow competing, interoperable implementations for any of the current allow competing, interoperable implementations for any of the current
BitShares platforms (Satoshi, BitSharesJ, BitShares-js, libBitShares). BitShares platforms.
* Discussion -- The BSIP shall include a discussion on positive and negative * Discussion -- The BSIP shall include a discussion on positive and negative
effects on the BitShares ecosystem shall it be accepted by shareholders. This effects on the BitShares ecosystem shall it be accepted by shareholders. This
section is supposed to be the most important section for shareholders to grasp section is supposed to be the most important section for shareholders to grasp
the full impact of the BSIP and help shareholders to make a decision. the full impact of the BSIP and help shareholders to make a decision.
* Summary for Shareholders -- Most BSIPs will probably be of technical nature.
However, many shareholders are not as technical as the author of a particular
BSIP. This non-technical paragraph serves as a place which can be used to
to interact with shareholders and help them form their opinion. It is not
meant to be a marketing driven paragraph to convince shareholders to vote
**for** or **against** a proposal, though.
# BSIP Formats and Templates # BSIP Formats and Templates
BSIPs should be written in mediawiki or markdown format. Image files should be BSIPs should be written in mediawiki or markdown format. Image files should be