NIP-17 Code Collaboration#561
Closed
DanConwayDev wants to merge 1 commit into
Closed
Conversation
Merged
Member
|
Closing because I assume this is superseded by #997 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a very early draft of a more wide ranging NIP relating to code collaboration than those that have come before it:
#223
#324
It builds upon the work of many others and stems from the ngit-cli prototype I built. It seeks to prioritise interoperability between models.
I have removed the use of the draft Public Groups NIP. I am unsure that the use of parameterized replaceable event is a good trade off. It reduces auditability, particularly around changes in maintainers and the knock on effect of that.