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.


Thursday
23 May, 2013


Michael Meeks: 2013-05-23: Thursday.

21:05 UTCmember

face
  • Up; mail chew, hand-held some odd Windows build issues - the old plague of DOS line-endings coming back to bite. Patch review, got the libreoffice-4-1 branch checked out and building.
  • Lunch. Team meeting, ESC meeting, Vojtech's staff.

face

Top of the World
I frequently get the question, by mail or over social networks:

But how do I get involved in $PROJECT?
Now a common answer is 'just do it' while others often point to resources like the KDE Developers Beginners Guide and Contribute to openSUSE, or write a simple how-to for building a package. But I usually don't actually reply with links to any of those. Mostly, people have found these resources by themselves.

What they want to know now is how to, you know, actually do it! And as that question can actually be answered rather project-independent so I thought it would be useful to write it down here.

Step one - Build the Code and get Familiar

After reading the various guides and how-to's, you set up a development environment. Be sure you can run the unstable application(s) or hack on a package. Getting that up and running is a very good first step.

I would also subscribe to mailing lists, read the blogs and hang out in IRC. Just watch what is going on: it will teach you the culture of the community and that's crucial to get stuff done later.

Step Two - Hack Something

Perhaps you will already find bugs, then: trying to report them is good, trying to fix them is better. It will not be easy to fix them but that is when you can ask for help on IRC, forums or here!

If you don't find any bugs you want to fix, perhaps you can think about what to add, what to change. What do YOU think is important and what needs to be done? It doesn't matter if you pick something yourself or find a todo list or wiki page of the project and pick something there. The hardest part will be: JUST DO IT. Get hacking. You'll get stuck, that is OK: read documentation and when you can't figure it out, just ask for help. Above all: don't give up until you are done! I would suggest not to pick something too big. A one-liner patch will take you a day, easily, and might not seem important, but this first step matters a lot. Don't try to fix the entire user interface or work flow with your first change! For example, fixing code style to comply with the project rules is already a perfectly fine first step.
Not getting Involved

Step Three - Get it in

Now you got something, so get it back to the project. On Github or on the Open Build Service you do a merge request; in other projects you have different work flows varying from sending the patch by mail to using review board or other tools. It doesn't matter.

This won't be easy, but that is mostly due to you being so anxious about it: it can take quite a while for the developers to review the patch and they're sure to have some comments on it. Don't


face
Nom : solutions linux 2013.jpg
Affichages : 169
Taille : 66.6 Ko

Le salon Solutions Linux, Libres et Open Source dévoile le programme de sa 15ème édition. Un rendez-vous au coeur
d'enjeux stratégiques pour l'ensemble de la filière numérique, qui se déroulera les 28 et 29 mai au Cnit de Paris La Défense. Structuré selon une approche métier, le programme des conférences et tables-rondes abordera les tendances actuelles

Wednesday
22 May, 2013


face

New features:
* ooldtp python client
* Support setting text on combo box
* Added simple command line options
* Support state.editable in hasstate
* Handle valuepattern in click API
* Support ToolBar type on click
* Write to log file if environment variable is set (set LDTP_LOG_FILE=c:\ldtp.log)
* Support control type Table, DataItem in Tree implementation
* Added scrollbar as supported type

New API:
* MouseMove
* setcellvalue
* guitimeout
* oneup
* onedown
* oneleft
* oneright
* scrollup
* scrolldown
* scrollright
* scrollleft

