Hi :)
You guys are over-complicating it. Just post a "feature request" via
the bug-reporting system
Similar problems occur in proprietary systems too but with less chance
of reporting the problem. Also the bosses need to understand the
problem and give it more attention than their golf handicap before
bothering to do anything about it. If it doesn't affect profits then
why spend money on fixing it? OpenSource allows anyone to get on with
sorting out a fix without having to wait for the bosses to give the
orders.
Also although the organisational structure is largely non-hierarchical
there are still ISO standards and other external rules to guide
development, there are committees, working groups, team discussions
and informal chats. At worst, development becomes more Darwinian with
successful forks developing and taking the lead positions but getting
inspired by other projects and even copying chunks of code from them.
Look at how Ubuntu was in the number 1 slot at Distrowatch for years
but now Mint has taken over. Mandrake evolved into Mandriva but then
forked into Mageia and now Mageia is far higher than either of it's
forebears managed.
Regards from
Tom :)
On 6 January 2014 09:46, Peter West <lists@pbw.id.au> wrote:
Peter West
"Where is he who has been born king of the Jews?"
On 6 Jan 2014, at 6:11 pm, James E Lang <jim+lou@lang.hm> wrote:
This has been a most enlightening discussion.
I am a big fan of open source software. That said, this discussion has shined a bright light on
one of the most problematic areas of the concept.
I might be totally off base here but as I view it, without a central management structure to
_enforce_ standards two separate groups of developers may develop what appear to the end user as
being similar related features that are inconsistent with each other. This results in unpleasant
surprises for the end user.
If there had been a central management structure to _enforce_ standards, there would be NO open
source software, full stop. No linux, no OS X, no samba, no python, no MySql, no Open Office and
no Libre Office, to mention but a few.
The productivity of OSS development teams, imperfect as it is, cannot be matched by any
structures designed for the management of software development. It is only matched by startups
with small, committed teams and inspired technical leadership. Success and rapid increases in the
scale of the development teams kills their productivity. Companies that have carved out a
fantastically profitable niche can survive this transition, bit they can only retain a fraction
of their original productivity.
--
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
--
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
- Re: [libreoffice-users] Calc cross-sheet issue with COUNTIF and AVERAGEIF... (continued)
Re: [libreoffice-users] Calc cross-sheet issue with COUNTIF and AVERAGEIF... · Hylton Conacher (ZR1HPC)
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.