I started with my work to migrate a first Plone addon to Plone 5.2 on Python 3. I did this work on the addon cioppino.twothumbs. I first applied ’sixer‘ on it and than run ‚python-modernizer‘ as described on this page. But I got some errors with the imports afterwards, once I started the Plone instance with ‚fg‘. This imports were implicite relative. I changed them to explicite relative or absolute. The addon is running yet in the Plone instance. But there is a remaining issue with the css-file of the addon. I pushed my changes to the new git branch ‚python3‘: https://github.com/tdf/cioppino.twothumbs/commits/python3.
Kategorie: Plone
Working Further With Plone and Python 3
I created a further buildout for Plone from the Plone coredev Github repository and checked out the 5.2 branch. The buildout went fine and I could create a new Plone site.
I tried out to create a new add-on with bobtemplates and it worked with my new Plone site (on Python 3.6). I was able to install the add-on without errors. I’ll try out some further add-ons with this buildout using my own extension of the core buildout script. I’m curious, if this add-ons will work with my buildout. If they will not run on Python 3 I’ll try to upgrade them.
Give Plone 5.2 On Python 3 Another Try
I updated my local git repository of the Plone development branch for the migration to Python 3 and run the buildout again. Everything went smoothly and I could start my Plone 5.2 site. I made some edits within the theme editor this time. I created already a copy from the default Barceloneta theme and made some edits on it and activated the new theme. It worked.
Myth About LibreOffice Presentation Templates On Extensions-Templates-Website
There was a post on the LibreOffice design-list this month that stated that no presentation templates were offered on the LibreOffice templates website: https://listarchives.libreoffice.org/global/design/msg08869.html
I followed the provided link in that email and got a different picture:
Uups, there were 45 projects found and some of them have already a lot of votes.
Plone Theming – So Difficult ;-)
The Plone CMS/DMS came with a theming editor, where you could create a new theme and edit themes. You could copy an already on the site available theme or create a theme from scratch. It’s your choice. I used the theme part in the administration interface to copy the Plone default theme ‚Barceloneta‘ and save it under a new name.
I could edit this new theme with the Plone theme editor (button ‚Modify Theme‘.
The theme is based on the Diazo theme engine (https://docs.plone.org/external/diazo/docs/index.html#diazo-theme-engine-guide)
Gave Plone 5.2 On Python 3 Another Try
I updated my local copy of the Github repository for Plone buildout.coredev and gave the branch for the Python 3 migration another try. I run the bootstrap-py3.sh script and all packages were updated. Then I started Plone with ‚./bin/wsgi fg‘ and created a new Plone site.
I activated the multilingual add-on to make the new Plone site available in different languages. This added a special dialog to the administration page. I opened this dialog and added a second language to the site (in my case German). Plone created different folders for each of the two languages. I gave first the English folder a try and added a first page to it. Because I don’t want to use my time for typing I copied content from the website of The Document Foundation website.
I published this page and choose it as the default page of the English section. Then I tried out the translation framework of Plone. I made a test with a translation of the page into German.
The dialog shows me the different fields of the English page and I could easily start to write a translation into German. If I had already local or somewhere else a translation of the English text, I could do copy and paste.
Once finished with the translation I saved it and published the page. I set it as the default of the German section. Users with German laguage setting or preference will get this translated page as their entry point now.
Fake News About Expense?
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.
Really Shocked!
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.
Fixed Issues With The Workflow State
I worked with the Plone instance of the LibreOffice extensions and template website the last days and fixed issues with the workflow state and the permissions. The site should work as expected again.
I worked on an improvement of the messaging system in parallel. This new notification will help to review current changes on the site. The improvements are currently living in the TDF Github repository and will go live with the next run of buildout.
A Quick Test With Plone 5.2 And Python 3.6.5
I created an buildout from the Plone corebot Github repository. I used the current development version 5.2 and run it on a Python 3.6.5 virtual environment. The buildout of the Plone instance took some time, but everything went well and I could create a new Plone site. I added the multilanguage addon to it and played a bit with the site. I added second language to the site, created a new page and tested the translation framework that came with the addon. It worked as expected and I got a page with a linked translation.
Then I tried out how the website of the Documentation would look like in a pure (not specially branded) Plone environment. I did a quick and dirty copy and paste of the homepage of TDF and the new Plone page was done in 1 minute. The page uses the default Plone layout and there were no issues with different screen size.
