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.


Wednesday
19 June, 2013


face

Georg Greve 2013 The openSUSE conference will feature Georg Greve as first keynote speaker, opening the event on Friday morning. He will talk about “Freedom in the world we live in and the value and importance of communities and Software Freedom”. That’s a mouthful and we’ve asked him to tell us a bit about himself and what he’ll talk about.

Personal life

We managed to catch him just before he was going to Hamburg for the holidays with the family, actively cleaning up the house and preparing for an early leave the next morning. Georg, born in ’73 on the tiny island of Helgoland outside the coast of northern Germany, spent the first 8 years of his life in this reclusive community before moving to the big city. There he studied biophysics and came across Free Software in 1993. Five years later he was the European speaker for the GNU Project, writing the well known ‘Brave GNU World’ column and in 2001 he initiated the Free Software Foundation Europe. Since 2009 he is the CEO of Kolab Systems AG and lives with his wife and “two utterly gorgeous” twin boys in the neighborhood of Zurich, Switzerland.

Free Software

We asked him about what he will share with us at the openSUSE Conference.

Georg: “I’m sure everybody is aware of current events around the leak of Prism. Watching it all unfold has been interesting from a variety of angles, both for our communities as well as the larger version of community: society at large. It is awesome that people look at what is going on, care and get upset. But at the same time, it is weird that they get upset now as much of this has been known for quite a while. If you cared for this topic at all you could have learned all of this from public sources in the past. Not with such detail and in such depth or with the drama, but the gist of it was actually not very much hidden. The fact that the USA treats its own interest above everything else and isn’t shy to use its power, knowledge and military for its self interest and most importantly the interest of its corporations isn’t exactly news. It has been like this for quite a while and they have been quite upfront about it.”

Jos: But at least people are angry about it, now…

social media logos

Frenemies?

Georg: “People are shocked. But a few years too late. It is good that they are but we should ask the question: why is it worse to give your data to the government (which may use it in name of the corporations) rather than giving it to the corporations directly?

And people give their data willingly. Even the public sector is affected, just last week the Swedish government banned Google Apps usage in Sweden. They noted that it could not be guaranteed that the data would remain private. News, really? Perhaps there will be some rethinking


Tuesday
18 June, 2013


face

At the risk of stepping on other people’s toes let me apologize before I start. I am certain we have many members in the community that have gone out of their way to overcome hurdles placed in their way by our “organization” or others. I was inspired by this story because it shows how dedicated our community members are and it really fits well with some of the issues we are still struggling with in the transition from Boosters to SUSE team and the transition between initiatives, Ambassadors to Coordinators and shipping of DVDs to boxes of promo material for designated events.

Peter Czanik was caught in the middle of all of this at a recent FSF conference where he and others had an openSUSE booth. With no DVDs being shipped, due to the transition in the promo material shipping procedure (this has been announced) and no money available through TSP for local production of marketing materials due to a snafu (a temporary solution is in the works) there was basically no help from the resources where help should be coming from, sorry about that Peter.

Despite these obstacles Peter and the team showed up and made due with what was available to have great success. In Peter’s words:

“”"”
- distributed the last few remaining openSUSE 12.2 DVDs. Many people complained, that it’s not the latest and greatest, but also many were happy, as they have an old machine and older Linux versions usually have lower resource requirements.
- reused the posters we printed last autumn to decorate the booth (at the end of the day they were in a sorry state, so can’t be reused any more…)
- used the few remaining openSUSE brochures, stickers we printed last year (printing was contributed last year by somebody working at a printing company and our company printer…)

- used my ARM machines and a few borrowed mini PCs to demo openSUSE and make the booth eye catching (people asked about the machines and went away with openSUSE DVDs and brochures )

So, in short: last autumn we had local contributions from community members, this year we used what was last few bits of it and some creativity.

The good thing is, that I was told from multiple directions, that openSUSE had the best booth among software projects at the conference (and they did not know, that it was from a ZERO budget…).

The bad thing is, that we don’t have any marketing materials left. No DVDs, posters or brochures.

“”"”"

There is no need to rose color the situation, leaving community members trying to represent openSUSE at a conference stranded like this should not happen and there is no excuse for creating this situation in the first place. Work is proceeding to address these issue. However, I want to focus on the positive, and that is undoubtedly how determined Peter and the team were to make the conference a success and how they overcame the obstacles presented to them.

Thank you


Monday
17 June, 2013


face

The openSUSE Conference 2013 is ad portas and the media has already caught on to this Open Source event in Thessaloniki, Greece. There was a recent request for having an ad about the openSUSE Conference featured in a German Linux magazine. I quickly jumped to the action looking for ideas on what ways are more effective in delivering an ad about our project.

