Hi Gerald, Hi all,
On Fri, 05 Aug 2011 22:51:55 +0200
Gerald Leppert <gleppert@gmx.de> wrote:
1. The whiteboard tag "ProposedEasyHack" does not seem to
have any effect. So far, I have not seen any bug tagged
as "ProposedEasyHack" which was touched by a developer
and changed to "EasyHack"
It might sound unfair to you, but I dont consider that a failure.
Developer resources are rare and we now have more than 100 EasyHacks
that were (hopefully) checked by a developers to indeed be assumed to
implementable by the target audience. What do you think will the
project gain by having 200 or 1000 possible tasks? Will suddenly more
people appear and work on them? If not, why should we waste scarce
developer resources on checking the ProposedEasyHacks now? It is still
good to have the ProposedEasyHacks in the pipe, should we have a drop
in open EasyHacks (because they where solved), but as of now, IMHO we
are in no hurry to make a proposal an EasyHack proper.
2. Furthermore, if an easy bug or enhancement request does
not contain any information on being a easy hack, I have
not seen anyone adding this flag to it afterwards, even if
it is really easy.
Thats being done, if a dev comes across such a case. But OTOH there
really is no lack of EasyHacks now, so we dont need to be proactive wrt
this.
3. You mentioned that it is very very rare that someone
"magically picks up" enhancement requests. My experience
is different. Please see: bug 33751, bug 36734, bug 36735,
bug 36946, bug 36977, bug 39167, bug 39168.
The kind of bug has little to do with it being easy or not. It is
mostly irrelevant to the question, if somebody is able to get a
motivating start as a code contributor with it.
This is an argument to be more laissez-faire with the end
users adding enhancement requests and EasyHacks to
bugzilla.
No, its not as we have no lack of EasyHacks.
I just propose this. In my opinion, it can help to drive
innovation, to collect ideas, to identify easy hacks and
to attract new developers.
It is great to collect ideas, but it does not have to be tagged as an
easy hack for that.
Please keep in mind that end users might not be that
stupid not to be able to identify easy enhancements.
Not to be able to identify an easy hack has nothing to do with
stupidity. Assuming to do so without code experience in the relevant
code however has. It is not even easy to get this right all the
time _with_ code experience.
Best,
Bjoern
--
https://launchpad.net/~bjoern-michaelsen
Context
- Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 (continued)
- Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Bjoern Michaelsen
Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Christoph Noack
Re: [Libreoffice] [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167 · Thorsten Behrens
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.