mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-02-23 13:49:00 +00:00
use 'p' tags instead of 'zap' tags for assignees
This commit is contained in:
parent
a2507ab77b
commit
d520ebcbc5
27
100.md
27
100.md
@ -36,19 +36,18 @@ Kanban boards are a popular project management tool that enables visual organiza
|
|||||||
["col", "col2-id", "In Progress", "1"],
|
["col", "col2-id", "In Progress", "1"],
|
||||||
["col", "col3-id", "Done", "2","Done, Completed, Finished"],
|
["col", "col3-id", "Done", "2","Done, Completed, Finished"],
|
||||||
|
|
||||||
// designate a 'maintainers' list who can add/edit cards in this board
|
// Clients may designate a 'maintainers' list who can add/edit cards in this board
|
||||||
// add maintainers using 'zap' tag so that the zaps go to them using zap-splits as per NIP-57, if 'zap' tags are absent, then only the owner can add/edit cards in the board
|
[ "p", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2" ],
|
||||||
[ "zap", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2" ],
|
[ "p", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52" ],
|
||||||
[ "zap", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52" ],
|
[ "p", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c" ],
|
||||||
[ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c" ],
|
|
||||||
// other fields...
|
// other fields...
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
In case there are no `zap` tags to designate maintainers, the owner of the board is the only person who can publish cards on the boards.
|
In case there are no `p` tags to designate maintainers, the owner of the board is the only person who can publish cards on the boards.
|
||||||
|
|
||||||
Editing of the board event is possible only by the creator of the board.
|
Editing the board event is possible only by the creator of the board.
|
||||||
|
|
||||||
### Card Event
|
### Card Event
|
||||||
|
|
||||||
@ -68,13 +67,13 @@ Editing of the board event is possible only by the creator of the board.
|
|||||||
["u","https://attachment1"],
|
["u","https://attachment1"],
|
||||||
["u","https://attachment2"],
|
["u","https://attachment2"],
|
||||||
|
|
||||||
// add assignees using 'zap' tag so that the zaps go to them using zap-splits as per NIP-57
|
// add assignees using 'p' tag
|
||||||
[ "zap", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"],
|
[ "p", "82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2"],
|
||||||
[ "zap", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"],
|
[ "p", "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"],
|
||||||
[ "zap", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"],
|
[ "p", "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"],
|
||||||
|
|
||||||
// The list of boards this card will be a part of.
|
// The list of boards this card will be a part of.
|
||||||
// However, the card will be displayed in a board only when this event's pubkey matches an entry in the board's maintainers list
|
// However, the card will be displayed on a board only when this event's pubkey matches an entry in the board's maintainers list
|
||||||
["a", "30301:<board-1-creator-pubkey>:<board-1-d-identifier>", "<optional-relay-url>"],
|
["a", "30301:<board-1-creator-pubkey>:<board-1-d-identifier>", "<optional-relay-url>"],
|
||||||
["a", "30301:<board-2-creator-pubkey>:<board-2-d-identifier>", "<optional-relay-url>"],
|
["a", "30301:<board-2-creator-pubkey>:<board-2-d-identifier>", "<optional-relay-url>"],
|
||||||
],
|
],
|
||||||
@ -98,8 +97,8 @@ In case one wants to just track another nostr event (like a tracker card, withou
|
|||||||
["d", "<card-d-identifier>"],
|
["d", "<card-d-identifier>"],
|
||||||
["k", "1"], //this one tracks a text note
|
["k", "1"], //this one tracks a text note
|
||||||
["e", "<event-id>", "<relay-url>"] // as per NIP-10
|
["e", "<event-id>", "<relay-url>"] // as per NIP-10
|
||||||
],
|
|
||||||
// other fields as per card event above...
|
// other fields as per card event above...
|
||||||
|
],
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -111,7 +110,7 @@ Any `30302` event with a `k` tag will be treated as a tracker card.
|
|||||||
|
|
||||||
In case of tracked card, its status is deemed to be the `s` tag value of the event it tracks.
|
In case of tracked card, its status is deemed to be the `s` tag value of the event it tracks.
|
||||||
|
|
||||||
This allows automatic movement of a card (like a Git issue) across different columns as the card's status changes in the source system, without any manual updates in the board.
|
This allows the automatic movement of a card (like a Git issue) across different columns as the card's status changes in the source system, without any manual updates in the board.
|
||||||
|
|
||||||
If the tracked event does not have an `s` tag, then tracker card event's `s` tag is the status of the card.
|
If the tracked event does not have an `s` tag, then tracker card event's `s` tag is the status of the card.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user