Hacker News Reader

Comment by foo101 | Hacker News Reader

I have always wanted something like this without having to move away from Git (to Fossil).

A bug tracker like this allows the bug history to be tracked and remain with the source code which is much better than keeping the bugs in a web based service because every 5 years you need to migrate it (Bugzilla to Trac to JIRA) and in every migration, some context or formatting is lost.

For something like this to be successful in enterprises, the tool should be management-friendly. Right now JIRA leads because it allows management to pull pretty reports out of it. Is there anything planned in git-bug to appease these management type people so that it has a good chance of taking off in the enterprise world too?

View on HN

Fossil's fantastic. The next release includes (in addition to their extant version-controlled tickets, wiki, and blog) discussion forums. https://www.fossil-scm.org/index.html/doc/trunk/www/forum.wi...

Are there any active Fossil instances available for free/open source projects? I found Chisel, but am not sure whether many of the projects are active.

Also, the design of Fossil and Chisel is s bit difficult to read on mobile.

If you click through Chisel you can find a few active projects. You're right about discoverability though; It's not great.

Fossil's neat because it really tries hard to be decentralized. Because of that the repo is really all you need. Hosting isn't so important when code, bugs, forums, and wiki can be moved by copying one file. The downside is that there's no FossilHub with thousands of projects using similar UIs and conventions.

As far as Fossil hosts go, I know of at least one more: https://secure.hydra.ecd.space/

I think one issue is that it's really easy to set up a public Fossil instance. It takes about two minutes to get it running if you've got a web server with CGI support.

If you mean active Fossil repos accessible over the web, there's Fossil itself (https://www.fossil-scm.org/index.html/doc/trunk/www/index.wi...), and SQLite (https://www.sqlite.org/cgi/src/doc/trunk/README.md). If you mean Fossil repo hosting, I know of Chisel but haven't used it and don't know anything about it. I don't think it requires much in the way of hosting though.

Edit: corrected SQLite URL.

or the mORMot ORM/REST framework: https://synopse.info/fossil/timeline

That is some phenomenal documentation.

> Also, the design of Fossil and Chisel is s bit difficult to read on mobile.

That's just the default. You can easily change the CSS, though it would be nice if you could select from themes created by others, particularly to get one that's friendlier for mobile users.

Looks like it exposes a GraphQL API - should be able to pull all the data you need out of it. Sounds like an excellent contribution opportunity :)

Upvoted for Fossil reference.

Now we just need to be able to also put a wiki in the same repo.

I do this with vimwiki: https://github.com/vimwiki/vimwiki

Can you describe your setup? I also use vimwiki but separately so interested to learn from your experience.

It's really just:

  mkdir Notes/
  vim Notes/index.wiki
  git add Notes/index.wiki

See ":help vimwiki-temporary-wiki" for details, but basically, it recognizes the Notes directory as the root of a wiki upon opening the file.

Since it's just tracked as a normal part of the repo, it gets branched and merged along with the code. So for example if I make an experiments branch, any wiki changes regarding the experiment won't sit around polluting the wiki if I decide to drop the branch. Similarly, any changes relevant to the branch I am working on get merged together along with the code merge.

Reply on news.ycombinator.com