Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.



Friday
27 February, 2015


face

Qactus, a Qt-based OBS notifier, is out in the wild. Version 0.4.0 is the first release.
I started it a long time ago together with Sivan Greenberg as a personal project for learning Qt. And now it’s back into life :)

It features
– Build status viewer
– Row editor with autocompleter for project, package, repository and arch
– Submit requests viewer
– Bugs

This application is possible thanks to Marcus ‘darix’ Rueckert. He has helped me getting further knowledge of the OBS API.

I think this version is usable. So, why don’t you give it a try?
The source code is hosted on GitHub.

qactus_040_1 qactus_040_3 qactus_040_2


face

¿Quieres echar un vistazo al sitio donde trabajan desarrolladores de Linux? Pues ellos mismos nos los muestran

kernel_workstations

Desde la web de Linux.com siguen con sus esporádicas visitas a los sitios de trabajo de diferentes desarrolladores del kernel Linux.

Después de poder ver el sitio de trabajo de varios desarrolladores del kernel Linux, entre ellos el gran jefe Linus Torvalds hoy toca otra entrega más. Los anteriores han sido:

En esta ocasión Tejun Heo que trabaja en Red Hat es quien nos mostrará su soleada oficina

Gracias a Libby Clark por la entrevista y a la web Linux.com por permitir la traducción y difusión! Puedes ver el artículo original en este enlace:

Tejun Heo desarrollador e ingeniero principal en Red Hat y en este vídeo nos muestra cómo es su lugar de trabajo donde desarrolla los sitemas para los que está trabajando.

¿En qué área del kernel estás trabajando ahora?

Trabajo en varias áreas del kernel. Mantengo LIB ATA, cgroups, workqueue y el getionador de memoria per-CPU. Pero últimamente he estado trabajando sobre todo en cgroups y ahora mismo trabajando en algo entre mem cg y block cg.

¿Qué es lo que más te gusta de tu lugar de trabajo?

Lo que más me gusta de mi sitio de trabajo es que es realmente abierto y muy luminoso. Cuando me aburro del trabajo simplemente miro fuera (por la ventana) y no es para nada nada cerrado. Y además es bastante simple. Así que no lleva mucho el mantenerlo. Sólo hay un escritorio una máquina de pruebas y eso es todo.

¿Qué es lo que menos te gusta?

Me gusta todo. La única pega que encuentro es estar en frente de una gran ventana. En los días soleados entra mucho brillo y mi monitor no puede con ese brillo.

¿Cual es el peor sitio de trabajo que has usado?

El peor sitio que he tenido fue en mi primer trabajo. La oficina estaba justo debajo de una sauna pública con una gran piscina. Cuando vaciaban la piscina el agua desbordaba de alguna manera por el sistema de tuberías y el agua goteaba hasta nuestra oficina.

¿Hay algún objeto en particular en tu sitio de trabajo que debiéramos conocer?

Mi sitio es bastante simple. Sólo el escritorio y el portátil. Pero tengo esta máquina de test, una AMD Opteron que compré por eBay. Es bastante lenta, pero es útil porque es una máquina NUMA y las características de NUMA son excelentes comparadas con máquinas más modernas.

Así que es útil para realizar pruebas. He pegado algunas cosas de conferencias en ella, así que ahora tiene mejor pinta.

—————————————————————-

 



face
Lobby of the venue
Back home. Tired and jetlaggy, but satisfied: SCALE rocked!

SCALE loves ownCloud

The 13th South California Linux Expo was awesome! It is the biggest LinuxFest in the USA. While decidedly different in nature from Europe's biggest Linux event that that took place just three weeks prior (FOSDEM), we met similarly enthusiastic existing and future users. Conversations were also similar: about half the visitors already knew ownCloud, often using it or planning on deploying it; and the other half was more than a little delighted to hear about it, often exclaiming they had been looking for 'something like that' for a while. Negativity was extremely rare: I don't recall a single negative comment at SCALE (merely a few people who liked ownCloud but had no use for it personally), FOSDEM had one conversation starting unpleasantly but quickly turning around - even though one feature of ownCloud wasn't up to snuff, the user was happy with the experience as a whole.
Before the action started!

For most users, ownCloud was simply a wonderful product and they used it at home, deployed it for customers or managed it in their company. Some asked what features were coming or just arrived in ownCloud 8, or asked about the state of specific features and in more than one occasion they very enthusiastically told me how excited they were about ownCloud, how they loved it and how they were telling everybody to use it!

ownCloud to-go

Those who didn't know ownCloud were almost invariably surprised and excited. I can't count the times I heard "wow, why did I never hear about this before" and "dude, I've been looking for something like this for ever!". Often, people wondered how long ownCloud had been around (we just turned five), if it was open source (yes, with love), how many people contributed to it (719 and counting) and how many users it has (we guestimate over 2 million, with 500,000 in this single deployment alone). Oh, and, does it scale? The deployment linked above and a mention of users like CERN can put most concerns to rest. Yes, ownCloud scales from Raspberry Pi to Atom Smashing size.

What came up a few times as barriers to their future usage of ownCloud was pretty much what I discussed before. Running a server at home is not easy and I walked by the EFF booth to ask about progress on Let's Encrypt to ask about the progress of solving one aspect of that problem: more easily getting SSL certificates. I was told the project is on track for the 2nd half of this year.
Frank and Bryan Lunduke

It is wonderful to have such energizing, positive, enthusiastic users - and to have such an enthusiastic booth crew to talk to them as well. At the booth we had Frank, Matt, Ron, Camila and myself. Awesome it was and we had great fun! Below a timelapse video of Saturday morning. It was

face

Apparently I haven’t blogged in nearly 5 years, wow! Most of my coding for fun in the last few years ended up being on internal systems to my previous company. Well all that’s in the past now, I’m about to start an adventure of traveling for 6 months around Central/South America and South-east Asia.

But just before that, had a couple days downtime so thought I would learn a little javascript and D3. You can see the result on:

http://francis.giannaros.org/fb-graph/
(works in Chrome/Firefox, you have to click ‘Accept’ on the Facebook popup)

Basically it will give you a graph visualisation of who you are tagged with on Facebook, and how your friend tags relate — at least all the ones available from the Facebook graph UI.

You can use the date slider at the top to restrict the timeline — it’s interesting to see how people come and go in your life, at least as far as Facebook photos are concerned.

Looking forward to future fun coding, maybe more directly in an established free software project again!

Facebook Photo Tag Graph

 

 

 


face

There’s a new build published today for the AMD FGLRX drivers.

It include the new patch made by Sebastian Siebert supporting Kernel 3.19x series you could have on 13.1, 13.2 and Tumbleweed openSUSE distribution.

The server just got the new rpms, so you should be able to update with zypper ref -f && zypper up

Have fun.


face

Como tive dificuldade na instalação do Android com boot UEFI, fica aqui a dica de como instalar o Android 4.4.2 em computadores x86 com boot UEFI , o que faz muito sentido principalmente se o seu hardware carrega o recurso touchscreen. Primeiramente arrumei um pendrive de 8GB, após efetuei o boot do imagem adquirida na página oficial http://www.android-x86.org/ . Prossegui com a instalação normalmente, porém efetuei toda instalação no pendrive. Após terminar criei uma particição ext3 e copiei todo o conteúdo do pendrive (mountado em /mnt/android) com o sistema recém instalado para a nova partição como comando a seguir:

# rsync -vxaHD --delete /mnt/android-4.4-r2/ /android/

Agora basta incluir a entrada no grub2:

menuentry "Android KitKat 4.4.2 x86" --class android {
 set root=(hd0,gpt13)
 linuxefi /kernel root=/dev/sda13 androidboot.hardware=android_x86 SRC=/
 initrdefi /initrd.img
 }

E Pronto! AQUI também um vídeo demonstrativo…

android-x86-4.4.2-3

 



Thursday
26 February, 2015


face

4:51 AM: I'm woken up by the sound of a loud chirp.  I roll over and pretend I didn't hear it.

4:52 AM: No luck, it's a smoke detector chirping from low battery.  Why can't this happen in the middle of the day?

I lay in bed for a while pretending that I can fall back asleep and ignore the chirp, I start thinking about the four Nest Protect systems I purchased and installed and how much I wish I had replaced all of my smoke alarms.  The only reason I hadn't replaced all of them is they are $99 each and I wanted to give them a test run before I completely replace them.

