During Hack Week 7 I worked on an archive of Qt-based libraries. The goal was to easily make all available Qt libraries accessible to developers. Think CPAN for Qt. So I hacked on a web site and a command line client.
There was a little bit of progress on the project since then, but with the upcoming KDE Frameworks 5 there will be quite a number of additional libraries available for Qt developers. This should be well represented in Inqlude as well. The coverage of Inqlude is also still not complete, and the tooling needs some improvement as well, especially regarding integration with distributions.
There are many 3rd party libraries based on Qt. Inqlude collects them all. The goal of this project is to package them all, ideally automatically from the meta data provided by Inqlude. The build service provides all the tools we need for that and would even make it possible to provide packages for a multitude of Linux platforms and maybe even Windows. Interesting challenges ahead...
almost 4 years
3 hacker ♥️.
Has no hacker:
We will have a series of short lightning talks to present what we have accomplished at Hack Week 12. In Nürnberg this will happen on Friday 17th Apr at 12:30 as part of the lunch session in the all-hands area. Lunch is served at 12:00, so you have a bit of time to settle in and satisfy your immediate needs before we go into presentation mode.
If you would like to tell a bit about what you did at Hack Week 12, please leave a comment (preferably with a link to your projects), and I'll add you to the schedule.
Writing code is wonderful, but it gets its real value, when it's released and shipped to the world. You know the mantra: "Release early, release often".
Releasing code is not hard, but it involves a lot of details, and you want to get them right, because a release is this public statement "Hey, it's done, it works, you can use it." and you can't take a release back, once it's out there. To help with releases there are tons of release scripts which try to automate things. But they usually are quite fragile in case something goes wrong and a pain to test and maintain.
There are a lot of open source projects out there. They have a wide spectrum of governance models. It's a critical component to the success of a project so it's worth learning from others and consciously deciding on how governance is set up for a project. It's also a critical factor to assess projects and a subject for research.
To facilitate all this a map of the models in use is a helpful resource. This project is about collecting data about open source governance models, make it available in a machine-readable form, and provide an overview via a web page.
SUSE Studio was shut down earlier this year. It has been online for more than ten years and there are tons of links and references out there. To not make them lead into the wasteland of 404 we should have a landing page on https://susestudio.com which leads to what users can use instead of SUSE Studio.
I did a mockup of a page which could be hosted there. See it at https://github.com/cornelius/goodbye-dister.