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.

15 September, 2014


Logo od tohoto autora bylo vybráno jako Oficiální Logo summitu.
openSUSE Asia community děkuje všem účastníkům soutěže za jejich čas a snažení, stejně jako lidem za hlasování, kteří se právě svým hlasováním postarali o aktivní účast.
Výsledky soutěže můžete shlédnout ZDE

12. září 2014 Manu Gupta


 Gracias al proyecto Neon finalmente me he decidido a probar Plasma 5 en mi portátil de uso diario. El objetivo es conocer de primera mano el rendimiento del nuevo escritorio Plasma de KDE, sus virtudes y sus defectos. En resumen, es esta entrada voy a comentaros las primeras impresiones de Plasma 5. Cómo instalar Plasma [&hellip

14 September, 2014



If running a booth is, for sure, an investment of time, energy and money (even if TSP contribute to help you), We often forget to say
how much it’s important for our community and project.

Booths makes openSUSE alive in all open source events! and it’s a great experience to live, for any of us.

Feel the beat!

I strongly believe that openSUSE has be to visible on events like KDE Akademy, Scale, Fosdem, Guadec.
It’s not a question of "Bang for the buck", than a simple obviousness:

  • Fosdem : the biggest open source event in Europe (perhaps in the world) with more than 5000 hackers visiting.
  • Scale : biggest event in North America with more than 3000 attendees
  • Guadec : The annual conference of Gnome Hackers with lot of worldwide attendees
  • KDE Akademy : This year with around 150 active contributors coming from all over the world.

The obviousness is: if openSUSE has no booth there, you just see Ubuntu and Redhat, and let’s add Debian, Mageia etc for Fosdem or Scale.

You all know how much I like our Geeko community. And when Akademy staff proposed us to run a booth, I said yes, great I will be there!
After comparing ways to go to Brno, the Geeko’s car was the less expensive, and allow me to pick the demo touch screen at SUSE Headquarter.
So I took a full week off and drive 2000 kilometers to make it happens.


Open the Fun can

Running a booth is not that hard. You will find flyers in the booth box presenting openSUSE and related tools.
There’s goodies like several kind of stickers, pens, USB flash keys, beer mate.
About the poster, if not allowed on walls, let’s your creativity soar. Use boxes, a pen can also fix that big banner around the guard-rail.

On the human part, I would say than 3 persons is not too much. For example at Brno, the booth was very calm during the talks, but when the break
arrives, you just see 30-50 people coming all at the same time in your direction.Don’t run away!
Organize yourself! For example one of the staff is delegated to spread swag, and drive attendees to the next expert.

Try to give as much as possible short-quality answers.

No matter if you are not at all technical guru, the priority is to welcome visitors and listen to them.

If you have a demo computer, organize a bunch of bookmarks related to the conference subject inside the openSUSE community.
At Brno, we were essentially demoing live factory with kde stable 4.14 and Factory with plasma5 and Frameworks 5, and all related web pages about kde on obs, wiki.
Our moto was What openSUSE can offer to KDE developers and contributors.

It’s rarely on a booth that we can resolve a bug, but that’s where a beginning of a social interaction starts.

Don’t worry if you can’t awnser directly, offer


Una de las aplicaciones favoritas por los desarrolladores de KDE es KDevelop. No por nada se trata de una aplicación que les permite crear aplicaciones, así que las mejoras que se produzcan en él servirán para mejorar el resto de las aplicaciones. Por esta razón me llena de satisfacción anunciar que ha sido lanzado KDevelop [&hellip

13 September, 2014


Twice recently we have had “fun” trying to get things using HK2 (Jersey), to place nicely with code built using Guice and Spring. This has renewed my appreciation for code written without DI frameworks.

The problem with (many) DI frameworks.

People like to complain about Spring. It’s an easy target, but often the argument is a lazy “I don’t like XML, it’s verbose, and not fashionable, unlike JSON, or YAML, or the flavour of the month”. This conveniently ignores that it’s possible to do entirely XML-less Spring. With JavaConfig it’s not much different to other frameworks like Guice. (Admittedly, this becomes harder if you try to use other parts of Spring like MVC or AoP)

My issue with many DI frameworks is the complexity they can introduce. It’s often not immediately obvious what instance of an interface is being used at runtime without the aid of a debugger. You need to understand a reasonable amount about how the framework you are using works, rather than just the programming language. Additionally, wiring errors are often only visible at runtime rather than compile time, which means you may not notice the errors until a few minutes after you make them.

Some frameworks also encourage you to become very dependent on them. If you use field injection to have the framework magically make dependencies available for you with reflection, then it becomes difficult to construct things without the aid of the framework – for example in tests, or if you want to stop using that framework.

Even if you use setter or constructor injection, the ease with which the framework can inject a large number of dependencies for you allows you to ignore the complexity introduced by having excessive dependencies. It’s still a pain to construct an object with 20 dependencies without the framework in a test, even with constructor or setter injection. DI frameworks can shield us from the pain that is useful feedback that the design of our code is too complex.

What do I want when doing dependency injection? I have lots of desires but these are some of the most important to me

  • Safety – I would like it to be a compile time error to fail to satisfy a dependency
  • Testability – I want to be able to replace dependencies with test doubles where useful for testing purposes
  • Flexibility – I would like to be able to alter the behaviour of my program by re-wiring my object graph without having to change lots of code

It’s also nice to be able to build small lightweight services without needing to add lots of third party dependencies to get anything done. If we want to avoid pulling in a framework, how else could we achieve our desires? There are a few simple techniques we can use which only require pure Java, some of which are much easier in Java 8.

I’ve tried to come up with a simple example that might exist if we were


La variedad de aplicaciones es algo necesario en el mundo de Software Libre. EN gnu/linux, y en KDE en particular, tenemos una infinita colección de aplicaciones: navegadores, exploradores, gestores de todo tipo, suites ofimáticas y de información personal, reproductores multimedia, etc. y aún así, cada ciento tiempo aparece una aplicación que cubre algún pequeño aspecto [&hellip


A new gem

A new gem has started in the world. Youtube_helper is not just another Youtube gem. It’s the helper gem. What it does? The Youtube_dlhelper gem downloads a youtube video from a defined space, creates the needed directories and transcodes the filde from *.m4a to *.mp3. Read the full README for using the gem.

Where is it?

You can find it there: https://github.com/saigkill/youtube_dlhelper (It goes directly to the README).

Ho to use?

Just run it with: youtube_dlhelper.rb YourUrl The new file is shown inside your $Musicfolder/Groupname/Youtube-Music or if you have choosen a Interpret it goes to $Musicfolder/Surname_Firstname/Youtube-Videos.

Have a lot of fun :-)

Sascha Manns: Welcome

01:30 UTCmember



Hello and welcome to my new Jekyll Bootstrap Page. Because of some Bandwidth problems i moved my blog out to Github.

Sascha Manns: Jekyll Introduction

01:30 UTCmember


This Jekyll introduction will outline specifically what Jekyll is and why you would want to use it. Directly following the intro we’ll learn exactly how Jekyll does what it does.


What is Jekyll?

Jekyll is a parsing engine bundled as a ruby gem used to build static websites from dynamic components such as templates, partials, liquid code, markdown, etc. Jekyll is known as “a simple, blog aware, static site generator”.


This website is created with Jekyll. Other Jekyll websites.

What does Jekyll Do?

Jekyll is a ruby gem you install on your local system. Once there you can call jekyll --server on a directory and provided that directory is setup in a way jekyll expects, it will do magic stuff like parse markdown/textile files, compute categories, tags, permalinks, and construct your pages from layout templates and partials.

Once parsed, Jekyll stores the result in a self-contained static _site folder. The intention here is that you can serve all contents in this folder statically from a plain static web-server.

You can think of Jekyll as a normalish dynamic blog but rather than parsing content, templates, and tags on each request, Jekyll does this once beforehand and caches the entire website in a folder for serving statically.

Jekyll is Not Blogging Software

Jekyll is a parsing engine.

Jekyll does not come with any content nor does it have any templates or design elements. This is a common source of confusion when getting started. Jekyll does not come with anything you actually use or see on your website - you have to make it.

Why Should I Care?

Jekyll is very minimalistic and very efficient. The most important thing to realize about Jekyll is that it creates a static representation of your website requiring only a static web-server. Traditional dynamic blogs like Wordpress require a database and server-side code. Heavily trafficked dynamic blogs must employ a caching layer that ultimately performs the same job Jekyll sets out to do; serve static content.

Therefore if you like to keep things simple and you prefer the command-line over an admin panel UI then give Jekyll a try.

Developers like Jekyll because we can write content like we write code:

  • Ability to write content in markdown or textile in your favorite text-editor.
  • Ability to write and preview your content via localhost.
  • No internet connection required.
  • Ability to publish via git.
  • Ability to host your blog on a static web-server.
  • Ability to host freely on GitHub Pages.
  • No database required.

How Jekyll Works

The following is a complete but concise outline of exactly how Jekyll works.

Be aware that core concepts are introduced in rapid succession without code examples. This information is not intended to specifically teach you how to do anything, rather it is intended to give you the full picture relative to what is going on in Jekyll-world.

Learning these core concepts should help you avoid common frustrations and ultimately help you better understand the code examples contained throughout Jekyll-Bootstrap.

Initial Setup

12 September, 2014


We are pleased to announce that the winner of our Logo Design contest is the No.8 candidate authored by *W.H*!

Congratulations, *W.H*! W.H’s logo has been chosen as the official logo.

openSUSE Asia Summit 2014

openSUSE Asia Summit 2014


A heartfelt thanks from the openSUSE Asia community to all the logo designers for their time and effort, as well as the voters who took care of the active voting! You made this happened!


Results of the voting contest can be seen here.



Je aplikace, která dovolí uživatelům experimentovat s dynamikou solárního systému.
Tento program pouze simuluje fyziku. Planety a jejich měsíce nemají žádné vlastnosti, kromě velikosti, pohybu a hmotnosti.


Je simulátor pohledu na hvězdy. Kde uživatel je v nějakém venkovském prostranství a dívá se na oblohu. Uživatelé můžou simulovat různé druhy dalekohledů a teleskopů. Lze také nastavit i čas, viditelné objekty i různé štítky. Stellarium je primárně využíván pro vzdělávací účely. Stellarium je možno používat na mobilních zařízeních Android, iOS a dalších mobilních systémech. http://www.stellarium.org/. Zde můžete sehnat i pluginy a další užitečné informace.


Kde uživatelé si můžou také užít Kstars, což je aplikace podobná Stellarium.


je detailní 3D simulátor, který dovoluje uživatelům prozkoumávat vesmír a to včetně jiných solárních systémů.
Uživatelé můžou cestovat různými vesmírnými cíli. Stisknutím tlačítek se můžete pohybovat nebo si prohlédnout celý objekt.
Grafika je velmi detailní.
Obvyklé využití této aplikace se najde ve vzdělání, nebo využití najdou také amatéři.
Domovská stránka aplikace je http://www.shatters.net/celestia/
tady jsou nějaké addony http://www.celestiamotherlode.net


je také dost podobná aplikaci Cellestia. Obě dvě aplikace mají podobné rozhraní a sadu fíčur, to záleží na vašich preferencích a na tom která aplikace vám bude víc vyhovovat. Takže dopoučuji si zkusit obě, aby jste viděli která se vám líbí víc.

Digital Universe

Je další opensource planetárium, které může uživatelům víc vyhovovat než Celestia nebo openUniverse.


Zase další kousek planetárního software pro Linux. Nicméně tento program je patentovaný.

Pro ty co mají rádi Vesmír a fikci je tu

veřejný simulátor vesmíru

Server poskytuje pouze jeden vesmír, který je veřejný. Tato hra můžu lidem pomoc pochopit vesmír tím, že ho uživatelé vytvářejí a manipulují s ním.

Hvězdné mapy mohou být vytvářeny softwarem zvaným PP3 (http://pp3.sourceforge.net/)
Mapy jsou ukládány ve formátech pdf, posrscript, nebo LaTeX.

Můžete také studovat povrch měsíce s „

Virtual Moon Atlas

“ domovská stránka je zde.

Objekty hlubokého vesmíru softwarem zvaným “

where is my M13

“ tento software je ka nalezení na

Pro ty kteří se hodně zajímají o astronomii, je tu přímo Linuxová



Have you ever dreamed making your own unique font set. You get on it and seek for decent cheap or open source alternatives for making Truetype fonts  and  probably you find at least Fontforge. You are very happy and make you mind I’ll do my fonts with Fontforge. After a while you realize Fontforge is a Swiss army knife for making fonts in open source but you just wanted to create TTF, EOT or SVG font set. Weep no more you can use Birdfont.
Birdfont in Ubuntu

Birdfont free font editor

Birdfont is developed by one man army Johan Mattsson. First it was hobby project now it has evolved pretty nice font editor  and it while ago it hit version 1.0 (actually now it’s already version 1.1). Biggest driver create Birdfont even though there is superior editor available was create grid based editor rather than exact coordinates system used in Fontforge. So in Birdfont you can snap to grid.

Birdfont is very stable and available native in Windows, Mac OS X and of course various Linux distributions (counting in openSUSE). Those who care it’s written in Vala and even though it’s GPL code although developer asks you to donate couple of $ or € before downloading binary. If you ask me it’s worth every dime but of course you can download source and make your own build.


You can create font or font set all in Birdfont (Which has very nice gird editor) or one can use free of choice vector editor that can export SVG and import glyphs in. After import you can edit imported glyphs because used curve math ain’t same in TTF than it’s SVG but Birdfont tries to make this part easy for you. You can also edit kerning and font location to make more complex fonts come true.

After you are satisfied with font. Just edit properties and export your font in TTF, EOT or SVG format.

So if Fontforge is too much and you just want to hop on  making fonts Birdfont can be what you are seeking for.

11 September, 2014


OpenSUSE uživatelé vždy přemýšleli jak se dostat k aktuálnímu software a aktuálním aplikacím.
Vědí že systém Ubuntu má něco co se nazývá PPAs což dovoluje uživatelům dostat se k nejnovějším balíčkům, které ještě nejsou v oficiálních repozitářích. Stejný případ je u Arch Linuxu díky AUR. Ale existuje něco takového pro uživatele openSUSE?
Jistě že ano!
OpenSUSE má službu která se jmenuje OBS nebo openSUSE Build Service, služba pomáhá nejenom openSUSE uživatelům, ale také jiným projektům k jednuduché kompilaci pro své uživatele. OBS nevytváří balíčky pouze pro openSUSE, ale vývojáři mužou a vytvářejí balíčky pro jiné distribuce, například pro Ubuntu.
Mnoho předních projektů používá OBS ke kompilaci balíčků.
OBS také dovoluje nezávislým vývojářům a projektům, aby nabídli své poslední balíčky openSUSE uživatelům skrze své vlastní repozitáře.
Je to podobné jako PPA v Ubuntu.
OpenSUSE má online nástroj pro vyhledávání, ve kterém lze najít software podle jména.
V mém případě, jsem chtěl update pro LibreOffice na verzi 4.3 – poslední verzi.
Navšivte software.opensuse.org a nejděte si balíček.
Defaultně se vám zobrazí stabilní verze z hlavního repozitáře, skrolujte níž a klikněte na „other versions“

Otevře se stránka, na které uvidíte seznam dostupných verzí LibreOffice z jiných repozitářů.

Klikněte na verzi LibreOffice, kterou používáte a pak na „unstable packages“ ukáže se sice varování, ale klikněte na pokračovat „continue

Teď uvidíte jaké verze aplikací jsou dostupné. Klikněte na tlačítko indikující instalaci pomocí jednoho kliku. Otevře se YaST softwarový správce. Automaticky se přidá repozitář do vašeho systému. Díky tomu váš software bude vždy aktuální tím, že novější verze budou ke stažení z repozitáře.

Od chvíle co se bavíme o přidávání nových repozitářů. Pokud chcete odinstalovat software, který jste instalovali pomocí OBS repozitáře třetí strany.
Jděte na YaST Control Center> Software repository
Zde vyberte repozitáře, které chcete odstranit a klikněte na tlačítko „delete“.
Jedna důležitá poznámka: pokud používáte repozitáře třetích stran (Jako třeba KDE current, přidávejte nové repozitáře, způsobem, který je výše uveden a povolte změnu prodejce vždy ve správci software.
Ušetříte čás tím že nebudete muset měnit prodejce při každém konfliktu mezi oficiálním repozitářem a OBS repozitářem
Když už jednou povolíte změnu prodejce, openSUSE atomaticky vybere OBS místo defaulního


Listaller-Logo (with text)It is time for another report on Listaller, the cross-distro 3rd-party package installer, which is now in development for – depending how you count – 5-6 years. This will become a longer post, so you might grab some coffee or tea ;-)

The original idea

The Listaller project was initially started with the goal to make application deployment on Linux distributions as simple as possible, by providing a unified package installation format and tools which make building apps for multiple distributions easier and deployment of updates simple. The key ideas were:

  • Seamless integration of all installation steps into the system – users shouldn’t care about the origin of their application, they just handle all installed apps with the same tool and update all apps with the same interface they use for updating the system.
  • Out-of-the-boy sandboxing for all 3rd-party apps
  • Easy signing and key-validation for Listaller packages
  • Simple creation of updates for developers
  • Resource-sharing: It should always be clear which application uses which library, duplicates should be avoided. The distribution-provided software should take priority, since it is often well-maintained and receives security updates.

The current state

The current release of Listaller handles all of this with a plugin for PackageKit, the cross-distro package-management abstraction layer. It hooks into PackageKit and reads information passing through to the native distributor backend, and if it encounters Listaller software, it handles it appropriately. It can also inject update information. This results in all Listaller software being shown in any PackageKit frontends, and people can work with it just like if the packages were native packages. Listaller package installations are controlled by a machine policy, so the administrator can decide that e.g. only packages from a trusted source (= GPG signature in trusted database) can be installed. Dependencies can be pulled from the distributor’s repositories, or optionally from external sources, like the PyPI.

This sounds good on paper, but the current implementation has various problems.

The issues

The current Listaller approach has some problems. The biggest one lies in the future: Soon, there will be no PackageKit plugins anymore! PackageKit 1.0 will remove support for them, because they appear to be a major source for crashes, even the in-tree plugins cause problems. Also, the PackageKit service itself is currently being trimmed of unneeded features and less-used code. These changes in PackageKit are great and needed for the project (and I support these efforts), but they cause a pretty huge problem for Listaller: The project relies on the PackageKit plugin – if used without it, you loose the system-integration part, which is one of the key concepts of Listaller, and a primary goal.

But this issue is not the only one. There are more. One huge problem for Listaller is dependency-solving: It needs to know where to get software from in case it isn’t installed already. And that has to be done in a cross-distributional way. This is an incredibly complex task, and Listaller contains lots of workarounds for various quirks. It contains so much hacks for

Yesterday Vignesh asked me if I could give some guidance to a college junior of mine who wants to start with Kernel programming. Being a filesystem developer on Novell for a while now, I thought I could share some things that I have learned. I wrote a somewhat long reply which I am reproducing below (with minor edits for clarity) in the hope that it may be useful to someone.

Since it was originally intended to be a mail, it is a little more verbose than a blog post. My advice is based on the situation on my college when I studied a decade ago. Things would have probably changed and the recommendations may need tweaking based on the context.


The most important quality that you need to inculcate if you want to do any kernel space programming is "Patience" (or persistence if you will). Though it is a good quality for any large scale project, it is a fundamental requirement for kernel programming. It is very easy to see progress and make an impact on userspace projects, but even simple changes in the kernel core will take a lot of time to get accepted, and will often require multiple rewrites. But fear not, as there are plenty of people who have conquered this mountain and it is not something to be worried about.

The starting steps will be:

1) Try to understand how to use git. We were (are ?) not taught to use a version control system in our college and it is such a fundamental thing. So start using git for college assignments and get the hang of it.

2) Start writing a lot of C programs and get experienced with pointers, memory allocation, threading. You can start implementing things like Stack, Queue, Trees etc. (whatever you study in datastructures) in a simple, thread-safe way. Do not focus on how you can visualize these datastructures but how you can effectively implement their functionality and thread safety. Use pthreads for threading. Do not use any library (like Glib) for giving you convenient datastructures (like Strings). Implement each of the things on your own. (But when you are writing code for a product, use a standard library always instead of re-inventing the wheel)

Write these C programs on Linux and compile using gcc. In our college days we were using turboc on windows and I hope things have changed. Use a linux distro (fedora, debian, openSUSE, Gentoo etc.) exclusively; Do not use Windows (at least for a while) to make yourself aware of the sysadmin, shell-scripting parts of linux, which will come in handy.

3) Grab a (any) book on Operating Systems theory and read it. The dinosaur book by Silberschatz et. al. is a good start.

4) Without hesitation buy, Robert Love's Linux Kernel Programming book. It is one of the best beginner material and start reading it parallel to the OS book. This is easier to read than the previous one and more practical. But the previous


I read an article today about how expensive the new iPhone 6 will be if you buy it off contract.  I admit, it's a lot of money but it's actually less money than what you'll pay if you buy it with a contract.

I recently switched back to AT&T from Verizon because they introduced a new plan called the Mobile Share Value plan that offers non-subsidized pricing if you own your phone.  There are two rates for each line on this plan. If you own your phone the rate is $15/month for the line.  If you buy a "contract price" phone that rate is $40/month for the line and you have a 2 year contract.

In case you didn't get that, they will charge you and extra $25/month for 2 years to pay for the rest of that phone.  Over 24 months that ends up being $600.
With that, here are the actual iPhone 6 Plus costs:

Contract Prices:
iPhone 6 Plus 16GB: $899
iPhone 6 Plus 64GB: $999
iPhone 6 Plus 128GB: $1099

Non-Contract Prices:
iPhone 6 Plus 16GB: $749
iPhone 6 Plus 64GB: $849
iPhone 6 Plus 128GB: $949 

The other thing to consider is with non-contract plans you don't have a 2 year contract.  I know that seems obvious but let me just say it once again... you don't have a 2 year contract.  You are free to terminate your service any time you want with no cancellation fees.

10 September, 2014

Alex Barrios: Conociendo la Deep Web

15:46 UTCmember


¿Qué es realmente la Deep Web?

La Deep Web no es más que la parte de Internet que no ha sido indexada por algún tipo de buscador, por lo que la única forma de llegar a este tipo de información es conociendo la dirección exacta. Las razones por las cuales alguien podría querer no indexar su información abarcan un gran abanico de posibilidades, de las cuales no todas son necesariamente ilegales. De hecho, por ejemplo para una empresa puede ser importante que la página de acceso a algún servicio web no sea conocida en Internet.

Por otra parte, las páginas que solemos visitar utilizan el protocolo http pero es importante tener presente que existen otros protocolos a través de los cuales también se puede acceder a información en Internet. Es el caso por ejemplo de FTP, que permite realizar transferencia de archivos, y aunque no está asociado a una página web, permite el acceso a información que muchas veces no está indexada en buscadores web.

Lo que podemos encontrar en la Deep Web

Seguramente cuando escuchamos hablar de la Deep Web, lo primero que se nos viene a la mente es información ilegal. Pero es importante tener claro que al haber Teras y Teras de información, se presta para que la variedad sea igualmente amplia. Si bien la cantidad y el hecho de que no sea indexada complica la intención de clasificarla, podríamos decir que en la Deep Web se encuentra gran cantidad de información de tipo multimedia, documentos, sitios web privados, sitios con restricciones de acceso por seguridad, contenido malicioso e incluso material que puede variar dependiendo del tipo de acceso, lo que se conoce como web contextual.

Ahora hay una realidad, y es que debido a los continuos escándalos relacionados con la violación a la privacidad de los datos en muchos servicios web, la posibilidad de publicar información sin que esta sea indexada se vuelve más atractiva. Por lo tanto es muy importante que como usuarios de la tecnología tengamos claro realmente en qué consiste esta parte poco accesible de la web, y que las características de anonimato que ofrece abren la puerta a que sea utiliza de forma maliciosa.

El “peligro” de navegar por la Deep Web

Antes de mencionar los peligros con los cuales nos podríamos encontrar es importante tener presente que el acceso a esta información tiene un poco de dificultad adicional para aquellos usuarios menos curiosos.

Dado que el proceso no es tan sencillo como abrir nuestro navegador web e ir a nuestro buscador favorito para encontrar lo que buscamos, la convierte en un terreno poco explorado, sin muchas regulaciones y que aloja una serie de riesgos para aquellos que no toman las precauciones necesarias.

Lo que si es claro es que como mucha de esta información no tiene un control sobre quien la puede acceder

09 September, 2014


O Intel® Innovation Week 2014 é o evento de tecnologia e inovação da Intel do ano, combinando os eventos Intel® Future Showcase, Intel® Software Day e Intel® Ecosystem Symposium. Seja você um desenvolvedor, fabricante de hardware, profissional de tecnologia ou apenas um apaixonado por inovação, este é o evento certo para se manter informado sobre as novas tendências do mercado. Neste evento apresentarei a palestra “Certiface e a tecnologia Intel no combate a Fraude” onde o case de sucesso Certiface que combate a fraude utilizando a tecnologia de reconhecimento facial. A sua solução é baseada em arquitetura Intel dos servidores aos tablets, devido ao uso de recursos de visão computacional e processamento de imagem com recursos intel como TBB, IPP e MKL junto a bibliotecas openCV e outros recursos de computação de alta performance. Mais informações AQUI.



