On 11/04/2013 11:09 AM, Josef Reidinger wrote:

On Mon, 04 Nov 2013 09:45:04 +0100 Ancor Gonzalez Sosa wrote:

...

As some of you may be aware of, openSUSE Team members were not able to take part in the last Hackweek because we were working in the 13.1 release. It has been decided that we will have our own Hackweek the last week of November. I would really like to do something related to YaST, so this is a call for ideas for my YaST related Hackweek project.

I have more than 10 years of experience with Ruby. I started using it for developing management applications with QtRuby3. At some point I started using Rails and since then I have become more and more a web developer. YaST looks like the perfect choice for my Hackweek: I can do what I do best (coding Ruby) staying away from Rails, CSS, etc.

So, is there something that needs to be done, that fits in one week and that requires some Ruby knowledge and not so much knowledge about YaST internals/legacy?

Cheers

Hi ancor, we are really glad that you want to hack on YaST. From your requirements it is not so easy to decide exact part as whole yast codebase is automatic transpiled, so it contain some tricky parts to not loose any functionality. Few ideas I have in mind where your experiences would really help:

- write really nice example rspec test suite on real module. Members of YaST team already try it, but noone have so big ruby experience and it would be nice to compare it.

Just to keep the expectations in the right level. When I said "I have more than 10 years of experience with Ruby" sounds like coding in Ruby code have been my main activity during 10 years, which is not true. It was back then, 10 years ago. But then I gradually started to spend more time in other tasks. During the last four years, I have only devoted 20% (or less) of my time to real coding. So most likely, your knowledge is way more up to date than mine.

[...]

-- Ancor González Sosa openSUSE Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Fri, Nov 08, 2013 at 04:17:17AM -0700, Suresh K Hosamani wrote:

Hi,

I have a small piece of code, if I run it in ncurses mode, it frame contents are displayed in a box, but if I run the same code in gtk it doesnt display it in box.

