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 mad skills in:

yast ruby

This project is part of:

Hack Week 14

Activity

  • over 3 years ago: locilka liked YaST2 code reorganization
  • over 3 years ago: mvidner liked YaST2 code reorganization
  • over 3 years ago: IGonzalezSosa joined YaST2 code reorganization
  • over 3 years ago: IGonzalezSosa liked YaST2 code reorganization
  • over 3 years ago: ancorgs started YaST2 code reorganization
  • Show History

    Comments

    Be the first to comment!

    Similar Projects

    Ruby Gem: Open Build Service API by mschnitzer

    I just recently started a new project which is ...


    geekos going production by digitaltomm

    We are running the geekos app at [geekos.prv.su...


    Differentiate Microsoft virtualization types (WSL1/WSL2/Azure/Hyper-V) in SUSEConnect by wstephenson

    People are interested in Linux on Windows via W...