On Dec 26, 2017, at 12:07 PM, Bob Friesenhahn <bfrie...@simple.dallas.tx.us> wrote: > > On Tue, 26 Dec 2017, J Decker wrote: >>> Why aren't you moving all of your GitHub projects over to Fossil! >>> >> Because Pull Requests, and a larger variety of tools to deal with Git >> repositories. > > It is good that such tools are available to help surmount Git's extreme > complexity. Are there such tools available for Fossil?
Fossil already offers a large subset of what GitHub adds to Git: 1. Issue tracker -> ticket tracker. 2. Wiki 3. Markdown file rendering, including README.md rendering in file view, allowing embedded web documentation. 4. Graphical commit history. 5. Branch and tag displays. 6. Web user management, role-based access control. 7. Full-text repository search. 8. Automatic cross-linking of tickets/issues, comments, wiki articles, etc. There are still some things GitHub does which Fossil does not, usually on purpose: 1. Pull request tracking. This falls out of GitHub’s centralization, which as I argued in a separate post is one of the risks of using GitHub. 2. Gists. Fossil has other ways of accomplishing much the same end, but nothing exactly like it. 3. Code review between push and pull. Fossil is intended for teams small enough where social solutions to bogus checkins are usually sufficient, with technical measures to back that up. (e.g. fossil merge --backout, fossil amend --branch bogus, etc.) 4. Social networking. (@ mentions, etc.) Again something that requires centralization. 5. github.io: Not needed with Fossil, since by using it, you’re already running a server of some kind, so you have the ability to run a web site alongside your code repository. My two largest public Fossils are hybrids of this sort, with some URLs served by Fossil and some by the static web server. 6. More and prettier graphs and such. Woo. :) And there are several things that Fossil does which GitHub does not: 1. Easy diffing between two checkins from the timeline view. 2. .wiki embedded documentation rendering in addition to .md 3. Skinning. Every GitHub-hosted project looks the same. Many built-in skins if you just want to pick one rather than design one, or if you’d rather riff off of someone else’s core design. 4. Single-executable, truly free, with no tie to a central authority. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