The first thought was to make something that talked about the conference and the things that will make the conference shine. However, a second thought also came through. The openSUSE Conference is just the result of a much bigger project, the openSUSE Project. If we are to feature an ad about our conference it should be centered on the project and not the conference necessarily.

Why? Because there are many conferences and events every year. It is hard for the general public to know and acknowledge the differences of conferences around the Linux world. However, there is only 1 openSUSE Project. The conference's main event is not the conference itself, it is openSUSE. Therefore, I thought that rather than having the conference-made logos and graphics, we should focus on the main event, openSUSE.

In the end, this is what will go on the magazine. I hope you like it!



Michael Meeks: 2013-06-17: Monday.

21:00 UTCmember

face
  • Up earlish, staggered downstairs before the babes left for school for a chorus of hugs & beautiful Father's day cards.
  • Really pleased to see the announcement of MIMO joining The Document Foundation Advisory Board. MIMO support the LibreOffice ecosystem by contracting developers to fix their bugs and improve LibreOffice for everyone.
  • Chat with Cloph, lunch. Chat with Marcos from Brazil, working on improving the equation editor. Fixed up some Arabic / UTF-8 in C++ that I pushed, apparently some compilers can't cope, dug at some bugs, reviewed a patch or two. Mail chew.

face

Hi!

This week in Barcelona:

Thursday 20, at 19:00 - Barcelona on Rails monthly meeting
XING's office at Consell de Cent 332
Topic still to be defined
http://barcelonaonrails.com/


The Barcelona Graphic + Web Design Meetup Group
Thursday, June 20 at 8:30 PM
http://www.meetup.com/graphicdesign-159/events/gfcdnyrjbbc/



face

As a consequence of the recent changes in the repositories, the openSUSE KDE team is happy to announce the availability of packages containing the first beta of the KDE Platform, Workspaces and Applications 4.11. 

Packages are available in the KDE:Distro:Factory repository. As it is beta software, it may have not-yet-discovered bugs, and its use is recommended only if you are willing to test packaging (reporting bugs to Novell’s bugzilla) or the software (reporting bugs directly to KDE). For specific queries on the 4.11 beta not related to specific openSUSE packaging, use the KDE Community Forums 4.11 Beta/RC area
Have a good test!


Sunday
16 June, 2013


Michael Meeks: 2013-06-16: Sunday.

21:00 UTCmember

face
  • Off to the hack-fest, lots of people there, poked at some horrible performance problem in a participant's monster document; interesting - lots of styles. Michael S. found and fixed an evil writer most annoying bug in 4.1, caught up with Astron, lots of fun. Caught up with Tim as I left, a good hack-fest.
  • Lengthy train (must remember to be in the right end of the Hamburg airport train - note to self: listen to Stephan harder); plane; coach; other coach; bed tired.

face

no osc13 for me

I’m not going to osc13


Sunny sky, rainy heart today.

Two days ago, I took the decision to not assist the certainly most fabulous openSUSE Conference next July in Thessaloniki.


A conjunction of several factors lead to that decision.
First what I regret was the chosen date. Damn July is the only expensive period to travel to Thessaloniki. The plane ticket never drop below the 800€ (hey! for sure I want to have Françoise with me), especially with the late announce of precise days. May, June, September would have been so cheaper…
I can understand the choice main sponsor SUSE do, and their need to spread osc and SUSECON at a 6 month delay in the year’s schedule, but sadly does not work for me this year.

Thessaloniki port

Thessaloniki port


Secondly after February marketing hack-fest, I missed (I still don’t know how) the opportunity to get my travel reimbursed by the TSP and then loose half of the budget for osc. Before TSP get improved, and send a bounce email to ask you to send back your forms. So if you are sponsored for osc, fill and send back your expenses quickly after the event. Don’t believe you do it, check twice you really do it! Don’t suppose, be sure!

Another side, I already knew that a customer project will happen during that time-frame. As it concerns a lot of partner’s I’ve to take in account the availability of each of them. Unfortunately, after believing that it could be doable to free-up time for osc I decide to stop persecuting myself, and make a deal to live in peace and go ahead: no osc this year.

Maths have their say: statistically, more osc will be, more the chance to miss one will increase :-) ( I know still not a real excuses)

I would like to share my deep apologizes to the whole Greek Community in charge of OSC13. You all know, how I was and still am a big found of your commitment and really appreciate each of you.
I will all miss you!

I really hope osc13 will stay in history as one of the ever greatest conference organized.

Don’t worry Thessaloniki, I know how great the place is, kind the people are, etc..
I’ll be back soon!

Αχ Θεσσαλονικη – Αντωνης Βαρδης


Saturday
15 June, 2013


Michael Meeks: 2013-06-15: Saturday.

21:00 UTCmember

face
  • Off to the hackfest, great to meet up with a trickle of people old and new coming to hack on fun stuff. Realised that my list of invisible things in 4.1 - missed Eike's great continuing work on langtag / bcp47 etc. Also Bjoern / David O / Norbert's awesome gerrit / on-demand multi-platform build integration: select a sha1 hash to be built on all three systems and wait for the result. Poked at the docs for that with David.
  • Pushed Benjamin's patch, got Issa setup with push access and his new flat icon theme included; got Rolf setup with some comment translation. Caught up with the KACST guys, poked at lots of bits of code variously, fixed a number of UI / ergonomic issues. Up until 4am hacking with the hardest of the hard-core guys - struggling with some awful bugs.

Friday
14 June, 2013


Michael Meeks: 2013-06-14: Friday.

21:00 UTCmember

face
  • Up early; E's fifth Birthday, present unwrapping and playing with at breakfast - fun. Off into Cambridge with J. and Emily - bus to the airport, plane to Hamburg, caught up with Thorsten, admired his new eco-flat, on to the meal / meet-up in the evening (kindly sponsored by Lanedo) - up rather late talking over this and that.

face

Before focusing my spare time completely on the GSoC* (as I have mentoring responsibilities this year \o/ ), I wanted to solve a problem that cannot wait after July...

Yes, I've been victim of Google's cuts too... And I was wondering, where should I move? Feedly? ThingyBob? Well, I shouldn't make the same mistake twice, right?

Actually, some time ago I was using a desktop app to avoid relying on software that I cannot control (yes, vendor lock-in, the most important thing that open source tries to solve, right?): Thunderbird. But somehow the convenience of a web app (that I can access from any computer) and the hassle of using my mail client for RSS reading made me move to the web.