Bugs fixed:
* Fix to support taskbar with consistent index
* istextstateenabled API
* Fallback to object state enabled if value pattern is not available
* Fix to support InvokePattern on Open button
* Use width, height if provided while capturing screenshot
* Work around for copying text to clip board
* QT 5.0.2 specific changes
* Check errno attribute to support cygwin environment
* Fix keyboard APIs with new supported key controls (+, -, :, ;, ~, `, arrow up, down, right, left)
* Don't grab focus if type is tab item

Java client:
* Fixed selectRow arguments
* Fixed compilation issues
Python client:
* Fix optional argument issue in doesrowexist
C# client:
* Added new APIs (scrollup, scrolldown, scrollleft, scrollright, oneup, onedown, oneleft, oneright)
Ruby/Perl client: No changes

Credit:

Nagappan AlagappanJohn Yingjun LiHelen WuEyas Kopty, VMware colleagues

Please spread the word and also share your feedback with us (email me).

About LDTP:

Cross Platform GUI Automation tool Linux version is LDTP, Windows version is Cobra and Mac version is PyATOM.

* Linux version is known to work on GNOME / KDE (QT >= 4.8) / Java Swing / LibreOffice / Mozilla application on all major Linux distribution.
* Windows version is known to work on application written in .NET / C++ / Java / QT on Windows XP SP3 / Windows 7 / Windows 8 development version.
* Mac version is currently under development and verified only on OS X Lion. Where ever PyATOM runs, LDTP should work on it.

Download source / binary (Windows XP / Vista / 7 / 8)
System requirement: .NET 3.5, refer README.txt after installation

Documentation references: For detailed information on LDTP framework and latest updates visit http://ldtp.freedesktop.org

LDTP API doc / Java doc
Report bugs


face
  • Horrible damage in Oklahoma, encouraged to hear the first response of this guy on seeing his house not there anymore. Call with Vojtech, mail chew.
  • Booked travel to the Hamburg Hackfest - which should be great: June 15/16th. Chat with Florian. Lunch. Partner call, filed expenses.

face

“Es un nombre muy divertido, lo elegí porque se me hacía mucho mejor que sólo poner directora de una división dentro de Chrome y realmente me gusta”, explicaba Tabriz, entrevistada durante el Google I/O 2013, en San Francisco, California.

Parisa Tabriz llegó en 2007 a Google como una hacker a sueldo para ayudar a la compañía a crear soluciones de seguridad en sus diversos sistemas, y luego de seis años se convirtió en la directora de seguridad dentro de Google Chrome, con el título de Princesa de Seguridad.

Según cifras de abril del Global Stat Counter, Google Chrome es el navegador más utilizado a nivel mundial, con 39,15% de mercado, por arriba de Internet Explorer de Microsoft, que posee 29,7% y Mozilla Firefox, con 20,06%.

La experta, quien asegura que cuando no está hackeando le gusta escaparse a escalar montañas en los alrededores de Silicon Valley, dice que le encantaría ver a más mujeres dentro del área de informática no solo en Google, sino en todo el sector.

A nivel general, siento que deberían haber muchas más mujeres trabajando en temas de tecnología y seguridad. No tenemos las suficientes mujeres haciendo cosas en este sector.”, comentó Tabriz, a Grupo Expansión.

Además agregó que para que una compañía funcione bien debe “tener todos los ángulos de vista” y poseer entre sus filas gente de todas las nacionalidades, etnias y preferencias.

Fuente: CNN en Español


Tuesday
21 May, 2013


Michael Meeks: 2013-05-21: Tuesday.

21:00 UTCmember

face
  • Up early, maiol chew, poked at some calc performance regression tests Kohei has written, call with him, stats crunching; ESC bug stats & agenda collation; dinner.

face

Manten tu openSUSE actualizado con los parches de los repositorios oficiales de manera sencilla!

consola-linux-shell

Lo más seguro para un sistema operativo es estar actualizado, y que incluya nuevas implementaciones a fallos encontrados, o ciertas mejoras que mejorarán nuestra experiencia usando nuestro sistema operativo.

Y en este caso openSUSE o cualquier otra distro de GNU/Linux no es una excepción. Por lo que es bueno comprobar de vez en cuando si hay parches disponibles para instalar.

Prefiero para el manejo de software las herramientas nativas de openSUSE, por supuesto estoy hablando de YaST o zypper desde la línea de comandos. Así que quería compartir un comando que he descubierto recientemente.

Se trata del comando you en consola, acrónimo de “yast online update” es decir: actualización on-line con YaST. Un comando que no es más que un alias, para abrir el correspondiente módulo de actualización con YaST.

Para ejecutarlo teclea el comando en la consola, introduce la contraseña de root  y espera que YaST haga su trabajo, refrescando los repositorios, y comprobando las actualizaciones.

También puedes hacerlo mediante YaST → Software → Actualización en línea

Estas actualizaciones instalarán SÓLO parches oficiales, no actualizaciones de programas no soportados, o software de repositorios de terceros. Eso tendrás que hacerlo mediante zypper up.

  • En este cuadro de diálogo, puedes seleccionar los parches que quieres descargar e instalar.
  • La lista de la izquierda muestra los parches disponibles y el tipo de revisión (seguridad, recomendado u opcional), así como el tamaño estimado de la descarga.
  • Esta lista contiene, normalmente, sólo los parches que todavía no están instalados en el sistema. Puedes modificar esta opción activando la casilla de control Incluir parches instalados debajo de la lista.
  • El campo Descripción del parche contiene una explicación más amplia del parche que está actualmente seleccionado. Pulsa en un parche de la lista para ver su descripción.

Enlaces de interés

————————————————–



Alionet: GNOME 3.8.2

13:19 UTC

face
Cliquez sur l'image pour l'afficher en taille normale

Nom : 38-tile.jpg 
Affichages : 555 
Taille : 11.5 Ko 
ID : 1855

GNOME 3.8.2 a été officiellement lancé le 16 Mai et il dispose d'un grand nombre de correctifs, d'ajouts de documentation et de mises à jour de traduction, sans oublier les

face
When I started this series of 'Organizing oSC13' posts I wanted to make three main things. 
  1. Blog about what it takes to make oSC13
  2. Include things that could be useful in the future to people who will take over the next conferences
  3. Inform people how things are going out of a strictly personal sight
Now I warned you before, this blog contains explicit content. If you are easily shocked or feel offended when someone talks a bit dirty then please stop reading. A lot of documentation can be found elsewhere.

Having said that I continue :D

Now so far I haven't wrote anything about the actual progress of the conference. Today I will write about it.

So far we have 36 people working on tasks on https://trello.com/osc13 which is where we put tasks and work on them. 
Now let's talk in numbers:

So far we have 111 total tasks separated in 3 sections. The Sections are Program - Promo - Venue.

We have a total of 22 tasks in Program. From those 22 tasks we have 17 on 'To Do', 1 on 'Doing' and 4 on 'Done'.

We have a total of 64 tasks in Promo. From those 64 tasks we have 11 on 'To Do', 15 on 'Doing' and 38 on 'Done'.

We have a total of 25 tasks in Venue. From those 25 tasks we have 15 on 'To Do', 4 on 'Doing' and 6 on 'Done'.

We also have tasks that were finished even before reaching https://trello.com/osc13 , like articles or gathering some equipment that we already have in our possession.

In order to finish all that tasks many work hours where spent, many people were on to them and many fights between us where given so that we succeed the best possible result. This is something I really want to point out. We fight over a lot of things, mostly because we want to do things perfect, have in mind that this is a good thing and in the end of the day we are more bonded than before. We are closer because we understand more the person we are working with. This leads to less fights and better results as we continue. If you have a solvent character those fights make you better in many ways. 
One thing I really like this year is that everyone of the people I've worked with so far is ready to take one for  the team. Another is that we all want the same thing, to make this Conference the best possible.

If you have some time and you want to be a part of this team then join us at https://trello.com/osc13 and help. If you have the will to do things, even if you feel you can't do anything, there are people there who will be happy to help you finishing tasks. Help needed, help wanted and help can be provided.

face
Cliquez sur l'image pour l'afficher en taille normale

Nom : skype-logo-placeholder.png 
Affichages : 559 
Taille : 20.9 Ko 
ID : 1851
Une nouvelle mise à jour majeure de Skype pour Linux a été publiée par Microsoft, et c'est l'une des plus grosses, jusqu'à présent.

face

Heya,

Tomorrow LinuxTag starts again. There'll be an openSUSE booth, although we won't be overstaffed this year. If you're up for helping, that would be greatly appreciated. You don't have to be a super technical person to be at a booth and help out: if you follow some blogs around openSUSE you already know more than most visitors and you can help out just fine! It's how I got started...
























See you at LinuxTag! You can find us Geekos at Hall 7.1a, Booth 130.

Monday
20 May, 2013


Michael Meeks: 2013-05-20: Monday.

21:00 UTCmember

face
  • Up early, mail chew; plugged at some make check failures, and tested build pieces on Windows and Linux. Built slideware, Lunch. Back to mail, debugging and patch review for the freeze. Worked late.

face

前幾天上課時剛好有個學員在詢問 .bash_logout 的使用問題,他希望每次登出時將 HISTORY 紀錄清空,預設操作十分簡單,將 history -c 指令語法添加到 $HOME/.bash_logout 即可,但學員反映怎樣測試都是會失敗。後來做了一個簡單的測試,確認一下 .bash_logout 是否有運作:

echo "Bye....." > $HOME/.bash_logout

然後嘗試登出系統後,會出現:

user@Host2:~> exit

logout
Bye.....

所以證明 .bash_logout 有正常運作,那麼為什麼我們的 HISTORY 紀錄沒被清空呢 ? 其實並不是沒被清空,而是在 $HOME 路徑下還有一個 .bash_history 檔案記住相關 HISTORY 紀錄,若各位還有印象預設我們的環境變數中有指定一個 HISTSIZE 與 HISTFILESIZE 兩個,預設當我們下達 history -c 時會將暫存區內的紀錄清空,也就是清除 HISTSIZE 所記錄的資料筆數,但檔案內的紀錄仍舊存在,因此下次登入系統後仍舊會看到之前存放在 .bash_history 檔案內的相關指令操作紀錄。解決方式如下:

user@Host2:~> cat .bash_logout

history -c
cat /dev/null > $HOME/.bash_history

這樣便可以解決無法清空紀錄檔案的問題 ~


face

ConsensusJono blogged about respect in community discussions. I have zero to say on the storm-in-a-teacup (his words) that started it other than, perhaps, suggest that when there are waves, there is wind. But whatever direction that wind blows, I'd like to focus on something else. Jono made the following statement:

Ubuntu is not a consensus-based community. Consensus communities rarely work, and I am not aware of any Open Source project that bases their work on wider consensus in the community.
I'm not entirely sure what he means with consensus and community here. He himself defines community as "a collection of people (or animals) who interact with one another in the same environment". Consensus decision making, according to Wikipedia, is:
"a group decision making process that seeks the consent of all participants. Consensus may be defined professionally as an acceptable resolution, one that can be supported, even if not the "favourite" of each individual"

Talking consensus

Let me take this as an opportunity to address a common misconception about consensus: that consensus means full agreement. The Wikipedia entry already points out that the outcome has to be 'acceptable', one that 'can be supported'. This matters: Jono probably meant to say that there is no sizeable community where everybody fully agrees on every decision and I can't imagine he is wrong on that. But that is not what consensus means.

(dis)agreement

The reality is that in a large and diverse group of people, it is impossible to really reach full agreement on any sufficiently complicated matter. Making decisions on agreement of all participants thus doesn't work. Consensus, instead, allows a decision to be made even in the face of disagreement. Essentially, it is a form of democracy without voting.

Ever heard the phrase: "Let's agree to disagree"? That is it: at some point in a decision making process, consensus requires some of the participants to be mature enough to step out of the way and let a decision actually get made. And others need to respect them for that.
No consensus

Voluntairy

What makes consensus different from voting?

Usually, those in a small minority are the ones who have to (wo)man up and accept that the decision and project is more important than them. The main difference between voting however, where minorities (anything below 50%, usually) don't get their way, is that it is not mandatory. In some cases, the minority can get their way and it can be the majority which steps back and lets them. And even if that doesn't happen, the difference between being forcefully over-ruled and gracefully accepting that you can't always win is big.

A second key point is that ruling by consensus requires discussion, much more than voting does. You can't make decisions by consensus without informing people of the choices - you have to know what you (dis)agree with. Certainly, a community where a few take decisions without talking about it does not decide based on


face

How can I get paid for free software development? That's a question many developers ask. And it's a good question, because software development is expensive, no matter what the license is. Money is one way to pay for this, but fortunately there are many other ways to get paid for free software. The one thing you should never do, though, is to sell free software cheap.


It's tempting. Put some ads on your blog, a donation button on the project page, get a low paid student job, etc. It's fine, if you can work on free software, right? Some money is better than nothing, isn't it?

No, it isn't. Because it interferes with other ways of being compensated for free software development, such as reputation, control, freedom, learning, or just satisfying your curiosity. Money adds dynamics which can go against these. It changes to whom you are accountable, it alters expectations, and it can actually harm your motivation, because money is a bad motivator. So you need to be very careful when putting money into the equation.

That doesn't mean that there are no good ways to get paid money for free software development. In fact an increasing number of companies have realized that they are better off developing a good part of their software as free software, and they don't compromise on quality or payment. So there are well-paid jobs for free software developers. Guess who gets these jobs. Not those who do it for cheap, but those who have built up a good reputation as a free software developer.

Contributing to free software actually is a great way to build up a career. You are in control. You don't need a university or company program, you can start any time. You can build a reputation doing something you want, something that matters. You can learn and grow following your passion. This is a great foundation for a professional career, and studies show that committers to free software actually get higher salaries than those who don't do this.

Your work on free software is an investment in your happiness, your career, and a better world. Don't sell it cheap.

face

Tým openSUSE s potěšením oznamuje, že nový milestone, nadcházející verze openSUSE s číslem 13.1, je dostupný pro testování. Jelikož se jedná o rané vydání, lze očekávat, že nebude příliš funkční nebo stabilní. Uvítáme oznámení chyb a zasílání oprav problémů. Toto je první krok ze série nadcházejících vydání, která budou končit vydáním stabilní verze 13.1 a to v listopadu 2013. Jako obvykle nejvýznačnější změny v openSUSE 13.1 Milestone 1 přichází z upgradů, kterými prochází balíčky.

Hlavní updaty softwaru

  • GNOME 3.6 > 3.8.1
  • apache2 2.2.22 > 2.4.3
  • digikam 3.0.0 > 3.1.0
  • giflib 4.1.6 > 5.0.3
  • icecream 0.9.7 > 1.0.0
  • kernel 3.7.10 > 3.9.0
  • libreoffice 3.6.3.2.4 > 4.0.2.2.1
  • ocaml 3.12.1 > 4.00.1
  • qemu 1.3.0 > 1.4.0
  • qt-creator 2.6.2 > 2.7.0
  • ruby 1.9.3 > 2.0
  • systemd 195 > 202
  • wpa_supplicant 1.1 > 2.0
  • xorg-x11-server 1.13.2 > 1.14.1

Nejvíce otravné chyby

Seznam nejvíce otravných chyb je stále krátký. Zraky upíráme na vás, prosím pomozte nám prodloužit délku seznamu. Potřebujeme zjistit, co je špatně, abychom to mohli opravit. Chyby nám můžete hlásit tady. Proces hlášení chyb zahrnuje jen několik kroků, které můžete udělat pro přispění do distribuce. Hlášení chyb a problémů je nepostradatelné pro zachování stability openSUSE. Prozkoumejte sekce jak přispět do factory a zasílání oznámení o chybách.

Jste více než vítaní při organizování bug-finding-and-squashing sezení! Koukněte na předchozí snahy na naší poslední beta-pizza-party!

Plánované změny

Před nějakým časem tým openSUSE zveřejnil seznam navrhovaných změn pro openSUSE 13.1. Učinil tak s myšlenkou skloubit změny poptávané komunitou s cíly jednotlivých týmů. Mějte prosím na paměti, že tento seznam slouží ke změnám a zároveň pomáhá pochopit to, kam chce vydání openSUSE směrovat.

Pro základní systém plánované změny zahrnují update GCC na verzi 4.8 a práce na integraci poslední verze kernelu. U bootování se diskutuje o kompletním přechodu na systemd a zahození sysv initu. Stejně jako nahrazení mkinitrd za dracut.

Prostředí KDE zvažuje zahrnutí podpory pro gstreamer 1.0 a výměnu kopete za KDE telepathy. Gnome plánuje přechod na verzi 3.10, úklid starých knihoven a změnu základního témata na více zelenejší verzi.

V případě bezpečnosti je zat


face

Volunteer and make a difference!
Master oSC13 Kostas just published his “only 58 days to go” blog in his series of daily how are we doing posts and it should be clear that with less than two months to go, we’re getting close! openSUSE conference 2013 is already just around the corner… And starting today, you can sign up to volunteer and help out at the venue!

Join the Team

Many people are already helping with the organization in trello.com/osc13 – if you have not seen where we are yet, just follow the link and check it out! We want to organize our event as openly as possible, and Trello is a great way of doing that.
Join the Greeko Team!
But there is more than preparation. We also need an ‘army on the ground’: the people who make it happen on the conference days! If you want to get more involved and help out during the conference days, you can apply to be a volunteer for oSC13 by filling out the form at http://bit.ly/10s5HDJ. We need you!

Training

One important thing to have in mind is that ALL Volunteers must attend the Volunteers Training, which means that you have to be at the venue on the 18th of July at noon. This year the training of the volunteers will be something you have never seen before. Beyond the regular volunteer training you will be able to get some basic knowledge on First Aid and how to react on-site in case of emergency or disaster (such as a fire or an earthquake). All the training will be conducted by professionals. Our purpose is for volunteers to acquire knowledge that can be used basically everywhere.

The Awesome Greeko's at oSC12 in Prague

The Awesome Greeko’s at oSC12 in Prague

About oSC13

As a quick refresher of your memory, this year the openSUSE Conference takes place in the beautiful city of Thessaloniki, Greece. The to-be-awesome event is organized by our Greekos, an elite team of Greek contributors to openSUSE.

The event is shaping up to be a one-of-a-kind, bringing together the beautiful beaches with the incredible history of Greece in one inspiring place. And you can be a part of it!


face

Meetings-planning-searching-meetings and here we go again meetings-planning-searching-meetings. Of course not always with that turn and some times with even more meetings. Having A LOT of meetings is the necessary 'evil' when organizing a conference. In meetings you get to interact with other people, get feedback and generate new ideas out of the interaction. You get to know what is going well and what it does not, where you need more things to be done and where you need less things to be done. What works and what it doesn't. Nevertheless meetings although they are necessary for the organization hide what I think is the biggest enemy of an organization. This enemy is Paralysis by analysis.

An experienced person should be able to recognize this after a while but the thing here is that if you fall into this loop, you will have time lost and time as I said before is really precious when you organize an event. Given the fact that within reasonably boundaries anything that you plan can take place, time is your only obstacle. It is the mail reason why many good ideas are left out of the organization of many conferences over the years.

This leads to the conclusion that recognition of Paralysis by analysis after the fact is not enough. When starting to organize something always have that in the back of your head. Avoiding it is not that difficult but at some points require to have a good programming of the meetings. What I've noticed over the year is that most of the times people who cause this are the people who lead and most of those times this happens for 2 reasons.

Case 1: Someone has an idea and you know that this idea is either not viable at the timeline you have or it has failed in the past(there are other reasons too but those are the most common). Now you try to convince this person that you should not do that for X reasons. The person is convinced that the idea is perfect and disagrees with you and you all fall in the loop of trying to prove your point. So after a while you spend more time talking that the actual time that would take for this to be done or for this to be failed. You should have a vision of either let the person do this (if you can afford it) or to have this person directed to documentation or other people so that the person will go look for it and see your point. This problem can be partially predicted while reading the agenda of the meeting and knowing the people you work with. Reading the agenda of the meeting before is always important.

Case 2: I often call that The conference bag problem. You and your team have an idea that will make the conference great. There should be a certain limit of how much time you will spent on talking about anything

face

openSUSE konference 2013 se blíží, zatímco náš tým pilně pracuje. Vyjádřeno čísly: máme dvě nová propagační videa, na výběr ze sedmi hotelů na stránkách konference a pouze 5 týdnů do 17. června, termínu vašich přihlášek.

openSUSE konference – Řecko!

Blíží se chvíle, kdy budete moci navštívit openSUSE konferenci 2013. Tentokrát se setkáme ve fantastickém městě Soluň (Thessaloniki) v Řecku. Naši vyslanci pracovali dlouho a tvrdě, aby zajistili všechny nezbytnosti pro účastníky. Konference se bude konat v Olympic Museu a nutno podotknout, že nemohlo být vybráno lepší místo. Evokuje většinu toho čím naše komunita je - tým lidí usilující o společný cíl.

Pamatujte na to, že ubytování je na vás samotných, ačkoliv projekt poskytuje místa, kde se můžete ubytovat za snížené ceny. Prosíme, přečtěte si více o možných místech ubytování v Soluni (Thessaloniki). Program na podporu cestování minulý týden informoval o dostupnosti finanční podpory dosahující až 80%, pro ty kdo přijedou z velké dálky. Jako vždy jsou zde kritéria, která musí být splněna pro obdržení této finanční pomoci, ale pomoc je dostupná a náš Travel tým je pro vás připraven.

Propagace

Prosíme, pomozte nám šířit informace o konferenci. Čím více lidí ví co se kolem nich děje, tím pravděpodobněji se zapojí. Tato událost je skvělou příležitostí propagovat tým kolem openSUSE jako celek. Vzhledem k nedávnému vydání openSUSE 12.3 media zeširoka popsala vývoj distribuce. Naše konference je tak dalším zaostřením na propagaci projektu. Můžete si stáhnout propagační bannery, letáky a plakáty na adrese https://conference.opensuse.org/#promote pokud máte blog, Facebook, Twitter nebo Google Plus nebo jiné sociální sítě. Nové propagační video je připraveno zde.

V chodu!

Ujistěte se, že máte odeslánu svoji přihlášku, a váš hotel a let jsou rezervovány. Prosíme, šiřte informace o konferenci i v případě, že ji nemůžete navštívit. Všichni můžeme být součástí úsilí o zvýšení povědomí o openSUSE týmu.

Ti kdo navštíví konferenci, by měli být připraveni aktivně přispívat k jejímu průběhu. Prosíme, buďte si vědomí, že týmové úsilí zahrnuje kohokoliv, a když jste na konferenci, tak můžete být požádáni o pomoc s organizováním věcí, které jste možná ani neplánovali. Očekáváme entuziasmus a ochotu přispívat!

Nyní nastal čas pro ty, kdo nejsou


Sunday
19 May, 2013


Michael Meeks: 2013-05-19: Sunday.

21:00 UTCmember

face
  • Up lateish; NCC - visiting speaker: empty cross + tomb & occupied throne. Back for lunch, Peter over - caught up with him through the afternoon. Played with babes in the garden and slugged in the evening happily.

face
Cliquez sur l'image pour l'afficher en taille normale

Nom : Failgeeko.png 
Affichages : 805 
Taille : 31.3 Ko 
ID : 1850
Croyez-le ou non : une voiture a percuté le bâtiment du bureau de SUSE à Nuremberg. Les geekos locaux vont bien, mais l'alimentation des serveurs devra être arrêtée pour que les réparations puissent

Saturday
18 May, 2013


Michael Meeks: 2013-05-18: Saturday.

21:00 UTCmember

face
  • Up earlyish; mail chew, poked at builds, and helped babes with games; M. struggling with the concept of minesweeper. Breakfast, out to Noughton Park for a wander around - various tree climbing feats, and a fine wander. Back for a disgracefully late, large, fried breakfast/lunch thing.
  • E. out to Sue's to play with Sophie; checked and re-started a Windows build.
  • Pleased to read theregister's take on 3D printed guns - only for the incredibly wealthy, deranged individual that likes to kill at ultra-close range. Annoyed by self promotion and the stupid knee-jerk responses it produces. There is a photo of a far more dangerous, and often cheaper device here, with which you can make a reasonably functional gun that 'actually works(TM)'.
  • One of the supreme amusements of life is that as soon as you do anything you think is cool & new you find out it's already been done before: see this neat new 3D printer thing ? turns out you didn't meet the self-replicating "anyone who has a lathe can build a lathe" mob of yesteryear (did you miss the industrial revolution perhaps ?). But wait ! surely these un-controllable, self-replicating 3D tools are a radical threat to the civilised world ? - time to ban the lathe, milling machine, drill-press ... toothbrush etc. ? Perhaps not.
  • Dinner. Argh - git submodules just beat me up again when I least needed it - translations module acting stupidly, and refusing to update - combined with trying to remove that submodule (can you even remove submodules? - and failing).

face

El equipo de desarrolladores de Amarok se complace en anunciar que desde el 15 de mayo está disponible la versión 2.7.1 del magnífico reproductor de audio de KDE, que lleva por nombre código ”Harbinger”.

Para los que no conozcan Amarok, os pongo la definición del propio equipo de desarrollo:

Amarok es un potente reproductor de música para Linux, Unix, MacOS X y Windows con una interfaz intuitiva. Hace que escuchar las canciones que te gustan así como descubrir nueva música sea más fácil que nunca – ¡y además lo hace bien!

 

Este nuevo lanzamiento se dedica básicamente a arreglar algunos errors, como uno bastante molesto en la interacción entre QtWebkit y GStreamer que hacía que fuera imposible una reproducción continua.

Además de este error se han solucionado otros como:

  • Una modificación en el manejo de la etiquetas de identificación de MusicBrainz para evitar problemas con pistas falsamente duplicados.
  • Solucionado un comportamiento extraño cuando se respondía a la pregunta “Use Music Ubicación?” con un “Si”.

Amarok-2.7.1-Screenie

  •  La base de datos que se crea en el directorio home ahora puede contener caracteres non-ASCII
  • Nepomuk Collection puede ahora mostrar los número de canciones.

Más información: Amarok

Descarga: Código Fuente


face

190px-FailgeekoLo creáis o no: un coche se ha estrellado contra las oficinas de SUSE en Nuremberg.
No os alarméis, nuestros geekos están bien, pero para poder reparar las instalaciones el edificio se mantendrá cerrado durante un tiempo.

De esta forma, nos podremos encontrar algunos problemas de disponibilidad de nuestros servidores los próximos días.

¡Esperemos que las cosas vuelvan a la normalidad la próxima semana!

Más información: openSUSE News

No related content found.


face

Failed geekoBelieve it or not: a car crashed into the Nuremberg SUSE office building. Our geekos are fine but the power will have to be shut down so repairs can take place. You can expect some availability issues for our servers the coming days. Hopefully things will be back up next week!


face

KDE4logo_75x75Con la corazón puesto en KDE 5, los desarrolladores del magnífico entorno libre no dejan de lado la evolución natural de KDE 4 y ya ha anunciado las primeras características que nos ofrecerá KDE 4.11, entre las cuales se encuentran:

  • Se añaden botones de arriba/abajo al editor del menú para facilitar su uso
  • Capacidad para ordenar las entradas en los sub-menus
  • Se añade un botón de configuración en las notificaciones
  • Se añaden varios plugins en Kate
  • Se añade soporte para Ogg Opus en Juk
  • Numerosos añadidos en Plasma comienzan a re-escribirse en QML
  • Previsualizaciones rápidas en Dolphin

Aprovecho para recordaros el calendario de lanzamiento de las versiones beta, RC y definitiva:

  • Miércoles, 12 de Junio de 2013: Lanzamiento de KDE 4.11 Beta 1
  • Miércoles, 26 de Junio de 2013: Lanzamiento de KDE 4.11 Beta 2
  • Miércoles, 10 de Julio de 2013: Lanzamiento de KDE 4.11 Release Candidate 1
  • Miércoles, 24 de Julio de 2013: KDE 4.11 Lanzamiento de Release Candidate 2
  • Miércoles, 21 de Agosto de 2013: Lanzamiento de KDE 4.11

¡KDE Rocks!

Vía: Libuntu | Ostatic


Friday
17 May, 2013


Michael Meeks: 2013-05-17: Friday.

21:00 UTCmember

face

face

Die openSUSE Entwickler haben den ersten Meilenstein zur kommenden Version openSUSE 13.1 zum Herunterladen und Testen bereit gestellt. Wie immer bei so einer frühen Entwicklungsstufe läuft diese Version noch nicht stabil und man muss ggf. mit Fehlern rechnen. Dieser erste Meilenstein bringt hauptsächlich Aktualisierungen verschiedener Pakete mit sich. In openSUSE 13.1 werkelt jetzt der Kernel 3.9 und Systemd ist in der Version 202 enthalten.

Einige Paketupdates in 13.1 Milestone 1:

  • GNOME 3.6 > 3.8.1
  • apache2 2.2.22 > 2.4.3
  • digikam 3.0.0 > 3.1.0
  • giflib 4.1.6 > 5.0.3
  • icecream 0.9.7 > 1.0.0
  • kernel 3.7.10 > 3.9.0
  • libreoffice 3.6.3.2.4 > 4.0.2.2.1
  • ocaml 3.12.1 > 4.00.1
  • qemu 1.3.0 > 1.4.0
  • qt-creator 2.6.2 > 2.7.0
  • ruby 1.9.3 > 2.0
  • systemd 195 > 202
  • wpa_supplicant 1.1 > 2.0
  • xorg-x11-server 1.13.2 > 1.14.1

Als Desktops sind KDE SC 4.10 und/oder Gnome 3.8 dabei. Für die finale Veröffentlichung von 13.1 sind dann aber KDE SC 4.11 und Gnome 3.10 geplant. Weiterhin ist geplant in 13.1 den IM-Client Kopete durch KDE-Telepathy zu ersetzen und den Gnome-Desktop stärker mit einem grünen Theme anzupassen. Ob letztendlich in der finalen Ausgabe der Kernel 3.10 oder sogar 3.11 enthalten sein wird ist noch nicht entschieden und wird noch diskutiert.
Das gleiche gilt auch für den Komplettersatz von Sysvinit durch Systemd. Bis November, wenn die finale 13.1 erscheint wollen die Entwickler ganz auf Sysvinit verzichten. Aber wie gesagt, sind auch hier noch nicht die letzten Würfel gefallen.

Die Entwickler bitten um ausgiebige Test und reges Fehler melden. Selbstverständlich sollte eine so frühe Testversion keinesfalls auf produktiven Systemen genutzt werden.
openSUSE 13.1 Milestone 1 kann von der Downloadseite des Projektes herunter geladen werden. Zur Verfügung stehen wie immer DVD-Images, Live-Images mit Gnome und KDE, Netzwerkinstallation-Images und auch seit openSUSE 12.3 Rescue-Images.

Quelle : openSUSE News
Golem.de


face

A few years ago, I gave a history of the 2.6.32 stable kernel, and mentioned the previous stable kernels as well. I'd like to apologize for not acknowledging the work of Adrian Bunk in maintaining the 2.6.16 stable kernel for 2 years after I gave up on it, allowing it to be used by many people for a very long time.

I've updated the previous post with this information in it at the bottom, for the archives. Again, many apologies, I never meant to ignore the work of this developer.

Older blog entries ->