To avoid discussions as in Bug 51597 and othrs please add a privacy hint nearby 'Submit' button: "All your contributions will be public in WWW! By clicking the 'Submit' button you irrevocably agree to release your contribution under the CC-BY-SA 3.0 License and the GFDL. If you can't agree to these terms for documents you planned to attach you can state in this report that such a document exists. QA team will discuss with you further proceeding in the bug." Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Firefox/16.0 SeaMonkey/2.13.2
IMHO a valid and very reasonable request, therefore set Status to NEW (confirmed). (Personally, I would flag this as ‘enhancement request’; but given the importance of legal problems in these days, the mere absence of such a disclaimer may very well be regarded as a bug ;-)
I have submitted a patch for this. It will be online after the next update of the BSA
(In reply to comment #2) > I have submitted a patch for this. It will be online after the next update > of the BSA Wow -- that was fast! Thank you very much!
@Joel Can you pleas update the BSA so that we see Rob's several bug fixes?
@joel @Rainer I want to update the bugzilla myself on tuesday/wednesday as there are many changes and then I can try and fix anything that went wrong by accident.
I did an update today, still seeing a bit strange output but it's working. I'm just going to make this a cron job and make bsa update every time I boot up my machine. If someone sees an issue with me doing this please let me know and I'll not do it but if no one says anything by Tuesday or so I'll go ahead and add it to my startup scripts
@joel: The BSA is broken at this moment as the version isn't copied correctly to the bug and it is required. I already patched it in the repository. Please don't auto-update the BSA. The problem is that there is no real test-system so sometimes I have to commit something that isn't tested and can only be tested in production. When I update myself then I can try it out and immidiatly fix it. Yesterday for example I did a lot of changes and some wheren't testable, so I wanted to update myself and test everything.
Makes sense, any idea how many people have the permissions to update BSA right now? We might want to keep each other in the loop a bit more as I update any time there is a new version in FDO, but from what you're saying, sometimes you'd prefer me not to.