Re:Github experiencing major service outages across all serv...
by chacha102 on Saturday December 22, 2012 @09:24PM
(#4958336)
Just to note, Github Wiki is git repo, so it you want to backup the data, branch, etc, you can push pull and everything else with any Github Wiki.
Github issues aren't however.
Re:Github experiencing major service outages across all serv...
by dchest on Sunday December 23, 2012 @11:28AM
(#4959810)
But you can't view GitHub Wiki in browser without some preprocessing. In Fossil, I just do
$ fossil ui
And view (and edit) a copy of the whole project website, including wiki, tickets, history, interface for diffs, etc. in my browser.
Re:Github experiencing major service outages across all serv...
by moe on Saturday December 22, 2012 @09:21PM
(#4958325)
The problem with fossil is that it's not git. However it would indeed be nice if someone built a distributed github on top of git.
Re:Github experiencing major service outages across all serv...
by zem on Sunday December 23, 2012 @03:49AM
(#4959004)
how does fossil do versioning of the issue tracker? i tried using a setup like that for a while, with ditz as the issue tracker. it turned out to be really inconvenient to have my issues versioned along with my code as part of the same repo - i want to navigate around in my code's history and branch layout with the issue tracker conceptually being an entirely separate repo that always points to HEAD unless i explicitly go scroll back in it.
Re:Github experiencing major service outages across all serv...
by dchest on Sunday December 23, 2012 @11:26AM
(#4959804)
Fossil doesn't track issues along with source code, unlike some scripts for bug tracking on top of git. While Fossil stores tickets in the same repository with source code, with the same basic format, tickets are separate entities and are not connected to the source code itself.
You can read more about it here: http://www.fossil-scm.org/index.html/doc/trunk/www/bugtheory...
In short, if you have a project's Fossil repo, you can work on everything locally, then push source, wiki, and issue tracker changes to a central repo at your leisure.