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


Hi Florian,

Item 4 on the agenda is a significant change to past decisions on the
subject by the Board. Is there any background information such as a paper
describing the rationale and impact of the change please?

Thanks!

Simon

On Mon, May 18, 2020 at 8:31 AM Florian Effenberger <
floeff@documentfoundation.org> wrote:

Dear community,

find below the public agenda for our

-> TDF board meeting with a public part, and if needed followed by a
private part (- no topics in the private part so far -)
-> on Friday, May 22nd at 1300 Berlin time

For time zone conversion, see e.g.

https://www.timeanddate.com/worldclock/converted.html?iso=20200522T13&p1=37&p2=136&p3=241&p4=589

-> at https://jitsi.documentfoundation.org/TDFBoard

as we gain good experience last time after improvements of the TDF
instance from the team, if possible use Chrome browser and do not use
video and until not speaking up please mute.

-> AGENDA:

Public Part

1. Q&A: Answering Questions from the community (All, max. 10 minutes)

    Rationale: Provide an opportunity for the community to ask questions
to the new board and about TDF.

2. Discuss: Ecosystem & Sustainability (Michael, All 15min)

    Rationale: Discussion, relevance and dependencies for TDF

3. Discuss: Quick check of fitting prerequisites and procedure of the
vote for the next agenda item (Lothar, Board members, All 5 minutes)

    Rationale: Clarifying about voting of the next agenda item

4. Voting on proposal of Paolo:  (Paolo, Board members 15 minutes)

    Voting proposal via Mail from Paolo Vecchi at 16.05., 13.15 UTC+2: "...

    Enable the infrastructure team to deliver the following packages
with TDF and LibreOffice branding:
     - docker images
     - ownCloud connector (from which we have already got confirmation
of acceptance) for LOOL
     - once that is in place I will ask NextCloud for the opportunity to
do the same
     - Univention marketplace packages for LOOL
     - all packages and connectors will be maintained and updated on a
monthly basis unless urgent patches/bug fixes are required sooner
     - the latest stable version of LOOL code will be used to build the
images
     - the infrastructure oversight team will ensure that all issues
that may impede the execution of this plan are identified and solved
promptly
     - the infrastructure oversight team should evaluate, and report
back to the BoD, if TDF should use its own Gerrit server for LOOL or
Collabora's see ticket
https://bugs.documentfoundation.org/show_bug.cgi?id=132349
     - LibreOffice branded documentation/help files should be created to
make it as easy as possible to install docker images/Univention packages
     - TDF's LOOL packages will be free and supported only by the
community. No paid/support options will be made available by TDF
     - In the download page it will be made clear that if LOOL is used
in enterprise environment support options are available through the
members of TDF's ecosystem
   At a later stage eventual limitations in terms of concurrent
users/documents will be discussed.
   ..."

   Rationale: explanation of voting item(s), getting a valid voting
result on Paolos proposal as described above

5. Discuss: Status of redmine tickets of the board (Thorsten, All 10min)

    Rationale: Clarifying which tickets/list, what todos, who is caring,
until when

  Private Part

  - No topic in private so far -

Florian


Context


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.