4:55 AM: I'm out of bed standing in the hallway at a strange angle hoping that on the next chirp I can determine which room has the chirping smoke alarm.  It's one of three because the hallway and one bedroom both have Nest Protect units in them and "they don't chirp!"

4:56 AM: The chirp comes from in front of me so it has to be the other bedroom.  I open the bedroom door, hear my teenage son stir and wonder how he can sleep through the chirping.  I open the battery compartment, yank out the battery, test it on my tongue (it seems strong) and then hear another chirp coming from behind me.

4:57 AM: I have opened every smoke detector on the floor and removed the battery because I simply want to get back to bed.  I will deal with this in the morning.

Then I heard another chirp.

How is that possible?  I don't have any more of these "old school" smoke detectors that chirp.  Is there something else in my house that makes a sound like that?

I stand very still and wait for it.

chirp!

It's coming from the other bedroom.  The bedroom that has a Nest Protect in it.  I walk up to the door and crack it open trying not to wake my other son.  I look up at the Nest Protect unit on the ceiling and I'm stunned.  It chirps again.

Why am I stunned.  Let me quote from the Nest Protect website (italics added):

What is Nightly Promise?
Have you ever woken up in the middle of the night because your smoke alarm was chirping? Nest Protect has a better way: Nightly Promise. Each night when you turn out the lights you’ll get a quick green glow which means the batteries and sensors of Nest Protect are working. It also means no dreaded chirps at midnight so you can sleep safe and sound.
 I pull the unit down and disconnect the power and tell my son to go back to sleep.  I take it in my office and it chirps again.

Problem Reported in my Phone

I decide to look at my phone and see that the Nest app


face

This time of the year again. The monitoring was prodding us with "Your certificate will expire soon". When we fiddled with the tools to create the new CSR, we were wondering "Can we go 4K?". 4K is hip right now. 4K video. 4K TVs. So why not a 4K certificate? A quick check with the security team about the extra CPU load and checking our monitoring.

"Yes we can"

So with this refresh the certificate for all the SSL enabled services in Nuremberg is 4096 bits long. The setup is running with the new certificate for a few days already and so far we did not notice any problems. Next stop will be upgrading the SSL end points to a newer distribution so we get TLS 1.2 and our A grade back. Stay tuned for more news on this front.



face

Several scientific packages were added to main openSUSE repositories (Factory) in January 2015.

  • harminv (web page)
    Program (and accompanying library) to solve the problem of harmonic inversion — given a discrete-time, finite-length signal that consists of a sum of finitely-many sinusoids (possibly exponentially decaying) in a given bandwidth, it determines the frequencies, decay constants, amplitudes, and phases of those sinusoids.
  • libctl (web page)
    Guile-based library implementing flexible control files for scientific simulations.
  • meep (web page)
    Finite-difference time-domain (FDTD) simulation software package developed at MIT to model electromagnetic systems, along with our MPB eigenmode package.
  • elpa (web page)
    A new efficient distributed parallel direct eigenvalue solver for symmetric matrices. It contains both an improved one-step ScaLAPACK type solver (ELPA1) and the two-step solver ELPA2.
    ELPA uses the same matrix layout as ScaLAPACK. The actual parallel linear algebra routines are completely rewritten. ELPA1 implements the same linear algebra as traditional solutions (reduction to tridiagonal form by Householder transforms, divide & conquer solution, eigenvector backtransform). In ELPA2, the reduction to tridiagonal form and the corresponding backtransform are replaced by a two-step version, giving an additional significant performance improvement.


Wednesday
25 February, 2015


Michael Meeks: 2015-02-25 Wednesday

21:00 UTCmember

