Skip to content

Commit

Permalink
remove authors from all proposals in STUB state
Browse files Browse the repository at this point in the history
  • Loading branch information
Erik Zhang committed Aug 17, 2017
1 parent b56e54c commit 7d18281
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 18 deletions.
34 changes: 17 additions & 17 deletions README.mediawiki
Original file line number Diff line number Diff line change
Expand Up @@ -23,103 +23,103 @@ First review [[nep-1.mediawiki|NEP-1]]. Then clone the repository and add your N
|-
| 2
| Passphrase-protected private key
| Erik Zhang
|
| Standard
| Stub
|-
| 3
| Wallet Standard
| Erik Zhang
|
| Standard
| Stub
|-
| 4
| URI Scheme
| Erik Zhang
|
| Standard
| Stub
|-
| 5
| Token Standard
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 6
| Superconductive Exchange
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 7
| Dynamic Sharding
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 8
| Compact Block Relay
| Erik Zhang
|
| Standard
| Stub
|-
| 9
| Peer Authentication
| Erik Zhang
|
| Standard
| Stub
|-
| 10
| Aggregate Signature
| Erik Zhang
|
| Standard
| Stub
|-
| 11
| SM2 Cryptography
| Erik Zhang
|
| Standard
| Stub
|-
| 12
| Homomorphic Encryption
| Erik Zhang
|
| Standard
| Stub
|-
| 13
| Zero-knowledge proof
| Erik Zhang
|
| Standard
| Stub
|-
| 14
| Stealth Addresses
| Erik Zhang
|
| Standard
| Stub
|-
| 15
| NeoID
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 16
| NeoFS
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 17
| NeoX
| Erik Zhang, Da Hongfei
|
| Standard
| Stub
|-
| 18
| NeoQS
| Erik Zhang
|
| Standard
| Stub
|}
2 changes: 1 addition & 1 deletion nep-1.mediawiki
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The NEP process begins with a new idea for NEO. It is highly recommended that a

Each NEP must have a champion - someone who writes the NEP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea.

Vetting an idea publicly before going as far as writing an NEP is meant to save the potential author time. Asking the NEO community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where NEO is used. Examples of appropriate public forums to gauge interest around your NEP include [https://www.reddit.com/r/NEO the NEO subreddit], [https://github.com/neo-project/proposals/issues the Issues section of this repository], and [https://neosmarteconomy.slack.com/join/shared_invite/MjE3ODMxNDUzMDE1LTE1MDA4OTY3NDQtNTMwM2MyMTc2NA one of the NEO Slack channels]. In particular, [https://github.com/neo-project/proposals/issues the Issues section of this repository] is an excellent place to discuss your proposal with the community and start creating more formalized language around your NEP.
Vetting an idea publicly before going as far as writing an NEP is meant to save the potential author time. Asking the NEO community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the Internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where NEO is used. Examples of appropriate public forums to gauge interest around your NEP include [https://www.reddit.com/r/NEO the NEO subreddit], [https://github.com/neo-project/proposals/issues the Issues section of this repository], and [http://slack.neo.org one of the NEO Slack channels]. In particular, [https://github.com/neo-project/proposals/issues the Issues section of this repository] is an excellent place to discuss your proposal with the community and start creating more formalized language around your NEP.

Once the champion has asked the NEO community whether an idea has any chance of acceptance a draft NEP should be presented as a pull request. This gives the author a chance to continuously edit the draft NEP for proper formatting and quality. This also allows for further public comment and the author of the NEP to address concerns about the proposal.

Expand Down

0 comments on commit 7d18281

Please sign in to comment.