Re: [board-discuss] [DECISION] Approve the attic proposal

2022-03-31 Thread Thorsten Behrens
Hi Daniel, all,

Daniel A. Rodriguez wrote:
> This all goes hand in hand with the refusal to hire developers within TDF.
> 
I don't see where that should have happened. See also Paolo's answer.

Cheers,

-- Thorsten


signature.asc
Description: PGP signature


Re: [board-discuss] Preliminary budget for 2022

2022-03-31 Thread Thorsten Behrens
Hi Simon, all,

Simon Phipps wrote:
> Can you tell is the voting details please?
> 
The vote on the budget was unanimous, among the board members present.

Best,

-- Thorsten


signature.asc
Description: PGP signature


Re: [board-discuss] [DECISION] Approve the attic proposal

2022-03-31 Thread Paolo Vecchi

Hi Andreas,

On 31/03/2022 14:49, Andreas Mantke wrote:

Hello,

Am 28.03.22 um 14:01 schrieb Florian Effenberger:

Hello,

The Board of Directors at the time of voting consists of 7 seat
holders (not including deputies). In order to be quorate, the vote
needs to have 1/2 or more of the Board of Directors members, which
gives 4.

A total of 4 Board of Directors members have participated in the vote.

The vote is quorate.

A quorum could be reached with a simple majority of 3 votes.

Result of vote: 4 approvals, 0 abstain, 0 disapprovals.
Decision: The proposal has been accepted.


once I looked over this decision making process, I find it striking that
only four BoD members participated. And also is remarkable that among
this participants are only long time TDF members and members which have
are part of LibreOffice ecosystem development companies or their
contract partner.

And because the starting point for this attic proposal (and its first
use case) is LOOL (online) it is not the best management, if members
with a potential CoI around this first use case participate. I'd expect
they abstain.



That the attic proposal has been pushed to archive LOOL, IMHO, is clear 
but is there any CoI at this stage?


That's a vote on the text, which still has room for improvement, not a 
vote to archive LOOL.


I proposed to open up the repository for 12 months and see if the 
community is still interested in bringing it forward or not and then, 
non CoI'ed directors, could vote on it's archival or not.




But independent from this, it is sad to see that there seemed to be
already no consent inside the board between the members connected to
LibreOffice ecosystem companies and the other members at the start of
the new BoD term.


Sorry but it seems like there are visions for the future of TDF that 
sometimes diverge quite a bit and yes heated discussions still happen.


I think it's very important that members of the community participate 
more so that all members of the board understand which direction our 
community want us to follow.




Regards,
Andreas


Ciao

Paolo


--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog




--
Paolo Vecchi - Member of the Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint



OpenPGP_signature
Description: OpenPGP digital signature


Re: [board-discuss] Board of Directors Meeting 2022-03-21

2022-03-31 Thread Paolo Vecchi

Hi Andreas,

On 31/03/2022 15:02, Andreas Mantke wrote:

Hello,

Am 28.03.22 um 12:48 schrieb Florian Effenberger:

The Document Foundation
Board of Directors Meeting 2022-03-21
Meeting Minutes

Date: 2022-03-21
Location: Jitsi

Session chair: Thorsten Behrens
Keeper of the minutes: Stephan Ficht

In the meeting:
   Board Members - Cor Nouws, Jan Holešovský, Thorsten Behrens, Caolán
McNamara, Emiliano Vavassori, Paolo Vecchi, Laszlo Nemeth
   Board Deputy Members - Gabriel Masei, Gabor Kelemen
   Membership Committee Members -
   Membership Committee Substitute Members -
   Team - Sophie Gautier, Stephan Ficht, Florian Effenberger, Guilhem
Moulin
   Community - "Fellow Jitster"

Representation: None
(...)



Public meeting ends at 17:13 UTC / 18:13 Berlin time.

Private part

3. Discuss & vote: budget for 2022 (Thorsten, all 40 mins)


because the discussion and decision was made in private, there is no
information given about the BoD members participated in this topic. But
I assume that the same members as in the public meeting take part in the
private meeting.


I believe you are correct.



If this budget includes items for development, e.g. for development
tender and for in-house developer, there would be at least a CoI, if a
company / organization connected to one of the BoD members would bit for
a tender.


I raised the issue and there has been an agreement to remove the 
in-house developers project from the budget vote.


You will notice from the preliminary budget that has been published that 
a proposal for a QA engineer, that hasn't been discussed openly as I did 
with the developers proposal, got through.


I demanded for the proposal to be discussed with TDF's team, which is 
finally happening, and also to be shared with the rest of the community 
so that you can help in evaluating it but that hasn't happened yet.