face
  • Up early, quick mail chew; set off for Cambridge; into the office to see Tracie; read a great report. Train on to Edinburgh, worked on budgets. Extraordinarily frustrating experience with intermittent connectivity and Evolution on the train for some hours.
  • Enjoyed some of the talks at the Open Source Awards, and a great meal mid-stream.
  • Extraordinarily honoured to recieve from Karen Sandler, on behalf of Collabora Productivity, the UK Open Source Awards 2015 - Best Organisation; gave a small acceptance spiel:
    • It is an honour: in a Cloud obsessed world to have a Commodity Client Software company represented. In a world obsessed by Tablets: to encourage Free Software that makes your PC/Mac keyboard really useful. Naturally, we do have a Tablet & phone version making good progress now (for the paper-haters).
    • LibreOffice 80+ million users: more than the UK's population. A brief correction - Collabora is only the 2nd largest contributor to the code - the 1st is volunteers in whose debt we all are. Everything we produce is Free Software.
    • Collabora - has a mission we believe in: To make Open Source rock (ono). We're betting our Productivity subsidiary on ODF and LibreOffice.
    • We're here to kill the old reasons not to deploy Free Software: with long term maintenance for three to five years; rich support options - backing our partner/resellers with a fast code-fix capability; and finally killing complaints - we can implement any feature, fix any bug, and integrate with any Line Of Business app for you.
    • In the productivity space - innovation is long overdue; Free Software can provide that. Thanks for coming & your support

face

It has been a while since we reported about YaST in this site. This post in Spanish from fellow openSUSE blogger Victorhck has inspired us to write about some exciting news that deserve to be shared with the whole openSUSE community. YaST has always been a completely free and open source project, but free and open source means way more than just having the code available in some server at Internet. You may know lowering the entry barrier to contribute to YaST has been one of the goals of the project.

The first big step was moving from YCP to a more popular, documented and widespread programming language like Ruby. The new Ruby-based codebase debuted in openSUSE 13.1, full of automatically converted code that looked “not so Ruby”. Now, with the revamped installation workflow introduced in openSUSE 13.2 and after a whole release cycle of refining and polishing the YaST code and the development tools, the world of YaST development is a nicer place for newcomers.

So we have the code publicly available and written in a nice popular language, we have easy to install development tools, we have a public IRC channel and an open mailing list and we have a group of experienced developers willing to help anybody wanting to jump aboard. What is missing?

Tons of documentation!

The YaST team has put some effort in the last months gathering all the development documentation that was disperse and creating new one. The result is the new YaST development landing page. The page is packed with information useful to anyone willing to introduce himself in the world of YaST development and also acts as a central documentation hub, containing links to information hosted in Rubydoc.info, doc.opensuse.org or the openSUSE wiki. Among other things, the page includes a guide with the first steps for newcomers, a section with documentation targeted at developers and another one with descriptions of the processes and guidelines observed while developing YaST.

One of the sources of information linked from the YaST landing page is the brand new tutorial titled “Creating the YaST journalctl module“. As the title suggests, the tutorial presents a very simple example of a YaST module developed from scratch in pure Ruby. The document is focused on the tools and the overall architecture trying to balance nicely theory and practice. All the example code and files used in the tutorial are available in a git repository that follows the learning time-line, with every tag corresponding to a step in the tutorial.

But this tutorial is not the only evidence of a flourishing Ruby future for YaST.

New modules

The last months have seen the born of several new YaST modules written in Ruby from scratch. The source code of all of them is available at Github and the modules themselves are all included and directly installable on openSUSE Tumbleweed, with the exception of the I/O Channels module, available only for SLE since it’s targeted at



face

Agora nesta terça-feira dia 24 a Mozilla liberou a versão 36 do Firefox com o suporte ao HTTP/2. Como ultima versão do protocolo HTTP é de 1999 e muitas mudanças ocorreram na Web, o mesmo começou tornar-se um gargalo no desempenho da internet. O HTTP 2 foi baseado no conceito do SPDY que reduz o tempo em torno de 40%, transmitindo obrigatoriamente os dados compactados e criptografados, como aproveitar a transmissão para diversas requisiçoes (também conhecido como multiplexão).

Clique AQUI e efetue o DOWNLOAD!

Firefox2



face

Neste post, veremos como obter o máximo desempenho com a placa de Vídeo NVidia Optimus que otimiza o seu notebook de forma inteligente, oferecendo o desempenho gráfico impressionante que você precisa, quando você precisa, e sempre aumentando o tempo de vida da bateria para que você aproveite por mais tempo.

Primeiramente instale o openSUSE com o parametro do kernel brokenmodules=nouvea, assim tornando desnecessário colocar este módulo no kernel na blacklist. depois, para instalar o Bumblebee que explora os recursos da NVidia Optimus, primeiramente instale os seguintes pacotes no openSUSE 13.2:

  • bbswitch-0.8-21.1.x86_64
  • bbswitch-kmp-desktop-0.8_k3.16.7_7-21.1.x86_64
  • bumblebee-3.2.1-16.1.x86_64
  • nvidia-bumblebee-343.36-1.1.x86_64
  • dkms-2.2.0.3-14.1.noarch
  • primus-20131226-16.1.x86_64
  • primus-32bit-20131226-3.1.3.x86_64
  • VirtualGL-devel-2.3.90-21.1.x86_64
  • VirtualBox-4.3-4.3.20_96996_openSUSE123-1.x86_64
  • VirtualGL-32bit-2.3.90-1.8.x86_64
  • VirtualGL-2.3.90-21.1.x86_64

Adicione o usuario nos grupos video e bumblebee:

# usermod -G video,bumblebee cabelo

Inicialmente o Bumblebee não esta em funcionamento,então os comando a seguir devolverão os seguintes resultados:

# cat /proc/acpi/bbswitch 
0000:01:00.0 ON

Testaremos o desempenho com o programa glxspheres com o comando a seguir:

$bglxspheres
Polygons in scene: 62464
Visual ID of window: 0x20
Context is Direct
OpenGL Renderer: Mesa DRI Intel(R) Haswell Mobile
59.977914 frames/sec - 66.935352 Mpixels/sec
60.040965 frames/sec - 67.005717 Mpixels/sec

nvidia.01

Aqui conseguimos um desempenho máximo de 60 frames/segundos, agora começaremos a brincadeira inciando o daemon Bumblebee:

# systemctl status bumblebeed
bumblebeed.service - Bumblebee C Daemon
 Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled)
 Active: active (running) since Ter 2015-02-24 21:34:38 BRT; 45min ago
 Main PID: 861 (bumblebeed)
 CGroup: /system.slice/bumblebeed.service
 └─861 /usr/sbin/bumblebeed
 # cat /proc/acpi/bbswitch 
0000:01:00.0 OFF
# optirun --status
Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.

Agora com tudo fucionando executaremos o glxsphere novamente precedido do comando optirun:

# optirun glxspheres
Polygons in scene: 62464
Visual ID of window: 0x20
Context is Direct
OpenGL Renderer: GeForce GTX 860M/PCIe/SSE2
192.146589 frames/sec - 214.435593 Mpixels/sec
193.858314 frames/sec - 216.345879 Mpixels/sec

nvidia.02

Reparem que agora conseguimos obter 192 frames/segundos no lugar do suado 60 frames/segundos. Agora vamos turbinar a brincadeira com o comando primusrun:

$ vblank_mode=0 primusrun glxspheres
Context is Direct
OpenGL Renderer: GeForce GTX 860M/PCIe/SSE2
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
273.449995 frames/sec - 305.170194 Mpixels/sec
274.683783 frames/sec - 306.547102 Mpixels/sec
278.195957 frames/sec - 310.466688 Mpixels/sec
280.331172 frames/sec - 312.849588 Mpixels/sec

nvidia.03

Com este recurso, podemos selecionar quando usar o recurso máximo da placa NVidia ou poupar a bateria do Notebook.

 

 

 

 

 

 

 

 

 

 

 

 



Kohei Yoshida: Orcus 0.7.1 is out

00:56 UTCmember

face

After more than a year since the release of 0.7.0, I’m once again very happy to announce that the version 0.7.1 of the Orcus library is now available for download. You can download the package from the project’s download page.

This is a maintenance release. It primarily includes bug fixes and build fixes since the 0.7.0 release with no new features. That said, the most notable aspect of this release is that it is buildable with the version 0.9.0 of the Ixion library which was just released a week ago. So, if you are trying to package and distribute the newly-released Ixion library but are unable to do so because of Orcus not being buildable with it, you might be interested in this release.

The next major upgrade will be 0.9.0 whose development is on-going on the current master branch. Hopefully that release won’t be too far away.


Tuesday
24 February, 2015


Michael Meeks: 2015-02-24 Tuesday

21:00 UTCmember

face
  • Mail chew, built ESC stats; mail; lunch. Customer call. Reviewed the LibreOffice 4.4 feature set to write a LXF column, rather encouraged.
  • Booked train tickets to the great Open Source Awards tomorrow in Edinburgh.

face
The "Ceph Developer Summit" for the Infernalis release is on the way. The summit is planed for 03. and 04. March. The blueprint submission period started on 16. February and will end 27. February 2015. 

