I’m currently working on the user documentation for the Plone add-on collective.templates. The documentation will describe not only the installation but also the creation of a template center and template projects. It will give information about messages which will be send on events to the Plone site administrator / reviewer as well as owner of templates projects.
I worked on the documentation of the Plone add-on ‘collective.addons‘ in my spare time during the last two weeks. I finished this user documentation some days ago and compiled a version in HTML file format and in the pdf file format. I also worked on the Python modules of the Plone add-on and got its build on Travis-CI ‘green’, thus it builds without issues and didn’t throw any flake8 errors anymore.
I published the first stable release of collective.addons on the ‘Cheeseshop’ (Pypi.org) today: https://pypi.org/project/collective.addons/. The add-on provides an ‘Add-on Center’, where contributors could create add-on or extension projects and publish their releases (especially Free Software releases). The Add-on Center make it possible to adapt it to nearly any software project. For detailed information have a look into the user documentation on Github: https://github.com/collective/collective.addons/blob/master/docs/collective.addons.pdf
I worked on the user documentation for the Plone add-on ‘collective.addons during during the last days. I published the first version of this user documentation in website style yesterday. Today I added this documentation in the PDF file format. You’ll find this documentation in the ‘docs’ directory of the Plone add-on on Github:
The slides from a free software conference states that a foundation spents more than half of its donation income to employ or contract staff. This covers a sum of around 430,000 Euro (56 percent of the project donations income). And only seven percent of the projects income by way of donation were spent for community and events.
There were no visible discussion and decision made about precise targets to reach. The foundation and its board didn’t publish such targets. There were no information for the community and the members of the foundation about the impact that should be reached. The community and the members never got an information, how the foundation board will measure, if the targets and the impact had been reached. And if the designated targets and impacts have not been reached, there will Not bei an evaluation of the reasons for that, thus the whole process could be improved. And thus there is and will not be any improvement in this whole process.
The further spending of donation money this way without a real and public (the community and the foundation states itself transparent) target setting and review process is wasting money from donors.
If a charity and its board are not able to set up such a target and review process after years, donors should rethink further donations.
I published a new release of the Plone add-on that drives the LibreOffice templates website. This release has some minor code fixes and is available on the ‘Cheeseshop’ (https://pypi.org):
I worked a bit further on the source code of the Plone add-ons that drives the LibreOffice extensions and templates site. I’ll publish new releases of this add-ons during the next days.
I pushed this changes of the source into the upstream Github repository too, thus they are available from the Github repository of The Document Foundation as well.
I worked a bit further through the Plone add-on that drives the current LibreOffice extensions website and made some smaller fixes on the source code during the last days. I published a new release with this changes on pypi.org today: https://pypi.org/project/tdf.extensionuploadcenter/
The LibreOffice extensions and templates website (https://extensions.libreoffice.org) got back his customized home page again since about a week. This site was created inside a Plone policy add-on package a time ago and its source code got some CSS-fixes some weeks ago. Great to see that it is again up.
There was the information that it would be difficult or impossible to install software on MS Windows 10 students edition without using the App-Store. Most often they use this version of MS Windows because they are short in money. Thus if they should pay for the installation of a free software from the App-Store they mostly will refuse to install and use this software. Especially if they should pay for every major version again (thus two times a year).
It’s moreover antisocial to charge this students for the installation of free software. Especially if you ask students (and others) to do volunteer work on the free software project and share their work.
If a free software project is going that direction you know that its members / leaders lost their society compass.
I created a Plone add-on from plone.bobtemplates some weeks ago and updated its functionality since then. The add-on comes with a .travis.yml file, created by bobtemplates.
But the .travis.yml file throw an error once it runs the tests in the test_example.robot file. I got the message:
AssertionError: Setup failed: WebDriverException: Message: 'geckodriver' executable needs to be in PATH.
After some searching as well as trial and error I found a solution to fix the issue. I made some edits to the ‘before_script’ section of .travis.yml.
before_script: - wget "https://github.com/mozilla/geckodriver/releases/download/v0.24.0/geckodriver-v0.24.0-linux64.tar.gz" - tar xfz geckodriver-v0.24.0-linux64.tar.gz - sudo mv geckodriver /usr/local/bin - 'export DISPLAY=:99.0' - Xvfb :99 -screen 0 1024x768x24 > /dev/null 2>&1 & - sleep 3
I removed the entry: ‘firefox -v’ and added the three lines at the beginning, thus the missing geckodriver got downloaded, extracted and put into the directory which fited.
With this edits of the .travis.yml file the robot example test runs. I got the same message, once I ran the robot test example on my computer. I could fix it by downloading the geckodriver and install it on the machine.
The LibreOffice version 6.3 had been published on August, 8th 2019: https://blog.documentfoundation.org/blog/2019/08/08/tdf-announces-libreoffice-63/
But it seemed nobody took care of an update of the available LibreOffice versions on the LibreOffice extensions website (https://extensions.libreoffice.org/extensions). This new version was added there just recently. Thus the contributors of the LibreOffice extensions website get a notice of the new LibreOffice version and the opportunity to mark their extension as compatible with that version very lately.
But there are some contributors of the LibreOffice extensions website which reacted very quickly and marked their extension compatible with the newest LibreOffice version. I want to thank them for their quick reaction and their contribution to the project.