<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><i>(I see that I replied to only one
list, so just wanted to include design and marketing. Sorry for
the double-up.)</i></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">Thank you all for sharing your
opinion.</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Please keep in mind that "a
really big jump" or "a major innovation" will always be very
subjective and depend on personal areas of interest or
specialties, and I suspect that we will have dozens of
different opinions (and no agreement) if we ask what
constitutes a feature that is significant enough to warrant
a major version number.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Concretely, here is the shortlist
of things that, in my _subjective_ opinion, are important in
the upcoming version (somewhat similar to László's):<br>
</div>
<div class="moz-cite-prefix">- availability on all major
desktop platforms, including through official app stores</div>
<div class="moz-cite-prefix">- advertise availability for ARM
processors on Windows</div>
<div class="moz-cite-prefix">- build baseline bump</div>
<div class="moz-cite-prefix">- zoom gesture support<br>
</div>
<div class="moz-cite-prefix">- cementing of updated visual
identity and improved theming following the OS's<br>
</div>
<div class="moz-cite-prefix">- improvements in accessibility
of documents, including accessibility checked in sidebar and
tagged PDF export by default<br>
</div>
<div class="moz-cite-prefix">- two new languages</div>
<div class="moz-cite-prefix">- multi-page floating tables</div>
<div class="moz-cite-prefix">- _maybe_ Skia by default on
macOS</div>
<div class="moz-cite-prefix">- _maybe_ new Windows installer<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Waiting for significantly
"bigger" (again, very subjective) changes in LibreOffice is
a bit unrealistic, knowing the project grows and has grown
very organically.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">In the end, I have no strong
opinion about it. I just hope everyone can remain respectful
and understand that sometimes, decisions have to be made,
and I believe the marketing team, after some discussion with
the rest of the TDF team, the Design team and the ESC, are a
good fit to take such decisions, instead of heated
conversations filled with subjective opinions on what
feature is or isn't important.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The recent interaction makes me
think a year/month versioning scheme is beneficial in that
discussing version bumps will not be needed anymore. It's
definitely not worth getting insulted, and I am sorry Italo
had to be at the receiving end of that. And as Jorge said:
let's not get bogged down into something that is in the end
quite trivial.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I do however want to say I
appreciate and take note of input from people like Regina
(associating major releases with ODF releases, the default
standard we are proud of), Kelvene (cultural aspect of the
number), David (deciding early on to allow work on more
disruptive projects) and Nigel ("The universal office
suite", highlighting our strength in language and platform
support).</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Cheers!</div>
</div>
</div>
<div class="moz-cite-prefix"><br>
</div>
</div>
<div class="moz-cite-prefix">On 29/3/23 21:36, Jaron Kuppers wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALupv_ezF7hChy5xzCGXrAbViudCnCozZpNgwOAPmsDx36TaGg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">I agree with Italo that changing to version 8
makes sense and that it is a marketing decision. Office
suite updates that become new version numbers rarely include
much in the way of ground breaking innovation and waiting
for some integration of some new 'ground breaking' feature
does not make sense. Nor does waiting for ODF1.4 which is
not a change in some way unique to LibreOffice. A new
version can also be framed around the plan for that new
version. What huge changes are we going to make during
version 8? It does not have to be limited to what changes
warranted a number change. I think universal accessibility
warrants a number change and makes for great marketing.</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">Italo, the way people talk to you is not
okay... know that you have the respect of many/most
community members who trust in your marketing expertise.
Many are quick to speak on a topic they have no formal
training in.<br>
</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:trebuchet
ms,sans-serif">My 2 cents...<br clear="all">
</div>
</div>
<div dir="ltr">
<div style="font-family:trebuchet ms,sans-serif"
class="gmail_default"><br>
</div>
<div style="font-family:trebuchet ms,sans-serif"
class="gmail_default">Cheers,</div>
<div style="font-family:trebuchet ms,sans-serif"
class="gmail_default">Jaron</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Mar 29, 2023 at
5:14 AM Pedro Rosmaninho <<a
href="mailto:mota.prego@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">mota.prego@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I would just like to
counter what Eyal Rosenberg says. Version number<br>
should be a marketing decision.<br>
But I agree with his points that marketing must consider
that major<br>
innovations or missing features should be included with a
major number<br>
change otherwise said number change will fall flat.<br>
The number 8 is a great opportunity so it shouldn't be
wasted without<br>
having something impactful when it is launched.<br>
<br>
<br>
Regina Henschel <<a href="mailto:rb.henschel@t-online.de"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">rb.henschel@t-online.de</a>>
escreveu no dia terça, 28/03/2023<br>
à(s) 15:40:<br>
<br>
> Hi Italo,<br>
><br>
> the change from 6.x to 7.0 happens together with the
change from ODF 1.2<br>
> to ODF 1.3. If the decision it to keep this kind of
numbering, I think a<br>
> change to 8.0 should happen when LibreOffice starts
support for ODF 1.4.<br>
> ODF 1.4 will hopefully be released end of 2024.<br>
><br>
> Kind regards,<br>
> Regina<br>
><br>
> Italo Vignoli schrieb am 27.03.2023 um 19:11:<br>
> > Moving to LibreOffice 8 (instead of 7.6) makes
sense for marketing<br>
> > purposes, as media is looking at LibreOffice as
the real innovator in<br>
> > the open source office suite market, and the
feeling of journalists is<br>
> > that we are forever stuck at 7.x.<br>
> ><br>
> > We all know that the next version will not include
any significant<br>
> > innovation which can justify the change of
version, apart from the new<br>
> > build system for Windows and the availability of
LibreOffice for Arm<br>
> > processors on Windows (which has not been
announced).<br>
> ><br>
> > Playing with the number 8, which can be rotated
90° to become the<br>
> > "infinite" symbol, we can frame the next version
as LibreOffice for an<br>
> > infinite number of users, as we cover all hardware
platforms and all<br>
> > operating systems for personal productivity.<br>
> ><br>
> > This is my opinion. If the community wants to
stick with 7.6, I won't<br>
> > insist. I have received enough insults both public
and private for the<br>
> > marketing plan, and I am still receiving them from
a few people, that I<br>
> > am not willing to enter into that process again
(even if the decision on<br>
> > the "community" tag has not been mine, but it
looks like people have a<br>
> > very short memory).<br>
> ><br>
> > Looking forward to your thoughts.<br>
><br>
><br>
> --<br>
> To unsubscribe e-mail to: <a
href="mailto:design%2Bunsubscribe@global.libreoffice.org"
target="_blank" moz-do-not-send="true">design+unsubscribe@global.libreoffice.org</a><br>
> Problems?<br>
> <a
href="https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a><br>
> Posting guidelines + more: <a
href="https://wiki.documentfoundation.org/Netiquette"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://wiki.documentfoundation.org/Netiquette</a><br>
> List archive: <a
href="https://listarchives.libreoffice.org/global/design/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://listarchives.libreoffice.org/global/design/</a><br>
> Privacy Policy: <a
href="https://www.documentfoundation.org/privacy"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.documentfoundation.org/privacy</a><br>
><br>
<br>
-- <br>
To unsubscribe e-mail to: <a
href="mailto:design%2Bunsubscribe@global.libreoffice.org"
target="_blank" moz-do-not-send="true">design+unsubscribe@global.libreoffice.org</a><br>
Problems? <a
href="https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/</a><br>
Posting guidelines + more: <a
href="https://wiki.documentfoundation.org/Netiquette"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://wiki.documentfoundation.org/Netiquette</a><br>
List archive: <a
href="https://listarchives.libreoffice.org/global/design/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://listarchives.libreoffice.org/global/design/</a><br>
Privacy Policy: <a
href="https://www.documentfoundation.org/privacy"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.documentfoundation.org/privacy</a><br>
</blockquote>
</div>
</div>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Stéphane Guillou
Quality Assurance Analyst | The Document Foundation
Email: <a class="moz-txt-link-abbreviated" href="mailto:stephane.guillou@libreoffice.org">stephane.guillou@libreoffice.org</a>
Mobile (France): +33 7 79 67 18 72
Matrix: @stragu:matrix.org
Fediverse: @stragu@mastodon.indie.host
Web: <a class="moz-txt-link-freetext" href="https://stragu.gitlab.io/">https://stragu.gitlab.io/</a></pre>
</body>
</html>