#GitPub

2020-11-14

@sammy
Yoi refer to #gitpub or #forgefed?

ClearCarbonclearcarbon
2020-01-08

Can't make it to this evening, hope everyone has a great time

2019-10-28

@L12C Überlege dir bitte auch, wie niederschwellig der Zugang für Beitragende sein soll. Da ist derzeit github leider super easy, da die meisten Devs dort einen Account haben. Auch src zusästzlich zu mirrorn ist ja kein Problem, leider ist #gitpub noch nicht so weit, dass das auch zwischen den Portalen funktioniert 😉

2019-01-22

@adlerweb Das Ganze nennt sich #forgefed (fka. #gitpub) aber da ist seit Monaten nichts mehr passiert github.com/forgefed/forgefed

2019-01-07

@kaniini

@jeff

Some time ago this idea was called #gitpub. IMHO this needs also to cover tickets e.g. to move distro issues upstream...

2018-10-05

@dansup I guess an good point would be to collect protocol extensions (or interpretations / flavours). So refer to #gitpub or similar approachs?

2018-07-27
With @giteaio and #teahub.io gaining traction, federation would be *the* killer feature to get people hosting their code on free and open platforms. #GitPub could provide that, and I hope many developers join this effort: https://github.com/git-federation/gitpub
2018-07-16

@sir by that time, the #GitPub folks could have spent a lot of energy going down what you claim is the wrong path. You hesitate now to put this claim in writing in one place, so it can potentially guide their work down the right path. Could it be that you are almost ready to concede the possibility that you were drawing on funds that weren't really in the bank?

2018-07-12

@sir . FWIW despite what the name suggests, #GitPub plan to support any and all version control systems, not just #Git (even raw patches)

2018-07-12

@sir #GitTorrent is one attempt to solve the decentralized GH problem, your #sr.ht is another, #GitPub is another, #Git-SSB is another (github.com/noffle/git-ssb-intr). Each one tries using a different standardized of protocols (#BitTorrent, email, #ActivityPub, #SSB). Ideally it would be possible to bridge them all, so users and projects could hosted anywhere, and users could contribute anywhere

2018-07-06

Any news on #GitPub? Where does it live now? I lost track of it during the last few weeks. Federalized code hosting would really be a valuable addition to the fediverse. So I hope this project flourishes well and fast.

#git #decentralized

2018-07-06

@sir @Wolf480pl @Michcioperz
This is precisely because of the problem #GitPub is trying to solve. Where should it be hosted? On GitLab.com? On a GL instance? Which one? Once GitPub (or something like it) exists, it won't matter, because anyone will be able to interact with it as if its on their own home instance (self-hosted, community-hosted, whatever).

2018-07-06

@sir @Wolf480pl @Michcioperz one more thing, I would be very interested to see you expand on this in long form, in fact on anything we've discussed today, so I can share a link with the #GitPub folks

2018-07-06

@sir @Wolf480pl @bob @Michcioperz this is all totally fair enough. You're scratching your own itch. You're making tools for users like you. Users who are not like you also need tools, and they need to be more like GH / GL. That's why people are working on #GitPub. If you can propose a protocol set to them that is simpler than the AP set, by all means, go for it! They'll love you for it and so will I.

2018-07-06

@sir @Wolf480pl @Michcioperz right, they're in #GitPub's target audience, which is why it is needed, despite the fact that you and other CLI-based software engineers don't need it. Yes?

2018-07-06

@sir @Wolf480pl @Michcioperz @Karneolius
> most people who use git are engineers

I don't think this is true, for a number of reasons. The main one being that engineers are only one of the specialists involved in post-CLI software dev, especially for net software. Other specialities include graphics, #UI, and #UX designers, doc writers, beta testers.

> I do not feel the need to make tools which are accessible to noobs.

I'm not saying you must, but that's the use case GH and #GitPub are for

2018-07-06

@sir @Wolf480pl @Michcioperz @Karneolius
> If any change would be good, it would be to move things like tickets into git objects.

OK, my understanding is that #GitLab does this. It doesn't seem to help users, projects, or organizations on multiple instances of #GitLab etc interact, creating a federate replacement for GH. If you have a better way to solve this problem that would work for doc writers who will never touch a command line, I'm all ears, and I imagine the #GitPub folks would be too

2018-07-06

@Wolf480pl @Michcioperz @Karneolius @sir fair point. Maybe something to talk to the #GitPub folks about? Would the lists.sr.ht tech allow existing instances of #GitLab etc to federate though?

2018-07-05

@Michcioperz @Karneolius @Wolf480pl #GitPub is about federating together instances of #GitLab, #Gogs, #Gitea etc, to create a similar #UX to GH (everything is connected, low barrier to drive-by contributions), without forcing everyone to develop free code on a proprietary platform now owned by one of software freedom's oldest enemies
ecis.eu/documents/Finalversion

2018-07-04

@Michcioperz @Karneolius @Wolf480pl sure but #ActivityPub != Mastodon or just microblogging. It's also #Hubzilla (blogging), #PixelFed (photos), #PeerTube (videos), and hopefully soon #GitPub (code). Why not forums?

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst