LibreOffice

Hossein Nourikhah writes: Ever wondered about using modern chat tools to discuss LibreOffice? Here we will discuss using a Matrix bridge to connect to the LibreOffice IRC rooms, to participate more efficiently in LibreOffice-related discussions. ... [More] Traditionally, IRC has been the preferred way of communication for the FOSS communities including the LibreOffice community. There are multiple […] [Less]

Do you want to contribute to the LibreOffice development, but you don’t know enough about the LiberOffice code internals? Do you want to enhance the application or fix a bug in LibreOffice, but you don’t know how to do that? LibreOffice developer ... [More] community can help you not only for at the beginning, but by helping you focus on the right aspect of the code. Reviewers will review your code that eventually will be part of the LibreOffice code! How to understand the LibreOffice code? There are good ways to grow your knowledge around LibreOffice. Let’s review some of them: 1)  Learn how to start development First things first: see our “Getting started with LibreOffice development video“: Getting Started (Video Tutorial) Also, make sure that you have read this page in the Wiki: GetInvolved – The Document Foundation Wiki 2) Read the developer documentation One way to understand the LibreOffice is to read the documents, manuals and other learning materials. We have gathered many of them here: Learning Materials – The Document Foundation Wiki But as a community driven project, not every aspect of the code has comprehensive documentation. So, the other way would be as follows: 3) Read the code The code itself is the best source to understand the internals of the software. You can use OpenGrok to browse the code better. Module documentation and Doxygen output (for example, see doxygen documentation for canvas) can help you to understand many aspects of each module. But as agile manifesto says, we are supposed to value people over other things: “Individuals and interactions over processes and tools Working software over comprehensive documentation” So, other than the referring to the code itself, a good way is to ask help from other people: LibreOffice Conference 2016 in Brno 4) Ask help from the experts and other developers: LibreOffice developers community consists of a large number of people. According to our developers’ page in the TDF Wiki, we have more than 1000 people involved in the development of LibreOffice in which a third of them were active during the previous year: Developers and Contributors list – The Document Foundation Wiki You can see the top contributors to LibreOffice core here: LibreOffice core contributors – Github Among these contributors, there are people with more experience and are experts in different areas of LibreOffice development. We have a list of these experts categorized by their field of expertise: Find the Expert – The Document Foundation Wiki These experts are available in the LibreOffice developer mailing list. Please do not ask your question directly from these people by email, but rather discuss it in the mailing list or CC them in a bug report or in Gerrit. Discussing the issues in the mailing list and bug reports can take a while, but the results are usually well thought answers. To get a quicker answer, the #libreoffice-dev IRC channel would be a better choice. While asking on IRC, please ask your question directly with enough details. If you want to send many lines of code or other lengthy text, please use a paste website like paste.debian.net and then provide a link. If you want to know how a specific feature is implemented in LibreOffice, or how to approach to fix a bug, or any other questions related to development, this room is a good place for you. For a suggested reading for asking smart questions that lead to good answers, take a look at this article from Eric S. Raymond: How To Ask Questions The Smart Way (with translations) One important note about IRC is that the LibreOffice IRC rooms are bridged into the matrix space: https://matrix.to/#/#libreoffice-space:matrix.org, so that you can easily use several Matrix clients to access to the IRC rooms. It is specially good when you want to access the previous chats, or you want to access the rooms via a mobile phone. There are several good Matrix clients available for the desktop, web and mobile platforms. Due to the nature of the FOSS software and its community, active people in the LibreOffice developer community are usually helpful and are willing to help. Get help from LibreOffice developer community and start contribution and help make things better in the LibreOffice! [Less]

Do you want to contribute to the LibreOffice development, but you don’t know enough about the LiberOffice code internals? Do you want to enhance the application or fix a bug in LibreOffice, but you don’t know how to do that? LibreOffice developer ... [More] community can help you not only for at the beginning, but by helping you focus on the right aspect of the code. Reviewers will review your code that eventually will be part of the LibreOffice code! How to understand the LibreOffice code? There are good ways to grow your knowledge around LibreOffice. Let’s review some of them: 1)  Learn how to start development First things first: see our “Getting started with LibreOffice development video“: Getting Started (Video Tutorial) Also, make sure that you have read this page in the Wiki: GetInvolved – The Document Foundation Wiki 2) Read the developer documentation One way to understand the LibreOffice is to read the documents, manuals and other learning materials. We have gathered many of them here: Learning Materials – The Document Foundation Wiki But as a community driven project, not every aspect of the code has comprehensive documentation. So, the other way would be as follows: 3) Read the code The code itself is the best source to understand the internals of the software. You can use OpenGrok to browse the code better. Module documentation and Doxygen output (for example, see doxygen documentation for canvas) can help you to understand many aspects of each module. But as agile manifesto says, we are supposed to value people over other things: “Individuals and interactions over processes and tools Working software over comprehensive documentation” So, other than the referring to the code itself, a good way is to ask help from other people: LibreOffice Conference 2016 in Brno 4) Ask help from the experts and other developers: LibreOffice developers community consists of a large number of people. According to our developers’ page in the TDF Wiki, we have more than 1000 people involved in the development of LibreOffice in which a third of them were active during the previous year: Developers and Contributors list – The Document Foundation Wiki You can see the top contributors to LibreOffice core here: LibreOffice core contributors – Github Among these contributors, there are people with more experience and are experts in different areas of LibreOffice development. We have a list of these experts categorized by their field of expertise: Find the Expert – The Document Foundation Wiki These experts are available in the LibreOffice developer mailing list. Please do not ask your question directly from these people by email, but rather discuss it in the mailing list or CC them in a bug report or in Gerrit. Discussing the issues in the mailing list and bug reports can take a while, but the results are usually well thought answers. To get a quicker answer, the #libreoffice-dev IRC channel would be a better choice. While asking on IRC, please ask your question directly with enough details. If you want to send many lines of code or other lengthy text, please use a paste website like paste.debian.net and then provide a link. If you want to know how a specific feature is implemented in LibreOffice, or how to approach to fix a bug, or any other questions related to development, this room is a good place for you. For a suggested reading for asking smart questions that lead to good answers, take a look at this article from Eric S. Raymond: How To Ask Questions The Smart Way (with translations) One important note about IRC is that the LibreOffice IRC rooms are bridged into the matrix space: https://matrix.to/#/#libreoffice-space:matrix.org, so that you can easily use several Matrix clients to access to the IRC rooms. It is specially good when you want to access the previous chats, or you want to access the rooms via a mobile phone. There are several good Matrix clients available for the desktop, web and mobile platforms. Due to the nature of the FOSS software and its community, active people in the LibreOffice developer community are usually helpful and are willing to help. Get help from LibreOffice developer community and start contribution and help make things better in the LibreOffice! [Less]

