andreasma at Free Software and other topics
I made some changes and fixes on the Plone add-on that drives the current LibreOffice templates website. This changes makes it possible for a site administrator to set allowed file extensions on the site within the template center content type (without the need to touch the source code).
I created a release of this Plone add-on and published it today on the Cheeseshop (https://pypi.org) (release 0.31):
https://pypi.org/project/tdf.templateuploadcenter/
I’m working on a further Plone add-on that provides an environment to upload and manage product add-ons or extensions. This add-on will work with the new Plone version 5.2 and Python 3. The add-on will be published under the GPL license and the source code will be available in the Plone community repository on Github.com.
It is easy to post a date for an online meeting (e.g. a public phone call). But such a meeting will most likely not take place, if the one, who invited, didn’t put himself/herself one vor more topics on the agenda. It is similar to offline meetings. You wouldn’t invite for such a meeting without an agenda. And you wouldn’t expect that the one, who invited, will not attend and lead the meeting, would you?
Thus some rules oft thumb:
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.