I’d like to share the slides I used for my talk at LibreOffice Conference 2014 in Bern, Switzerland.

slides preview

During my talk, I hinted that the number of unit tests for Calc have dramatically increased during the 4.2 bug fix cycle alone. Since I did not have the opportunity to count the actual number of unit test cases to include in my slides, let me give you the numbers now.

ucalc filters subsequent-filters subsequent-export total
4.1 65 10 49 9 133
4.2 107 13 54 15 189
master 176 15 67 34 292


The numbers represent the number of top level test functions in each test category. Since sometimes we add assertions to existing test case rather than adding a new function when testing a new bug fix, these numbers are somewhat conservative representation of how much test case we’ve accumulated for Calc. Even then, it is clear from this data set that the number has spiked since the branch-off of the 4.2 stable branch.

Now, I’ll be the first to admit that the 4.2 releases were quite rough in terms of Calc due to the huge refactoring done in the cell storage structure. That said, I’m quite confident that as long as we diligently add tests for the fixes we do, we can recover from this sooner rather than later, and eventually come out stronger than ever before.


Causa gracia algunos comentarios que me han hecho llegar de que la responsabilidad de demostrar que fue lo que sucedió debe ser de los que estamos pidiendo las muestras. Y causa gracia porque la responsabilidad no es de los que piden información, sino de aquellos que realizaron la afirmación al principio. Cuando se realiza una […]


Stojí 70 dolarů ale je víceméně nagware. Čas od času na váš vyskočí okno, které nabízí koupi licence. Já osobně mám licenci na systém Mac, atak se moc nestarám o to jestli můžu použít tuto licenci na více počítačích.
Takže pokud už máte Sublime Text licenci a chcete ji použít na váš openSUSE systém, tento článek vám může pomoct.

Krok 1) vyberte si 32 nebo 64 bit verzi, která bude záležet na architekuře openSUSE kterou používáte.
Krok 2) když už je balíček stažený cd do adresáře kam se stáhnul a extrahujte.

tar vxjf Sublime_FILE_NAME.tar.bz2
Step #3 Nyní přesuňme extrahovanou složku do vybraného adresáře
sudo mv Sublime_FOLDER_NAME /opt/
Step #4 Poté vytvořte symlink in bin
sudo ln -s /opt/PATH_TO_SUBLIME/sublime_text /usr/bin/sublime
Teď už můžete jednoduše spustit Sublime Text z Konzole příkazem


Můžete také použít pravé tlačítko na openSUSE icon/launcher a vybrat položku edit applications.
Potom klikněte na new item zadejte jméno Sublime Text v name „sublime“ jako příkaz.

5. září 2014
Swapnil Bhartiya
Já jsem sáhnul po Sublime Text image/icon z Google/wikipedia a použil jsem ikonu.
Klikněte na save a máte hotovo.

