| Status | Name | Summary | Skill level | Required knowledge
|
| Automatic generation of YCP bindings
| Make it easy for YaST module developers to access upstream system libraries.
| n.a.
| n.a.
|
|
| Better Integration into Windows Domain
| Allow clients in a Windows domain to automatically mount the home directory and run scripts during login.
| n.a.
| n.a.
|
|
| Rewrite Storage Proposal
| Rewrite the storage proposal.
| n.a.
| n.a.
|
|
| Build YaST using cmake
| This project aim to modernize YaST build system to make it easier for people to contribute and gain new developer features.
| n.a.
| n.a.
|
|
| Bootloader UI Rewrite
| Remove the current way user interface of the bootloader module is generated and use standard way, which allows to use the full flexibility of YaST UI library and not only a limited subset of its functionality.
| n.a.
| n.a.
|
|
| Currently Supported Hardware Tool
| To be able to use YaST to generate a list of supported hardware, by type or by type and vendor.
| n.a.
| n.a.
|
|
| CVS/SVN for System Config Files
| Revision control for the system's config files so sysadmins can keep track of changes, revert them or apply them to other systems as well. A simple version would keep all files below /etc in a CVS or SVN (or other versioning system) repository.
| n.a.
| n.a.
|
|
| Make YaST Independent of YCP
| Leverage the YaST toolkit and component system to popular languages and keep YCP as a component technology but not as a dependent language, but as an available one.
| n.a.
| n.a.
|
|
| Make YaST more IPv6 compatible
| Now YaST is not able to set up static IPv6 routes and not able to setup IPv6 tunnel. Student should make YaST network module able to setup static IPv6 configuration and create a new one IPv6 tunnel configuration module.
| n.a.
| n.a.
|
|
| Signals and Slots for Libzypp
| Add a generic signal / slot mechanism (very much like the Qt lib does) to libzypp to make it easier for application to receive a notification upon libzypp events (package is being installed, new package in the system). The old callbacks have serious limitations, and they require a lot of very special code in libzypp commit actions.
| n.a.
| n.a.
|
|
| Using CIM from YaST modules
| Easy access to CIM services from YaST components.
| n.a.
| n.a.
|
|
| YaST Libzypp module
| Configuration module for Libzypp
| n.a.
| n.a.
|
|
| YaST XML UI Dialogs
| Define dialogs in XML or similar formats.
| n.a.
| n.a.
|
|
| 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.
| n.a.
| n.a.
|
|
| YaST on other Distributions
| Leverage YaST to other distributions and communities.
| n.a.
| n.a.
|
|
| YaST PackageKit Service
| Remove PackageSystem.ycp dependency on libzypp and use PackageKit instead.
| n.a.
| n.a.
|
|
| YaST PolicyKit configuration module
| Define/change PolicyKit policies with a easy to use user interface.
| n.a.
| n.a.
|
|
| YaST Skeletons for Rapid Development of New Modules
| Enhanced skeletons to use as a base for YaST components.
| n.a.
| n.a.
|
|
| 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.
| n.a.
| n.a.
|
|
| YaST Webcam Module
| YaST module to set up webcam devices
| n.a.
| n.a.
|
|
| YaST debconf Module
| When packages are being installed, debconf asks the user questions which determine the contents of the system-wide configuration files associated with that package.
| n.a.
| n.a.
|
|
| Make YaST Documentation Better
| We've seen a lot of reports how the current YaST documentation sucks, how it is not well-maintained and how it could be enhanced, but a glamorous documentation is still only a dream. You can be the hero that will make the dream come true! Let the world remember you as the one who has resurrected the YaST documentation from the ashes!
| n.a.
| n.a.
|
| YaST as a Service
| Define a service-oriented architecture for YaST, ideally REST based, and refactor modules toward this architecture.
| n.a.
| n.a.
|
|
| YaST DBus Service
| Allow easy access to DBus services from YaST.
| n.a.
| n.a.
|
|
| YaST PolicyKit integration
| Allow YaST tasks to be performed on a fine grained access policy configurable by the system administrator.
| n.a.
| n.a.
|
|
| 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.
| n.a.
| n.a.
|
|
| 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).
| n.a.
| n.a.
|
|
| (K)Desktop Integration for plug'n'play Hardware
| Offer (k)desktop user to automatically start YaST if plug'n'play hardware has been attached
| n.a.
| n.a.
|
|
| 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...
| n.a.
| n.a.
|
| AutoYaST documentation
| The docs about profile is maintained by Uwe and thus is constantly obsolete.
The worst offender seems to be X11. IMO we should push the documentation to the module maintainers and provide
infrastructure for that. Uwe cannot scale.
| n.a.
| n.a.
|
|
| Everything must be available in autoyast
| All functionality needs to be configurable via autoyast, but for us autoyast
is commonly just the 2nd thought.
| n.a.
| n.a.
|
|
| Heartbeat module enhancements
| The module is very rudimentary and it is a question for PM how they want to
position it. But it's clear customers need autoyast support for heartbeat
configuration.
| n.a.
| n.a.
|
|
| How to integrate customer-own changes
| The example was progress dialog, but a generic framework might be of interest
here.
| n.a.
| n.a.
|
|
| LDAP server
| The module is SMB-only, e.g. does not support departments.
| n.a.
| n.a.
|
|
| storage API brainstorm
| (proposal code, map abuse, proposal UI, nil returns)
| n.a.
| n.a.
|
|
| builtin cleanup
| Can be moved to Research projects when there is a list of what to remove and what to add.
| n.a.
| n.a.
|
|
| module loading error message improvement
| Can be moved to Research projects as soon as there is minimal specification.
| n.a.
| n.a.
|
|
| scr parsing error on stderr (not y2log only)
| ?????
| n.a.
| n.a.
|
|
| deprecated functions
| Can be moved to Research projects when there is a list of what to remove and what to add.
| n.a.
| n.a.
|
|
| Move YaST to git
| Can be moved to Research projects as soon as there is minimal specification on how to tackle the problems of such a migration. ZYpp migration done.
| n.a.
| n.a.
|
|
| package bindings testsuite
| Can be moved to Research projects as soon as there is minimal specification.
| n.a.
| n.a.
|
|
| package bindings api cleanup
| Can be moved to Research projects when there is a list of what to remove and what to add.
| n.a.
| n.a.
|
|
| package bindings use namespaces (AddRepository -> Repository::Add)
| Can be moved to Research projects when there is a list of what to change.
| n.a.
| n.a.
|
|
| DBus:: in ycp
| Can be moved to Research projects as soon as there is minimal specification.
| n.a.
| n.a.
|
|
| Command line internal API, introspection, bash completion
| Can be moved to Research projects as soon as there is minimal specification.
| n.a.
| n.a.
|
|
| Integrate YaST into KDE 4 SystemSettings
| Integrate YaST modules into KDE 4 SystemSettings. Instead of having two separate applications to configure one's system, integrate the YaST modules into SystemSettings and also eliminate duplicated functionality.
Totally disagree with this note, openSUSE's tools (Yast modules) must be into KDE SystemSettings (as is already doing a known distro) because the things must be most standard as possible (as now with the packagekit project for install software) at the GNU/Linux world (where there are already many differences). If each distro develops its own Control Center, is a chaos; like install software was before packagekit.
| low or medium (?)
| C++, Qt, YaST2 (?)
|
|
| SAN to speed up the bottleneck disk
| Integrate YaST modules SAN SystemSettings
- Some smart algorithm allows to predict the disk read and write commands. Some part of the RAM get used to buffer the read and write requests. As options of each disk you can choose if you like to have on/off the read-buffer and extra the write buffer. In the settings you can choose the total amount of buffering (e.g. 12GB if you run 16 GB and need for the applications and operating system only 4GB). Or you can choose the buffer space dynamic via some percentage x%. As an alternitive you use 90% of the statistically unused RAM of the last week. The SAN-middleware software should be scaleable to use different kind of disks (USB, IDE, SATA and Fiberchannel.) and be able for hotpluging new disks.
| This will support ressource intencive applications which access a lot the disks, like databases, CAD, video and image manipulation, virtualisation and indexing - searching - organizing your diskspace
|
| high (?)
| C++, YAST (?)
|
|
| Videoconferencing
| Save Videoconferencing in a professional 64bit environment
- Some intelligent alogrithm use the peernetwork to distribute telephonecalls and videoconferences. Realtime intelligent allogrithm allow to adapt to the bandwith (priorities like audio first, etc.) and to deliver hight quality communication in full HD and Hifi Surround Audio. Echo get suppressed and the webcam can follow the participants (automatic zoom in & out) and the visualisation get adaped to the best image results with the actual light. It could handel 25 participants including a parallel chatroom, presentationmode and sketch via tablets digiboards.
|
| See also some state of the art webcams: [1]
|
| high (?)
| Realtime Applications, Voice over IP, C++, YAST (?)
|
|
| Minimalistic User Friendly Yast Interface/Plug&Play Background Facilities
| Produce a minimalistic interface for the *regular-non-technical* user. And also a backend which helps the user automatically when needed.
One of the long running problem with non-technical users is the perpeption that "Linux" is difficult and painful to configure and use. Part of the problem is where YaST offer too much, so the regular users are overwhelmed by the posibilities and the choices. Other problem is the way that regular users "think" when they want to use their computers.
So a minimalistic approach would look to make easier and pain free the most common task such as application install, peripheral install: printer/scanner/webcam , Folders sharing/Network printing and drivers installation for recently connected hardware.
More info: [2]
| n.a.
| n.a.
|
