The first Kokoa and Friends meeting took place the 20th of December at the Computing and Electrical Department of ESPOL.
This meeting supported by the openSUSE community, gathered people from different levels of the Kokoa community and the ESPOL university. From students that are just getting interested in using FLOSS (a.k.a. newbies), students who are “candidates” to join the Kokoa community, the current “active” members and the experienced “senior” members.
In this event different topics were discussed covering FLOSS usage in the academia and the industry. Stories of success and guidelines were shared with people interested in going forward in the world of FLOSS.

Special thanks to Cristina Guerrero, Nervo Verdezoto, Marisol Villacrés, and from Jarflex, Adonis Figueroa and Jessica Zuñiga the speakers of this meeting and specially to Arturo Tumbaco, who helped me with the logistics to make this event possible.

Here some pictures about the meeting.

Hi,
Now I work for SLMS ( Suse Lifecycle Management Server ) project. It cooperate with SuSE studio and use its API. I get idea that more people could benefit from easy access to studio API from ruby so I extract functionality and improve behavior, documentation and testing and now there is new rubygem studio_api.
Why you should use this gem?

• ActiveResource Behavior
• Actively maintained ( and will be due to SLMS support )
• Tightly developed with guys from studio team
• Well documented with yard
• Good test coverage

I think then a lot of glory words is better to show example. It is example based on example from documentation.
Example goal is simple. Create new appliance in studio, add own cool rpm and build appliance with it. It can be useful to test your new version of software in stable environment and have automatic appliance in which you can test it.

  require 'rubygems'
  require 'studio_api'

  # Fill up Studio credentials (user name, API key, API URL)
  # See https://susestudio.com/user/show_api_key if you are using SUSE Studio online
  connection = StudioApi::Connection.new('user', 'pwd', 'https://susestudio.com/api/v1/user')
  # Setup the connection for all ActiveResource based class
  StudioApi::Util.configure_studio_connection connection

  # Find template with KDE4 for SLE11SP1
  templates = StudioApi::TemplateSet.find(:all).find {|s| s.name == "default" }.template
  template = templates.find { |t| t.name == "SLED 11 SP1, KDE 4 desktop" }
  # clone template to new appliance
  appliance = StudioApi::Appliance.clone template.appliance_id, :name => "New cool appliance", :arch => "i686"
  puts "Created appliance #{appliance.inspect}"

  #add own rpm built agains SLED11_SP1
  File.open("/home/jreidinger/rpms/cool_rpm-1.0-1.60.noarch.rpm","r") do |f|
    StudioApi::Rpm.upload f, "SLED11_SP1"
  end
  # and choose it in appliance ( and of course add repository with own rpms)
  appliance.add_user_repository
  appliance.add_package "cool_rpm", :version => "1.0-1.60"
  #check if appliance is OK, like dependency problems with new rpm
  if appliance.status.state != "ok"
    raise "appliance is not OK - #{appliance.status.issues.inspect}"
  end
  
  build = StudioApi::RunningBuild.new(:appliance_id => appliance.id, :image_type => "xen")
  build.save
  build.reload
  while build.state != "finished"
    puts "building (#{build.state}) - #{build.percent}%"
    sleep 5
    build.reload
  end

  final_build = StudioApi::Build.find build.id
  puts "Appliance to download: #{final_build.download_url}"

So I hope that you like interface how I design it. Of course I welcome any suggestion how to improve it. You can use comments here, novell bugzilla or issues on github.
How to install it:

• In opensuse: 1-click for 11.3 and 1-click for factory
• alternative possible everywhere is to use
  gem install studio_api

At the end few useful links if you are interested:
repository on github
yard documentation
gem at rubygems.org

Thanks for attention and I welcome any comments

Have you ever tried WebYaST ? No ? Then it is time for.

We have noticed that WebYaST is not really known in the OpenSuSE community. One reason for is that WebYaST is not really user friendly regarding the installation.

So we have investigate here some effort. Lets  see….

Installation

The simplest way is the one-click installation which is already installed on your OpenSuSE 11.3.

Just use a web browser (like firefox) with the url:

http://download.opensuse.org/repositories/YaST:/Web/openSUSE_11.3/webyast.ymp

The browser will ask you to start the installation via the one-click installation. Start the installation and go through the installation workflow.

Starting and managing WebYaST

WebYaST is a web application which runs on two http servers on your system. For starting and managing these servers Thomas Goettlicher has written a nice Qt-applet which can be started e.g. in KDE:

After starting the WebYaST applet the WebYaST icon appears on the right edge of the frame :

WebYaST is disabled

WebYaST enabled

With the right mouse click you can manage WebYaST:

With this applet you can start WebYaST in your browser too. After accepting the GPG-key please login with your “root” account.

And that’s WebYaST:

That’s all.

(Yes, I know that sentence is written almost in every post here. Even in posts where problems just starting after the sentence has been read. :-))

But I think that should be really all. If not, please use bugzilla and blame us !

Have fun !

(Yes, I know that’s the second sentence which should be in every blog :-))

I’m a supporter of mail encryption since I started using free software. At least, I sign all my own mails, with the exception of mails to people, who don’t know what an *.asc file is and might not open my mail for this reason.

By the way, my public gpg key fingerprint is:

F6A9 332D AA28 625E 59A8 F758 7BF6 0F4A 861B C3A3

I’m also involved in the CAcert project. If you want to get “assurced”, don’t hesitate to contact me, if you are in Berlin.

There is just one problem. If you want to sign all your mails, you have to type your hopefully long passphrase at least once[^1] for every single mail. If you get some encrypted mails from your friends, you have to type your passphrase for viewing mails, too. That’s not so nice. So were the gpg-agent invented, which task is to cache your passphrase for a given time, but it didn’t work for me - until today.

I followed the tutorial from the opensuse SDB with no success. Please note, that you might need to change the pinetry-qt to pinetry-qt4.

The solution, which works for me, was to copy the mentioned line to ~/.zprofile instead of .xinitrc, as I am using the awesome zsh.