Inqlude, the Qt software archivea project by cschum 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. |
|
|
Add github and/or gitlab support to Zuulan idea by aspiers UPDATE: it turns out that people upstream are already working on this, so the idea would be to join that work. As per |
|
Learn gitbook.coman invention by lrupp https://www.gitbook.com/ allows you to combine repositories on https://github.com with a simple to use WebUI for writing books. As result, your crazy content in your README.md (or whatever *.md) files will become available for your customers as book in form of a pdf, epub or mobi download. This hackweek project is about to learn new things and try to do something useful by collecting all my former experiences in a book that is on my TODO list since more than 10 years now: |
Improve Nailedan idea by itxaka Nailed is a great tool for gathering development data. Unfortunately it hasn't seen any improvements in some time and some of the most needed data is not available (PR life, review numbers, open and closed PRs) |
|
help clojure upstream with clj-common with some PR and contributionsa project by dmaiocchi Rationale:There is around in the clojure community (https://clojure.org/) a GitHub opensource organization which aims to maintain in a centralized manner some useful community libraries. |
Extract lead and cycle times from Githuban invention by jochenbreuer When all of the SUSE Manager squads switched from SCRUM to a Kanban we lost estimations and therefore also the ability to do predictions. But there are other ways to get insights that are even more reliable, since they are based on anecdotal data. The lead and cycle times of issues are the two most important here. I'd like to extract those two for all of the issue from the spacewalk project and explore how they can be visualized in meaning- and helpful ways. |
|
Polish filtra and move data collection to Postresqla project by jochenbreuer Last hackweek filtra was created – a tool to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban. The collected metrics can then be visualized with Grafana. Currently there are two problems with filtra: |
|
Zero-ish downtime deploy on da cheap!a project by josegomezr Zero-ish downtime deploy on da cheap!This project aims to get a 0-ish downtime deployments (very easily achievable with Kubernetes) just using: |
multipath-tools: improve CIa project by mwilck Project Descriptionmultipath-tools is in urgent need of better CI, both unit tests and "real world" tests. We a very basic set of unit tests, but the coverage is miserable. Also, there's some minimal github workflow code, which could be improved a lot while I'm learning about github workflows. |
Generic retry command in openSUSEan invention by okurz MotivationWhen automating tasks often the requirement comes up to retry commands, for example when network connections are involved and commands do not return successfully immediately or if resources are temporarily not available. Sometimes a simple for-loop in bash is sufficient. Sometimes it is necessary to use additional waiting between retries, sometimes timeouts are desired. Getting all those combinations right can be tedious and error-prone so a generic "retry" command should be available in usual environments so we should provide a retry command to openSUSE distributions. |
Tinker with mirror, a tool to watch and backup source code repositoriesan invention by andreas-kupries Project DescriptionRestart work on the |
|
|
obs_scm_demoan invention by smithfarm Project DescriptionFor a long time, I have been planning to learn more about how OBS is integrating with "SCMs" (Source Code Management systems - for me, that means primarily git, GitLab, and GitHub). For Hack Week 22, I decided to bootstrap a trivial software project on GitHub, with automated builds in OBS, and document the steps as I go along. |
|
Deep clean-up of the Uyuni documentation filesan idea by omaric Project DescriptionThis project is planned as a collection of random changes to the documentation files in order to rid them of cluttered in the content, outdated comments, inconsistent style (minor issues), unused parameters, duplications, etc. |
Collect flaky test cases identified by the team in a GitHub board and highlight them in the Test reportan invention by oscar-barrios Project DescriptionFlaky tests: Those that have not a consistent result, and sometimes are failing and others are passing. |
|