You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of a more formal Namecoin Enhancement Proposal process (similar to Bitcoin, Python, et. al) has been kicked around for a while but no action taken on it.
Usually, these documents are static, with the commenting mostly happening in a mailing list somewhere. This way of doing things misses out on an important opportunity to capture institutional knowledge along with the proposal.
So, instead of a separate website, what if we just create a label (like NEP) for Github issue/ticket system and put them there? We can label it as draft/rejected/accepted as well and when an idea is implemented it can be attached to the correct milestone.
I've created a dummy version of this in a repo I own, if you want to see what it would look like.
The text was updated successfully, but these errors were encountered:
Probably not, the ticket system doesn't have a history feature nor does it allow for headlines. It may also clutter the developer workflow. Khal requested that we wait until after the hosting and website situation has stabilized.
The idea of a more formal Namecoin Enhancement Proposal process (similar to Bitcoin, Python, et. al) has been kicked around for a while but no action taken on it.
Usually, these documents are static, with the commenting mostly happening in a mailing list somewhere. This way of doing things misses out on an important opportunity to capture institutional knowledge along with the proposal.
So, instead of a separate website, what if we just create a label (like NEP) for Github issue/ticket system and put them there? We can label it as draft/rejected/accepted as well and when an idea is implemented it can be attached to the correct milestone.
I've created a dummy version of this in a repo I own, if you want to see what it would look like.
The text was updated successfully, but these errors were encountered: