Hi Michael,
Thanks, mostly agree with your thoughts, with two comments...
On 10/3/2014 6:55 AM, Michael Meeks <michael.meeks@collabora.com> wrote:
B. It is true that there is a sense in which large corporate
users of LibreOffice capture a lot of benefit and cost saving
from that - and a great way to contribute back is to help
fund someone to represent your interests in the development
community - by writing regression tests for your pet features
and being present in the discussions.
+ arriving after the fact and complaining doesn't work.
1. Some people (like me) are of limited skills.
Setting up an entire automated build/test environment is simply way
beyond my capability. The best I can do is download installable builds
and simply test them by using them.
I'm happy to do this, but hopefully you recognize that it is basically
impossible for someone to test all or even most of the features that
they use on a daily basis, and it would be very easy to miss something.
C. Anything is possible, don't assume that because it is
'broken' today, it will not be fixed tomorrow. Please don't
assume that because it is difficult a volunteer won't fix it
I know volunteers of amazing skill and tenacity nailing
horrible bugs left/right =)
2. There is a huge difference between:
a) bugs that are directly introduced by a specific developer while
working on a new feature or a specific bug, and
b) old pre-existing/legacy code/bugs that current developers had
nothing to do with.
Meaning - a developer should be responsible for the code they write,
including fixing bugs when they are found *without* resorting to
"'patches welcome' or 'pay someone to fix it'" type responses in the bug
reports (or on this list) - the latter only being appropriate for:
a) new feature/enhancement requests, and/or
b) old pre-existing/legacy code/bugs
If the vast majority of the developers don't agree with this principle,
and in fact believe that they should be able to just commit code for
something, then go on their merry way and/or respond with the "'patches
welcome' or 'pay someone to fix it'" responses, then I guess we are so
far apart philosophically that I should just stfu and go away.
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
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.