Avatar
DanConwayDev
a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d
freedom tech developer and creator of ngit, https://gitworkshop.dev and https://metadata.nostr.com

Yeah. A CLI command should be as short as possible but that makes finding something meaningful with a domain name near impossible.

That's quite good :) but I'm not crazy about reading it as to-git-her.

Choosing a name is hard! I'm definitely in need of suggestions. I thought about gittogether but the .com is also taken.

https://ngit.netlify.app/ stay tuned as I'm freeing up my time to light a fire under code collaboration over nostr.

I think you must have accidentally missed GBP off the list. You can tell it belongs their because it begins with the word 'Great'; a clear indication of its preeminence.

This looks great. Wouldn't it be nice if you could specify different clients for different kinds? This could be taken from your NIP-89 l app recommendations. Unfortunately it would require the kinds to be embeded in the link.

I really like this as a solution. Here are some thoughts:

1. Projects may be resistant to embedding repository metadata like this directly into the commit history. Perhaps this isn't a big issue issue. It would be interesting to gauge opinion on this.

2. All commits and merges that take over as the new tip must be PGP signed. This may be a barrier for some projects but potentially less so for projects that would be attracted to a more decentralized option.

3. The rules for transferring repository ownership must be resistant to a compromised PGP key but also a key loss by one maintainer.

4. It maybe hard to extract this information for other usages without the repo being cloned. For example a nostr client may want a list of maintainers for things such as issue and PR moderation.

We could write a git server that allows commits signed by maintainers to be written without authentication / user accounts.

The commit id provides a hashed state which goes a long way in providing a source of truth but more information is needed.

How do you know whether the author of a PGP signed commit believes it is has had adequate review to be integrated into the

main branch? How do you know whether repository maintainers agree with this?

Where do you go to find the top commit?

The draft NIP proposes resolving these questions either via a centralised git repository, or by nostr events sent over relays signed by repository maintainers.

nostr events can provide this.

PullRequest

fix-branch-push-permissions

A user who isn't a repo maintainer can create a branch, create a PR but cannot push to the branch. This update checks whether thye are authorised to push to the branch and if so allows them to proceed, displaying a slightly different message.

https://void.cat/d/668Yog3y8tALyh5FzDH21y.webp

launching ngit, a prototype cli built in rust for a github alternative over nostr.

Try it out. I'd love your feedback. It implements clone, push, pull, PRs and merge all using the a tweaked patch model entirely over nostr.

Let's work together to loosen the chains of centralised walled gardens and embrace a permissionless world!

Downloads and info at https://ngit.netlify.app

I'd love to collaborate with any and all who are working on this important challenge so please reach out on nostr or this Telegram group: https://t.me/code_collab_over_nostr

PullRequest

fix hello world! grammar

added punctuation (!) to hello world

I meant smaller bounties that you could do deliver within a much smaller time frame.

Yes. If it doesn't fail now, the features will be added to relays to block larger events if lots of them get posted.