Welcome to The Document Foundation Planet

This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.

To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.

14 July, 2020


Franklin Weng from The Document Foundation’s Board of Directors writes:

Dear Community,

we hereby officially announce the upcoming elections for the next Membership Committee of The Document Foundation.

As per § 12 II of our statutes (binding version in German and non-binding translation), the Membership Committee’s term lasts two years. The current Membership Committee started its duty on September 19, 2018. Therefore, the old Membership Committee remains in charge until the end of September 18, 2020, so the new MC will be in charge the day after that, which is September 19, 2020.

That upcoming term will then (regularly) end on September 18, 2022, so the next election of the Membership Committee will take place before.

As per § 6 III, only members of the Board of Trustees of The Document Foundation, as well as current members of any of its bodies, are eligible to be elected into the Membership Committee, and the election is overseen by the Board of Directors (§ 12 II).

The active electoral right is reserved to those who have been members of the Board of Trustees before this announcement (§ 12 II).

§ 6 III also states that members of the Board of Directors or their substitute members may not be members of the Membership Committee and vice versa.

There is one more notable limitation: Per § 8 IV of the statutes, a maximum of 1/3 members of the Membership Committee is allowed to work on an employment basis for the same company, organization, entities, affiliates or subdivisions.

Nomination of candidates fulfilling the above requirements, as well as self nomination is welcome. In total, at least five members of the Membership Committee are required, and given there are enough candidates, up to four substitute members can be elected based on the last board decision on this matter.

Re-election of current members of the Membership Committee is explicitly permitted (§ 12 II).

Please send nominations and self-nominations via e-mail to elections@documentfoundation.org (which reaches the Board of Directors in private) and also (!) to board-discuss@documentfoundation.org (which is a public mailing list).

We kindly ask nominees who would like to stand for elections to provide a statement of up to 75 words – longer statements will be cut off at the maximum – on their candidacy as continuous text (so no bullet lists or multiple paragraphs). In addition, you have to provide your full name, e-mail address and your corporate affiliation, if any, and please announce that you will provide information on all future changes as soon as possible. Specifically, it is necessary to indicate all information regarding § 8 IV of the statutes.

Discussions with the candidates and questions to them as well as questions about the elections should take place on the public board-discuss@documentfoundation.org mailing list. For details on how to use the mailing list, see https://www.libreoffice.org/get-help/mailing-lists/

Eligible voters will receive further details via e-mail prior to the start of elections, including a summary of the candidates, details on how to access the

13 July, 2020


Today we’re talking to Khairul Aizat Kamarudzzaman from our Malaysian community. He’s a long-time fan of free and open source software, and is helping with LibreOffice advocacy and marketing…

To start off, tell us a bit about yourself!

I’m from Kuala Lumpur, Malaysia. I started exploring and using FOSS way back in 2004 (Debian, Red Hat, the BSD family and sticking with Ubuntu till today) when I was studying at the university. From there I started exploring and contributing to Ubuntu, which you can find here, and I was accepted to be an Ubuntu Member, Kubuntu Membes (merits as Ubuntu contributor). Finally I was appointed to be part of the Asia Oceania Membership Board.

A a FOSS community member, I work in a few IT companies in Malaysia and was one of the engineers working at Open Source Competency Centre (OSCC) under Malaysian Administrative Modernisation and Management Planning Unit (MAMPU). Now I own my own IT company, namely Informology Sdn Bhd. Not stopping there, I continue actively being a FOSS enthusiast in Malaysia. When the cloud computing era came, I was involved by leading Malaysia OpenStack User Group, and I’ve recently been exploring and leading the Endless OS user group for Malaysia.

What are you working on in the LibreOffice project right now?

I started the LibreOffice Malaysia Group on Facebook, and I’m planning with the group to finish the LibreOffice Malay translation as soon as possible, with guidance from the Indonesian LibreOffice translation team – so that we can have Malay language support in LibreOffice and Collabora Office.

Why did you decide to become a member of The Document Foundation?

It’s in line with what I’ve done since I started using FOSS: open source advocacy targeted at students, teachers, government staff and the open Source community members in Malaysia. I especially focused on Linux, and office automation like LibreOffice and Collabora Office as an alternative to Microsoft Office. Then, last year in 2019, I managed to participate in the Gnome Asia Summit 2019 in Surabaya, Indonesia where I met a lot of FOSS enthusiasts who are advocating and spreading open source in Indonesia, along with a few awesome TDF members (Ahmad Haris), TDF Board member (Franklin Weng) and GNOME Foundation Staff.

So I asked myself… since I already pitching the Open Document Format (ODF) since I was in OSCC, why not start contributing more to LibreOffice by doing translations? So I challenged myself by applying to become a TDF member, with advice from Ahmad Haris and Franklin Weng.

Anything else you plan to do in the future?

Keep spreading and marketing LibreOffice in Malaysia – especially in the government and educational sectors. Give these sectors LibreOffice as an alternative, by not using piracy and a cracked version of Microsoft Office.

Maybe the LibreOffice Malaysia group can suggest to TDF to host the LibreOffice Conference in Malaysia one day in the future!

Thanks Khairul! And indeed to everyone in the Malaysian LibreOffice community. Your work

[en] = Ahmed ElShreif: Week 6 Report

04:10 UTC

Hello all,

The last week was the 6th week of coding weeks in GSoC program. I continued adding support for the non supported items.

 Report in points:
  • Finalize the 5 patches that still under review by solving any comments .
  • Add support for "ToolBox" Objects for example" "bottom find bar" .
  • Add demo for "bottom find bar" using ToolBox support .
  • extend the ComboBox UIObject .
  • patches status.

1) The last week I left 5 patches without merging. They are mainly the patches that add support for Calc-comments and Vertical Tab Control. Also the patches of the Calc-comment demo , Writer-comment demo and insert hyperlink demo. The five patches now are merged after working on solving all the comments. The patches can be found in patches status section in the report .

2) I also This week worked on the "bottom find bar" item from the list of unsupported items. After working with this bar I found that it wasn't work because of 2 reasons. First Reason was that the FindBar has no id when it's defined. Which can be solved by this change. The second was that we don't have support for toolbox objects which added in this patch.

this patch will help us in testing any ToolBox Objects by this lines :
>> variable_name = MainWindow.getChild(Bar_name)
>> variable_name.executeAction("CLICK", mkPropertyValues({"POS": poition_x }))
For position_x you just put the id of which entry in the ToolBox do you want to press on it . Also This patch set the ID of the bottom find bar to be "FindBar" to be able to select it in UITests .

The video here show how the find bar can be used now:

3) I worked also in adding  test case for "bottom find bar" using ToolBox support . The test case tests the Find Bar in searching for all matched words the navigate between the matched words. the test case can be found here in this patch.

4) I worked also in extend the ComboBox UIObject. As ComboBox UIObject can be treated as Edit UIObject so this minor change will let us do all Edit UIObject actions on the ComboBox UIObject if needed . So now you will not only be able to select or type from the ComboBox But also you will be able to SET Text and CLEAR the text. the work will be found in this patch .

5) patches status:

Next week Tasks:
  • Finalize the 3 patches that still under review by solving any comments.
  • Work on another unsupported item.

Thanks for reading. And I am really interested to hear all your feedback and comments.

11 July, 2020


Perlas de sabiduría de los usuarios

Existe un canal de Telegram, llamado LibreOffice-ES (https://t.me/libreoffice_es) donde se comparte mucha sabiduría, conocimientos y muy buena vibra en todo lo que respecta a LibreOffice (LO). Desde temas técnicos hasta filosóficos se …

09 July, 2020


Lothar Becker, Presidente de la Junta Directiva de The Document Foundation, escribe:

Querida comunidad,

gracias por los comentarios sobre el borrador del plan de marketing a través de diferentes canales hasta ahora. Queremos hacerles saber y hacerlos participar, ya que …

[en] Michael Meeks: 2020-07-08 Thursday

10:56 UTC

  • Mail chew; interested to see Open Usage announced for holding and managing FLOSS trademarks in a light-weight way. If it can reduce the galloping bureaucracy and the risk of in-fighting that can come with formal governance structures, as well as avoiding the extraordinarily overheads of formal entities, that sounds rather positive. Just having the pleasant, collegial engineering relationships in a project without the overhead would be great. Then again, I guess SFC, SPI, Public Software and others already provide nice containers for projects with varying degress of flexibility, lets see what happens.


Lothar Becker, Chairman of The Document Foundation’s Board of Directors, writes:

Dear community,

thanks for the feedback on the marketing plan draft via different channels so far. We want to let you know and have you take part, as the board is discussing the options now available with that draft.

In the meantime, some more feedback will be integrated in the document already and will be published on next Monday. This is still not the last chance for a change for version 7.0.0, but we will reach that point soon.

The last change for all strings and tags would be possible the latest by Monday, July 20. With some preliminary phase for decision making of the board the public feedback phase on all this will end by the time of the next public board call, i.e. Friday, July 17, 1300 Berlin time.

What are the realistic options so far:

  • Variant 1: Implementation of a marketing plan would be postponed to V7.1, as no UI changes can be made in minor releases. This would imply a longer discussion period.


  • Variant 2: Implementation of the marketing plan draft with V7.0.0 with flavour tags.

At the moment it looks like, this would be called “Community Edition” (in change to the RC1) and with the introduction of the umbrella brand “Enterprise Edition” with explanations and pointer to ecosystem partner offerings.

The feedback here we still need until the mentioned Friday, July 17, 1300 Berlin time is about all strings and tags (e.g. “Community Edition”), you can give that on the board-discuss mailing list, or on Bugzilla.


  • Variant 3: As variant 2 above and further tweak all strings and tags for V7.1, after gaining experience and more feedback with it from V7.0.

We encourage all the community to bring in your opinions further, also on the public board call (Friday, July 17, 1300 Berlin time), and all the other channels. Please be aware, that any sort of decision of the board must be made the latest at the dates stated above.

Thanks so much for your input so far! All the best, and keep healthy!

Chairman of the Board


Videos created by our community are a great way to spread the word about LibreOffice, and help new users to get the most out of the software. This video, from Harald Berger, summarises the different ways to start LibreOffice 6.4 – and its various modules – under Windows 10:

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

08 July, 2020

[en] Michael Meeks: 2020-07-08 Wednesday

21:00 UTC

  • A morning of marketing bits; catch up with Paolo, admin and community mail reading.


General Activities

  1. Adolfo Jayme Barrientos, Steve Fanning, Gábor Kelemen, Olivier Hallot (TDF) and Johnny_M made many Help improvements and cleanups
  2. Jan-Marek Glogowski improved the Writer comments ruler UI control and fixed a few Qt-related issues
  3. Tomaž Vajngerl (Collabora) implemented searching inside PDFs inserted as a graphic and added support for reading annotations in PDFs
  4. Chris Sherlock did graphics-related refactoring work
  5. Mike Kaganski (Collabora) improved the look of soft edges and shadows in slideshows
  6. Martin van Zijl added the ability to reset standard filter in Calc
  7. Luboš Luňák (Collabora) continued with the Skia graphics engine integration and improved the performance of undo operations in Calc
  8. Xisco Faulí (TDF) made over 40 additions and fixes to unit and UI tests
  9. Vasily Melenchuk (CIB) fixed many issues with DOCX lists and fixed a DOCX paragraph spacing issue
  10. Noel Grandin (Collabora) made many code cleanups and made performance improvements in Calc in the areas of autofilling, loading of spreadsheets with huge autofilters and sorting data
  11. Caolán McNamara (Red Hat) continued the crucial user interface backend work and did many cleanups and crash fixes
  12. Rizal Muttaqin made many improvements in the icon themes and refreshed the Presenter Screen
  13. Balázs Varga (NISZ) fixed some OOXML chart issues
  14. Miklos Vajna (Collabora) improved the digital signing of PDFs and added signature line support for Draw. He also added support in Writer for anchoring shapes relative to the bottom of the page content frame
  15. Michael Stahl (CIB) fixed many issues with change tracking and anchoring in Writer
  16. László Németh (NISZ) fixed issues with DOCX table borders, bullet indenting, chapter numbers. He also improved AutoCorrect for several languages.
  17. Stephan Bergmann (Red Hat) made many cleanups and build fixes. He also fixed a nasty deadlock in a UI test while improving how the continuous integration handles jobs
  18. Julien Nabet fixed some crashes and made many cleanups
  19. Heiko Tietze (TDF) helped with the gallery rework
  20. Srijan Bhatia added time pause/resume and exit buttons to Impress Presenter console
  21. Tor Lillqvist (Collabora) worked on the iOS app and did code cleanups
  22. Serge Krot (CIB) worked on implementing a conditional in mailmerge for expanding/collapsing bookmarks and fixed an interoperability issue related to DOCX not supporting dropdown text fields
  23. Andreas Kainz continued to improve the galleries, dialog layouts and Notebookbar UIs
  24. Samuel Mehrbrodt (CIB) added a DOCX compatibility option for keeping spacing below last paragraph in header
  25. Attila Bakos (NISZ) fixed frames misbehaving in connection with shapes and mispositioned shapes in table cells
  26. Tibor Nagy (NISZ) fixed a bunch of DOCX frame text wrapping issues
  27. Gábor Kelemen (NISZ) fixed dropdown list form fields having an incorrect font at the beginning of a line in DOCX files
  28. Tünde Tóth (NISZ) fixed some issues with OOXML chart legends and titles
  29. Szabolcs Tóth (NISZ) fixed shape width relative to margins in DOCX file import
  30. Julian Kalinowski (Dataport) fixed a couple of webdav lock refresh issues
  31. Maxim Monastirsky fixed the importing of fields with user defined number formats

07 July, 2020


I’ve started past week by going over my implementation of simulated animation effects and getting rid of the rough parts, so it would be somewhat ready to be merged into LO master. While doing so, realized I’ve forgot to add support for other types of ongoing animations in parallel with a simulated animation.

So to implement this, I thought all animation instances would have a reference to box2DWorld, if box2DWorld is initiated (as in there’s a simulated animation going on), these animations would supply box2DWorld with required information on how to update shape corresponding to this animation instance. The information supplied would have the uno shape reference of that animation effect, type of the update box2DWorld will perform (change position, appear/disappear, change size etc.), and if required any additional info (for instance, if it is an path motion animation, it would supply the updated position of the shape).

box2DWorld would hold all incoming information in a queue so that it can process this information before stepping through the simulation.

So far I’ve only implemented this for path motion animation effects – since my finals have started last week, and they are slowing down my progress :/ –

For the instance of path motion animations, when there’s an position update it doesn’t make sense to just change the position of the shape (teleport) in box2DWorld, even though this would make it push shapes out of it’s way, the end product wouldn’t seem “simulated” since the body didn’t have any velocity. To fix this problem, positions of the shapes are updated by calculating linear velocity required to make the shape travel to the desired position in the delta time box2DWorld will step through. And then assigning this linear velocity to corresponding body. This results in convincing simulations that have a higher degree of realism.

Here’s a small demo illustrating this in action:

Please accept YouTube cookies to play this video. By accepting you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

check out the source on the private experimental branch: gsoc-box2d-experimental

[en] Michael Meeks: 2020-07-07 Tuesday

21:00 UTC

  • Spent lots of time reading, and writing up (again) some of the problems with TDF / LibreOffice - none of which are very new.

06 July, 2020

[en] Michael Meeks: 2020-07-06 Monday

21:00 UTC

  • Mail chew; read through a slew of E-mail, telegram, bugzilla and other feedback on LibreOffice Personal. Tech. planning call with Andras - much of the mgmt team on vacation. Lots of E-mail.


Querida comunidad de LibreOffice, colaboradores y amigos,

Gracias al duro trabajo realizado por muchos individuos y proveedores del ecosistema, trabajando juntos como un equipo en diferentes campos, como el desarrollo, QA, diseño, marketing, localización, ingeniería de lanzamiento, infraestructura, sólo para …


Dear LibreOffice Community, supporters and friends,

Thanks to the hard work put in by many individual and ecosystem contributors, working together as a team in different fields, such as development, QA, design, marketing, localisation, release engineering, infrastructure, just to mention some, in a few weeks’ time we will be welcoming our LibreOffice 7.0 milestone.

At the same time, we are discussing our vision for the next five years, with a starting point being marketing and branding. See our marketing and board-discuss mailing lists.

Due to draft and development work in the area of branding and product naming, some speculation, in particular related to the “Personal Edition” tag shown in a LibreOffice 7.0 RC (Release Candidate), has started on several communication channels. So let us, as The Document Foundation’s Board of Directors, please provide further clarifications:

 1. None of the changes being evaluated will affect the license, the availability, the permitted uses and/or the functionality. LibreOffice will always be free software and nothing is changing for end users, developers and Community members.

 2. Due to the short time frame we are working with, the tagline appeared on the RC and we apologise if this caused some of you to think we unilaterally implemented the change. Rest assured that the consultation with the Community is still ongoing.

 3. This “Personal Edition” tag line is part of a wider 5 year marketing plan that we are preparing, and it has the purpose of differentiating the current, free and community-supported LibreOffice from a LibreOffice Enterprise set of products and services provided by the members of our ecosystem. The marketing plan is still under development and discussion so we are eager to receive and evaluate your feedback!

 4. Any feedback (in an appropriate way) to our marketing plan is welcome. There are several ways to send feedback to the Board of Directors: the most preferred way is to subscribe to the “board-discuss” mailing lists (e-mail here to subscribe), in which many of the discussions will take place in public and be archived. Besides the mailing list, we have a regular time slot (around 10-15 minutes maximum) in our Board meeting public section, for which we welcome all the community members to join and raise their questions. The Board meetings are held every two weeks and are announced in a timely fashion on the board-discuss mailing list.

 5. We are strongly opposed to any form of harassment, on any medium. Feedback itself is not an harassment, but personal attacks are. Please stay focused on the objective and be polite in your conversations!

 6. The team of editors for the marketing plan is weighting all the input, as it is important to get the feedback to define a clear strategy supported by the entire Community. We encourage everybody to support the Board, the marketing team and the Community working out the details; certainly we don’t want to make any decisions that is backed only by a small minority.

 7. This is a


The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 7.0 RC1 is available for testing!

LibreOffice 7.0 will be released as final at the beginning of August, 2020 ( Check the Release Plan for more information ) being LibreOffice 7.0 RC1 the forth pre-release since the development of version 7.0 started in the beginning of June, 2019. Since the previous release, LibreOffice 7.0 Beta2, 174 commits have been submitted to the code repository and 116 bugs have been fixed. Check the release notes to find the new features included in LibreOffice 7.0.

LibreOffice 7.0 RC1 can be downloaded from here for Linux, MacOS and Windows.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).

For help, you can contact the QA Team directly in the QA IRC channel or via Telegram.

LibreOffice is a volunteer-driven community project and your help is much appreciated.

Happy testing!!

Download it now!

[en] = Ahmed ElShreif: Week 5 Report

06:54 UTC

Hello all,

The last week was the 5th week of coding weeks in GSoC program. I continued adding support for the non supported items.

 Report in points:
  • Finalize support for Calc-comment .
  • Fix some DSL grammar errors .
  • Add support for "Hyperlink dialog. Insert ->Hyperlink".
  • Add test cases that test "Hyperlink dialog. Insert ->Hyperlink" .
  • Finalize the unfinished patches .

1) The last week I left the Calc Comments support in this patch not merged waiting the final review. the patch added a function in FuDraw class to help in closing the Comment window. So the work this week done was to move this function from the FuDraw class to the UI testing code. This approach is done in the last patch and tested on the test case in this patch. So the patch waiting for the final review.

2) I worked this week also in fixing the issue in the DSL grammar that related to "EditUIObject". It was simple modification in the string of the grammar rule but without it any selection of text inside any EditUIObject will make the automatic generation of the test case fail. The patch is now merged .

3) I also This week worked on the "Hyperlink dialog. Insert ->Hyperlink" item from the list of unsupported items. After working with this dialog I found that it wasn't work because the tabcontrol of the dialog is vertical tabcontrol not the normal tabcontrol. So I worked on adding support for vertical TabControl Object. This patch has the support.

We need support for this Object as some dialogs use it like Hyperlink Dialog. So now we can navigate in the dialog in the same way we navigate with the normal TabControl Objects.

You can use this lines in your test case that test a dialog that has vertical TabControl Object:
xtab.executeAction("SELECT", mkPropertyValues({"POS": "0"}))

The video here show how the vertical tab control can be used now for this navigation:

4) I worked also in adding  test case for Hyperlink Dialog. The test case tests the Hyperlink Dialog in inserting a Hyperlink . Also it tests the Vertical TabControl Support that added in this patch. the test case can be found here in this patch.


5) From the last week this is the status of the patches:

Next week Tasks:
  • Finalize the 5 patches that still under review by solving any comments.
  • Work on another unsupported item.

Thanks for reading. And I am really interested to hear all your feedback and comments.


LibreOffice’s basic conception is to be not just a product, the office suite, but a community around it. So we do not only provide downloads and support for the development but also make it easy to join the project. As a consequence, the ecosystem and web presence has grown to a point where we think renovation and consolidation might be necessary.…

04 July, 2020

[en] = Ahmed ElShreif: Week 4 Report

21:24 UTC

Hello all,

The last week was the 4th week of coding weeks in GSoC program. So this report is final report before phase 1 evaluation . I continued adding support for the non supported items.

 Report in points:
  • Finalize the demo of Writer comments.
  • Add the support for Calc-comment.
  • Add test case for Calc-comments .
  • Add support for Writer Format-Bullets and numbering dialog Selection.
  • Add demo for Writer Format-Bullets and numbering dialog Selection.

