Hi :)
Some online 'meetings' use a simple "+1" to vote in favour of something.
Some people often use it in an informal way, as i do (i copied them).

Most of the ones i've seen (ie LibreOffice and TDF ones) have usually
talked through the issue until a mutually satisfactory proposal can be
posted or consensus reached.  So i've never noticed anyone posting a "-1"
or whatever is normally used to vote against.  I've seen people abstain but
that usually seems to be because they are busy and just didn't get around
to it (usually they had deputised someone to make their votes for them)
rather than out-right making a statement.

So it's 1 person = 1 vote = total support, although i kinda agree with
James' sentiment there.
Regards from
Tom :)


---------- Forwarded message ----------
From: James Wilde <[email protected]>
Date: 11 October 2015 at 12:18
Subject: Re: [libreoffice-users] Re: Installing Libreoffice in Ubuntu
To: Alex Thurgood <[email protected]>
Cc: [email protected]


+20

Alex Thurgood <mailto:[email protected]>
> 11 Oct 2015 11:44via Postbox <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach
> >
>
> Le 10/10/2015 23:36, Italo Vignoli a écrit :
>
> Suffice it to say that Andreas is a vociferous participant in this
> discussion list, but that doesn't make his criticisms any less justified
> or relevant. What he dislikes is badly implemented change for change's
> sake, and that is an inherent problem in LibreOffice's development. The
> project from the start has sacrificed behavioural stability with regard
> to the end user for feature creep. We are quite clearly in the "bazaar"
> mode of the cathedral and bazaar dichotomy, where no overlying
> dictatorship (benevolent or otherwise) exists to govern the direction
> code development should take. This has positive and negative effects -
> the positive being that people can just turn up and work on the thing
> they want to implement - the negative being the law of unintended
> consequences, or collateral damage, i.e. bugs newly introduced that
> change long standing behaviour to which users have become accustomed.
>
> Fortunately, there are still people like Andreas to call the code
> contributors out on those decisions.
>
> I would suggest putting yourself in an admin's place where they have
> probably invested long hours in developing a turnkey
> OpenOffice/LibreOffice solution for their group of users, then finding
> one day that that longstanding behaviour has changed because someone
> else has not thought through a code change due to the tentacular nature
> of the code base with no one having an overarching knowledge of it all,
> and you will perhaps understand Andreas' frustration (which I happen to
> share and have voiced it on the mailing lists in the past).
>
> At present, long term support (bug fixes, security updates) for older
> versions is to my knowledge only available on Linux and only with regard
> to certain distributions. If you are not on Linux, then you are stuck
> playing catch up with versions that successively introduce new bugs or
> behaviours that don't get fixed for at least several point releases, or
> for certain OSes, over multiple major version releases. Steve's mention
> in this thread of EPS support and printing is just yet another
> illustration of a change that was made that has a huge impact on
> non-Linux OSes - all because someone thought it would be a good idea to
> make that change without providing a solution for all platforms. Video
> support in Impress is yet another issue that got significantly worse
> with the move to the 4.x branch. What was the message we gave to our
> users ? "Suck it up." There is only so much of that that users and their
> admins are prepared to do, and in the end, it won't be surprising if
> people switch to another product that offers them greater longterm
> stability where such changes are less invasive or devastating to the
> day-to-day running of the organisation.
>
>
> Alex
>
>
>
>
>
>
>
>
>
> Italo Vignoli <mailto:[email protected]>
> 10 Oct 2015 23:36via Postbox <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach
> >
> Please avoid entering in a discussion with a well know enemy of
> LibreOffice. Andreas Saeger aka Villeroy has been spreading FUD about
> LibreOffice since forever. People happy with a dead and buggy software -
> aka Apache OpenOffice - should avoid commenting on LibreOffice mailing
> lists.
>
> Florian Reisinger <mailto:[email protected]>
> 10 Oct 2015 15:27via Postbox <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach
> >
> Would you be so kind as to tell us which aspects got worse?
>
> Andreas Säger <mailto:[email protected]>
> 10 Oct 2015 15:26via Postbox <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach
> >
>
> LO introduces far too many changes to the worse which is why I still
> prefer OpenOffice.
>
>
> Philip Jackson <mailto:[email protected]>
> 10 Oct 2015 15:23via Postbox <
> https://www.postbox-inc.com/?utm_source=email&utm_medium=sumlink&utm_campaign=reach
> >
>
> Thank you Tom for that interesting explanation of the documentation
> website.
>
> It explains why I often have trouble finding answers there. I keep a local
> copy
> of "OpenOffice.org 3 Writer Guide" on my machine and can often find answers
> there faster than on the website.
>
> Philip
>
>
>

-- 
To unsubscribe e-mail to: [email protected]
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: [email protected]
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

Reply via email to