4 ms·
I think this is a great question. I was originally interested in BugsEverywhere, but noticed that the website linked to a demo at http://bugs.bugseverywhere.or
by ChristianBundy 7y ago
I think this is a great question.
I was originally interested in BugsEverywhere, but noticed that the website linked to a demo at http://bugs.bugseverywhere.org/ http://bugs.bugseverywhere.org/ which was... not a demo. This gave me the impression that the project was completely dead, so I moved on.
Recently I've been looking at git-bug, which is similar, but I've been hesitant to use it because the readme talks about how it's alpha software and I'm not super excited about the demo web interface.
I'd be interested to hear what others think.
- smoyer 7y agoI have a clone of the final repository state and had created a Java implementation in about 2013. I was interested in integrating it with Github and Eclipse at the time. Now I'm wondering about resurrecting that project and converting it to Go but I don't want to create something that doesn't get used.
- smoyer 7y agoI just played around with git-bug a bit ... I like it! It's kind of what I had in mind but I was going to create a BE compatibility mode. What it does do differently is stores the bugs in the reference tree so that no files are added to the project (well ... the ones that are added are in .git). Bugs and comments are committed and show up in the tree so I'm experimenting with how to run git log (aliases) without them showing up).
- michaelmure 7y agoAuthor of git-bug here, the webui is definitely just a proof of concept for now. I would definitely love to have someone help over there. As for the alpha status, yes, the data model will likely change before becoming stable, but i suppose i have enough user to warrant a migration tool if that happen.