If only there was a protocol of some sorts that allowed you to send/receive code and patches even if the centralized hub everyone uses for synchronization was down...
If only there was a protocol of some sorts that allowed you to send/receive code and patches even if the centralized hub everyone uses for synchronization was down...
Repeat after me: GitHub is more than just Git. GitHub is more than just Git.
I would like to see Git be extended with a decentralized approach to bugtracking, code reviews, wiki's for documentation etc.
Isn't that Fossil?
https://fossil-scm.org/home SCM, bug tracker, wiki...
What do you need for wikis? Just put text files in a folder?
Bug tracking in git: https://github.com/MichaelMure/git-bug
Code review in git: https://github.com/google/git-appraise
Repeat after me: Git is more than just files. Git is more than just files.
Yes, it's also good a variety of different systems to store and address Markdown.
Which you could, you know, put in git.
Git is more than just GitHub though, that much is true.
Most of the time it's not about the code. Project management, issue tracking and prioritization, discussions, PR reviews, searching across the organization repos, etc.
There are (all too rare) tools that back those objects with git as well.
And there's always fossil ...
https://fossil-scm.org/home/doc/trunk/www/index.wiki
But it's not git. :-(
I know git claims to be decentralized, but has anybody ever actually managed to use it in a decentralized manner? Not even the git or Linux projects themselves are without a centralized sync point.
Grandparent can still work off their local git repository, create local branches and commits, unlike the traditional VCS model which required branching and commits to be immediately synced to a centralized node.
The centralization issue that you raise is a different one; most projects intend to take contributions from folks and merge them into a single product.
Noted on the definition of the word “decentralized”, but the comment I was replying to was specifically about the ability to “send/receive code and patches”, that’s what I haven’t seen done without a central sync point.
I wonder, have there been any case studies on phishing/trojan type attacks by code (git changes) via email?
Something distributed??