Hi, [email protected] wrote: >> Usually that reason is "security issue" or "customer sensitive >> information". >> > This seems to fall under the "csi" category probably.
The unfortunate thing for me is "this will increase in the near future before it gets better". Is there a possibility of putting in place some kind of process whereby the bugs can be public & sanitised (without any CSI) and any super-zoomed surveillance photos, ballistic reports, DNA profiles, fingerprint searches and other CSI stuff can be somewhere else? (excuse my attempt at levity - hope it doesn't get lost in cultural translation!) Having closed bugs is one thing - planning to have more is another. >> But like you said, there should be a way to request access for people >> who need to know. >> > As far as I can tell, this situation is exceptional and we should return to > normal very soon. > I completely understand the frustration and actually share it... a suggestion would be to have a "Reason" field which would be required when closing a bug to public - at least that way people would know why the bug was closed off. Reasons could be "confidential information", "Security issue" or "Oops, I checked the checkbox by mistake" :) Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
