Looks like a couple of days ago nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 reorganized the GitHub org and team for nostr-protocol. Is this what you’re talking about? I see 19 people in the team as having commit access.

I spent years in and around the Ruby on Rails community. They eventually developed rails-core which had a process for joining and leaving. While a protocol is different from a framework, this feels broadly similar. Rails wasn’t perfectly managed but it has worked for almost 20 years and handled a bunch of conflicts while staying open. Nostr feels broadly similar.

Reply to this note

Please Login to reply.

Discussion

Yes, this is good. The main thing for me is that no one entity, no matter how well meaning, can have complete control. ie there should be 2+ owners. I believe bluesky has 3 board members. Nostr needs to go multi-stakeholder too, to really be a community driven open protocol. The Ruby system, or any such simliar open source system (like bitcoin) would work too. Room for improvement.

Rails is an implementations; whereas nostr is not defined by the nips repo, nostr lives in its many implementations and the nips repo are useful as documentation on what can be expected, but any nostr developer knows this specs are very far from the chaotic reality of what lives on the relays

He’s talking about the fact nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 removed the authors tags from the NIPS and how he went about doing it.

FWIW, I don’t think the NIPs should have owners or authorities so asking for consent to remove the attribution doesn’t make sense as the people who wrote them were never the owners (it’s stated as “public domain” after all)

Do what works for you, but dont remove the authorship from the work of others, without consent. And certainly not in 12 hours. That is not an open process.

I think Melvin may be too used to the W3C world where the spec is the only thing that matters and people write tons of specs and then 99% of them are never implemented but they still talk about the specs and spec authors with religious respect and ceremony -- so he thinks the NIPs repo is a very powerful entity.

In fact the NIPs repo is constantly running behind implementations and trying to stay relevant in a chaotic scenario of 32 different clients each with their own priorities.