Thus at least every company / organization connected to one of
the BoD members has to be excluded from TDF tender process.


That's an interesting statement which deserves further evaluation.

IIRC every member of the board always voted for the budget without 
distinction.




Regards,
Andreas


Ciao

Paolo



--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog




--
Paolo Vecchi - Member of the Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint



OpenPGP_signature
Description: OpenPGP digital signature


Re: [board-discuss] Preliminary budget for 2022

2022-03-31 Thread Simon Phipps
Can you tell is the voting details please?

Thanks

Simon

On Thu, 31 Mar 2022, 18:36 Florian Effenberger, <
flo...@documentfoundation.org> wrote:

> Hello,
>
> find below a summary of the preliminary budget that the Board of
> Directors agreed on 2022-03-28. It is now made public in accordance with
> our statutes.
>
> Recurring: 901.444,52 €
>
>Salaries and compensations 694.840,88 €
>Accounting and legal advice 32.603,64 €
>Running cost & discretionary spending 25.000,00 €
>Trainings 5.000,00 €
>Infrastructure 74.000,00 €
>LibOCon & FOSDEM 30.000,00 €
>Community projects 20.000,00 €
>Marketing budget 20.000,00 €
>
>
> Pending projects (as of January 1):
> cf. https://wiki.documentfoundation.org/Development/Budget2021
>
>Various tenders 414.053,54 €
> Streamline tendering process
> Text layout
> Cleanup & further improve ODF conformance
> Rolling Release: Finish MAR-based autoupdater for Windows
> C++ accessibility tests
> MC request: Improvements on the Membership Committee tooling
> Improve the accessibility checker for PDF/UA
> Support for Editing and Creation of SmartArt
> Convert Impress slideshow to drawinglayer primitives
> Writer tables: support cell margins (next to cell padding)
>
>Campus programme for student ambassadors 12.000,00 €
>MC request: TDF welcome kit for the members 2.000,00 €
>statutory auditor/chartered accountant 5.000,00 €
>
>
> New projects:
> cf. https://wiki.documentfoundation.org/Development/Budget2022
>
>Various tenders 400.000 €
> [ESC] Bitmaps in vcl: Merge RGB and A layer into one
> [ESC] Stabilize cross-page table layouting
> [ESC] Text runs of RTL scripts (e.g. Arabic, Hebrew, Persian) from
> imported PDF are reversed, PDFIProcessor::mirrorString not behaving
> [ESC] Font subsetter for font embedding
> [ESC] Bitmaps in vcl: Use a native format/depth
> [ESC] ODT export nondeterminism
> [ESC] Remove/Replace usages of XOR-Paint
> [ESC] Table Styles improvements
> [ESC] Fix accessibility issues
> [ESC] Unify Writer and Draw Images
> [ESC] Decouple master slide and layouts
> [ESC] Multi-color gradient
> [ESC] Look-ahead styleref field for Writer
> [ESC] GraphicFilter clean-up
> [ESC] UNO API changes subscription/feedback channel
> [ESC] Regular scan-build reports like we do with CppCheck
> [ESC] Normalized spell checking
> [ESC] Missing ODF Features: Concentric gradient fill of custom-shapes
> [ESC] Bridge the gap between drawinglayer and VCL
> [ESC] XLSX Aggressive Competitors tracker: gridlines for 3d line charts
>
>Various contracts and tenders 100.600 €
> Contract Weblate to sort out issues pointed out by the l10n community
> Hire 1 x New QA analyst
> part-time web technology expert
> Update & translate LibreLogo manual, complete LibreLogo unit tests
> Decidim startup
>
>[MC] Carbon compensation 3.750,00 €
>2-4% budget to FLOSS software as devprojects or support (incl. 2021
> leftover) 27.265 €
>
> Florian
>
> --
> Florian Effenberger, Executive Director (Geschäftsführer)
> Tel: +49 30 5557992-50 | Mail: flo...@documentfoundation.org
> The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
> Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
> Legal details: https://www.documentfoundation.org/imprint
>
> --
> To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive:
> https://listarchives.documentfoundation.org/www/board-discuss/
> Privacy Policy: https://www.documentfoundation.org/privacy
>
>


[board-discuss] Preliminary budget for 2022

2022-03-31 Thread Florian Effenberger

Hello,

find below a summary of the preliminary budget that the Board of 
Directors agreed on 2022-03-28. It is now made public in accordance with 
our statutes.


