Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Le 2010-11-15 20:36, Andrea Pescetti a écrit :
Sebastian Spaeth wrote:
I don't know if and how easy this would be in drupal. So far I have
coded a very simple webform in "django" (python is my thing :-)) to
allow uploading a document and a comment.

This would be elementary in Drupal.

Thanks for this Andrea.

The only thing that is then left, is to link the uploaded doc to a
bugzilla issue and display the status from the bug in question. The
linking to a bug would (in my vision), not necessarily happen by the
user, but by QA team, that vets those entries.

And this triaging phase is indeed the main challenge, both in technical
and in resources (volunteers) terms.

IMO, I believe that we could probably get a good LO triage team together. We have a growing membership and some have been with OOo for quite some time as OOo could be called at this point a mature product (albeit young). But our user base as well as our "potential user-base" is in the millions. Getting a triage team in various languages should be a feasible project.

If we keep the process as personal as possible (i.e. <user with a potential bug> + <triage member vetting the potential bug>), then the bug reporting remains unchanged.


E-mail to for instructions on how to unsubscribe
List archives are available at
All messages you send to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.