YaST/Events/Workshop Nuremberg 2008

From openSUSE

YaST Hackshop Nürnberg (June 30 - July 4, 2008)

original photo

Motto & Goal

Taking YaST to the future.

The main goal is to move YaST further, both in terms of functionality, but also higher flexibility and more openness. We want to give developers a chance to work on something new, something we often neglected for some time, something cool and have fun with that.

The list of topics and projects ideas is available in the YaST Research homepage.

You can also get ideas for new projects by reading (or contributing to) the lists of things we don't like.

Schedule

• Monday: 11:30 Arrival of Prague participants, 12:00 Opening&Lunch
• Tuesday: 12:00 Lunch, 13:00 5+5 minutes each team
• Wednesday: 12:00 Lunch, 13:00 5+5 minutes each team, 15:00 Outdoor event, 18:00 Dinner
• Thursday: 12:00 Lunch, 13:00 5+5 minutes each team
• Friday: 12:00 Lunch, 13:00 Wrapup, 15:00 Departure (to Prague)

How to participate

Making YaST more relevant can be done through various ways

• Integrate YaST with existing technology/projects
• Make YaST widespread i.e by porting to other distros

Projects eligible to be tackled during this year's 'YaST hack week' must fulfill the required information described in the research project template

Important conventions

Once projects are admitted, be aware that

• Each project should have at least 2 people working on it
• Each project should have a maximum of 6 people working on it
• Participants must prepare themselves by learning and experimenting in advance. If you fail to do this for a project you're enlisted, you can be relocated to another project
• Documentation is more important than result. Documented failure is acceptable, undocumented success is not

Hackshop Project List

Installation in IPv6 Environment

Allow installation in an IPv6 setup. Requires changing linuxrc and YaST network setup code (to get the IPv6 config from linuxrc).

YaST as a Service

Define a service-oriented architecture for YaST, ideally REST based, and refactor modules toward this architecture. This affects a couple of other research areas, namely

• Make YaST Independent of YCP
• Using CIM from YaST modules (not required)
• YaST DBus Service
• YaST PackageKit Service
• YaST Web User Interface (side effect possibility)

YaST Interface for Webpin

Enhance YaST Repositories / Add-Ons module(s) with possibility to search through all known openSUSE repositories and packages via the famous tool Webpin. Make the dreams about searching and finding come true! Users want to install~and~use software, not to add random repository, search for software in it, install, add another...

YaST module using mod_ui directly

The goal is to prove that the mod_ui is ready to be used directly for a YaST module. As the registration logic will move to libzypp and the registration module needs a rework anyhow, this module is excellent cadidate for this task.

YaST PolicyKit integration

Allow YaST tasks to be performed on a fine grained access policy configurable by the system administrator.

YaST Web User Interface

Being able to http to your virtual appliance and set it up as you do it with your DSL router, with the YaST recognized "it just works" experience.

YaST Style Guide

It's mandatory for all software projects maintained and created by several developers to have a simple, understandable, and easy-to-remember style guide. It helps users to learn the basic rules and understand all other dialogs later.

The list of all YaST reseach project is at the YaST/Research page.