Hi, prompted by Miska, Pavol, and Stano, I've been thinking how YaST can take part in GSoC, under the openSUSE umbrella. This is not finished, but I am being distracted by bugs so here is what I have so far for inspiration and discussion. Google starts accepting organization applications on Monday. For http://en.opensuse.org/openSUSE:GSOC_2011_Ideas == YaST === Template: Idea Name Abstract '''Required knowledge:''' '''Skill level:''' '''Mentor:''' [[User:foo|Foo Bar]] '''Student:''' STUDENT NEEDED === Use Augeas in YaST back-end [http://augeas.net/ Augeas] is a library to parse and write configuration files, using a generic mechanism driven by grammars ("lenses"). YaST has been using "agents" for this task, some of them also configurable, though in a more limited way. ==== Ambitious goal: replace all parser agents by Augeas lenses. ==== Medium goal: replace the major agents by Augeas The major agents include ag_ini and ag_any. ==== Small goal: replace a couple of agents by Augeas Choose some agents for the pilot. The majority of the project would be infrastructure: binding Augeas to the YaST library so that it can be easily used from the YCP language. '''Required knowledge:''' C++ for binding A to Y (? maybe unnecessary, could go via py/rb/pl); learn a little YCP '''Skill level:''' '''Mentor:''' [[User:Mvidner|Martin Vidner]] (feel free to replace me) '''Student:''' STUDENT NEEDED === Separate libyui yast2-libyui is still coupled to YaST too much. Make it a truly standalone project. === Do the whole Amaranth (But we want to work on that too at the same time. What part is well separated?) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu