continue / push osc2
a project by mstrigl
Updated over 6 years ago. 5 hacker ♥️.

While osc is growing and getting more and more complex and hard to maintain, there is an object oriented rewrite of osc which key points are:

  • separate library and cli code
  • better user interface
  • easier implementation of new commands
  • tests, tests, tests (test driven development)
  • pep8 conform

The rewrite was started by Marcus Hüwe and since 2015 it's very silent around this tool.

At the end of the hackweek I want to have:

  • evaluated the as-is state
  • evaluated what is missing
  • of course new features
  • devel project in openSUSE:Tools

The source code is on github and can be found here

Description from the github project: >osc2 is an object-oriented rewrite of the Open Build Service command line tool osc. > >Its aim is to improve the code structure and to provide a consistent commandline interface.

A few more information on this project can be found on the blog of Marcus Hüwe

Join this project

Looking for hackers with the skills:

python openbuildservice

This project is part of:

Hack Week 15

Activity

  • over 8 years ago: TBro liked this project.
  • almost 9 years ago: osukup liked this project.
  • almost 9 years ago: Marcus_H joined this project.
  • almost 9 years ago: thomas-schraitle liked this project.
  • almost 9 years ago: sleep_walker liked this project.
  • almost 9 years ago: pluskalm liked this project.
  • almost 9 years ago: mstrigl added keyword "openbuildservice" to this project.
  • almost 9 years ago: mstrigl added keyword "python" to this project.
  • almost 9 years ago: mstrigl started this project.
  • almost 9 years ago: mstrigl originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/