I should be able to find a replacement that no company or individual can "take down", and which feels less clunky than Thunderbird for reading RSS. So, enter blam (in the future I'll figure out how to sync its state between computers, maybe using SparkleShare?, to achieve that same convenience that a web-app provides), that Gnome app that has strangely managed to not catch my eye until now...

Well, maybe because if I install it from debian sid and I try to import my very first RSS feed from my GoogleReader list it doesn't work? Well, apparently it is a bug that is already fixed upstream, thanks to Carlos which has modernized the way that the program deals with XML and serialization.

Then I went ahead and tried to compile master myself... and guess what, the autogen.sh execution fails. Here the yak shaving begins, when I feel like this when trying to fix the autotools stuff:


Fortunately, after some tinkering (and some copy&paste from banshee's build scripts), I managed to fix the problem, and also modernized a bit some things (like using the brand new ".ac" extension instead of ".in" for the configure script, or using properly the AC_INIT and AM_AUTOMAKE_INIT macros,...).

Anyway, the real thing to highlight here is that while I was fixing this stuff and pushing to the repository...


... I saw some really good stuff committed by Carlos: using the new .NET 4.5 C# async patterns to get rid of those ugly callbacks! Kudos to him.

And if you're willing to help more with our autotools housekeeping, please do, I still feel this autogen.sh is way too long and needs some ironing.

* And if you're wondering what's up with GSoC (aka Google Summer of Code):

  • I had Nicholas Little lined up to work on Rygel+Banshee integration, but sadly he couldn't apply due to work commitments (hopefully he will still work with me on it in his spare time).
  • I had Rashid Khan lined up to work on Cydin+Banshee integration, but sadly there were not enough GSoC spots for him :( (fortuntately he told me he still wanted to work on it with me in his spare time).
  • I had Tomasz Maczy


face

Since KDE has released the first beta of Platform, Workspaces, and Applications 4.11, there will be some changes in the packages offered in the openSUSE repositories.

In short:
  • KDE:Distro:Factory will now start tracking 4.11 betas and RCs: packages are being worked on. Use this version to test packages and to report bugs upstream.
  • KDE:Release:410 has been decoupled from KDE:Distro:Factory. If you were using 4.10 packages from KDF, you’re highly encouraged to move to this repository.
  • KDE:Unstable:SC will keep on carrying snapshots from KDE git repositories.

If you test the 4.11 packages, report bugs in the packaging (or openSUSE-specific functionality) to Novell’s bugzilla, and bugs in the software to bugs.kde.org. Also, please use the dedicated area on the KDE Community Forums to discuss issues.
Let the testing commence!


Thursday
13 June, 2013


face

It's been almost 18 months since I last made any change to this site, and I've been meaning to do it for a while. In all honesty, it's been a while since I last blogged so I thought it was as good a time as any. Thanks to the likes of Twitter and Google+, and my corporate blog I'm finding myself blogging less an less.

As my blog is getting less content, is it really worth running an sql server etc? I don't think it is. There's the system overhead (I'll explain why I'm thinking about system overhead in another post), the maintanence of a critical component, the backups etc. WordPress is OK, but it really is overkill for simple blogging. After seeing peers, friends, and general interweb related buzz, I finally decided to move and use a static site generator. Problem is which one - there are loads?! I read and an LWN article which somewhat helped, so now I needed to choose. I finally bit the bullet and went for Nanoc after recommendations from trusted people.

So far I'm loving it. I had already started to get into Markdown, so creating content using the language was easy enough (I'm by no means an expert though). I get most of the functions that I want straight out of the box, it renders perfectly regardless of browser - desktop or mobile, it is immensly portable, backups are a breeze, and overall maintanence is simple. I regularily ask myself why I took so long to make the move.

As part of the move I've also rejigged URLs etc, so if you crazily had my blog bookmarked for whatever reason you will need to update. I've not quite finished fiddling yet, I've not implemented comments yet, but you could always use G+ or whatever in the meantime. I also want to tweak the theme and some other bits. I'd like to thank Marcus Ruckert for helping me with some of the code tweaks, Peter Aronoff for the current theme and some ideas.

openSUSE Conference 2013 I'm Going to oSC13


Michael Meeks: 2013-06-13: Thursday.

21:00 UTCmember

face
  • Up, pushed a blog about where we're at, technically with our 4.1 betas, and with some credits for our hidden heros. Pleased to see Minh push his first VLC integration work to our GSOC feature branch. Dug into some callgrind traces.
  • Team meeting, ESC meeting, Vojtech's staff.
  • Really pleased to see the LibreOffice 2012 conference videos show up, you can enjoy them, slides have been up for a long time. Perhaps it's a great time to watch a video and then book for LibreOffice conference 2013 - September in Milan/Italy - to best the see progress.
  • Booked coach to the Hamburg Hackfest tomorrow - it should be great. Dinner. Poked at a horrible leak with StarView meta files compounded by piles of architectural lunacy.

face

Rather soon we will be releasing LibreOffice 4.1—currently we're in a Beta phase of that, and we appreciate people getting stuck in and helping with testing. You can download builds from here pre-releases or if you like some up-to-the-hour builds from dev-builds.

( This post is also available in French )

We're still building our list of features and credits. We have a number of new visible features of course with credits against them. Cor has made a pair of beautiful blog entries highlighting UI improvement and the Photo Album features in 4.1. That made me think of the many developers who have been working extremely hard on things that are under the covers and not so easily seen, but are still really important. I'd like to explain just some highlights of that here, (crediting the developers' employer where there is one at the first mention). Often these are tasks that are easy to get involved with, and may seem trivial in isolation but cumulatively add up to a code-base that is far easier to understand and to contribute to.

Build system: configure / make

One of the tasks that most irritates and has distracted new developers from doing interesting feature work on the code-base over many years has been our build system. At the start of LibreOffice, there was an incomplete transition to using GNU make, which required us to use both the horrible old dmake tool as well as gnumake, with configure using a Perl script to generate a shell script configuring a set of environment variables that had to be sourced into your shell in order to compile (making it impossible to re-configure from that shell), with a Perl build script that batched compilation with two layers of parallelism, forcing you to over- or undercommit on any modern builder; it looked something like this:

# old and awful
autoconf
./configure --enable-this-and-that
source LinuxIntelEnv.Set.sh
./bootstrap
cd instsetoo_native
build --all

Thanks to the stirling efforts Björn Michaelsen (Canonical), David Tardon (Red Hat), Peter Foley, Norbert Thiebaud, Michael Stahl (Red Hat), Matúš Kukan, Tor Lillqvist (SUSE), Stephan Bergmann (Red Hat), Luboš Luňák (SUSE), Caolán McNamara (Red Hat), Mathias Bauer (Oracle), Jan Holesovsky (SUSE), Andras Timar (SUSE), David Ostrovsky, Hans-Joachim Lankenau (Oracle) and more—(more details) the 126 thousand targets, and 1700 makefiles are now fully converted to GNU make so we have the significantly simpler:

# LibreOffice configure & make as of now:

./autogen.sh --enable-this-and-that
make

No shell pollution, no 'bootstrap' script, no Perl build wrapper, no obsolete 'dmake' required, just plain GNU make files—and incredible build parallelism—after generating headers, we could utilize a thousand CPUs. This is a clean-cut task with a clear boundary; like the process of removing dead code in previous releases, it is now complete—freeing up developers for more interesting things.

Graph of gnumake vs. dmake conversion by version

Build system: make dev-install

LibreOffice, in contrast to much other software, is fully relocateable—you can plonk it down where you like, and run it from


face

Michal Hrušecký has been helping out on maintaining Factory in shape and shares his experiences.

Factory is development version of openSUSE and it is where the next openSUSE is taking form. Hundreds of packagers send packages into Factory to be integrated as a part of the new release and many more use Factory for testing or for their daily work. Thus it is really important to keep Factory rolling and usable. Everybody knows that Coolo is the Factory master and he does everything to make next openSUSE be the best ever. But keeping factory in shape is really complicated and stressing task. There are dozens of request everyday and each one of them can potentially break something. So Factory can always use a pair of extra hands and for some time I have been one of them. I’d like to give you some insight in what we do, working on keeping Factory building and working.

obs-logo

Keep it building

With a constant influx of newer and cooler versions of libraries and tools it is easy to break existing applications with shiny new software. So we always have some build failures in Factory. Part of our job is to resolve them because if it doesn’t build, you can’t test nor ship it. As developer, you may have seen submit request in various projects in OBS fixing builds for Factory. Everyday I take a look at a number of build failures, investigate why they are not building in Factory and try to do something about it.

For example new version of the GNU C Compiler (GCC) is quite often more strict on includes, requiring developers to be more verbose about the exact internal and external libraries there applications require to be build. What used to build now doesn’t, because you are missing include files. The older GCC let you slip by, but now you have to fix it, build failure by build failure. Another example is GTK which keeps deprecating old API functions and you have to keep up and replace them with correct counterparts from the new API. Sometimes even the kernel changes API and third party modules stops building. All these errors will get eventually resolved upstream (if upstream is alive), but as we follow upstream quite closely before feature freeze, it may happen that we are first facing these issues because sometime we are the first ones who tried to compile this software using new GTK or the new GCC. Of course, we attempt to get these fixes back upstream and share them with other distributions where appropriate!

Factory_workflow

Image depicting the Factory Workflow

Test it

Another important part of working on a better Factory is testing. If everything builds, we’re happy. You might have heard the saying:

if it builds, ship it!

(un)fortunately, this isn’t Coolo’s idea of how the world works. In Factory, things not only have to build, but also work. Oh, AND conform to some stringent requirements. Here


Wednesday
12 June, 2013


face
  • Up early; patch merging, mail catchup, partner call, worked late.
  • Disappointed with 'Arch Memory' on Amazon, whose memory did not work work with my W500, even after BIOS upgrades, North Bridge reset etc. and who refused to refund return postage. Tried Crucial instead - lets see if they can do better, or if it's jusy my hardware / BIOS.

face

This was a problem I didnt think I would face while getting a new laptop. I got the Toshiba C580 laptop, which has quite decent specifications. It is a nifty machine, and openSUSE works more or less flawlessly. The only issue I faced was with the Wireless card. It is a Realtek device, which is usually well supported, but this particular model, the 8273AE is yet to be fully supported by the kernel. I had to dig around a lot to get this to work, but received a lot of help from the openSUSE forums, and managed to get it to work. Thanks to lwfinger for writing the patch to get it to work properly.

1.) Use YaST to install the Kernel Development, C/C++ development and Base Development patterns

2.) Download the compat-wireless package from
http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2012-10-03.tar.bz2

3.) Download the patch from
http://www.lwfinger.com/realtek_drivers/rtl8723ae_master_patch

4.) Run the following commands

tar jxvf compat-wireless-2012-10-03.tar.bz2
cd compat-wireless-2012-10-03/
patch -p1 < ../rtl8723ae_master_patch
make
sudo make install

5.) Check if the driver is working with
sudo modprobe -v rtl8723ae

This should get the driver working properly

Source: http://forums.opensuse.org/english/get-technical-help-here/wireless/477285-rtl8723ae-realtek-wirless-driver-hell-3.html



Tuesday
11 June, 2013


Michael Meeks: 2013-06-11: Tuesday.

21:00 UTCmember

face
  • Up early, mail chew, continued to wrestle with cairo canvas & compositing. It seems the bane of my life is VCL's horribly unhelpful design around separate alpha, and some combination of pre-multiplied alpha, bogus 24bit alpha masks and worse. Eventually unwound it all, and a number of un-related issues - now it renders correctly at least.
  • Poked GSOC student, built ESC bug stats and prototype agenda, more mail chew.

face

12_1vs13_1For those of you waiting for (or working on) openSUSE 13.1, we have good news: milestone 2 is now out for you to download. As to be exptected, the inclusion of newer software versions is the highlight of this release. Broken in M1 and fixed now are automake, boost, and webyast. But first, let’s talk openSUSE 12.1: it is no longer maintained.

openSUSE 12.1 no longer maintained

openSUSE 12.1 has reached end of life. This release came into the world on the 16th of November 2011, giving it a life span of about 19 months. With openSUSE releasing new versions every 8 months, this means there are already a 12.2 and an 12.3 – with 13.1 to be released by the end of this year! For 12.1 users, the time has come to move on to a newer version and benefit from more, better and faster software!

As the announcement from the security- and maintenance team explains:

openSUSE 12.1 was the first openSUSE distribution maintained using OpenBuildService methods (known as “OBS Maintenance”), allowing full community participation, from the beginning.

Currently, there are no plans to add 12.1 to the evergreen-project. If something changes, I’ll inform you as soon as possible.

Here are some statistics of our released updates (compared to 11.4):

  • Total updates: 789 (+65)
  • Security: 389 (-28)
  • Recommended: 398 (+92)
  • Optional: 2 (+1)
  • Fixed CVE-entries: 1508 (+193)
  • Fixed Bugs (overall): 1874 (+319)

The increase of the resolved issues is related to the easier participation in working on openSUSE with the OpenBuildService.
Thanks on this point to our awesome packagers, community and OpenBuildService-Team!

Your maintenance- and security-team

Changes, changes: openSUSE 13.1 M2 is out!

With M2 out, openSUSE 13.1 is still in an early period of development and lots of changes are coming. The most notable list of changes made in Milestone 2 includes:

  • livecds using overlayfs now with persistent hybrid support
  • automake 1.12.1->1.13.2
  • boost 1.49.0->1.53.0
  • util-linux 2.21.2->2.23.1
  • evolution 3.8.1->3.9.1
  • gtk3 3.8.1->3.9.0
  • icu 50.1.2->51.2
  • iproute2 3.7.0->3.9.0
  • kernel 3.9.0->3.10.rc4
  • libreoffice 4.0.2.2.1->4.0.3.3.2
  • MozillaFirefox 20.0->21.0
  • pulseaudio 3.0->4.0
  • qemu 1.4.0->1.5.0

For Milestone 3 the major goals are to bring Perl 5.18 and GCC 4.8 on board. You can get Milestone one from software.opensuse.org.

Most Annoying Bugs

The list of most annoying bugs is still short. We’re looking towards you to help us make that list bigger! We need to find out what’s wrong so we can fix it. You can report bugs with this link. The process of reporting bugs involves a couple of steps that you can take in order to contribute with the


face
Today I feel like talking about history. The history of all the openSUSE confernces in the past. If I made my research right the first openSUSE Conference was in 20-23 of October in 2010.


Here are some graphics that was used at that time. I really find them interesting since I like history and I believe that a lot of lessons can be tought by history. I don't really know much about oSC10 since I was really new to the openSUSE project at that time and I hessitated on going there at that time. Looking back now I think I made a mistake not going there. Of course I found this out when joined the second conference in 2011 which also took place in Nuremberg from 11 to 14 of September in 2011. This was a lifetime experience. If you ever joined an openSUSE conference I am sure you all remember your first time there. It was amazing since I was a volunteer and I went to Nuremberg one day before the conference and there I had Allan Clark making pins, Juergen Weigert making the lights and a bunch of other top coders carring arround stuff in order to set up the venue. No Rock stars there, just people who are devoted in openSUSE and in making the conference work, for all.

 Then it was oSC 2012. This was different for me. The Greeks were so close at taking oSC2012 but when Prague also claimed it we took a step back since we understood and we knew that we were not 100% ready for it. We needed more people for the Greek community to get practically involved with it so that next year we would have even more experience and feedback. You see sometimes stepping back is better.
We joinned oSC12 more active than oSC11 and we tried to do the most we could and we learned a lot there. The idea though was the same, people hanging around and talk to each other. There was no need to know someone from before or to be friends from before. Afterall the meaning of the conference is also to have people meet and talk F2F. I have to say here that I made actuall friends in all oSC's, people that I am happy to hear their news beyond openSUSE matters. People from all over the planet and this is something you can't do sitting in front of a keyboard.



 Then we finally got the oSC13 to Greece. Not many things stayed as originally planned but this is only a good thing. We are prepairing a conference that for the first time is organized exclusively by the community and it is planned to be friendly to everybody and to produce a lot of work for the project. If you have any hessitations on comming to the conference because you don't know people or you fear that you will be a stranger among strangers forget it. Just track someone

face
When I presented Polka, my experiment to reframe the user interface for address books, some people suggested that it would be interesting to try something similar for todo lists. So I did try. The result is a small app called Bliss, because it makes you happy and gives you peace of mind.


I started with taking the concept from Polka to have freely arrangeable items on a canvas organized in groups. That works, but it had a flaw, because the basic element of todos is not the individual item, but a list.

Todos are much more dynamic than information about people. You create, remove, and rearrange them all the time. Context matters. One powerful effect of writing todos down is that you relieve your brain from having to constantly make sure you don't forget about them. This only works, if it's easy and quick enough to structure and arrange the todos according to your mental model. Lists are the natural structure here to keep priorities and order.

So basically a group became a list, where you can reorder items by dragging them around, either within the list or to other groups.


But in addition to this it's also quite useful to have multiple lists in one view. You can for example model a flow between things to do today, this week, and this month, where items in one list are replenished from the next one. Or you can have something like a personal Kanban with lists for things to do, being done, and done. Or you can use a scheme like in the Getting Things Done method. The combination of groups and lists is pretty powerful here.


