We can already do code collaboration via Nostr using ngit, but ngit still requires you to use a git server, and most people use GitHub.

Reply to this note

Please Login to reply.

Discussion

If we start hosting a public git server, we'll use it as a platform to start developing and testing new Nostr/git integrations.

Something to consider is we only need the git part... Onedev GitLab and whatever else you can think of are WAY too much.

Maybe we shouldn't even bother considering those extra features since we prioritize and encourage the use of nostr. We can do this literally with HTTP servers. Sure I can get more complicated but lets keep in mind what we need for a simple git remote server to work

Good point. Ngit can already handle a good deal of the collaboration, and our team will build more collaboration tools as we work more on git stuff. We just need a place to stash code that's not GitHub and that doesn't require reinventing git in the form of Nostr events.

So like gists?

Thanks for reminding me. I should prolly work on that a bit tonight when I get home...

I need to figure out how to include propose edits like amethyst, and maybe some kind of community voting system to approve edits. 🤔

the point of this conversation was to share code for a single developer even raw code parts

Polls like on https://pollerama.fun/ can be an option

or functionality like changing the relay, towards your own or one relay that the user has access to, in that case it is the community relay

I think posting and commenting with nip 22 is fine, what kind is the post, can I try to post?

For those who don't know, we host a gitstuff client here, with issues and PRs:

https://gitcitadel.com/repos

Here is the Alexandria repo event:

https://gitcitadel.com/r/naddr1qvzqqqrhnypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqsuamnwvaz7tmwdaejumr0dshsqzjpd3jhsctwv3exjcgzqk5dt

You can see the problem we want to solve here:

You can list multiple gitservers there, but most repo events just have GitHub listed. We want to offer a second "low-friction" gitserver.