Originální článek ze kterého jsem čerpal ZDE


Projekt prožil prudký nárůst u Factory uživatelů po tomto vyhlášení.

Víc a víc uživatelů přechází právě na Factory.

Viz graf níže
Ancor Gonzalez Sosa z open SUSE tvrdí že:
Můžeme si všimnout velkého nárůstu právě uživatelů Factory.
Z července 1952 uživatelů na 5969 uživatelů na konci srpna. Factory téměř trojnásobně zvýšila počet instalací, anichž by nějak poškodila Tumbleweed. ( 5471 instalací v červenci a 5637
instalací v srpnu)
Nicméně jak je vidět, že Tumblewed instalace klesají.

Dokonce Greg KH z tumbleweed a vývojář ace Linux předpovídá, že Tumbleweed může skončit uplně.
Factory se trefila do černého, uplně zapadá do mého pracovního modelu. (konstantně updatuje stabilní distro.).
Jako openSUSE uživatel (spouštím také Kubuntu, openSUSE a Arch Linux na mých počítačích)
Už jsem na Factory a funguje skvěle – vždy běží poslední balíčky.
Pokud se chcete přesunout na Factory doporučuji tento článek (v angličtině)
Swapnil Bhartiya
6 září 2014
Zde je článek ze kterého jsem čerpal


FFG 2014 button

The annual GUUG Frühjahrsfachgespräch 2014 will take place in two weeks from now, from September 23.-26. at the Ruhr-University in Bochum, Germany.

The agenda is packed with interesting sessions covering a wide range of topics relevant to developers and system administrators. In addition to the regular talks, the first two days provide day-long tutorials to get a deep-dive into interesting technologies like OpenStack, Puppet, secure web development or setting up file services.

I'll be speaking about reStructuredText and Sphinx, a very powerful framework for writing technical documentation.

Register now!


Al mediodía de hoy fui contactado por una corresponsal de BBC Mundo para conocer mis comentarios sobre el tema. (Sugerencia de un buen amigo periodista, Arturo W.). Pongo acá el enlace a la publicacion en la Web de BBC Mundo. Ademas de mis palabras, incluyen comentarios de Don Yeoman, del JPL de NASA; de Bill […]


