Earlier quoted context omitted.
You can host your own.
Same with github :)
Too bad you have to pay for github.
GitHub is down
81–90 of 175 posts
Re: GitHub is down
#82The webpage works fine for me. Can you tell me which part of the infrastructure is down?
Back up now, apparently, but GitHub themselves were reporting "Major service outage" in bold red letters. It looked very serious, but it seems they've done a great job getting everything back up fairly quickly.
Re: GitHub is down
#83Status page[1] is now saying everything is operating normally... now waiting for the post mortum...
Re: GitHub is down
#84I hope the world realizes that clouds are not just fluffy white things in the blue sky, but can create destructive storms too, with wind, rain and so on. Make sure your infrastructure is ready to weather such storms - have local backups and fallbacks, make sure your code is available even if github (or the Internet) goes down. The more I hear 'cloud', the more I try to depend only on tools that work offline.
Metaphors like that only makes it even more confusing. It's a marketing scam, let's call it for what it is. Servers. They are servers.
There can be difference between hosting on bare metal boxes and hosting on cloud providers.
If you are connecting different services (message queues, databases, storage, transcoding), and spinning up and down instances based on current demand and spot prices, then cloud hosting is totally different. On the other hand, if you are just renting a couple of dedicated cloud instances, then yeah - they're just (virtualized) servers.
Re: GitHub is down
#85Earlier quoted context omitted.
Now if only we had a convenient way of using a distributed VCS without a central hub.
That sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …). Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people u…
Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step.
If you don't want special git semantics around it, you'd have to be clever about how you store it so you don't have conflicts within the metadata. I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable.
Re: GitHub is down
#86Earlier quoted context omitted.
We do, it's called Fossil! http://fossil-scm.org/ Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. You can then respond to tickets and perform repo maintenance offline, syncing everything to the server when you're back up. Edit: A few weeks ago I got a job a one-hour train ride away. I…
the parent commentator was joking that git _is_ decentralised, but that we made it centralised again by relying on a small number of hosters (github, bitbucket and others)
Heh, don't worry, I got the joke. But I also got the joke the last time this was posted, and the time before that, and the time before that...
This just keeps happening. It's not GitHub's fault that they keep getting DDoSed or have a network outage every now and again. But it's not a problem with no solution.
Re: GitHub is down
#87Earlier quoted context omitted.
That sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …). Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people u…
What about BitTorrent DHTs? Or dat http://dat-data.com/ Or Camlistore? https://camlistore.org/
The problem of content-addressing — aside from the opaqueness to "shallow" contributions (nobody is going to install a content-addressed distributed filesystem just to report a bug to your software, don't kid yourself) — is what content-addressing means for resource updates. How do I get the most recent comment on the most recent bug report on one of my projects? In fact how do I even discover their existence from knowledge of the project's existence?
Re: GitHub is down
#88Earlier quoted context omitted.
That sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …). Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people u…
Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step. If you don't want special git semantics around it, you'd have to be clever about how you store it so you don't have conflicts within the metadata. I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doa…
> Has anybody tried to store a project's metadata (issues and PRs) within the project's git repository itself? Seems like a logical step.
There were a number of tentative distributed bug trackers a few years ago, they sucked and fizzled out. IIRC Fossil is an attempt at an entire distributed project management system, I don't know how it fares.
> I.e. a naive design just adding a markdown file per issue or for all issues will require manual merging all the time. Still, it seems doable.
That only works for your own personal project where you're the only user and contributor. Bug reporting by editing a markdown file (or even something actually usable like an org-mode file or an sqlite or BDB file) isn't going to scale very high and is way more effort than most bug reporters (even technical ones) will be willing to put in.
And even if your users were willing to subject themselves to that, they still need a way to send back those contributions somehow.
Re: GitHub is down
#89Just a friendly reminder to store source locally.
Generally try not to put external services in a critical path.
Re: GitHub is down
#90I like how they write there "Everything operating normally." :) when it is down...