Hey there!
I have been searching the web today for a good decentralized bug tracker
and stumbled upon bugs-everywhere. After I removed other projects from
my selection as they seemed abandoned, not mature etc., be was the only
project that seemed worth trying.
However, it really took me a while to get going:
I'm currently using Ubuntu Natty Narwhal, the 11.04 release, and the
package is still very old. I know that you guys are working on it,
however, I decided to compile it myself, but I ran into many errors.
After some searching I found out that I had to use "make DOC= install"
to prevent the missing dependencies. The installation process afterwards
seemed ok, but calling "be" just told me that the class
"libbe.ui.command_line.py" could not be imported. I had to investigate
that there's a PYTHONPATH variable that I could set to the appropriate
path, in my case
export PYTHONPATH=/home/heinrich/lib/python2.7/site-packages/
Afterwards, it worked! Now, please, could you put that on your website?
It really took me ages to find that out and I suppose there are many
people who run into these problems.
--------
I tried "be" a little bit, and there are some suggestions I would like
to make.
1.) 4a4:os Is a good point. The reason for including something like
"medium" or "normal" is that I want to differentiate between e.g. a
typo, which really is a minor bug, and lets say an if-condition that
always evaluates to false. (You know what I mean..)
2.) The overview created by "be list" could be slightly improved. It
might look like this:
---------------------------------------------------------------------
ID | TYPE | TITLE | SEVERITY
---------------------------------------------------------------------
1 | BUG | Missing file doc comment | CRITICAL
2 | TO-DO | Missing class doc comment | Future
3 | TASK | Foo | NORMAL
---------------------------------------------------------------------
I believe that this is really nice and it shouldn't be too much work. I
could try and implement it myself, if you wish. However, I really don't
know much of python :)
By the way, I would like to differentiate between "Bug Description" and
"Bug Title". The Bug title should be a short description (say, < 50
chars)
3.) Using wrong syntax should receive better help messages.
Current:
"be new" -> ERROR:
Missing required argument SUMMARY
Should be:
"be new" -> usage: be new [options] SUMMARY
Options:
-h, --help Print a help message.
--complete Print a list of possible completions.
-r NAME, --reporter=NAME
The user who reported the bug
-c NAME, --creator=NAME
The user who created the bug
-a NAME, --assigned=NAME
The developer in charge of the bug
(This is the be help new output without the text)
4.) "be show" should also list the "target" just as "tags"
5.) Interesting: The ID (the long hash) displayed with "be show" is
*NOT* the BUG-ID, which actually is the "short name". Maybe change the
name? Confused me a lot!
6.) "be help" displays weird description for command "be serve"
7.) Might be some more work, but
7.1) Integrate a log for changes to a bug. Could be implemented as
additional comments, like: "<date> Severity changed to CRITICAL by
<user>"
7.2) Create a "be vote BUG-ID +|-" command. You can vote on bugs either
pro (+) or against (-) it.
----------------------------------
Guys, you really have done great work so far and I do believe that this
project has some potential, however, there might be more things to do.
I would really appreciate if you could comment on my suggestions. If you
like, I will try to implement some of the changes myself - always wanted
to dig into python.
Thanks a lot!
Christian
_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
