Interesting. Where can I read about that spec?
Some of benefit of the current setup is the immutibility of code proposals for audit purposes, the simplicity and the minimal number of required events.
Just a thought: maybe you could separate the metadata event from the human-readable descriptions and conversation.
The issue/cover letter event could reference other events needed to reconstruct an issue thread, including a PR description, references to code or commits, comments, etc.
This could use a model similar to the index events in nostr:nprofile1qqsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpspzemhxue69uhkyetkduhxummnw3erztnrdakj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0uxxcg6's Nostr Knowledge Base spec.
Discussion
Take a look at Liminal's spec here: https://wikistr.com/nkbip-01*dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319
Perhaps things that should be immutable can stay in the proposal, while comments and other things that should be editable are referenced.
Thanks, I'll take a look tomorrow
