https://bugs.freedesktop.org/show_bug.cgi?id=71534
--- Comment #4 from Charles <[email protected]> --- (In reply to comment #3) > (In reply to comment #0) >> Say I have a Microsoft Office document (doc/x, xls/x, ppt/x) that exhibits >> compatibility issues. >> >> I want to submit this document, along with a description of the problem(s), >> somewhere that it can be triaged (confirmed or not) by someone, and >> submitted to the right person to look at it more closely. > The main danger with the above is that it can result in an increase of > reports like bug #67450. Please just use 'bug 67450' (without the # sign) when referncing bugs so that the bug link is clicky... :) As for your fear... > As Joel Madero (QA) points out in the related comments to that bug, > it is fundamentally unhelpful to simply provide an example problematic > file with a comment like "does not work" or similar. While I agree that the more precise a users initial description of the problem the better, the fact is, it only takes a minute or so to download a problematic document, open it in both Libreoffice and Microsoft Office (remember - this bug/feature request is *only* about Microsoft file format issues), and look for for obvious errors/problems. > A report needs to be more specific if it is to have any chance of: (a) being > understood / comprehended; (b) being reproduced; (c) being fixed. Again, I agree that in most cases more detail is better, but I totally disagree that a developer cannot simply open a document in both programs, and spend a few minutes, and ascertain formatting problems/discrepancies... possibly even doing a much better job of doing so than the original reporter would ever be capable of. A bare minimum from the user should just be something like 'open it in Libreoffice Writer 4.1.3 and Microsoft Word 2010 and compare pages 1 & 2'... And these two pieces of information (the versions of each software) should obviously be part of the minimum mandatory info the user must provide. > We've had a bit of discussion about whether one should have to > login before submitting a bug report or feedback. > > How would you address the problem of SPAM Explain in very clear language that in order for the user to submit a document for analysis, they must either log in with their bugzilla account, or provide an email address for confirmation purposes. Clearly explain that before their submission will be accepted, they will have to click a confirmation link in a confirmation email that will be automatically sent to them upon their initial submission. At least this would be the most obvious way off the top of my head. > I think SPAM is one issue but IMO an even more important one is social > responsibility. This is essential to the wellbeing of any community. > Demanding that participants register for an account promotes this and is a > fairly consistent approach across most sites where users can provide > feedback and generally comment on issues. Again, I am much more concerned with Libreoffice having improved file format fidelity with Microsoft Office document formats than I am forcing someone to 'participate' in our community more than they wish to do. Encourage it, certainly, but don't *require* it... -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