Bliss keeps the complete history of what you did, so you can always look or go back without cluttering your views with done items. It animates all the transitions when moving items or navigating groups, so you don't lose context when items are rearranged or you change the view. Especially when dealing with such dynamic objects like todo items, animations really make sense, not as eye-candy, but as a way to support you in keeping track of what's happening. That said, they also make the app more fun to use.

The menus are done in the same way as in Polka, as semicircular context menus, which works nicely not only with the mouse, but also on a touch screen.


The code is in the KDE git as well as on GitHub. If you want to give it a try and play around with the UI you can get it from there. I'm happy about feedback.

The technology behind this experiment doesn't matter much. It's mostly reusing Polka code, a QGraphicsView based Qt GUI with an Kode-generated XML backend, which stores data in a git repository. To move forward it would be nice to redo the UI in QML and connect it to Akonadi. But the more interesting part it experimenting with the user interface

Monday
10 June, 2013


Michael Meeks: 2013-06-10: Monday.

21:00 UTCmember

face
  • Up early; mail chew, tried to test remote-X over ssh behaviour, and ended up falling foul of this ssh / IPv6 issue, worked around that. Chewed through some code reversion / tweaking.
  • Pregnancy Crisis Centre annual meal in the evening - rather nice to catch up with all that came and enjoy some food together.

Jos Poortvliet: oSC2013 next!

17:44 UTCmember

face

After Akademy 2013 in Bilbao, we will fly (via Berlin...) to Thessaloniki, Greece, where the openSUSE Conference will take place. Like I argued for Akademy, oSC is a relevant and useful event for the openSUSE folk.

History - oSC 10, 11 and 12


This year oSC takes place in Greece, a fact far more relevant than it might seem. The first three openSUSE Conferences I attended took place in Nürnberg. First in a conference center, the third was the legendary oSC2011 in the Zentrifuge, an old factory building creating an absolutely amazing atmosphere. Both events were largely organized by SUSE employees from the Nürnberg office but oSC11 already had a fair involvement of volunteers and a strong focus on BoF sessions and 'getting stuff done'. We had a lively marketing and ambassador team by then. I vividly remember the day before the event, when I rode a van full of crazy geekos by a few stores, buying everything from carpets and plants to lights to dress up the location. Every day we figured out who would staff the bar, organize stuff in the rooms - and moving the chairs was a matter of asking outside if a few folk would be willing to help out. At this event, there was already talk about doing the openSUSE conference in Greece.
Hallo with openSUSE, LibreOffice, Gentoo

First Prague

But going from doing the event in Nue and by SUSE people (with help) to doing it in Greece by volunteers (with help) seemed a big step and the team also had limitations as to the date and time: the event would have to be in May or June. As it was already September when oSC'11 took place, that was very close.

There came a different proposal from Michal and others in Prague, and with an office there, we decided it made much more sense to do it there and told Kostas that he'd have his oSC in Thessaloniki, but one year later. I joined Michal in scouting for a location in Prague and discovered a local community was about to organize another Linux event a mere two weeks after the openSUSE Conference! I proposed to merge the two, and the format of oSC'12 was born. Like oSC'10 two years earlier, this event tried to focus on collaboration and bringing communities together. I unfortunately had to scale back my involvement in the conference significantly after LinuxTag Berlin in May 2012 due to health issues and barely could make it to the event itself. Meanwhile, the Greeks had already started preparing the organization of oSC'13 and were present with a large team at oSC'12 to help run the show.


Greece in 2013

Feedback from the event did show that the openSUSE community wanted more 'Geeko time', so the Greek team has made sure that there will be a good openSUSE focus at the event. Of course, without compromising our open nature: there will be plenty colors besides green. Naturally, SUSE input will be lower


face

the openSUSE Conference kicks off in less than 6 weeks! The conference Paper Committee has been receiving and judging a lot of presentation proposals and while there is still time to send in papers, a number of sessions has been confirmed already. In this article we will present you some of these sessions!

Community and Project

The Community and Project track gathers talks around openSUSE and community activities, quoting the CfP page: “including but not limited to project governance, marketing, artwork, ambassador reports, collaboration with other FOSS communities and other topics”.

statistics geeko inside

Find the geeko

Currently accepted talks will introduce local openSUSE communities, intro the new ambassador and merchandising programs and discuss Free and open in general.

One particularly interesting subject will be openSUSE statistics. It is given by Athanasios Ilias “zoumpis” Rousinopoulos, student and Greek openSUSE ambassador from Spain (long story…) and Alberto “aplanas” Planas from the openSUSE team. They will each talk about numbers in a different area. Zoumpis is a MSc student doing research on doing quantitative analysis on communication in Free Software projects. He has studied the openSUSE repositories, mailing lists and bugzilla and extracted information from them. He will analyze the activity of the openSUSE community with interesting graphs and statistics!

