From f911a99754610650798e7bdedfb6d4a26a4b84ab Mon Sep 17 00:00:00 2001 From: Gary R Krause Date: Tue, 14 Feb 2023 18:58:55 -0500 Subject: [PATCH] Update NIP numbering --- draft.md => 69.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) rename draft.md => 69.md (92%) diff --git a/draft.md b/69.md similarity index 92% rename from draft.md rename to 69.md index ec16b4e..118bffa 100644 --- a/draft.md +++ b/69.md @@ -1,4 +1,4 @@ -NIP-?? +NIP-69 ====== Source Control Context @@ -6,18 +6,18 @@ Source Control Context `draft` `optional` `author:garyKrause_` -This NIP defines ways source control (git, etc.) context can be stored using nostr. Git is already decentralized, but the contexts around a git repository are largely centralized (PR comments, issue tracking, releases, etc). With the correct approach a nostr relay could store this context using many of the existing NIPs. This NIP defines a new kind, `kind: ??`, to represent a source control repository. This NIP purposely does not indicate git as a requirement but many of the concepts will be based around git methods of source control. The author hopes that the NIP is flexible enough to accommodate other source control methodologies. +This NIP defines ways source control (git, etc.) context can be stored using nostr. Git is already decentralized, but the contexts around a git repository are largely centralized (PR comments, issue tracking, releases, etc). With the correct approach a nostr relay could store this context using many of the existing NIPs. This NIP defines a new kind, `kind: 69`, to represent a source control repository. This NIP purposely does not indicate git as a requirement but many of the concepts will be based around git methods of source control. The author hopes that the NIP is flexible enough to accommodate other source control methodologies. ## Definition of a Source Control Event -`kind: ??` uses tag the `b` tag to identify the base repository. The value of this tag SHALL be a list of remote source control repository URLs. These URLs MAY be a nostr relay URL or a traditional repository URL. The first URL in this list SHALL be considered the "default" repository URL for the context. +`kind: 69` uses tag the `b` tag to identify the base repository. The value of this tag SHALL be a list of remote source control repository URLs. These URLs MAY be a nostr relay URL or a traditional repository URL. The first URL in this list SHALL be considered the "default" repository URL for the context. The `content` of a Source Control Event MAY contain a text description of the event or other information about the repository. ```json { ... - "kind": ??, + "kind": 69, "tags": [ ["b", , , ...], ], @@ -25,7 +25,7 @@ The `content` of a Source Control Event MAY contain a text description of the ev ... ``` -A relay MAY host the repository along side it's nostr database which can be discovered using a standard `REQ` message filtering for `kind: ??`. +A relay MAY host the repository along side it's nostr database which can be discovered using a standard `REQ` message filtering for `kind: 69`. ### Merge Requests @@ -34,7 +34,7 @@ A source control event MAY contain an `m` tag indicating the event is specific t ```json { ... - "kind": ??, + "kind": 69, "tags": [ ["b", , , ...], ["m": , , ],