ACTUALIZACION: Unos 30 minutos despues de posteado esta entrada y de haber sido mostrada en 100% Noticias (en donde claramente hice notar la falta de sustento del video),  varios amigos que me siguen en Facebook lograron desmentir este video. Excelente movimiento pro-investigacion critica! ——————————- Paren las prensas! O mas bien, el teclado! Por favor su […]


GSoC:My journey with openSUSE begins

Hello everyone, I am Gopesh Tulsyan from India.I got involved with openSUSE community during GSoC to add features to OSEM(Open Source Event Manager Application).I am currently studying  Information Technology in National Institute of Technology, Durgapur ,India.

During GSoC I added two big features to OSEM, one is the Event Splash Page for Visitors and the other is Email Notifications.This was my first time with open-source project and it was really great.I learnt a lot while fixing bugs and adding new features.Previously, I had already worked with Ruby on Rails application by freelancing for some projects, but this time I learnt the coding standards for a fully-fledged software in use.

My Way to Work

So the general way that I worked was my mentor James Mason, segregated my project into various To-Do’s in  a Trello Board with a checklist to keep track of things I am currently working on.We also used the GitHub ticketing system but that was mainly for the bugs.So I used to pull the small modules(to-do cards) from To-Do’s to Doing(board) .After compeletion I used to send a Pull request for my mentor and other members to review to my patch and I used to move that feature on Trello from Doing to Blocked with a PR link.James used to review it and if there was any room for improvement then he just shifted back the card from Blocked to Doing with a comment on it.This used to continue until I have successfully, done that feature without any discrepancy.And then finally that feature card used to go to Done .By this practise even now I have separate record of things I have implemented during GSoC which is I already mentioned broadly at the top.

Learning Git

During my GSoC I learned git very efficiently.Prior to it I only some basic features such as pull, push, merge(branch), log were known to me.During the course I got well versed with one of the most versatile tool of git which was git rebasing branches instead of creating new one.I learnt this the hard way by redoing patch of 500 lines of code, but atlast I learnt it.Cherry picking – git cherry-pick this command is incredibly useful for including your previous work which is not merged yet to an on going feature. I used this git tool and that resulted in atomic commits.I also learnt squashing and rebasing, the fact that how to resolve the merge conflicts in stale Pull requests.


Learning Best Practises

I started pushing code with Tests for the OSEM application.My mentor told me at the beginning of the project that for every new line of code that I add I should write corresponding tests to support it for making this application less prone to bugs and thus making it robust.During the start none of my patch weren’t getting accepted

08 September, 2014


Eran las 11:04 pm del Sábado 6 de Septiembre del 2014. Me encontraba procesando unas fotos para mis álbumes en Flickr cuando de repente las redes sociales en Nicaragua literalmente estallan. Comentarios alarmados tanto en Facebook como en Twitter de un tremendo sonido semejante a una explosión que se hizo sentir en gran parte de […]

06 September, 2014


Got snail mail from DAD GmbH, Postfach 11 35 68, 20435. I should update my business info (which I never gave to them) and by submitting updated info, they would charge me 500 euro (small notice so that you are likely to miss it). I hope they go to jail for this.

05 September, 2014


wikilovemonmentsÎn luna septembrie, are loc ediția 2014 a concursului Wiki Loves Monuments. În cursul acestei luni vă invităm să fotografiați monumentele istorice din țara noastră și să le trimiteți sub o licența liberă la Wikipedia, pentru a îmbogăți enciclopedia online cu informații despre cultura și istoria României.

Anul trecut concursul a fost un adevărat succes și asta în primul rând datorită vouă, contribuitorilor: peste 140 de participanți din România au trimis mai bine de 5.000 de fotografii, dintre care un juriu experimentat a ales 10 câștigătoare la nivel național.

Pentru anul acesta vrem să vă oferim mai mult decât în anii precedenți. Avem cel mai mare fond de premiere de până acum, iar fotografiile câștigătoare vor participa la o expoziție ce va fi prezentată în București și Timișoara.

Așa că va așteptăm alături de noi încă o dată pentru a putea face parte din cel mai mare concurs fotografic ce a existat vreodată. Peste 20 de țări și-au anunțat participarea anul acesta, veți avea șansa de a câștiga premii și veți putea face România și mai cunoscută.

Pentru Wikipediștii cu experiență precum și pentru începătorii care preferă să scrie articole avem o provocare suplimentară: două secțiuni dedicate în cadrul concursului de scriere, fiecare secțiunea fiind premiată cu câte 250 de lei.

Articol preluat de pe http://wikilovesmonuments.ro/2014/09/incepe-wlm-2014/

Older blog entries ->