Hello, most important thing first: your bugreporting tool (at least what I've seen in the usage example) looks good :-) Nevertheless, there are always things that can be improved. You probably already know/remember I'm scaring each and every developer with bugreports, and you are not an exception ;-) on Montag, 11. Juli 2011, Mihnea Dobrescu-Balaur wrote:
* aid - helps the user to determine which is the „suspected” package that causes a problem
Can you paste an example, please?
* check account - verifies that the user has a valid account and if so, it stores the user's credentials in a hidden file, base64 encrypted and pickled to make them not human readable; if the data is
Just for the records: base64 does not mean "encryption", it's only "make it unreadable for humans".
Some sample usage for submitting is here [0].
I'll include parts of the sample usage in the mail:
These are the similar bug reports found 0. python-django-annoying just scheduled and can't commit to OBS
Do you want to contribute to one of the bug reports above or submit a new one? yes (contribute)/no (new one) Yes: contribute No: submit new
Answer: no
Instead of yes/no, something self-explaining would be good - maybe c/n for [c]ontribute / [n]ew And please include the bug number of the "similar bug reports" in the output so that I can check the content if needed.
Getting list of components from Bugzilla for product openSUSE 11.4. Available components: 0. Apache 1. AppArmor 2. AutoYaST 3. Banshee 4. Basesystem 5. Bootloader 6. Commercial 7. Compiz 8. Development 9. Documentation 10. Evolution 11. Firefox [...] Which one? Enter a valid index number between 0 and 48: Index: 8 Using component Development.
The component is a difficult beast (in general, not only in your tool) - the question is if there is some way to autodetect it based on the package name. The special thing in your tool is that you already know the package (and therefore the assignee), which makes the component less important (but not superfluous, it's still needed for QA contact, statistics etc.). Besides that, I'd say you should avoid index "0" - humans usually start at 1 ;-) (that's valid for more "choose one" options)
This/these address(es) were found: assignee: bg@suse.com
I wonder about the assignee - osc maintainer openSUSE:11.4 python gives me jmatejek@, not bg@.
cc: ['mrueckert@suse.com', 'ro@suse.com', 'cgardner@novell.com']
Just curious: where do you get the CC list from? I can't get any of those people via "osc maintainer".
Do you want to change the assignee? Yes/No
Answer: no Do you want to add another cc(s)? Yes/No
Answer: no
What about an option to remove someone from the default CC list?
Please describe the impact of the bug, choose a severity for the issue. Available severities: 0. Blocker
"Blocker" is a separate field in bnc, not an option for severity.
1. Critical 2. Major 3. Normal 4. Minor 5. Enhancement
Would you like to see their descriptions? Yes/No
Answer: 3 Invalid answer: yes/no only! Try again: no
Thanks for showing this usability bug yourself ;-) I like the concept zypper uses - in this case it woul mean "enter a number to choose the severity, or ? to see the description" It does not annoy users with "do you need help" questions, but still offers help for those who need it.
Which one? Enter a valid index number between 0 and 5: Index: 3
Do you want to add an automatically gathered system description? Yes/No
Answer: yes
Is the system description gathering the same for all reports or do you have some special handling to include specific logs - for example the y2logs when reporting a YaST bug, zypper.log for zypper, X.org*.log for X bugs, ...? BTW: Is there a real bugreport in bnc that was created with your tool? OK, that are enough bugreports, enhancement requests and questions for one mail ;-) No, wait, I have one more:
You can find the repo here: [1]
An OBS repo with a nice RPM package would be nice ;-) Regards, Christian Boltz -- Funktionieren Windows 98-Witze auch unter Windows 2000 oder braucht man da ein Update? -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org