Hi all,
On 01/09/2022 22:47, Michael Meeks wrote:
I would expect the ESC should intervene and cut out the
politics.
I believe that politics have nothing to do with what happened.
Your grep shows that there aren't that many "lool" that could be renamed
"cool" by mistake so I guess it's
What a silly thread.
Some neutral name for the integration should be picked and
implemented and/or both names be accepted; I would suggest 'lok'
for LibreOfficeKit. Commit/revert wars are a nonsense that helps
no-one - I would expect the ESC should intervene and cut out the
Hi Andreas,
On 01/09/2022 20:22, Andreas Mantke wrote:
I think there should be clear rules that there should not be any
barriers or something similar in the LibreOffice vanilla code.
But once I saw the changes from 'lool' to 'cool' in the source code I
wonder why the ESC didn't discussed and
Dear Community,
find below the agenda for our
TDF board meeting with a public part, and followed by a private part
on Monday, September 05 at 1800 Berlin time at
https://jitsi.documentfoundation.org/TDFBoard
For time zone conversion, see e.g.
Hi all,
On 01/09/2022 19:31, Simon Phipps wrote:
TDF's Board is not expected to intervene in the ESC's work beyond its
recent approval of ESC appointees. The request here is out-of-order.
I was wondering as well why Andreas would send a request to
board-discuss for a patch.
While delays
Hi Paolo,
Am 01.09.22 um 19:32 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 18:48, Andreas Mantke wrote:
I remember variable changing going on when LOOL has been forked into
COOL, and the removal of "This file is part of the LibreOffice project
:-(, but I thought that it was affecting only
Hello Shinji,
Am 31.08.22 um 23:00 schrieb Shinji Enoki:
Hello Andreas, all,
Thank you for your questions.
- What are the criteria to measure the value of a contribution?
- Which are the criteria for a non trivial or obviously insignificant
contribution?
- Would your rating differ from
Hi Regina,
It's still the ESC's role to resolve it, not the Board's. All the work on
code is done by individuals, and open source projects don't get to instruct
individuals on what to do or when to do it - there is no SLA. If none of
those individuals are interested in prioritising any
Hi Andreas,
On 01/09/2022 18:48, Andreas Mantke wrote:
I remember variable changing going on when LOOL has been forked into
COOL, and the removal of "This file is part of the LibreOffice project
:-(, but I thought that it was affecting only their own repository,
not LibreOffice core so I'm
Hi Paolo, all,
Am 01.09.22 um 18:09 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 17:36, Andreas Mantke wrote:
It is this patch (only a small one with two lines of code):
https://gerrit.libreoffice.org/c/core/+/138884
I see a comment "The correct naming for LibreOffice is lool"
and a
Hi Simon,
I think, a large delay between review and submit is not a technical
problem, but it needs a person who is responsible for an overview.
A technical problem is to provide a tool for a quick overview. However,
the dashboard-links from Guilhem look promising.
A large delay is
Hi Andreas,
On 01/09/2022 17:36, Andreas Mantke wrote:
It is this patch (only a small one with two lines of code):
https://gerrit.libreoffice.org/c/core/+/138884
I see a comment "The correct naming for LibreOffice is lool"
and a request to change a variable ending with cool into lool in
Hi Guilhem,
Am 01.09.22 um 17:27 schrieb Guilhem Moulin:
On Wed, 31 Aug 2022 at 19:48:57 +0200, Andreas Mantke wrote:
I wonder what is the usual time slot it needs to merge a reviewed and
ready patch into the LibreOffice repository.
Given TDF separates administrative and technical responsibilities
between the Board and ESC respectively, I am unclear why this matter is
being raised here - has it already been raised at ESC without a resolution?
Can someone explain please?
Cheers
Simon
On Thu, Sep 1, 2022 at 3:37 PM Andreas
Hi all,
I think it is about this patch:
https://gerrit.libreoffice.org/c/core/+/138884
It has a +2 from Adolfo Jayme Barrientos but is not yet submitted.
Kind regards,
Regina
Paolo Vecchi schrieb am 01.09.2022 um 16:47:
Hi Andreas,
On 01/09/2022 16:34, Andreas Mantke wrote:
Hi Thorsten, hi
Hi Paolo, all,
Am 01.09.22 um 17:29 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 17:13, Andreas Mantke wrote:
Hi Paolo,
Am 01.09.22 um 16:47 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 16:34, Andreas Mantke wrote:
I wonder if it is useful to open a second (or more than that)
Hi Andreas,
On 01/09/2022 17:13, Andreas Mantke wrote:
Hi Paolo,
Am 01.09.22 um 16:47 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 16:34, Andreas Mantke wrote:
I wonder if it is useful to open a second (or more than that)
communication channel for this with Gerrit for code review (with
On Wed, 31 Aug 2022 at 19:48:57 +0200, Andreas Mantke wrote:
> I wonder what is the usual time slot it needs to merge a reviewed and
> ready patch into the LibreOffice repository.
https://dashboard.documentfoundation.org/app/kibana#/dashboard/Gerrit-Timing and
Hi Paolo,
Am 01.09.22 um 16:47 schrieb Paolo Vecchi:
Hi Andreas,
On 01/09/2022 16:34, Andreas Mantke wrote:
I wonder if it is useful to open a second (or more than that)
communication channel for this with Gerrit for code review (with an
email messaging) in place. I thought that Gerrit has
Hi Andreas,
On 01/09/2022 16:34, Andreas Mantke wrote:
Hi Thorsten, hi all,
Am 31.08.22 um 21:28 schrieb Thorsten Behrens:
Hi Andreas,
Andreas Mantke wrote:
I wonder what is the usual time slot it needs to merge a reviewed
and ready patch into the LibreOffice repository.
Answering as a
Hi Thorsten, hi all,
Am 31.08.22 um 21:28 schrieb Thorsten Behrens:
Hi Andreas,
Andreas Mantke wrote:
I wonder what is the usual time slot it needs to merge a reviewed
and ready patch into the LibreOffice repository.
Answering as a developer here (and not as board member) - I think you
will
21 matches
Mail list logo
