I worked on some further improvements of the Plone addon tdf.templateuploadcenter. A site administrator is able to edit the allowed image and template file extensions. Thus I wrote a new validator for this file extensions. I created a field to inform contributors about the currently allowed file extensions (with dynamic content).
The add-on provides not only projects with releases but also small projects where the template files are uploaded to the small project content type directly.
Today I made a new release of this Plone add-on, which drives the current LibreOffice templates website. The Plone add-on and its release are published as Free Software under the GPL-2 (General Public License version 2): https://pypi.org/project/tdf.templateuploadcenter/
I worked on a new Plone add-on during the last two month. This add-on provide an environment to upload and manage office template projects and files. I finished my work on a first alpha release of this add-on, which is named ‘collective.templates’. It is hosted in the Github repository of the Plone community: https://github.com/collective/collective.templates .
The add-on is compatible with Plone 5.2 and runs on Python 2.7 as well as on Python 3.6 and newer.
I published a first alpha release of this new Plone add-on on the ‘Cheeseshop’: https://pypi.org/project/collective.templates/ .
I worked on a new Plone add-on during the last weeks, which provides an environment to upload and manage office template files. This add-on is nearly finished yet. I’m going to publish this product, which is hosted on the Plone community Github repository (https://Github.com/collective), soon.
The statutes of a foundation states that at a maximum one third of the members of each body are ’employed’ by the same firm, organization, entity or one of its affiliate organizations. The candidates for the board elections had to declare their affiliation therefore in front of the elections.
Because this statements are very important for the composition of the board it’s necessary that every member of the board inform the foundation members and the public in the same way, once this affiliation changes later. The first statement usually was made in an email to a foundation mailing list. Thus the change needs also an email to the same list (and maybe to other foundation communication channels of the fundation).
And the information had to be send out by the person concerned very timely, which means in this case immediately. Are about four weeks for a short email notice immediately? In my opinion this is not the case.
A member of the leading body of a foundation, which has the goal of transparency and openness, should be able to write an email with such a short information latest the next day after the change in the affiliation. If she or he failed to do this should think about his workload and take responsibility for her or his behavior.
I decided to not renew my application for a membership of The Document Foundation some weeks ago. I did this because leading members of the foundation communicated badly about my volunteer work for the foundation and LibreOffice during the last eight years and nobody from the board of the foundation stopped this. For this reason I stopped my contributions to The Document Foundation in last October.
I got also the feeling that some leading people of the foundation are not able to communicate openly and that it often works like a closed group with mostly interests in LibreOffice business (and income from it). The latter was not my main objective.
It’s always no good idea to thank someone without the exact knowledge about the real work he or she had done and the exact period he or she were on duty. Such a commendation – especially in a published report or in a public speech looks to the one who get it the opposite, because it reflects that it is not worth the time to collect and check the correct data.
I read such commendation about my work on the LibreOffice extensions and templates website in the annual report of The Document Foundation today. I invested a lot of my spare time to work as a pure volunteer for the foundation and on the website for about eight years (I worked for about sixteen years inside the community of the free office software project).
I worked on a new Plone add-on during the last weeks. I created this add-on within a Python 3 environment. It runs within a Plone 5.2 instance. During the coding of the new add-on I run into an issue in connection with Zope 4 and filed a bug report.
The code of my new Plone add-on need some further testing and further coding. The add-on provides an environment to upload templates and publish them.
It’s always interesting to see the communication strategy (?) of a board. Don’t publish an agenda of a public meeting to early (only the evening before the event) to certainly avoid to get people from the public into your (public) board call.
The next communication step should be to complain about the lack of participation from the public.
If the communication of a board follows this road it has not to wonder about a lack of participation from the public. The public wouldn’t feel invited.
If you run a new website there is most often a small amount of content at its start. But later the content is growing and users may get an issue to find the content they are looking for. That’s the time when a good build in live search is needed latest.
But it would be the best solution to have such live search already implemented before you go live with your website. And if you expect your website to grow fast you need a very capable live search.
I created such a website together with a service provider for the LibreOffice extensions and templates repository. The site is build on Plone with some add-ons. The Plone Content Management System (CMS/DMS) already provides a build in fast live search. The search is already running by default. There is no need for another implementation of a live search or search function except possibly very big or special environments. But for such cases there are add-ons available in the Plone add-on repository to get e.g. Apache Solr integrated within your Plone installation.
I worked on improvements of the Plone addons for the LibreOffice extensions and templates website during last time. I finished this work yet with two new releases of the addons. There is one of them for the extensions part of the site and another one for the templates part. The new feature of both addons is mail form to get in contact with the author of an extension or a template and give the author some feedback. The mail forms are protected with a recaptcha.
The releases are available on the ‘cheesehop’ (https://pypi.org):
This releases would be probably the last ones, because The Document Foundation want to change the environment for the extensions and templates website to another software.
I already explained in different contextes that I had to limit my volunteer engagement for The Document Foundation in my spare time to give other topics more room (e.g. family and sport). I stated that my contributions include only the maintenance of the current LibreOffice extensions and templates website running on Plone. My work on the website stopped already in October 2018 for communication issues. I did some work on the addons, that I developed for The Document Foundation, since then. But with the decision of The Document Foundation to drop the current LibreOffice extensions and templates website soon, I see no need to further develop the addons within the current setting. I’ll rethink if and how to proceed (most probably in another environment etc.).