Do you want to contribute to the LibreOffice development, but you don’t know enough about the LiberOffice code internals? Do you want to enhance the application or fix a bug in LibreOffice, but you don’t know how to do that? LibreOffice developer ... [More] community can help you not only for at the beginning, but by helping you focus on the right aspect of the code. Reviewers will review your code that eventually will be part of the LibreOffice code! How to understand the LibreOffice code? There are good ways to grow your knowledge around LibreOffice. Let’s review some of them: 1)  Learn how to start development First things first: see our “Getting started with LibreOffice development video“: Getting Started (Video Tutorial) Also, make sure that you have read this page in the Wiki: GetInvolved – The Document Foundation Wiki 2) Read the developer documentation One way to understand the LibreOffice is to read the documents, manuals and other learning materials. We have gathered many of them here: Learning Materials – The Document Foundation Wiki But as a community driven project, not every aspect of the code has comprehensive documentation. So, the other way would be as follows: 3) Read the code The code itself is the best source to understand the internals of the software. You can use OpenGrok to browse the code better. Module documentation and Doxygen output (for example, see doxygen documentation for canvas) can help you to understand many aspects of each module. But as agile manifesto says, we are supposed to value people over other things: “Individuals and interactions over processes and tools Working software over comprehensive documentation” So, other than the referring to the code itself, a good way is to ask help from other people: LibreOffice Conference 2016 in Brno 4) Ask help from the experts and other developers: LibreOffice developers community consists of a large number of people. According to our developers’ page in the TDF Wiki, we have more than 1000 people involved in the development of LibreOffice in which a third of them were active during the previous year: Developers and Contributors list – The Document Foundation Wiki You can see the top contributors to LibreOffice core here: LibreOffice core contributors – Github Among these contributors, there are people with more experience and are experts in different areas of LibreOffice development. We have a list of these experts categorized by their field of expertise: Find the Expert – The Document Foundation Wiki These experts are available in the LibreOffice developer mailing list. Please do not ask your question directly from these people by email, but rather discuss it in the mailing list or CC them in a bug report or in Gerrit. Discussing the issues in the mailing list and bug reports can take a while, but the results are usually well thought answers. To get a quicker answer, the #libreoffice-dev IRC channel would be a better choice. While asking on IRC, please ask your question directly with enough details. If you want to send many lines of code or other lengthy text, please use a paste website like paste.debian.net and then provide a link. If you want to know how a specific feature is implemented in LibreOffice, or how to approach to fix a bug, or any other questions related to development, this room is a good place for you. For a suggested reading for asking smart questions that lead to good answers, take a look at this article from Eric S. Raymond: How To Ask Questions The Smart Way (with translations) One important note about IRC is that the LibreOffice IRC rooms are bridged into the matrix space: https://matrix.to/#/#libreoffice-space:matrix.org, so that you can easily use several Matrix clients to access to the IRC rooms. It is specially good when you want to access the previous chats, or you want to access the rooms via a mobile phone. There are several good Matrix clients available for the desktop, web and mobile platforms. Due to the nature of the FOSS software and its community, active people in the LibreOffice developer community are usually helpful and are willing to help. Get help from LibreOffice developer community and start contribution and help make things better in the LibreOffice! Read the rest [Less]

The LibreOffice Quality Assurance ( QA ) Team is happy to announce LibreOffice 7.3 RC2 is available for testing! LibreOffice 7.3 will be released as final at the beginning of February, 2022 ( Check the Release Plan for more information ) being ... [More] LibreOffice 7.3 RC2 the forth and last pre-release since the development of version 7.3 started in mid June, 2021. Since the previous release, LibreOffice 7.3 RC1, 117 commits have been submitted to the code repository and 65 issues got fixed. Check the release notes to find the new features included in this version of LibreOffice. LibreOffice 7.3 RC2 can be downloaded from here for Linux, macOS and Windows, and it will replace the standard version. 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!! … [Less]

Many OpenOffice users are seeing warnings when trying to access files in the OpenDocument Format (eg .odt, .ods). The full text is: This document was created by a newer version of OpenOffice. It may contain features not supported by your current version. In this case, the document was probably made in LibreOffice, which supports newer […]

Today we have a quick chat with Baltasar García Perez-Schofield, who recently became a Member of The Document Foundation, the non-profit entity behind LibreOffice… Tell us a bit about yourself! I’m from Spain, in that north-west corner called ... [More] Galicia. Professionally I’m a teacher of computer science, and dedicate my spare time to my family, swimming, […] [Less]