New Release Of Collective.Templates

I worked further on the source code of the Plone add-on collective.templates and added a feature to display the username and the e-mail address of a project owner on his/her choice. The new release contains also an improved user documentation.

You could download the new release from the Cheeseshop (https://pypi.org):
https://pypi.org/project/collective.templates/
The source code is available from the Github repository of the Plone collective:
https://github.com/collective/collective.templates

New Releases Of TDF.Templateuploadcenter and TDF.Extensionuploadcenter

I worked on some improvements of the code of the Plone add-ons tdf.templateuploadcenter and tdf.extensionuploadcenter. This add-ons were used to drive the current LibreOffice extensions and templates website.

I moved all unicode strings to ‘safe_unicode’ strings to make it more smooth to migrate the content of the current website to the current version of Plone, 5.2, and Python 3.x.

I published a new release of the add-on tdf.templateuploadcenter (https://pypi.org/project/tdf.templateuploadcenter/) on the Cheeseshop (https://pypi.org) during the weekend. Today I submitted a new release of the add-on tdf.extensionuploadcenter on the Cheeseshop (https://pypi.org/project/tdf.extensionuploadcenter/).

The source code of both Plone add-ons is available in their Github repositories:
https://github.com/andreasma/tdf.templateuploadcenter
https://github.com/andreasma/tdf.extensionuploadcenter

Worked On Collective.ClamAV

I worked with the Plone add-on for virus scanning yesterday and evaluated an issue with a new feature in the Plone add-on plone.formwidget.namedfile. If a file field was not changed (no replacing upload) the return is ‘NOT_CHANGED’ and validator module of collective.clamav was not able to get any data to scan. But there was no need to run a scan in such a situation and thus I added a appropriate check to the validator module. There will be no virus scanning for unchanged file fields anymore.

My changes are already in the Github repository of collective.clamav available: https://github.com/collective/collective.clamav.

The add-on is compatible with Plone 5.2 and Python 3.

LibreOffice Extensions Website Repository Updated To Python 3

I worked on the complete migration of the LibreOffice extensions and templates website repository to Python 3 and Plone 5.2.x during the last days. I was able to upgrade the staging (development / single instance) buildout first. I worked on some Plone add-ons to reach this goal in my spare time during the last weeks.

But for the success of the migration to Python 3 and Plone 5.2.x is necessary a working production buildout. Thus I worked on the live.cfg buildout script for the site and created a new version of it: live2.cfg. I used this new script for the setup of a pure zeoserver with four instances. I could also add the supervisor controller to start and stop the zeoserver and its instances.

Supervisor monitor on my local Plone 5.2.x Python 3 buildout / environment

Then I worked on adding the support of Varnish to it. I used the add-on plone.recipe.varnish from the Github repository for that and changed Varnish to the a current LTS version 6.0.6. I could start varnishd with supervisor although I got an error message with supervisorctl status for it. The Varnish log stated that it could not get the socket of the port, it is configured to run on.

I looked with netstat -pln into the processes running on my PC and found varnishd running and listening. Thus Varnish had been started, but supervisor lost control over it. I was not able to stop Varnish with a supervisorctl command.

I worked further on the migration of HAProxy to the new Python 3 setup. I got a hint from a member of the Plone community that he already created a working branch of plone.recipe.haproxy for Python 3. I changed my buildout scripts to use this branch and I could build and run HAProxy too. But HAProxy didn’t get in contact with Varnish and the zeoserver instances in my setting. It stated that this instances were not running / available, although they are.

I got another hint from this community member and changed my buildout further. I changed the ‘bind’ Varnish configuration line to point to the Haproxy port of my buildout setting. The error message from Varnish disappeared. I was under control of supervisor yet.

Then I read in a blog about an issue of the HAProxy configuration, if it checks via http for the availability of Plone instances. I removed this option (httpchk) from the haproxy.conf file and everything went green. I could finish the migration to Python 3 and Plone 5.2.x.

HAProxy Monitor on my local Plone 5.2.x Python 3 buildout / environment (only 2 of 4 instances are started by supervisor)

The next step would be a test with a copy of the database and content of the current LibreOffice extensions website. I asked for this some days ago, but got no answer yet.

Another Release Of TDF.Extensionuploadcenter

I added a new mail form to contact a project owner to the Plone add-on tdf.extensionuploadcenter yesterday. This new feature made it to the new release of this Plone add-on which I published on the Cheeseshop (https://pypi.org) today:
https://pypi.org/project/tdf.extensionuploadcenter/
It is published with the release number 0.49.

The source code of the add-on is available on Github:
https://github.com/andreasma/tdf.extensionuploadcenter

And here some screenshots of the new feature:

The section with the link to new project owner contact form
The new project owner contact form secured by recaptcha

This Plone add-on (former release) is driving the LibreOffice extensions website https://extensions.libreoffice.org. The new release of this add-on could be integrated into the website by running Buildout.

Published New Release Of Collective.Addons

I worked during the last two days on an extension of the Plone add-on collective.addons. I added a new mail form to contact an owner of an addon project to the product. This mail form is linked from the project pages yet. The form field for the project, whose owner should be contacted, is already filled by default. The screenshots below show the link to the mail form and the mail form itself.

Link to the project owner contact form on the project page
The project owner contact form with filled in project name and recatcha field.

I published a new release of the Plone add-on collective.addons on the Cheeseshop (https://pypi.org) today:
https://pypi.org/project/collective.addons/
The release number is 1.1.

The source code is available from the collective Plone Github repository:
https://github.com/collective/collective.addons

Improved Collective.Templates And Published New Release

I get back to the Plone add-on collective.templates during the last two days and added especially a new improved form to directly contact a template project owner by email. This new form is linked from every project page yet.

There is also the former email form available, which is linked from the sidebar of the template center yet.

I updated the localization of the add-on and made a new release today. The release (version 1.1) is available from the cheeseshop (https://pypi.org): https://pypi.org/project/collective.templates/

You can download the source code of the project from Plone collective repository at: https://github.com/collective/collective.templates

TDF – True Thanks For Volunteer Work?

It’s not funny to read the blog post about the development of a new LibreOffice extensions and templates page. The post lacks of the whole picture about the development and history of the current LibreOffice extensions and templates site. It seemed as if there were no development over the years since the start of the site. But that’s not the case.

The site was first launched in summer 2011 during the first LibreOffice conference in Paris. This site (correctly two sites) was running on Plone 4 using the Plone add-on ‘Plone Software Center’ with the blobstorage addition. This site runs for some years up to the end of 2016.

In the meantime I worked on two new Plone add-ons for an update of the site. I adapted the structure of the new add-ons to the needs of the extension and template submitter from the few feedback I got over the years. I gave presentations about my work on LibreOffice conferences, but without attendance of The Document Foundation (TDF) core members (e.g. board, employees, staff). There were no real vested interest in this area of the project.

I finished my work on a first stable version of the new add-ons in 2016 and I could launch the new (renovated) LibreOffice extensions and templates with the support of a Plone service provider at the end of December 2016. The service provider created a highly scalable productive environment for the new site and migrated the content from the old site into the structure of the new one.

I worked further on the Plone add-ons for the extensions and templates site since then and made some further improvements following the few feedback I got from contributors to the site. I worked in parallel as admin of the site and content reviewer for new extensions and templates. This took a lot of my spare time.

I dropped this admin and review work in autumn 2018 because a member of TDF board criticized my work on the site in public without any preceding talk to me. This was a contempt of my volunteer work on the site and the endless spare time which I spent contributing to LibreOffice and The Document Foundation. In addition other board members didn’t support me and criticized the behavior of the board member in public. This showed me that TDF is not really connected to its Code of Conduct (https://www.documentfoundation.org/foundation/code-of-conduct/). It’s more of a nice to have (written text) but not part of the TDF DNA. The project has no real supportive sustainable culture in communication style and behavior.

Although I dropped my admin and reviewer role on the LibreOffice extensions and templates site I worked on the code of the site further. I made some additions to the structure of the Plone add-ons following the feedback I got from contributors and updated the site’s buildout to Plone 5.1.

Because Python 2 got at the end of its live I worked in parallel on a migration of the Plone add-ons for the LibreOffice extensions and templates site to Python version 3. I finished this work some weeks ago and made Python 3 compatible releases of the add-ons. They were published on the Cheeseshop (https://pypi.org). Each add-on got also it’s own user documentation which I wrote during the development process.

I did also some work for Python 3 compatibility on the LibreOffice extensions and templates site buildout in a seperate branch. This work is making good progress and should be finished during the next weeks (depends on my available spare time). The site could run on Python 3 and Plone 5.2 then.

My current work is already publicly available on Github. I published it under the General Public License v. 2 (GPL-2).

The new post on TDF blog paints a different picture, as if the site and its code hasn’t changed and developed over the years. From my point of view this is a new threat on me and my countless volunteer work on LibreOffice and for TDF. I could not take the words of thank in the TDF blog post seriously. Seemed to be (necessary) flowers of speech.

Updated Extension Site Repository To Plone 5.1

I worked on an update of the source code for the LibreOffice extensions and templates website from Plone 5.0 to Plone 5.1 during last days. I finished this work today. The Plone buildout for the website points to Plone 5.1.6 yet.

I run tests against the new Plone version with data created with the currently used Plone version (5.0) and they succeeded all. The source code of the website is available at Github: https://github.com/tdf/extensions.libreoffice.org

The new Plone version 5.1 will be available at the LibreOffice extensions and templates website once the TDF infra team got time slot to checkout the Github repository and run buildout afterwards.