[Yast] Provide useful understandable error messages for Storagean idea by locilka It has probably already happened to you: Creating volume /dev/sda2 failed with error -1008 Did it tell anything useful to you? Maybe if Storage gave you some more info, you could have continued, fix the problem by yourself. |
Make ruby-ui usable for YaSTan idea by dmacvicar ruby-ui was a hackweek project with jreidinger to make libyui (YaST text/graphical engine) usable from pure-ruby without going through YCP. We experimented a bit extreme trying to make the usage of SLIM templates possible. It kind of worked. |
Travis CI support for Yastan invention by lslezak DescriptionTravis provides nice integration with GitHub, it can automatically run tests for every commit or every pull request. |
rewrite YaST2 AppArmoran idea by cboltz The YaST2 AppArmor module is still based on the Immunix::* perl modules that are deprecated upstream and therefore causes some maintenance "fun". Upstream AppArmor utils were rewritten in python. The idea is to rewrite the YaST2 AppArmor module to use the python modules or JSON interfaces. |
yast2-fontsan invention by pgajdos
|
Use Jenkins as a Travis replacement for YaST (or possibly any other GitHub project)an invention by lslezak Use Jenkins as a Travis replacement for YaSTIntroduction |
YaST2 code reorganizationa project by ancorgs YaST code organization is a mess at many levels (files location, namespaces, code dependencies...). Recently we created this gist to put some of the issues on the table Many YaST developers will be at openSUSE Conference, that overlaps with Hackweek. The plan is to lock them all in a room with a blackboard and reach agreements on how the code should be organized in the future. Then use Hackweek to iron the details, document everything in some kind of style guide and, if time permits, even do some experiments about how to adapt the existing code to the new conventions. |
YaST Dialog Editor (UI "Designer")a project by lslezak Unfortunately there is no UI designer or editor for YaST dialogs. All dialogs are hand crafted in Ruby code. The idea of this project is to provide some way how to create or edit the existing dialogs in a user friendly way, without touching any code. |
Edit Widget Properties in YDialogSpya record by shundhammer SummaryThe YaST UI has introspection on the widget level: In any YaST dialog, hit Ctrl-Shift-Alt-Y (Qt UI) to open the YDialogSpy. Use the widget tree that pops up to highlight the corresponding widget in the dialog. Hit the "Properties" button to see the widget's properties (current value, layout stretch factors, layout weights, ...). |
Integrate AutoYaST with software configuration management systemsan invention by IGonzalezSosa FATE#319830, FATE#319843 and FATE#319842 propose integration of AutoYaST with different software configuration management systems like Salt, Chef and Puppet. |
Use linear programming for the partitioning proposalan idea by ancorgs The YaST team is rewriting yast2-storage. That includes new shiny code for the storage proposal during installation. It calculates what partitions and/or volumes need to be created to allocate the system and finds the best way to create those partitions in the existing free spaces. The second part becomes more complicated than it looks as soon as you start considering the restrictions imposed by each volumes and by the technology (primary vs logical partitions, for example). Right now, the problem is solved by brute force. All the possible distributions of partitions and LVM physical volumes are considered and the best one (according to several simple criteria) is chosen. |
yast2-storage-ng as a libstorage-ng wrapper. POCa project by ancorgs The goal of this project is to write a proof of concept of a new philosophy for yast2-storage-ng. Instead of just extending the API offered by libstorage-ng, the idea is wrap libstorage-ng so the Ruby code using yast2-storage-ng does not have direct visibility (unless explicitly desired) on the libstorage-ng classes and methods. If you don't know what all that means, keep reading. |
Get rid of perl-apparmora project by goldwynr Perl-apparmor is obsolete in the apparmor community. No one is maintaining it. However, opensuse has to keep it to interact with yast, which is the main consumer of perl-apparmor. Getting rid of perl-apparmor would mean: + Creating a new interface (JSON) to interact with outside world (IOW, yast) |
YaST Integration Tests Using Cucumbera project by lslezak Currently we use openQA for the the YaST integration tests. It runs YaST in a VM and controls it via emulating keyboard input. The result is checked by comparing the screenshots. This approach has several disadvantages: |
YaST module for (SUSE Manager) salt parametrizable formulasa project by dmacvicar Parametrizable formulas is a normal salt module plus some metadata in order to interactively parametrize them. The metadata is used to automatically generate forms that are then injected as pillar data. See original Hackweek project, SUSE Manager support for formulas blog article and its (internal for now) docs. |
openQA-butler - Application that offers a GUI for installing and configuring openQA and openQA workers.an invention by SLindoMansilla Docker & YastGoals |
Controlling and Testing the YaST UI Remotely (for Integration Tests, openQA)a project by lslezak Hackweek 18 UpdateWhat Has Been Done During HackWeek 18 |
Implement QEMU Firmware Config device support in Linuxrc/AutoYaSTa project by dmacvicar While normally data is passed to linuxrc (including an AutoYaST profile), modern auto-install tools like Ignition from CoreOS support a very interesting method: the QEMU Firmware Config device.
This allows to read from inside the VM a blob by reading |
Better support for Chromebooksan idea by suntorytimed Better support for Chromebooks Chromebooks do have very limited hardware in terms of storage and RAM. But it is still the cheapest solution to a truly open source notebook, as it allows to replace its coreboot based bootloader with your own coreboot and payload (f.e. Tiano Core or Seabios). |
Make Yast CA Mgm-Ng out of Yast RMT modulean idea by ikapelyukhin :warning: Bold and crazy ideas down below, read only if you dare :warning:
Yast CA management module isn't on SLE15 yet, so now in Yast RMT module (package name |
Graphical view of the changes to be made to disks during installationa project by ancorgs Right now, during the (open)SUSE installation process, the changes to be performed on the storage devices are presented as a list of actions such as: * Resize ntfs partition /dev/sda1 by 100 GiB |
openSUSE on ZoL from OpenZFS projecta project by jkohoutek Idea is to have SUSE system with OpenZFS as root FS. Why ZFS |
Learn Crystal by porting part of YaST to that languagean invention by ancorgs For a very long time, I have been planning to play with Crystal as possible substitute/complement for Ruby. With that goal, I have isolated a very small subset of the Ruby project I know the best (yast-storage-ng) and I want to migrate that subset to Crystal to get a general feeling about the language. See the repository with the experiment already in progress. There is no evil plan to migrate YaST to Crystal. This is just done in the Hack Week spirit of "what if". But if more people join maybe we could get this to an state in which some benchmarks can be executed to check what's the real gain in speed and memory consumption using Crystal instead of Ruby (note: speed and memory are not the only goals of the migration). |
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. |
Analyser for YaST logsa project by jreidinger Well, we often stuck in YaST team with knowledge what users really use and how much. But we have yast logs in many bug reports. And from those logs we can see which modules users use the most. So goal of this project is to write script that analyze given tarballs with logs and print result about usage of yast clients. |