Hi,
On Fri, Aug 5, 2011 at 5:23 PM, Thorsten Behrens
<thb@documentfoundation.org> wrote:
can you propose an alternative patch in the bug report?
I'll try to produce something in the next few days.
And about all the politics here ... I just don't know where to stand.
The two Easy Bugs in question here really seem to have been easy
hacks, so at least superficially the description fit. About the notion
that there should always be a dev to mentor people on Easy Hacks, I
don't know... the term "Easy Hack" doesn't really fit then, "Mentoring
bug" might be more appropriate here (but I agree that outsiders – like
myself – can't actually judge how hard certain code is to change).
The most important thing is probably that TDF has a good and
consistent definition of the term Easy Hack, and following that, a
section about filing (proposed) Easy Hacks) should be added to the EH
wiki page.
What might be a good idea would be to have a script run once a day
that checks which bugs have been newly marked with "EasyHack" and then
have someone sort through the results (this would probably need work
from developer and also a designer/UX'er).
Astron.
Context
Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Christoph Noack
Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Thorsten Behrens
- Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Astron
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.