I made a quick test with a currently published LibreOffice extension and it seemed there were no accurate review of the file before it and the project were published. Sad situation.
I read about a new Plone UI named ‘Volto’ and created a new instance from the Github repository: https://github.com/plone/volto
I had to install node.js and yarn on my notebook. I created a new volto package with ‘create-volto-app my-volto-app’. I could build my volto app with the command ‘npm start’. This build everything and the instance is available at port 3000 of your URL, e.g. ‘http://localhost:3000’. But you need to fire up the Plone instance too with e.g. ‘bin/instance fg’ too (otherwise you will get error messages).
The screenshot above shows the Plone site within a resolution for mobile devices. The Volto app uses the Pastanaga theme and is ‘mobile first’.
In about two weeks many free software developers and enthusiast meet at the FOSDEM in Brussels for at least two days. They are traveling from other countries inside the European Union as well as from countries around the world to Brussels. Many developers (and some open source supporters too), which attend the event are employed by open source companies, they are traveling to Brussels within the scope of their payed job (for different reasons) and give talks on topics around their dayly work.
If there is a connection between the the payed job of an attendee and the participation at the FOSDEM, people from inside the European Union that travel (in this case) to Belgium, Brussels need a form A1. If they didn’t own such a certificate their work runs under the rules of the Belgium social security. I explained the features of the A1 form already some weeks ago on my blog here. A connection to the daily could be e.g. a presentation with the branding of the employer or even the statement of a business trip at the hotel reception.
I finished my migration of a first Plone addon some a week ago sucessfully and started with migration of a further addon, collective.dexteritytextindexer to Python 3 compatibility. I was able to migrate the source code of the addon itself, but run into issues with the behaviors test script. The tests ran successful on Plone 4.3 to 5.2 and Python 2.7, but failed on Plone 5.2 on Python 3.
I did pour volunteer work for LibreOffice and its antecessor for about sixteen years. I worked in different roles for the open source project during this long periode. The project consumed a lot of my spare time. But then I experienced a ‘nice’ communication experience inside the community (from some ‘core’-members), that showed me a lack of respect for my project work, its value and also for my person. Thus I decided to completely stop my pour volunteer work within the project three month ago. The LibreOffice extensions and templates website (extensions.libreoffice.org) lost its maintainer and project reviewer since that time.
I used my free cycles to improve my fitness. And I was able to do this way something in balance to my day by day payed office work. Seemed it was a smart decision 😉
I worked on my first migration oft a Plone addon to Python 3 during the last days. There were some instructions available on Github how to procide and I followed them. I was able to run the addon inside my local environment, but I got some issues with the continous integration test on Travis-CI, once I submitted a pull request. I had to fix the scripts inside the addon for building and testing on Travis-CI and was successful with the great support from a member of the Plone community. He merged my pull request and released a new version of the addon cioppino.twothumbs today: https://pypi.org/project/cioppino.twothumbs