Recurring: 901.444,52 €

  Salaries and compensations 694.840,88 €
  Accounting and legal advice 32.603,64 €
  Running cost & discretionary spending 25.000,00 €
  Trainings 5.000,00 €
  Infrastructure 74.000,00 €
  LibOCon & FOSDEM 30.000,00 €
  Community projects 20.000,00 €
  Marketing budget 20.000,00 €


Pending projects (as of January 1):
cf. https://wiki.documentfoundation.org/Development/Budget2021

  Various tenders 414.053,54 €
   Streamline tendering process
   Text layout
   Cleanup & further improve ODF conformance
   Rolling Release: Finish MAR-based autoupdater for Windows
   C++ accessibility tests
   MC request: Improvements on the Membership Committee tooling
   Improve the accessibility checker for PDF/UA
   Support for Editing and Creation of SmartArt
   Convert Impress slideshow to drawinglayer primitives
   Writer tables: support cell margins (next to cell padding)

  Campus programme for student ambassadors 12.000,00 €
  MC request: TDF welcome kit for the members 2.000,00 €
  statutory auditor/chartered accountant 5.000,00 €


New projects:
cf. https://wiki.documentfoundation.org/Development/Budget2022

  Various tenders 400.000 €
   [ESC] Bitmaps in vcl: Merge RGB and A layer into one
   [ESC] Stabilize cross-page table layouting
   [ESC] Text runs of RTL scripts (e.g. Arabic, Hebrew, Persian) from 
imported PDF are reversed, PDFIProcessor::mirrorString not behaving

   [ESC] Font subsetter for font embedding
   [ESC] Bitmaps in vcl: Use a native format/depth
   [ESC] ODT export nondeterminism
   [ESC] Remove/Replace usages of XOR-Paint
   [ESC] Table Styles improvements
   [ESC] Fix accessibility issues
   [ESC] Unify Writer and Draw Images
   [ESC] Decouple master slide and layouts
   [ESC] Multi-color gradient
   [ESC] Look-ahead styleref field for Writer
   [ESC] GraphicFilter clean-up
   [ESC] UNO API changes subscription/feedback channel
   [ESC] Regular scan-build reports like we do with CppCheck
   [ESC] Normalized spell checking
   [ESC] Missing ODF Features: Concentric gradient fill of custom-shapes
   [ESC] Bridge the gap between drawinglayer and VCL
   [ESC] XLSX Aggressive Competitors tracker: gridlines for 3d line charts

  Various contracts and tenders 100.600 €
   Contract Weblate to sort out issues pointed out by the l10n community
   Hire 1 x New QA analyst
   part-time web technology expert
   Update & translate LibreLogo manual, complete LibreLogo unit tests
   Decidim startup

  [MC] Carbon compensation 3.750,00 €
  2-4% budget to FLOSS software as devprojects or support (incl. 2021 
leftover) 27.265 €


Florian

--
Florian Effenberger, Executive Director (Geschäftsführer)
Tel: +49 30 5557992-50 | Mail: flo...@documentfoundation.org
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint

--
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy



Re: [board-discuss] [DECISION] Approve the attic proposal

2022-03-31 Thread Daniel A. Rodriguez



El 31/3/22 a las 09:49, Andreas Mantke escribió:

Hello,

Am 28.03.22 um 14:01 schrieb Florian Effenberger:

Hello,

The Board of Directors at the time of voting consists of 7 seat
holders (not including deputies). In order to be quorate, the vote
needs to have 1/2 or more of the Board of Directors members, which
gives 4.

A total of 4 Board of Directors members have participated in the vote.

The vote is quorate.

A quorum could be reached with a simple majority of 3 votes.

Result of vote: 4 approvals, 0 abstain, 0 disapprovals.
Decision: The proposal has been accepted.


once I looked over this decision making process, I find it striking that
only four BoD members participated. And also is remarkable that among
this participants are only long time TDF members and members which have
are part of LibreOffice ecosystem development companies or their
contract partner.

And because the starting point for this attic proposal (and its first
use case) is LOOL (online) it is not the best management, if members
with a potential CoI around this first use case participate. I'd expect
they abstain.



Indeed, should be that way.



But independent from this, it is sad to see that there seemed to be
already no consent inside the board between the members connected to
LibreOffice ecosystem companies and the other members at the start of
the new BoD term.



It's not the first time that happens, previous term had a lot of that.

However, I believe that a consensus does not necessarily have to be 
reached. One can disagree. What is of utmost importance is to promote 
the best decision for TDF.


This all goes hand in hand with the refusal to hire developers within TDF.



Regards,
Andreas

--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog



--
Uso LibreOffice, por privacidad, seguridad y control de mis datos.
Da un vistazo a la mejor suite de oficina: https://es.libreoffice.org
O únete a la Comunidad Hispana en Telegram: https://t.me/libreoffice_es

