Posts by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
(DIR) Post #ATH2NJIPo8tBivcgDI by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T12:56:48.000Z
0 likes, 0 repeats
Does the author of that bounty really know how git works and realize that git is already decentralized?Emailing patches is one of the main features that Linus wanted when he wrote git. Replacing email with nostr is already being done with git-nostr.The problem of who gets to decide what to merge into Bitcoin core is not going to be solved by putting it on nostr.
(DIR) Post #ATH2NKVZIj0LU0mhM0 by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T13:46:46.000Z
0 likes, 0 repeats
http://git.jb55.com/git-nostr-tools/file/README.txt.html
(DIR) Post #ATH4Exdwd0OoA0q7DU by bfc058c9abb250a2f4f0f240210ae750221b614f19b9872ea8cdf59a69d68914@mostr.pub
2023-03-04T13:41:06.000Z
0 likes, 0 repeats
Linus wrote git to be distributed (decentralized) and his workflow with email patches was a core design feature.Github projected a centralized workflow onto git (branch permissions and all that jazz are not a part of git). This has its place especially in the enterprise world. So why do we want branch permissions for open source projects?I think it comes down to trusted reviewers. There are those rare combinations of talent, common sense and OCD that make excellent master branch guardians.So all I think we need is1. the feature of broadcasting merge requests on nostr2. the feature of trusted reviewers signing their approval to this request3. the feature of cryptographically coming up with a deterministic merge outcome and commit hash so every distributed client would have an identical merge4. a git client/client extension to automatically merge based on preconfigured sign eventsEvery developer could still hold the code local, plus there could be X public repository servers.