Nice to see "report Bug"
(i) Will it gather information about the current context user is in?, would be good as the user may not be very descriptive or specific while filing a bug
(ii) if collecting such data care should be taken to not breach and privacy or gather any sensitive financial information. just the screen landed or path to the screen could be sufficient
Subscribe to:
Post Comments (Atom)
4 comments:
The bug report will only collect version information of KMyMoney and underlying libraries. No personal data and no info about your data file are sent with that.
Also, if you need to send your data to the developers, there is an anonymized file format that will strip all personal data off the file, and scramble the numbers so that you don't share any data. Also, the file you send is in plain format, so you can check it with a text editor before you send it to verify that.
Thats reasonable, but along with version info it will be good to capture the interaction flow/path user took if possible.
IMHO, capturing that interaction flow begins to enter into privacy issues. Even if it is sometimes handy to have, so far we have managed to fix bugs without it.
In those cases, I normally request an anon file and try to reproduce the bug myself. If it is a very special usage flow, we will follow up with the user or with other developers until we manage to reproduce and fix it. It has worked so far, and personally, I prefer to do it that way rather than with an automated tool even if it takes a little longer sometimes. Since we deal with important personal data, the trust of our users is very important to us and the automatic collection of data should be reduced to a minimum.
As I said, it has worked so far, but we could explore other ways if it were deemed necessary.
Okay then.
Post a Comment