I once reported the missing frame as a bug (https://bugzilla.novell.com/show_bug.cgi?id=791897) but was told that it's on purpose (https://github.com/libyui/libyui-gtk/blob/master/src/YGFrame.cc#L11). Regards, Arvin -- Arvin Schnell, Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

Hi Suresh, On Tuesday 12 November 2013 02:56:30 Suresh K Hosamani wrote:

Ok, in my requirement, it looks good if we have the information in a box. (Its an important notice to the admin).

Just an idea: If its just about to highlight the content, you could use a "RichText" field and use html markup in the text. You can create headlines, text decorations, lists, aso... Here is an example: http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-13.1-DVD-i586... And this is the code that creates this Window: https://github.com/yast/yast-installation/blob/Code-11-SP3/src/include/misc.... Ciao, Daniel -- J. Daniel Schmidt SUSE LINUX Products GmbH Research & Development Maxfeldstr. 5 HRB 16746 (AG Nürnberg) D-90409 Nürnberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Tue, 12 Nov 2013 19:03:38 +0100 Ancor Gonzalez Sosa wrote:

On 11/04/2013 11:09 AM, Josef Reidinger wrote:

...

On Mon, 04 Nov 2013 09:45:04 +0100 Ancor Gonzalez Sosa wrote:

...

As some of you may be aware of, openSUSE Team members were not able to take part in the last Hackweek because we were working in the 13.1 release. It has been decided that we will have our own Hackweek the last week of November. I would really like to do something related to YaST, so this is a call for ideas for my YaST related Hackweek project.

I have more than 10 years of experience with Ruby. I started using it for developing management applications with QtRuby3. At some point I started using Rails and since then I have become more and more a web developer. YaST looks like the perfect choice for my Hackweek: I can do what I do best (coding Ruby) staying away from Rails, CSS, etc.

So, is there something that needs to be done, that fits in one week and that requires some Ruby knowledge and not so much knowledge about YaST internals/legacy?

Cheers

Hi ancor, we are really glad that you want to hack on YaST. From your requirements it is not so easy to decide exact part as whole yast codebase is automatic transpiled, so it contain some tricky parts to not loose any functionality. Few ideas I have in mind where your experiences would really help:

- write really nice example rspec test suite on real module. Members of YaST team already try it, but noone have so big ruby experience and it would be nice to compare it.

- Look at libyui and its attempts for ruby bindings [1,2] and move it forward, because current way where it goes to Yast terms and then to libyui is not much nice. Or you can propose any other reasonable API for creating UI for all supported GUI/TUI ( gtk, qt, ncurses ).

- Improve access system. Currently we use SCR[3] with its agents which seems little outdated when you compare it with other solutions. You can improve current one or propose new API which make sense and we can implement various backends for it ( current agents for some tasks, augeas for others, etc. )

All those ideas about improving bindings, testing are APIs looks perfect for a second stage, once I have become familiar with YaST development. I'm really willing to help in those areas, but first I need a more "introductory" Hackweek project. Proposing the right approach without having experience with the problem sounds too ambitious to me.

OK, then I propose to just try module you are interested in and try to improve it. There is always a lot of stuff that can be improved.

...

- Take simple module and make it nice module that looks like real ruby that is intuitive for ruby programmer. I recommend to choose module that is not so hard or where you know how to setup given component, so you understand what happen here.

I have a reasonable knowledge and some interest in sound systems, Samba, Linux containers and databases. Is any of those areas looking for some more love?

All yast modules looking for some more love, so feel free to try any of them and improve it. Often simple run of module and try to configure something show some weak points which you can improve. Few info I get from office to your interested modules: yast-sound - in fact it is not much used today as common sound card is configured automatic yast-samba* - ask samba team if they need improvement or try to use it. I heard e.g. from thorsten that it sometimes doesn't work, so you can try to improve it. yast-lxc - its maintainer doesn't know about any missing feature, but feel free to try to use it and improve it for databases we drop our last database module yast-mysql-server as noone is interested in it. So if you want maintain it and think it make sense, feel free to revert last commit and become maintainer of it. And of course this module need a lot of love.

...

- Alternative is that you can choose part of configuration that is not yet covered by yast and write new module that looks like real ruby and report any obstacle you have ( we try to improve documentation, make some shortcuts or facades, but there is still lot of work ).

- As I write above you cna also improve documentation, try to fix the most annoying bugs, etc. but it usually require some problem specific knowledge

If you choose any idea or have your own, do not hesitate to contact us here or on IRC freenode#yast. It would be also nice if you can write at the end report what obstacles you see as contributor, so we can try to remove it.

Yes, of course. That would be one of the main goals, in fact.

Great, I am looking forward for your feedback. I already know some weak points, but you can show what new comers see as the most paintful. Josef

Cheers.

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Tue, Nov 12, 2013 at 07:03:38PM +0100, Ancor Gonzalez Sosa wrote:

On 11/04/2013 11:09 AM, Josef Reidinger wrote:

...

- Take simple module and make it nice module that looks like real ruby that is intuitive for ruby programmer. I recommend to choose module that is not so hard or where you know how to setup given component, so you understand what happen here.

I have a reasonable knowledge and some interest in sound systems, Samba, Linux containers and databases. Is any of those areas looking for some more love?

Hi Ancor! Containers (yast2-lxc) sound interesting to me. When I run yast2 lxc in a kvm VM on 13.1, I see some things that could be improved: - bridge creation: if there is no bridge, you have to click through the network module to create it. That should be done by a single click. - while the container is being created (by lxc-create), there is no progress indicator. Perhaps we could continually show the console output of that command. But I am a beginner with containers. Maybe you can see something else there. -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

On 11/05/2013 06:32 AM, Rajko wrote:

On Mon, 04 Nov 2013 09:45:04 +0100 Ancor Gonzalez Sosa wrote:

...

...

So, is there something that needs to be done, that fits in one week and that requires some Ruby knowledge and not so much knowledge about YaST internals/legacy?

Just stumbled on a fact that YaST Software Management has no graphic setup (preferences) available from running module. Almost any other GUI application has one.

For instance when one wants to make module to show "summary" of package installation by default instead to "close", one has to edit /etc/sysconfig/yast2 .

Rajko refers to this thread: http://lists.opensuse.org/opensuse-factory/2013-11/msg00130.html Qt-frontent for the openSUSE software management is here: https://github.com/libyui/libyui-qt-pkg On the other hand, it's not Ruby. Bye Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Tue, 5 Nov 2013 15:15:30 +0100 Martin Vidner wrote:

...

started using Rails and since then I have become more and more a web developer. YaST looks like the perfect choice for my Hackweek: I can do what I do best (coding Ruby) staying away from Rails, CSS, etc.

So, is there something that needs to be done, that fits in one week and that requires some Ruby knowledge and not so much knowledge about YaST internals/legacy?

YaST covers quite a broad area. Maybe first get an idea what specifically interests you and we can find something in there. You can start by browsing the control center on the desktop, or the code at https://github.com/yast/

Package management? Network services? User interface?

Hmm, perhaps the top-voted feature https://features.opensuse.org/120340 "decouple download and installation" could be done mostly in Ruby?

I think it cannot be done purely in ruby, as you need support in libzypp to download and install in parallel. Josef