Don't forget that fossil has the wiki+issues in the repo, so if chiselapp.com (or your host) with your repo would go down, you wouldn't lose those, as opposed to issue tracking being gone if github goes down. Of course, this is disregarding network effects and discoverability, but for those you wouldn't need a monolithic service like github, either.
On 5 April 2016 at 16:35, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Tue, 5 Apr 2016 09:34:34 -0400 > Richard Hipp <d...@sqlite.org> wrote: > > > GitHub has apparently suffered another outage. Fossil comes up a lot > > in the resulting discussion over on Hacker News > > (https://news.ycombinator.com/item?id=11428776). I didn't read it > > all, but most comments seem positive. > > I know I will state the obvious thing but Git != Github. > > To my knowledge, Fossil currently has the single hosting solution > available: chiselapp.com; should it have had its outage, the > repercussions for its users would be roughly the same. > > Sure, the canned answer to this claim is that self-hosting with Fossil > is super-easy but > > 1) Hosting on Github (or any other such solution) is, and will always > be, easier. > I mean, it's indeed simple to roll your own Fossil server, but > it's still easier to register with a go-to service and click through > some sort of "create me a repo" wizard. > > 2) People host on Github not because they have to but because > it's readily accessible to a wide audience (everyone has a Github > account). > I mean, it's a purely social thing which has nothing to do with > peculiarities of different DVCS-es. > > And please also consider the reverse problem. Suppose I decided to > self-host my repos. So I rented a VPS, made Fossil up and running there > and started to host some project there, which gained some popularity. > Then I lost interest and that VPS got its support terminated and went > offline. Sure, since it's a DVCS, some folks will have backup repos, > but then there's this problem of resurrecting the stuff back. With a > well-visible hoster like Github, someone will merely fork my repo and > start caring about it. Everyone will be able to see what have happened > using that "network" feature of the Github web UI, which basically > allows to see which clones are more recent. > > To recap, centralization has both its pros and cons, and this has > nothing to do with particulars of DVCSes. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
