Plone On Python 3 – First Try Out

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).

Worked Further Through Projects Review List And Fixed A String Issue

I worked to the through the review list of  the LibreOffice extensions and templates website and managed to look at the remaining projects. I sent hints to the contributors and am looking for their project site changes and updates of their release files.

I fixed some string issues inside one of the Plone add-ons that we use to drive the website. I got to this issue by an error message inside the website log. The fixes are available in the TDF Github repository yet.

New Add-On Release For The LibreOffice Extensions Website

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.

Volunteers – Spare Time / Vacation?

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.