1) The last week I left the Writer Comments test case in this patch not merged because of some failures but now it's ready to be merged but waiting the final review.

2) I added the support for Calc-comments here in this patch. We can now use this support in writing test cases that handle Calc's comments using the lines as descriped in the last report.

In this video I just want to show the results of this support:
Note that the patch still under review.

3) I also added a test case for Calc-comments that can be found here in the patch. It test all the functionalities that added for comments. The patch still under review.

4) I also worked this week in Adding support for Writer Format-Bullets and numbering dialog Selection. I found that the selecter is a object from class SvxNumValueSet so I added support for it.

The support of SvxNumValueSet can be found in this patch which also will help us to add support for test cases that test  Writer Format-Bullets and numbering dialog Selection.

You can choose any item from the selector by this line for example:
obj_name.executeAction("CHOOSE", mkPropertyValues({"POS": "pos_num"}))

You can also check the selector by these lines:
In this video I just want to show the results of this support:

Note that the patch still under review.

5) Finnaly, I created a test case to test the selectors of the 4 tabs of the Writer Format-Bullets and numbering dialog and added them to this file as it test the dialog.

The test case can be found here in this patch. and the patch still under review .

Phase (1) Achievements :
  • Solving some issues in the logger DSL .
  • Add support for Calc-Zoom .
  • Add support for Calc / Format cell / background color selector .
  • Extend the ability of ComboBoxUIObject to be able to select with text .
  • Add support for Writer-comments .
  • Add support for Dropdown items in grid window .
  • Add support to Calc - comments .
  • Add Support for SvxNumValueSet .
  • Add test cases for each added support.

Next week Tasks:
  • Finalize the 5 patches that still under review by solving any comments.
  • Start working on adding support for "Hyperlink dialog. Insert ->Hyperlink".
  • Adding test cases that test "Hyperlink dialog. Insert ->Hyperlink" .
  • Work on another future unsupported item.

Thanks for reading. And I am really interested to hear all your feedback and comments.

[en] Michael Meeks: 2020-07-04 Saturday

21:00 UTC

  • David came over and helped wrestle with the house - moving and fixing MDF, pulling cables and building a den with E. Pulled pork lunch, and worked until late.

