I read in an email on the LibreOffice design list that has been resources allocated to the extensions and templates website for about 25 thousand Euro (from a long time member of the board of The Document Foundation: https://listarchives.libreoffice.org/global/design/msg08869.html). This generates the impression that there has been spent this amount of money to improve the site. But if you look into the accounting legers of The Document Foundation (TDF) (https://wiki.documentfoundation.org/TDF/Ledgers) you will get the real data. TDF spent in 2017 6399,44 Euro and in 2018 642,60 Euro; all in all 7042,04 Euro, which seemed only a bit less than 25 thousand Euro 😉
This TDF resources were used espially to migrate the content of the first LibreOffice extensions and template websites into the new one, for smaller fixes within the code, a professional buildout and maintenance environment and a training of two TDF staff member on the platform and its maintenance (myself wasn’t part of the training session).
The biggest part of the development of the new LibreOffice extensions and templates website was done during my spare time. I tried to save as much as possible expenses for TDF, because I thought it would help to lower the adminstration expenses of TDF and free more money for the promotion of education and science.
I’m doing volunteers work in different roles and areas of the project for about sixteen years yet. I spent a lot and for some longer periods nearly my whole spare time on the project. I suffered from a public accusation of a destructive communication style. This harmed me very intense. I though this could be a singular ‘event’. But I was tought today that this seemed to be the new behavior of members of the leading body.
I created and maintained the LibreOffice extensions and template website for more than seven years yet. I read today on a public maiing list that the work I had done during my spare time for this period was not even werth to talk to me (even by email). Instead I felt my work devaluated in public. I felt like being in the pillory. I though the methods of the Middle Ages were not such popular anymore. But I had to confess that I was at fault.
This is behavior and communication style is not appropriate for a project, where I want to spent my spare time and do volunteer work. Because the behavior is not a single ‘event’ I stop my work for and within the LibreOffice project as from now.
I’m open for intensive and also critical discussions but not for a behavior and communication style that I wouldn’t accept in the office during my paid work.
I started my work on a new Python script to evalute LibreOffice extensions. It’s currently in a very early state and I’m going to use only very limited spare time to update it. I’m going to concentrate on more healthy activities than sitting in front of PC. Thus don’t be surprised if this and other task will not be finished immediately. I’ll adapt my workflow / workload to the favored range of the open source project, particularly it’s only pure volunteer work.
Meine Dokumentation zum Erstellen von LibreOffice extensions, mit denen neue Inhalte ausgeliefert werden, habe ich um einen weiteren Abschnitt zu Icon-Sets ergänzt. Die neue Fassung kann über den folgenden Link heruntergeladen werden. Die Dokumentation ist in deutscher Sprache.
It is possible to extend the office suite LibreOffice with add-ons, named Extensions. If such an Extension will be licensed as Free Software using an Open Source license, it could be published on the website https://extensions.libreoffice.org. I have a look into such extensions, regularly, that are submitted for publication on that website. Thus made me aware, that contributors (extension developers in this case) didn’t know about the need to include the license information into the Extension in the form of a text file and link to that license information from the ‘description.xml’ file inside the Extension. But without a proper license the Extension it is not appropriate to publish the Extension on the LibreOffice Extensions website.
But it is not a very difficult task to add such a license information to the Extension. Just add a text file with the license to the Extension (zipped) container (preferably in a subfolder) and update the description.xml with the following xml-tag:
<simple-license accept-by=”admin” suppress-on-update=”true” >
<license-text xlink:href=”<relative link to the license file>”
It’s also possible to add another license file to the Extension, that is localized in another language, e.g. German or French. In this case add a further xml-tag ‘license-text’ with the link to the license file in that language:, e.g.
<license-text xlink:href=”registration/license_de” lang=”de” />
If the license information is available in the users language setting, the LibreOffice extension manager will display the license in that language.
And another tripping hazard on the way to a published LibreOffice Extension project is the state of an Extension release. It’s necessary to change the initial state ‘pre-release’ to a release state from ‘alpha’ to ‘final’ correspondent to the development state of the Extension. This change could be done on the menu bar (left side of the website). It’s not appropriate to publish an Extension project without a ‘released’ Extension file.
I was a (deputy) member of the board of directors (BoD) for about six years and decided not to run again for this body at the end of last year. I followed a lot of discussions and decisions of the board during this period.
At the time I decided to not run again for the board I reflected on the topic, if I should run for the MC (Membership Commitee) this summer and came to the conclusion that this is not appropriate. The MC is not only responsible for the decision on new TDF members and renewing membership. This is the role that the most people inside TDF already know. But the MC has also another important role. it is in some kind in the position of a supervisory board. It receives complaints against the BoD the Board of Trustees and initiates a possible impeachment process against the board of directors. The MC also represents the foundation in court and out of court against the BoD (see Par. 12 I of the statutes). The latter one were the main reason for me to request a cool down period for myself [as an ex-(deputy-)member of the BoD] before I could run for another leading body of TDF. I thought that such a cooling down period should be at least one year. But maybe two years are more appropriate.
In addition I think its role as a kind of supervisory board should lead to a reflection, if it would be appropriate when members of the BoD and the MC would be personally or economical closely connected. It’s also a topic of rethinking, wether a member of the MC should be able to switch without a break into the BoD.
Im Zusammenhang mit der Betreuung der LibreOffice webseite für Extensions (Erweiterungen) und Templates (Vorlagen) habe ich vor einiger Zeit angefangen, eine kleine Dokumentation für den Bau von LibreOffice Extensions zu schreiben, die keine Zusatzprogramme enthalten, sondern weitere Inhalte für das Office-Programm ausliefern. Dies können beispielsweise weitere Grafiken, Autokorrekturen oder Farbpaletten sein. Die Dokumentation ist ein Projekt “im Fluss”. D.h., ich werde weiter an ihr arbeiten und sie ergänzen. Hier nun die aktuelle Fassung der Dokumentation. Sie enthält auch Links zu Beispielen für die Struktur entsprechender Extensions.
The Plone team is working on a migration of the CMS to Python 3. I read about this migration and that there are good progress. Thus I decided to try the ported version out. There is a repository with a working on Github. I checked it out from https://github.com/collective/demo.plone.de. I followed the instructions in the file https://github.com/collective/demo.plone.de/blob/master/local_demo_latest_py3.cfg and it worked out. I could create a new site with Plone 5.2a1 and Python 3.6.5 (see screenshot below).
I worked during the last days on some issues within the Plone add-on which drives the LibreOffice extensions website. I made a new release of this add-on today and published it on the ‘Cheeseshop’ (https://pypi.org). You can get the source code of this add-on from the TDF repository on Github (https://github.com/tdf/tdf.extensionuploadcenter). I’m working on an update of the Plone add-on that drives the template part of the website and I’m going to publish a new release during the next days too.
In addition to this work I reviewed some new LibreOffice extensions and templates projects that has been contributed during my vacation break and during the last days and published them, if they are ready for publication.
I added the current LibreOffice version 6.1 to the compatibility list for extensions and templates and sent out an information about this new version to all members of the website, thus they could update the compatibility of their extensions or templates.
I read a tweet during the last days that a community didn’t stop during the weekend and that make me thinking, if such a tweet would evoke the impression that a volunteer in an open source project works all day and around the clock (24/7). I got this impression because there are some people during the last days that are posting impatient messages on the work done by others.
I myself decided to limit my volunteer work to a proper amount. I’ll not extend a long working day in the office with some volunteer work in front of computer. I think an open source project should avoid to set the impression that volunteers never have to relax, sleep etc., because this helps to keep active people healthy and keep the barriers for new volunteers lower.