On Wed, Apr 23, 2014 at 3:03 AM, Andrea Pescetti <pesce...@apache.org> wrote: > When someone complained that OpenOffice crashed on their company documents, > I've always answered that either they made the documents available in > Bugzilla or we couldn't do anything about it. Now it happened to me and I > realize that my suggestion is easier said than done! > > I received a DOCX document that OpenOffice Writer cannot open (crash). The > company that sent it to me cannot make it public: it's a confidential work > document. > > In general how can we handle this? It's very important for the project to > have a good reputation in companies, so if we crash on company templates we > should be able to know it and fix it. > > What options do we have available? Do we accept private attachments in > Bugzilla? Can a properly obtained stack trace replace the need for the > actual document, maybe? Other options? >
We have the technical ability to do this in Bugzilla. We do that with security-related bugs, for example. They are only visible to those on the security team. The entire bug report is restricted, not just the attachment. But I don't think this is a good practice to do in general. I don't think we want volunteers to consider themselves responsible for the handling of their confidential documents. -Rob > Note: in my case I already asked for, and received, a working ODT version. > I'm interested in the generic discussion. > > Regards, > Andrea. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
