Kudos aka openSUSE Recognition Platform
Description
Relevant blog post at news-o-o
I started the Kudos application shortly after Leap 16.0 to create a simple, friendly way to recognize people for their work and contributions to openSUSE. There’s so much more to our community than just submitting requests in OBS or gitea we have translations (not only in Weblate), wiki edits, forum and social media moderation, infrastructure maintenance, booth participation, talks, manual testing, openQA test suites, and more!
Goals
Kudos under github.com/openSUSE/kudos with build previews aka netlify
Have a kudos.opensuse.org instance running in production
Build an easy-to-contribute recognition platform for the openSUSE community a place where everyone can send and receive appreciation for their work, across all areas of contribution.
In the future, we could even explore reward options such as vouchers for t-shirts or other community swag, small tokens of appreciation to make recognition more tangible.
Resources
(Do not create new badge requests during hackweek, unless you'll make the badge during hackweek)
- Source code: openSUSE/kudos
- Badges: openSUSE/kudos-badges
- Issue tracker: kudos/issues
Looking for hackers with the skills:
javascript nodejs artwork inkscape uix prisma express npm opensource opensuseheroes sqlite netlify community rpm
This project is part of:
Hack Week 25
Activity
Comments
-
26 days ago by lkocman | Reply
I'd meet daily at 10-11am CET at https://meet.opensuse.org/kudos to sync on upcoming work. I do have a kudos-test space at https://matrix.to/#/!rVFpPrxfQYrCumMFjn:matrix.org?via=matrix.org which we can use for general kudos communication.
I'd really appreciate collaboration in a form of tested PRs against issues at https://github.com/openSUSE/kudos But mainly any help with deployment on openSUSE/Heroes infra.
-
-
-
12 days ago by lkocman | Reply
Georg is working on deploying the VM on Leap 16.0, unfortuatelly there we require a newer salt minion
The chalenge is building of prisma engines, which are unfortunatelly fetched on dbx prisma migrate ...
Meanwhile I'm doing an offline rpm build in https://build.opensuse.org/project/show/home:lkocman so we can have rpm based deployment on the heroes infra.
-
9 days ago by lkocman | Reply
Oky opensuse Infra deployment is blocked on Heroes at the moment. I don't think that this will happen during hackweek.
Seems like there is a breakage with salt that has to be fixed first. I'm talking with Adam Majer on testing the new package submission with Kudos to https://src.opensuse.org/nodejs/_ObsPrj.git#master Meanwhile we build package in https://build.opensuse.org/project/show/openSUSE:infrastructure:kudos
-
-
-
9 days ago by lkocman | Reply
Hackweek 2025 Summary – Kudos Deployment Work
Kudos is now fully ready for deployment. The main blocker is the current issue with the heroes salt-based deployment, which is broken at the moment. Georg is working on a fix, but due to the Leap 16.0 transition and related salt issues, it will likely take some time. The relevant merge requests are here: MR 2673 MR 2672 (both are currently blocked on broken pipelines)
On the application side, Kudos was cleaned of local authentication. It now relies entirely on tokens + OIDC, which is the setup we want for production.
I fixed and polished the Admin UI for badge, bot, token, and user management. The visuals are now consistent across pages, as headings previously looked very different. I also received approval from Russ Dastrup to use the vocal-less What does the chameleon say track as background music, so the app now officially includes it.
Kudos is now packaged as an RPM. There is still room for improvement, especially around pre-built Prisma binaries, since without them Prisma migrate fetches binaries from the internet.
The app is currently building in: openSUSE:infrastructure:kudos and will be deployed to kudos-o-o from there.
I also created a nodejs Devel project submission. Adam Majer wanted to pilot the new package submission workflow on Kudos: Node.js Devel project request
The packaging process forced me to fix several production deployment issues, such as redirects that assumed separate backend and frontend servers. With both now running on a single port, these inconsistencies are resolved. We also now have a dedicated production seed.js.
Relevant pull requests from this Hackweek can be found here: Hackweek 2025 Kudos pull requests
Similar Projects
Work on kqlite (Lightweight remote SQLite with high availability and auto failover). by epenchev
Description
Continue the work on kqlite (Lightweight remote SQLite with high availability and auto failover).
It's a solution for applications that require High Availability but don't need all the features of a complete RDBMS and can fit SQLite in their use case.
Also kqlite can be considered to be used as a lightweight storage backend for K8s (https://docs.k3s.io/datastore) and the Edge, and allowing to have only 2 Nodes for HA.
Goals
Push kqlite to a beta version.
kqlite as library for Go programs.
Resources
https://github.com/kqlite/kqlite
Hackweek 25 from openSSL office in Brno, Czechia by lkocman
Description
Join South Moravian colleagues, Austrian friends, and local community members for Hackweek 25 at the openSSL corporation office in Brno, Czechia. This will be a relaxed and enjoyable in-person gathering where we can work on our Hackweek projects side by side, share ideas, help each other, and simply enjoy the atmosphere of hacking together for a week.
Food, snacks, coffee will be available to keep everyone energized and happy throughout the week. We'd like to throw a small party on Tuesday.
Goals
- Bring together SUSE employees and community members from the South Moravian region and nearby Austria.
- Create a friendly space for collaboration and creativity during Hackweek 25.
- Support each other’s projects, exchange knowledge, and experiment freely.
- Strengthen local connections and enjoy a refreshing break from remote work.
Resources
Report from Grand openning of the office
Switch software-o-o to store repomd in a database by hennevogel
Description
The openSUSE Software portal is a web app to explore binary packages of openSUSE distributions. Kind of like an package manager / app store.
https://software.opensuse.org/
This app has been around forever (August 2007) and it's architecture is a bit brittle. It acts as a frontend to the OBS distributions and published binary search APIs, calculates and caches a lot of stuff in memory and needs code changes nearly every openSUSE release to keep up.
As you can imagine, it's a heavy user of the OBS API, especially when caches are cold.
Goals
I want to change the app to cache repomod data in a (postgres) database structure
- Distributions have many Repositories
- Repositories have many Packages
- Packages have many Patches
The UI workflows will be as following
- As an admin I setup Distribution and it's repositories
- As an admin I sync all repositories repomd files into to the database
- As a user I browse a Distribution by category
- As a user I search for Package of a Distribution in it's Repositories
- As a user I extend the search to Package build on OBS for this Distribution
This has a couple of pro's:
- Less traffic on the OBS API as the usual Packages are inside the database
- Easier base to add features to this page. Like comments, ratings, openSUSE specific screenshots etc.
- Separating the Distribution package search from searching through OBS will hopefully make more clear for newbies that enabling extra repositories is kind of dangerous.
And one con:
- You can't search for packages build for foreign distributions with this app anymore (although we could consume their repomd etc. but I doubt we have the audience on an opensuse.org domain...)
TODO
Introduce a PG database- Add clockworkd as scheduler and delayed_job as ActiveJob backend
- Introduce ActiveStorage
- Build initial data model
- Introduce repomd to database sync
- Adapt repomd sync to Leap 16.0 repomod layout changes (single arch, no update repo)
Make repomd sync idempotent
- Introduce database search
- Setup foreman to run
rails sandrake jobs:workoff - Adapt UI
- Build Category Browsing
- Build Admin Distribution CRUD interface
Create a page with all devel:languages:perl packages and their versions by tinita
Description
Perl projects now live in git: https://src.opensuse.org/perl
It would be useful to have an easy way to check which version of which perl module is in devel:languages:perl. Also we have meta overrides and patches for various modules, and it would be good to have them at a central place, so it is easier to lookup, and we can share with other vendors.
I did some initial data dump here a while ago: https://github.com/perlpunk/cpan-meta
But I never had the time to automate this.
I can also use the data to check if there are necessary updates (currently it uses data from download.opensuse.org, so there is some delay and it depends on building).
Goals
- Have a script that updates a central repository (e.g.
https://src.opensuse.org/perl/_metadata) with metadata by looking at https://src.opensuse.org/perl/_ObsPrj (check if there are any changes from the last run) - Create a HTML page with the list of packages (use Javascript and some table library to make it easily searchable)
Resources
Results
Day 1
- First part of the code which retrieves data from https://src.opensuse.org/perl/_ObsPrj with submodules and creates a YAML and a JSON file.
- Repo: https://github.com/perlpunk/opensuse-perl-meta
- Also a first version of the HTML is live: https://perlpunk.github.io/opensuse-perl-meta/
Day 2
- HTML Page has now links to src.opensuse.org and the date of the last update, plus a short info at the top
- Code is now 100% covered by tests: https://app.codecov.io/gh/perlpunk/opensuse-perl-meta
- I used the modern perl
classfeature, which makes perl classes even nicer and shorter. See example - Tests
- I tried out the mocking feature of the modern Test2::V0 library which provides call tracking. See example
- I tried out comparing data structures with the new Test2::V0 library. It let's you compare parts of the structure with the
likefunction, which only compares the date that is mentioned in the expected data. example
Day 3
- Added various things to the table
- Dependencies column
- Show popup with info for cpanspec, patches and dependencies
- Added last date / commit to the data export.
Plan: With the added date / commit we can now daily check _ObsPrj for changes and only fetch the data for changed packages.
Day 4
A CLI for Harvester by mohamed.belgaied
Harvester does not officially come with a CLI tool, the user is supposed to interact with Harvester mostly through the UI. Though it is theoretically possible to use kubectl to interact with Harvester, the manipulation of Kubevirt YAML objects is absolutely not user friendly. Inspired by tools like multipass from Canonical to easily and rapidly create one of multiple VMs, I began the development of Harvester CLI. Currently, it works but Harvester CLI needs some love to be up-to-date with Harvester v1.0.2 and needs some bug fixes and improvements as well.
Project Description
Harvester CLI is a command line interface tool written in Go, designed to simplify interfacing with a Harvester cluster as a user. It is especially useful for testing purposes as you can easily and rapidly create VMs in Harvester by providing a simple command such as:
harvester vm create my-vm --count 5
to create 5 VMs named my-vm-01 to my-vm-05.
Harvester CLI is functional but needs a number of improvements: up-to-date functionality with Harvester v1.0.2 (some minor issues right now), modifying the default behaviour to create an opensuse VM instead of an ubuntu VM, solve some bugs, etc.
Github Repo for Harvester CLI: https://github.com/belgaied2/harvester-cli
Done in previous Hackweeks
- Create a Github actions pipeline to automatically integrate Harvester CLI to Homebrew repositories: DONE
- Automatically package Harvester CLI for OpenSUSE / Redhat RPMs or DEBs: DONE
Goal for this Hackweek
The goal for this Hackweek is to bring Harvester CLI up-to-speed with latest Harvester versions (v1.3.X and v1.4.X), and improve the code quality as well as implement some simple features and bug fixes.
Some nice additions might be: * Improve handling of namespaced objects * Add features, such as network management or Load Balancer creation ? * Add more unit tests and, why not, e2e tests * Improve CI * Improve the overall code quality * Test the program and create issues for it
Issue list is here: https://github.com/belgaied2/harvester-cli/issues
Resources
The project is written in Go, and using client-go the Kubernetes Go Client libraries to communicate with the Harvester API (which is Kubernetes in fact).
Welcome contributions are:
- Testing it and creating issues
- Documentation
- Go code improvement
What you might learn
Harvester CLI might be interesting to you if you want to learn more about:
- GitHub Actions
- Harvester as a SUSE Product
- Go programming language
- Kubernetes API
- Kubevirt API objects (Manipulating VMs and VM Configuration in Kubernetes using Kubevirt)