andreasma at Free Software and other topics
I worked on the first bits for a new Plone development environment. I’ll use this to create a new website for the ODFAuthors team. The new site should run on Plone 5.1 or later. Maybe it is possible to upgrade the site to a Plone version that runs on Python 3.
I read already on a blog of a Plone developer that Core-Plone is already ported to Python 3, but that there are a big bunch of tests that are not yet ported and need some love (and work time).
The Plone developers work hard to port the CMS to Python 3 before the support for Python 2 ends. This will be in about 1 and a half year from now. LibreOffice made this step a longer time ago and comes currently with Python 3.5.4. Thus the LibreOffice Python programming environment and connection will get updates and security fixes after the end of 2019 too.
If you use another office suite with Python support you should take a closer look into the supported / delivered version. If it is not Python 3 yet have an eye on alternatives in time.
I reviewed the Python code for the LibreOffice extensions and templates website and started with improving the string formating handling. I changed it in a first Python module to the current method (available also in Python 3). I’ll work on further Python module during the next days.
I worked through more than 120 bouncing emails from the LibreOffice extensions and templates website yesterday. There were a lot of them with no valid email account. I had to search for this accounts inside the website and delete the accounts using the Plone admin interface of the site. I spent about two hours of my spare time on this task in the evening.
I worked with the German speaking community of LibreOffice (and OOo) for more than fifteen years. I stopped this involvement for some reasons some weeks ago. I don’t know, if the reasons for my decision will disappear next time.
I currently continue my work with the LibreOffice extensions and templates website, a volunteer project that I founded in 2011 and whose environment I developed together with a service provider to a new status (2.0). The LibreOffice extensions and templates website uses the Content Management System Plone with additional plug-ins, all developed and published under free software licenses.
I worked a bit inside the virtual machine which runs the LibreOffice extensions and templates website today and reordered the files and moved some of them inside new subfolders. The directory with the Plone instance is much cleaner again.
I had also a look on the content of the site and reviewed some template projects. I had to remove two of them because they didn’t fit the terms of use.
I updated the LibreOffice extensions website with the source code fix that I added yesterday. The issue with documentation files is gone now.
I worked on an issue that a contributor to the LibreOffice extensions and templates website (https://extensions.libreoffice.org) forwarded to me. I had to investigate the source code for the connection to the uploaded documentation file for an extension and submitted a fix for this issue today the TDF github repository. The fix will be available within the next run of buildout for the LibreOffice extensions and templates website.
I started my examination of LibreOffice extension projects which remain in review state private and sent some owners an email. Let’s wait for the response and see if the projects could make it to publication. Will continue my work during the next days.
I worked on an improvement of my script to find LibreOffice extension and template projects that are in the review state private and never made it to the review queue. I’ll run that script soon and evalute the resulting lists. Maybe some of the authors have forgotten about their projects or have other issues with the publication process. Let’s see what happens.