Alberto has been working on measuring statistics before, during and after the openSUSE release. How many downloads does openSUSE have, how many installations? And where do these numbers go? This gives interesting insights in where we, as a community, are going and what options we have before us.

Geeko Tech

An interesting array of speakers will give attendees insight into the inner workings of openSUSE during the great workshops and talks on the Geeko Tech track. Although it often seems that openSUSE works by an act of magic, reality is that there are very dedicated developers behind it. Here is a snippet of sessions dealing with the more technical aspects of openSUSE.

Volunteer and make a difference!

Starting with the Open Build Service, Henne Vogelsang will deliver a two-part masters workshop on how to get your packages processed by OBS. Ranging from the conception of new packages to updates for older releases, Henne will show the way.

Making sure that openSUSE stays stable is important for a good User-distribution relationship! What started as a way to improve quality for the final release of openSUSE by Bernhard Wiedemann became a important project to improve development of openSUSE. Through his mighty Perl scripts openQA is able to provide information to users about the state of openSUSE’s stability during development. A workshop and a talk dealing with the subject will teach attendees to use openQA to find and report issues and build further test cases, helping make sure that we all have the best openSUSE available.

Other talks include Lars Vogdt presentation of openSUSE’s infrastructure, showing what’s behind building and serving a Linux Distribution; a review of what openSUSE can do to make a tastier Raspberry Pi, making sure that openSUSE’s installations are secure and how you can carry


face

If you are not a criminal, please publish your PIN, bank account password, email/facebook passwords and complete medical history. You don't have anything to hide, do you?


Sunday
09 June, 2013


Michael Meeks: 2013-06-09: Sunday.

21:00 UTCmember

face
  • Out to Church on the Green, sadly not a terribly sunny day: cold even. Back for lunch, watched HSM 2, out for a cycling expedition en-masse. E. managed her full length cycle, and won the babes an ice-cream: finally.

Saturday
08 June, 2013


Michael Meeks: 2013-06-08: Saturday.

21:00 UTCmember

face
  • Up lateish, slugged variously; H. and Charlotte out to netball, and took the babes onto the race-course for more cycling practise; E. nearly got did the whole length of the race-course drive under the trees, but just missed it; great progress though. Home, tea, bed.

Friday
07 June, 2013


Michael Meeks: \2013-06-07: Friday.

21:00 UTCmember

face
  • Up early, call; dug away at EMF+ issues with Fridrich & Thorsten. Mail chew, more poking at corner-cases and rendering quality. Charlotte over in the evening for a sleep-over with H.

face

Database ServerRecently I had some time to do some clenaups/changes/updates in server:database repo regarding MySQL (and MariaDB). Nothing too big. Well actually, there are few little things that I want to talk about and that is the reason for this blog post, but still, nothing really important…

MySQL 5.5, 5.6 and 5.7

MySQL 5.6 is stable for some time already, so it’s time to put it in the action. So I sent the request to include it in Factory and therefore in openSUSE 13.1. There is off course a list of interesting stuff you might want to take a look at before you update. If you don’t want to update, you can install mysql-community-server_55 from server:database repo and stay a little bit longer with version 5.5. On the other hand, staying with old versions is boring, so you can also switch to mysql-community-server_57 which provides new MySQL 5.7. So if you are into databases and especially into MySQL and forks (we have MariaDB 5.5 and 10.0 as well), we have plenty of toys for you to play with.

NOTE: Having MySQL 5.6 in openSUSE 13.1 doesn’t mean switching default back to Oracles MySQL, M in LAMP still means MariaDB for whatever it is worth. It just mean, that you have MySQL 5.6 as an alternative available if you prefer it.

Default configuration

One of the interesting changes that happened in MySQL 5.6 is new default configuration. MySQL usually shipped with some examples of configuration that you can use. It  was there since forever and never changed, although typical computers went from 256M of RAM to 8G. It contained some buffers sizes and various other optimizations. I heard various complains that it would be better shipping without it than with the one that is there. What folks at Oracle did was drop most of it and replace it with pretty much empty one, with various settings commented and described. They probably heard the same complains :-D I consider it a really good step. Defaults are bult-in after all, so why to put them in config file? So I took theirs, added few things. For example Barracuda file format. It was set to be default upstream for few versions but they decided to go back to Antelope. But it’s also one of the thing people complain to me the most about – that they have to set file_per_table and Barracuda manually. And I added examples for multi configuration that we for some reason have included and exposed. This same config file will be pushed to MariaDB as well.

If you are interested in current state, you can see the config file on github and if you have some suggestions that everybody can benefit from, let me know either via comments or via pull request on github ;-)

 

Older blog entries ->