So... I was very surprised when I saw this in About dialog in LibreOffice (that screenshot was made in current master 7.1, but you can see the same in 7.0 RC1 version):
Look at LibreOffice logo with "Personal Edition" phrase, look at sidebar in Start Center with the same phrase and note to "The Personal edition is supported by volunteers and intended for individual use."
And what is mean? Where is any public announcement? They say it was in marketing mail list. How many people read that mail list? Five?
It means that I can't install LibreOffice 7.0 in any organization in Russia, because our controlling people will be see very simple to legality in this case: open the About dialog -> read that "intended for individual use" and LibreOffice logo with "Personal Edition" -> you can't use LibreOffice here! Nobody will check what say MPL 2.0 license about it or why TDF made it, they just point a finger at it and they will be right!
It will close for LibreOffice any education organizations like schools or colleges or universities.
I wont popularize LibreOffice for young people because they will never see LibreOffice in them schools.
I against these changes. Please revoke it!
ps: I had a suggestion about add into About dialog phrase like "You can use/install LibreOffice to any number of computers in any place (at home, organizations, etc.)" but they were against! See the bug report. And now they make own changes in to opposite side from free.

03 July, 2020

[en] Michael Meeks: 2020-07-03 Friday

21:00 UTC

  • Mail chew, calls, Employees, Board calls. Met the A/C business owner at the end of the road, quick customer call, sync with Kendy.

02 July, 2020

[en] Michael Meeks: 2020-07-02 Thursday

21:00 UTC

  • Finally interview, internship job offer; lunch, another internship offer. Pulled cables with H. until lateish.


LibreOffice 7.0 está siendo desarrollado por nuestra comunidad mundial, y se espera que sea presentado a principios de agosto de 2020 – vea las notas de lanzamiento que describen las nuevas características.

Con el fin de encontrar, reportar y …


The Document Foundation anuncia la disponibilidad de LibreOffice 6.4.5, la quinta versión menor de la familia LibreOffice 6.4, dirigida a los entusiastas de la tecnología y a usuarios avanzados. LibreOffice 6.4.5 incluye más de 100 correcciones de errores y mejoras …


Donate TodayBerlin, July 2, 2020 – The Document Foundation announces the availability of LibreOffice 6.4.5, the 5th minor release of the LibreOffice 6.4 family, targeted at technology enthusiasts and power users. LibreOffice 6.4.5 includes over 100 bug fixes and improvements to document compatibility and interoperability with software from other vendors.

LibreOffice 6.4.5 is optimized for use in production environments, even by more conservative users, as it now includes several months of work on bug fixes. Users of LibreOffice 6.3.6 and previous versions should start planning the update to LibreOffice 6.4.5, as the new major LibreOffice release – tagged 7.0 – is going to be announced in early August.

For enterprise class deployments, TDF strongly recommends sourcing LibreOffice from one of the ecosystem partners, to get long-term supported releases, dedicated assistance, custom new features and other benefits, including SLAs (Service Level Agreements): https://www.libreoffice.org/download/libreoffice-in-business/. Also, the work done by ecosystem partners flows back into the LibreOffice project, and this represents an advantage for everyone.

LibreOffice individual users are supported by a global community of volunteers: https://www.libreoffice.org/get-help/community-support/. On the website and the wiki there are guides, manuals, tutorials and HowTos. Donations help us to make all of these resources available.

Availability of LibreOffice 6.4.5

LibreOffice 6.4.5 is immediately available from the following link: https://www.libreoffice.org/download/. Minimum requirements are specified on the download page. TDF builds of the latest LibreOffice Online source code are available as Docker images: https://hub.docker.com/r/libreoffice/online/.

LibreOffice 6.4.5’s change log pages are available on TDF’s wiki: https://wiki.documentfoundation.org/Releases/6.4.5/RC1 (changed in RC1) and https://wiki.documentfoundation.org/Releases/6.4.5/RC2 (changed in RC2).

All versions of LibreOffice are built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

Support LibreOffice

LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. People willing to contribute their time and professional skills to the project can visit the dedicated website at https://whatcanidoforlibreoffice.org.

LibreOffice users, free software advocates and community members can provide financial support to The Document Foundation with a donation via PayPal, credit card or other tools at https://www.libreoffice.org/donate.

01 July, 2020


Un nuevo encuentro virtual de la Comunidad hispana tendrá lugar este mes, en esta ocasión será el sábado 18 donde, una vez más, contaremos con la presencia de varios miembros reconocidos por su participación y colaboración en el ámbito del …

Older blog entries ->