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.

Final result

After some meetings in oSC'16 and in the Prague office, we reached a quite extensive agreement. We are polishing the minutes and will publish a final document in the following days.

Looking for hackers with the skills:

yast ruby

This project is part of:

Hack Week 14

Activity

  • over 5 years ago: locilka liked this project.
  • over 5 years ago: mvidner liked this project.
  • over 5 years ago: IGonzalezSosa joined this project.
  • over 5 years ago: IGonzalezSosa liked this project.
  • over 5 years ago: ancorgs started this project.
  • over 5 years ago: ancorgs added keyword "yast" to this project.
  • over 5 years ago: ancorgs added keyword "ruby" to this project.
  • over 5 years ago: ancorgs originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    Sharing logic between desktop and web based applications through WASM by IGonzalezSosa

    Project Description

    A few months ago, the...


    openSUSE on ZoL from OpenZFS project by jkohoutek

    __Idea is to have SUSE system with OpenZFS as r...


    Requirements Management Tool on Graph Database by mknop

    Project Description

    Create a requirements...


    Dawnscanner: revive the project and create an RPM package by pperego

    [comment]: # (Please use the project descriptio...