--
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy



Re: [board-discuss] Board of Directors Meeting 2022-03-21

2022-03-31 Thread Andreas Mantke

Hello,

Am 28.03.22 um 12:48 schrieb Florian Effenberger:

The Document Foundation
Board of Directors Meeting 2022-03-21
Meeting Minutes

Date: 2022-03-21
Location: Jitsi

Session chair: Thorsten Behrens
Keeper of the minutes: Stephan Ficht

In the meeting:
   Board Members - Cor Nouws, Jan Holešovský, Thorsten Behrens, Caolán
McNamara, Emiliano Vavassori, Paolo Vecchi, Laszlo Nemeth
   Board Deputy Members - Gabriel Masei, Gabor Kelemen
   Membership Committee Members -
   Membership Committee Substitute Members -
   Team - Sophie Gautier, Stephan Ficht, Florian Effenberger, Guilhem
Moulin
   Community - "Fellow Jitster"

Representation: None
(...)



Public meeting ends at 17:13 UTC / 18:13 Berlin time.

Private part

3. Discuss & vote: budget for 2022 (Thorsten, all 40 mins)


because the discussion and decision was made in private, there is no
information given about the BoD members participated in this topic. But
I assume that the same members as in the public meeting take part in the
private meeting.

If this budget includes items for development, e.g. for development
tender and for in-house developer, there would be at least a CoI, if a
company / organization connected to one of the BoD members would bit for
a tender. Thus at least every company / organization connected to one of
the BoD members has to be excluded from TDF tender process.

Regards,
Andreas

--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog


--
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy



Re: [board-discuss] [DECISION] Approve the attic proposal

2022-03-31 Thread Andreas Mantke

Hello,

Am 28.03.22 um 14:01 schrieb Florian Effenberger:

Hello,

The Board of Directors at the time of voting consists of 7 seat
holders (not including deputies). In order to be quorate, the vote
needs to have 1/2 or more of the Board of Directors members, which
gives 4.

A total of 4 Board of Directors members have participated in the vote.

The vote is quorate.

A quorum could be reached with a simple majority of 3 votes.

Result of vote: 4 approvals, 0 abstain, 0 disapprovals.
Decision: The proposal has been accepted.


once I looked over this decision making process, I find it striking that
only four BoD members participated. And also is remarkable that among
this participants are only long time TDF members and members which have
are part of LibreOffice ecosystem development companies or their
contract partner.

And because the starting point for this attic proposal (and its first
use case) is LOOL (online) it is not the best management, if members
with a potential CoI around this first use case participate. I'd expect
they abstain.

But independent from this, it is sad to see that there seemed to be
already no consent inside the board between the members connected to
LibreOffice ecosystem companies and the other members at the start of
the new BoD term.

Regards,
Andreas

--
## Free Software Advocate
## Plone add-on developer
## My blog: http://www.amantke.de/blog


--
To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy



Re: [board-discuss] Re: New draft of the proposal for in-house developers

2022-03-31 Thread Paolo Vecchi

Hi Hossein,

thanks for your feedback and support.

I'll follow up shortly with you to see if your experience in joining the 
team as Developer Community Architect could provide further insights on 
how to best integrate and manage new in-house developers.


Ciao

Paolo

On 31/03/2022 07:32, Hossein Nourikhah wrote:

Hello,

I've read most of the feedback emails, and I want to add these points:

1. The good thing about this proposal is that it addresses many of the 
declared concerns from the ecosystem companies. This is important 
because the ecosystem companies and their programmers have a big role 
in the LibreOffice development. The in-house developers will 
complement the companies' efforts.


2. Any action in this area may have some drawbacks. While it is good 
to provide means of minimizing possible problems, it is also good to 
talk about the price of NOT doing that action. In this case, facing 
hundreds of issues from 5 to 10 years ago that are still there is a 
real problem that we should not ignore. Addressing these issues will 
also benefit ecosystem companies.


3. Some of the mentioned problems and requirements for hiring an 
in-house developer such as management, accountability and things like 
that are also relevant for other recruiting attempts. But, I think 
this proposal should only target things that are specific to hiring 
developers, and not the general management principles and practices.
On the other hand, because the in-house developers are supposed to 
work mostly on maintenance tasks that were ignored for a while, clear 
practices and performance indicators can be defined to guide and 
measure the success of the developers throughout the projects assigned 
to them. Adding these to the "project management" section of the 
proposal can help address the possible concerns.


Regards,
Hossein



--
Paolo Vecchi - Member of the Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint



OpenPGP_signature
Description: OpenPGP digital signature