Improve the supportconfig database toolan idea by leonardocf The tool, developed in previous HackWeeks, is mostly abandoned. The plan is to: |
|
|
SUSE Manager: Windows client supportan idea by pagarcia Let's see how much, if any, of the steps described here I can get done: https://confluence.suse.com/display/SUSEMANAGER/Windows |
Port Salt virt modules to idema project by cbosdonnat Salt is moving towards a plugable architecture using POP and Idem. This project is about experimenting with those new concepts by applying them to a real life case: the virt execution and state modules. The goals of this project are: |
Build admin-tools in a stand-alone environment without obs dependenciesan invention by dmulder The admin-tools appimage provides several samba team YaST packages in a portable way, such as yast2-aduc, yast2-gpmc, yast2-adsi, and yast2-dns-manager. Currently I build the appimage on obs, but this pulls in lots of unnecessary dependencies. Making it build independently would allow building on other distros. The difficult part here is going to be building minimal YaST dependencies. |
Fix terracumber, add some python unit tests, try to extend it and publish itan invention by juliogonzalezgil Last year I developed Terracumber and, for the moment published it at one internal GitLab repository. We intended to replace the set of scripts we have to launch sumaform for the Uyuni and SUSE Manager CI, but lacked adding the monitoring part. |
Modernize Mash deploymenta project by seanmarlow Mash is a Python based CI/CD pipeline for automated testing and publishing of public cloud images. Currently the production and development deployment for the package is inconsistent, slow and manual. This is a barrier to rapid development, deployment and testing. It also means the development workflow is different than production. This can lead to production issues which were not seen during development. In order to modernize the Mash workflow I plan to spend the week digging into a plethora of tools to first learn then build out a new workflow. The goal is to simplify deployment by choosing tools that provide consistency, modularity and repeatability. By leveraging the best tools available we can harden the code and accelerate the release cycle. |
Home assistant that doesn't spy on you - developer's editiona project by DKarakasilis There are various home assistant solutions out there but all of them transfer your voice to some server for processing. This is a no-go for sane people although the technology is interesting and could be useful. There are various open source tools out there to achieve the same result but there is no turn key open source self hosted solution. The goal of this project is to implement a way to have a home assistant running locally - ideally with one command. The project that is closer to the desired result is Mycroft (https://mycroft.ai/). It is very easy to run the client side components using one docker command but their backend is running remotely. All the tools they use though are open source so it only needs one to do the work and package them in a nice little docker-compose file (https://mycroft-ai.gitbook.io/docs/about-mycroft-ai/faq#can-mycroft-run-completely-offline-can-i-self-host-everything). |
libsolv web interfacean invention by lnussel In order to inspect rpm dependencies inside the distro I wrote some python command line tools that leverage libsolv. Since navigating the ball of wool that is the result of solving a package is on the command line, I'd like to create a web app. Implementation by means of Flask, bootstrap and jquery to keep it simple. UI should be entirely created on client side with Flask only server json endpoints. |