On 4/23/14 9:03 AM, Andrea Pescetti 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? > > Note: in my case I already asked for, and received, a working ODT > version. I'm interested in the generic discussion.
I understand the problem and we know this situation. I believe it is not easy to address in an open source project. Either the documents can be cleaned up and confidential data get removed or the company contacted another company where special agreements can be done. If you need more than the community project can provide it is possible to buy professional help and support. Not everything is for free and that has nothing to do with good or bad reputation. It's up to the company, either they can provide a clean document containing the problem or buy professional support/service. I personally don't want to deal with confidential data/documents in public or in the bugtracker. Juergen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