Do you miss something in Ceph or plan to develop some feature for the next release? It's your chance to submit a blueprint here.

face

Since the release of the 3.19 kernel in openSUSE Tumbleweed the vmnet module will fail to build for VMware Workstation 11.0.x

VMware community message

Credit for the patch

patch available at 1

Execute the following steps to patch your VMware Workstation 11.0.x


Download the patch to /tmp:
# curl -L "https://docs.google.com/a/seader.us/uc?authuser=0&id=0BxMaO3Y-qL_1Z2NMSkxRdndzNlk&export=download" -o /tmp/vmnet-3.19.patch
Extract the vmnet module from sources:
# cs /usr/lib/vmware/modules/source
# tar -xf vmnet.tar
Apply the patch to the source:
# patch -p0 -i /tmp/vmnet-3.19.patch
Recreate the source archive:
# tar -cf vmnet.tar vmnet-only 
Remove leftover folder:
# rm -r *-only
Rebuild VMware modules:
# vmware-modconfig --console --install-all
Enjoy!


face

openSUSE Conference 2015

Link to oSC15 webpage

 

As you may already know, the Travel Support Program (TSP) provides travel sponsorships to openSUSE community who want to attend the openSUSE conference and need financial assistance. The openSUSE conference 2015 will held in the city of The Hague – Netherlands, from May 1st to May 5th.

 

 

The goal of the TSP is to help everybody in and around openSUSE to be able to go to the openSUSE Conference!

 

When and how

The application period will be opened from February 24th to March 5th. The approval results will be done by TSP App on March 9th and the sponsoship acception must to be done until March 12th. In case the requester doesn’t Approve the sponsorship the amount will be given for the next on the waiting list.

Remember: All requests will be managed through the TSP application at http://connect.opensuse.org/travel-support.

You will need an openSUSE Connect account in order to log in the application and apply for sponsorship. Please be sure to fullfil all of your personal details at openSUSE connect account to avoid delays or negative request. A good application with good information will be processed faster.

A few reminderstips

  • Please read the TSP page carefully before you apply.
  • Any information you send to the Travel Committee will be private.
  • We want everybody there! Even if you think you would not qualify for the travel support, just submit and make it worth! If you don’t try you won’t get!
  • If you submitted an abstract to be presented you should mention it in your application.
  • The Travel Committee can reimburse up to 80% of travel and/or lodging costs. That includes hotel, hostel, plane,train, bus, even gas for those willing to drive. Remember, no taxi!
    • Important: Food and all local expenses are on you!
  • We want to sponsor as many people as possible so please check the best deal.
  • The Travel Committee won’t be able to book or pay anything in advance. The reimbursement will be done after the event finishes and based on your expenses receipts.
  • no receipts = no money It is the rule!

If you have any question regarding your trip to the conference do not hesitate to ask the TSP or oSC15 organizers.

We hope to see you there!


Monday
23 February, 2015


Michael Meeks: 2015-02-23 Monday

21:00 UTCmember

face
  • Mail chew, 1:1 calls with people, lunch. Team call, sync with Lubos, mail, hacked a little bit on gtktiledviewer wrt. zoomed in selection overlay rendering. 2nd team call.

face

Realizar documentación para una herramienta como YaST, hace que esta se abra a la comunidad, y siga creciendo y actualizándose para las nuevas necesidades.

Yast_logo

YaST (Yet another Setup Tool) es la herramienta de instalación y de configuración por excelencia de las distribuciones openSUSE y SUSE Linux Enterprise. Ofrece al usuario una interfaz fácil de utilizar y con potentes posibilidades de configuración de la distro.

Hace unos días os hablaba en el blog de la creación de un nuevo módulo para esta gran herramienta de openSUSE. Podéis leer la entrada en este enlace:

Este y muchos otros nuevos módulos (http://yast.github.io/modules.html) hacen a YaST cada vez más completa, gracias tanto al proceso de apertura que vivió YaST, como a que los desarrolladores documentan sus trabajos y comparten con todos esa documentación.

En una comunidad de sofware libre, el código permanece libre y al alcance de todos, puedes descargarlo, estudiarlo, modificarlo, y redistribuirlo.

Pero para poder ejercer todas esas libertades, el código debe estar documentado, y la documentación también ser libre, es decir, que aquel que quiera estudiarlo y tenga los conocimientos necesarios, encuentre fácilmente la manera de hacerlo. Sólo así el software además de ser libre se podrá expandir, y ser mejorado por una comunidad de hackers.

En openSUSE se trata de que así sea. openSUSE es un proyecto de software libre en el que el código de todo su software está al alcance de quien quiera echarle un vistazo y realizar las mejoras que crea convenientes y YaST la herramienta por excelencia de openSUSE no iba a ser ninguna excepción.

Un primer paso para poder poner al alcance de todos este software fue la “traducción” del lenguaje en el que estaba desarrollado. Se convirtió el antiguo YaST creado en lenguaje YCP a Ruby, un lenguaje de programación más actual, y más expandido. Con esta conversión, ahora es más sencillo crear nuevas funcionalidades para YaST.

Tenemos el código disponible (https://github.com/yast) , y además lo han hecho más accesible a todos aquellos que quieran darle nuevas funcionalidades, entonces ¿qué nos falta? Un poco de documentación sobre el proceso correcto para realizar dicha tarea.

Para solventar ese obstáculo, sólo queda ponerle remedio documentando el proceso y la manera de realizar las cosas, unificarla, y centralizarla en un sólo sitio, desde el que enlazar a las múltiples posibilidades que existen.

Eso es lo que trata de hacer esta página (http://yast.github.io/documentation.html) disponible, para consultar y aprender todos sobre el proceso. Quiere servir de guía para indicar el camino idóneo a seguir. Estandarizando procesos, y distintas metodologías.

Esta documentación quiere ser una ayuda útil, no un simple manual que muy pocos leen, o


face

La sortie d'openSUSE 13.3 n'est pas encore à l'ordre du jour… mais pourquoi ne pas commencer à participer à la traduction de votre distribution préférée ? Si vous comprenez l'anglais et que l'idée de vous impliquer en douceur dans un projet open-source vous intéresse, c'est l'occasion !

La traduction d'openSUSE : où en est-on ?

Nom : statistics-geeko-inside.jpg
Affichages : 1127
Taille : 24.0 KoL'équipe de traduction francophone n'a jamais été très fournie, du moins depuis que je la suis, mais elle a toujours fait

Sunday
22 February, 2015


Michael Meeks: 2015-02-22 Sunday

21:00 UTCmember

face
  • Lie-in, out to NCC - Claire preached well; back for lunch with Dean and Moulouia(?) and their fun-sized girls. Quarter practice with the babes, watched a notably terrible 'Cindy' film; tea, read stories bed.

face

Una crónica personal de la visita de Richard Stallman en su charla de Oviedo este febrero de 2015.

Autógrafo de Richard Stallman

 

Tal como comenté en el blog, Richard Stallman, el creador de GNU y el software libre, visitó de nuevo España. Esta vez Gijón, Oviedo y Zaragoza serían las ciudades por las que pasearía melena al viento.

Esta es mi crónica personal de la cita de Oviedo, a la que asistí. Toda una experiencia que todo geek tendría que tener! ;)

Finalmente, después de mucho dudar, decidí hacer la maleta y asistir a la charla de Stallman en Oviedo. La oportunidad era única, estaba relativamente cerca y no había otras citas que me lo impidiesen.

Además habría otros hackers que iban a asistir, como por ejemplo Jessica, bloguera y activista incansable, que hizo de anfitriona, y Dani Rulos acompañado de su amigo Manuel, estos dos chicarrones, pudieron con un madrugón importante, y un viaje en autocar desde tierras castellanas.

Fue un placer conoceros en persona y disfrutar con vosotros de la experiencia!! ;)

Así que a reservar tren y habitación en la capital Astur!

Al compás del chaca-chá del tren

 

Ir a Asturias siempre es un placer, buena tierra y buena gente. El trayecto en tren me permitió recuperar una manera de viajar que hace tiempo que no disfrutaba. Comodidad, relax, poder disfrutar del paisaje, etc…

Llegada a Oviedo, y como no, omnipresente lluvia, que con treguas intermitentes estuvo presente todo el día. Paseo a cubierto, resguardarse en un bar, y quedar con los hackers arriba citados.

Se hace la hora, así que al edificio Calatrava a coger sitio. Allí vamos encontrándonos con más hackers que repetían, después de haber estado viéndole el día anterior en Gijón.

El auditorio donde se celebró la sala, muy grande, y bien cuidado. El aforo, al final calculamos que serían de unas 200 400 personas más o menos (según el ayuntamiento de Oviedo)… Al entrar ya pude estrecharle la mano a Stallman, pero va con prisa… Toca coger pegatinas geeks para el ordenador o lo que te apetezca…

Grupo Xera actuando

 

Cogemos sitio y a esperar a que empiece. Lo hace de manera puntual, pero antes de la conferencia de Stallman, sale a actuar el grupo Asturiano Xera, grupo que licencia su contenido bajo Creative Commons, tocando un par de canciones. Por cierto grupo al que Jess entrevistó en una ocasión y se publicó dicha entrevista, buscadla por internet…

Terminada la actuación Stallman empieza su charla “Por una sociedad libre”. Por supuesto empieza la charla con las consabidas indicaciones de no subir sus fotos a Facebook, ni Instagram. Compartir los vídeos de la misma en formatos libres (OGG y WebM) etc…

Stallman preparándose

 

Y empieza poniéndonos en situación, explicándo las 4 libertades del software libre, para que este pueda ser llamado


Saturday
21 February, 2015


Michael Meeks: 2015-02-21 Saturday

21:00 UTCmember

face
  • Up earlyish; counted the area for tiles, into Bury to order just the right kind; to Noughton Park to play with the babes. Back for lunch.
  • Spent much of the afternoon moving more cupboards from wall A (the wrong wall) to wall B (the right wall). Considered the plans to create fitted family lockers for the assorted junk that four babes produce - to match JP's version we admired in Toronto.

face

openSUSE miniSummit T-shirtBy Bruno Friedmann

Hi Geekos, here is a small summary of our Thursday February 19th openSUSE miniSummit event here at SCALE 13x.

Located in Century AB room, a 80 seats room, the average attendance rate was varying between 50% and 85%.

Qualifying the attendance 50% or more were not related to SUSE / openSUSE, which had a good wealth of questions and feedback.

The day started by a talk about openSUSE / SUSE Xen and openstack by Peter Linnel and Russel Pavlicek.

One hour later Manu Gupta has presented all the bolts and nuts about Google Summer of Code at openSUSE.

We then go for lunch, and corridor exchanges.

I opened the afternoon with my talk “them + me = we” about breaking mythic frontier.

Then, just after a small break, Mark Fasheh, a member of filesystem SUSE Labs group, had a talk about the project Duperemove: dedupe on btrfs (have a look of the source on github, and the package available on obs).

The day continued with a Town Hall talk by myself and Peter running an open discussion with attendees. With interesting remarks and feedback from openSUSE users, and also complete foreigners. For example, the way systemd was introduced in openSUSE distribution was appreciated (having choice during 2 versions). It was an unstressfull, open and positive exchange.

To follow, Bryan Lunduke and Peter animated a talk about “the 10 things you would love about SUSE and openSUSE if you only you knew…”

I did really enjoy the way they numbered the slides …
Freschy, punchy, funky, the kinda talk I would like to see again at OSC15.

To finalize the day, Markus Feilner​ for Linux Magazine (Germany) talked about openQA.

I found the day interesting and a perfect mix between openSUSE and SUSE during this day, confirming the excellent partnership we have.

Thanks you to the sponsors of this day and to all those who helped make it happen.

Links :
SCALE picture album day 1 : by Françoise on G+

openSUSE miniSummit day album :
Bruno’s Album on G+

Follow the news on G+ channel

Stay tuned for more news during this week-end.


Friday
20 February, 2015


Michael Meeks: 2015-02-20 Friday

21:00 UTCmember

face
  • Mail chew, patch review, fixed an Android crasher, and tried to avoid a SIGILL running Android/Atom code on my AMD x86_64 machine in the android emulator: nasty, failed to overcome that with my Core II Duo. Perhaps new NDK's really generate lots of hyper-new instructions, odd.
  • Took apart my Motorola Xoom which has failed to charge reliably recently. Very impressed with the non-soldered-in, surface-mount - get really well secured (by moulding in the chassis) power connector; removed and tweaked this with a needle to mend it (for now).

<- Current blog entries