Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index

Hi Felipe,

The option is not going to go away, because it is now an included
feature of the LibreOffice NextCloud instance. The only reason for this
thread is to determine if the Docs Team wish to use the feature or not.
Once we have reached consensus on that point I will make the appropriate
changes to the Contributors Guide chapters and relevant wiki pages.

Best Regards

On 15/10/2020 13:01, Felipe Viggiano wrote:
Hello Dave,

Thanks for the information. It was very clarifying!
It sounds like a good feature, and I agree it is very conflicting with our
current workflow for the revision of the guides.

Perhaps we can leave this option on the table for other assignments for the
Doc Team that may arise.

Best regards,
Felipe Viggiano

Em qua., 14 de out. de 2020 às 17:08, DaveB <>

Hi Felipe,

It shows good judgment to to keep an open mind. I gave my initial
assessment in my post:

The Nextcloud versioning system is an excellent mechanism to use under
the circumstances for which it was designed. Let's say you and I are
cooperatively working on a document inside LOOL via our web browsers
(Not downloading, editing and uploading), then every time one of us uses
the LOOL "Save" option that saved edition is versioned and either one of
us can go back and recall/recover any one of the previous versions. In
my limited testing I found issues as to what we would do with the
recalled/recovered versions. The mechanism is very safe, but demands
absolute and total compliance to a working regime with no deviation
permitted, otherwise we could finish up in a confused mess.

Through circumstances beyond our control, the Docs Team were obliged to
move our workspace arrangements from the "ODF Authors" Plone instance to
a LibreOffice NextCloud instance. In so doing we tried, as far as
possible, to retain the same or a similar reliable workflow where
contributors retracted (downloaded), edited and returned (uploaded)
edited/reviewed documents to our workspace. To continue with this
workflow and to adopt the Nextcloud versioning system, would mean that
the filename given by the first editor/author must never be changed for
any reason or under any circumstances (no extra or missing dots, dashes,
underscores, etc.), otherwise the Nextcloud versioning system fails and
becomes a hindrance, not an advantage to us.

As I have said previously, I am *NOT* opposed to the very good Nextcloud
versioning system, but it is a solution to a problem we currently do not

Best Regards

On 14/10/2020 13:57, Felipe Viggiano wrote:
Since I'm not familiar with the Nextcloud versioning system, I'm going
option #1 as well.

But I would like to keep an open mind about this for the future. Has
tested this feature?

Best regards,
Felipe Viggiano

Em qua, 14 de out de 2020 09:25, Samantha Hamilton <> escreveu:

Option 1 looks great!


On Wed, Oct 14, 2020 at 5:55 AM Steve (GMail) <>

Option 1 for me.

I'm unconvinced of the need for a versioning system.



------ Original Message ------
From: "DaveB" <>
To: "LibreOffice Documentation" <>
Sent: 13/10/2020 18:08:37
Subject: [libreoffice-documentation] [VOTE] On changes to documentation

Hi All,

Other than Peter Schofield nobody else has expressed any thoughts or
opinions as whether or not we should adopt the NextCloud versioning
system, or should we continue with the proposed folder structure and
file naming format, so I propose a poll:

Option 1.
Go ahead with the simplified folder structure and file naming format,


Option 2.
Adopt the NextCloud versioning system.

I propose closing the vote at 17:00 UTC on Friday 16th. October 2020.

Best Regards

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.