On 19 Mar 21:14, Matthias Beyer wrote: > Hi, > > I'm looking for text based bug tracking software and BE looks promising, > though > there are no commits since 2013... so... > > Is this project still alive? > Is it usable?
Matthias, Bugs Everywhere was usable when I last used it, years ago, and I can't imagine that it would have broken, as it is packaged well and has straightforward dependencies. Since you mention that you want a text-based bug tracking software, I have a feeling that you may not care for many of Bugs Everywhere's other features, so you might also consider text-based "note-taking" software, such as org-mode (which I don't use either). But do try it at least; it should be pretty easy to install on Debian or Gentoo or Fedora. I apparently submitted it to PyPI a while ago, and you might find that helpful on other operating systems. https://pypi.python.org/pypi/bugs-everywhere/ On 19 Mar 23:17, Matěj Cepl wrote: > https://matej.ceplovi.cz/blog/current-state-of-the-distributed-issue-tracking.html > > Matěj Matěj, I enjoyed your overview of the distributed issue tracking. It got me thinking about why I never used Bugs Everywhere very much. The idea of storing issues as files is the same repository as the code is very appealing to me, and this was what originally attracted me to Bugs Everywhere. I still do this now, but I use very plain text files with simple lists. Here is an excerpt of one of them. Wider testing -------------- Test in other environments * Some sort of BSD * Windows I rarely work very closely with large teams of people, so it is easy enough to discuss things in person (if I'm working closely with a few people) or over email (if I'm working distantly with a lot of people). Then I copy the conversations to the source code repository. The projects that I work on are usually quite simple technically or at least have minimal human interfaces. When they are more complicated, they have very few users. Because of this, I didn't really use Bugs Everywhere's features for cataloging issues; there are very few issues and users, so there is also very little feedback, and it is very easy to catalog. Bugs are usually very easy to replicate too. Occasionally I succumb to the temptation to accept a job, and this is pretty much the only time that complex issue trackers are necessary. Bugs Everywhere is poorly suited for this use case because it's not hip and you have to install it. To be clear, it's not like marketing Bugs Everywhere differently and providing hosted Bugs Everywhere services would make it any more appealing than any presently hip web-based issue tracking service. In my experience, the purpose of submitting issues for paid work is only to maintain the illusion that people are working hard, using advanced technology, and making consistent, predictable progress; and all of the popular issue trackers are pretty good at these things. Someone always finds the issue tracker confusing or cumbersome, but frustration with a particular issue tracker only contributes to the aforementioned illusion, as does the substitution of one issue tracker with another. I suspect that real issue tracking is beneficial for free software projects with many people who make small contributions, but I have never been in a position choose the issue tracker for such a project. _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
