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.


Tuesday
28 July, 2015



face

For a short while, the Plasma Mobile forums were hosted outside of the official KDE Forums. In our quest to put everything under KDE governance, we have now moved the Plasma Mobile forums under KDE’s forums as well. Enjoy the new Plasma Mobile forums.

As a few users had already registered on the “old” forums, this means a smallish interruption as the threads could not be quickly moved to the new forums. We’re sorry for that inconvenience and would like to ask everyone to move to the new forums.

Thanks for your patience and sorry again for the hassle involved with that.


Monday
27 July, 2015


face
  • An inlaid GNOME logo, part 5

    Esta parte en español

    (Parts 1, 2, 3, 4)

    This is the shield right after it came out of the clamps. I had to pry it a bit from the clamped board with a spatula.

    Unclamped shield

    I cut out the shield shape by first sawing the straight sections, and then using a coping saw on the curved ones.

    Sawing straight edges

    Coping the curves

    All cut out

    I used a spokeshave to smooth the convex curves on the sides.

    Spokeshave for the curves

    The curves on the top are concave, and the spokeshave doesn't fit. I used a drawknife for those.

    Drawknife for the tight curves

    This gives us crisp corners and smooth curves throughout.

    Crisp corner

    On to planing the face flat! I sharpened my plane irons...

    Sharp plane iron

    ... and planed carefully. The cutoff from the top of the shield was useful as a support against the planing stop.

    Starting to plane the shield

    The foot shows through once the paper is planed away...

    Foot shows through the paper

    Check out the dual-color shavings!

    Dual-color shavings

    And we have a flat board once again. That smudge at the top of the sole is from my dirty fingers — dirty with metal dust from the sharpening step — so I washed my hands and planed the dirt away.

    Flat shield

    The mess after planing

    But it is too flat. So, I scribed a line all around the front and edges, and used the spokeshave and drawknife again to get a 45-degree bevel around the shield. The line is a bit hard to see in the first photo, but it's there.

    Scribed lines for bevel

    Beveling with a spokeshave

    Final bevel around the shield

    Here is the first coat of boiled linseed oil after sanding. When it dries I'll add some coats of shellac.

    First coat of linseed oil


Saturday
25 July, 2015


face

At Blue Systems, we have been working on making Plasma shine for a while now. We’ve contributed much to the KDE Frameworks 5 and Plasma 5 projects, and helping with the transition to Qt5. Much of this work has been involving porting, stabilizing and improving existing code. With the new architecture in place, we’ve also worked on new topics, such as Plasma on non-desktop (and non-laptop) devices.

Plasma Mobile on an LG Nexus 5

Plasma Mobile on an LG Nexus 5

This work is coming to fruition now, and we feel that it has reached a point where we want to present it to a more general public. Today we unveil the Plasma Mobile project. Its aim is to offer a Free (as in Freedom), user-friendly, privacy-enabling and customizable platform for mobile devices. Plasma Mobile runs on top of Linux, uses Wayland for rendering graphics and offers a device-specific user interface using the KDE Frameworks and Plasma library and tooling. Plasma Mobile is under development, and not usable by end users now. Missing functionality and stability problems are normal in this phase of development and will be ironed out. Plasma Mobile provides basic functionality and an opportunity for developers to jump in now and shape the mobile platform, and how we use our mobile devices.

As is necessary with development on mobile devices, we’ve not stopped at providing source code that “can be made to work”, rather we’re doing a reference implementation of Plasma Mobile that can be used by those who would like to build a product based on Plasma Mobile on their platform. The reference implementation is based on Kubuntu, which we chose because there is a lot of expertise in our team with Kubuntu, and at Blue Systems we already have continuous builds and package creation in place. Much of the last year was spent getting the hardware to work, and getting our code to boot on a phone. With pride, we’re now announcing the general availability of this project for public contribution. In order to make clear that this is not an in-house project, we have moved the project assets to KDE infrastructure and put under Free software licenses (GPL and LGPL according to KDE’s licensing policies). Plasma Mobile’s reference implementation runs on an LG Nexus 5 smartphone, using an Android kernel, Ubuntu user space and provides an integrated Plasma user interface on top of all that. We also have an x86 version, running on an ExoPC, which can be useful for testing.

Plasma Mobile uses the Wayland display protocol to render the user interface. KWin, Plasma’s window manager and compositor plays a central role. For apps that do not support Wayland, we provide X11 support through the XWayland compatibility layer.

Plasma Mobile is a truly converged user interface. More than 90% of its code is shared with the traditional desktop user interface. The mobile workspace is implemented in the form of a shell or workspace suitable for mobile phones. The shell provides an app


Friday
24 July, 2015


face
  • An inlaid GNOME logo, part 4

    Esta parte en español

    (Parts 1, 2, 3)

    In the last part, I glued the paper templates for the shield and foot onto the wood. Now comes the part that is hardest for me: excavating the foot pieces in the dark wood so the light-colored ones can fit in them. I'm not a woodcarver, just a lousy joiner, and I have a lot to learn!

    The first part is not a problem: use a coping saw to separate the foot pieces.

    Foot pieces, cut out

    Next, for each part of the foot, I started with a V-gouge to make an outline that will work as a stop cut. Inside this shape, I used a curved gouge to excavate the wood. The stop cut prevents the gouge from going past the outline. Finally, I used the curved gouge to get as close as possible to the final line.

    V channel as a stop cut Excavating inside the channel

    Each wall needs squaring up, as the curved gouge leaves a chamfered edge instead of a crisp angle. I used the V-gouge around each shape so that one of the edges of the gouge remains vertical. I cleaned up the bottom with a combination of chisels and a router plane where it fits.

    Square walls

    Then, each piece needs to be adjusted to fit. I sanded the edges to have a nice curve instead of the raw edges from the coping saw. Then I put a back bevel on each piece, using a carving knife, so the back part will be narrower than the front. I had to also tweak the walls in the dark wood in some places.

    Unadjusted piece Sanding the curves Beveling the edges

    After a lot of fiddling, the pieces fit — with a little persuasion — and they can be glued. When the glue dries I'll plane them down so that they are level to the dark wood.

    Gluing the pieces Glued pieces

    Finally, I clamped everything against another board to distribute the pressure. Let's hope for the best.

    Clamped


face

My "Generalised Penrose pattern generator" van be seen at http://gppg.rogerwhittaker.org.uk/.

The code is available at http://code.rogerwhittaker.org.uk/gppg/.

You can build a command line executable gppg which will generate svg, pdf and ps formats, as well as a text file of co-ordinates for further processing.

Sample PDF output.


face

Leap1The newest openSUSE release Leap 42.1, which is based on core SUSE Linux Enterprise source code, has just released its first development milestone.

Milestone is being used to avoid the term Alpha because the milestone is able to be deployed without the additional future items and subsystems that will become available when Leap is officially released.

“This is where the excitement for Leap begins,” said Richard Brown, chairman of the openSUSE board. “The opportunity for topping this SLE core with the things you want in a long-term release really makes this attractive and I see people wanting to get involved with this next chapter of openSUSE.”

As Tumbleweed keeps rolling with the latest features and subsystems, Leap will fill the gap between the longevity of a SLE core and the innovation related to Tumbleweed, he said.

The quality and environmental care Tumbleweed provides with its development model should quickly translate to a top-quality distribution for Linux users, sysadmins and developers.

The milestone was moving forward with a 3 series Linux Kernel, but the Long-Term Support 4.1 Kernel, which enhances EXT4 file-system encryption and power improvements for both ARM and x86 devices, was needed for the release of the first milestone. The new Kernel was practically flawless when added to the next build, which had some minor errors. 

Updated drivers and more general improvements are expected in the second milestone.

GNOME 3.16, KDE Plasma 5 and Firefox 38 are projected for the release of Leap in November at SUSECon in Amsterdam.

Stephan “Coolo” Kulow, the release manager, provided an update on the packages for Leap. Since the announcement four weeks ago, the sources leaped from 2,000 to about 5,450 source, which about 1,150 are from SLE 12. The binary packages for the milestone currently stand at about 56,500 compared to 13.2’s 71,750 for the same measure.

If you want to see what the future of Leap will be, try the milestone and contribute to making Leap an LTS-rock release, which will have enduring updates and maintenance commitments by the community and SUSE. Part of that commitment can be seen through the recent job announcement of a Release Engineer for openSUSE.

There is currently no plans for live CDs, but expect other media formats to be added later.


face

In case you missed the openSUSE images for Docker got suddenly smaller.

During the last week I worked together with Marcus Schäfer (the author of KIWI) to reduce their size.

We fixed some obvious mistakes (like avoiding to install man pages and documentation), but we also removed some useless packages.

These are the results of our work:

  • openSUSE 13.2 image: from 254M down to 82M
  • openSUSE Tumbleweed image: from 267M down to 87M

Just to make some comparisons, the Ubuntu image is around 188M while the Fedora one is about 186M. We cannot obviously compete with images like busybox or Alpine, but the situation definitely improved!

Needless to say, the new images are already on the DockerHub.

Have fun!


face
As mentioned before: then next OpenStack Summit will take place in Tokyo, Japan from 27-30 October 2015. The "Call for Speakers" ended some days ago and now the vote for presentation period started and will end 30. July, 11:59 PDT (31. July  6:59 UTC / 08:59 CEST). 

I've submitted for Toky two talks:

  • "99.999% available OpenStack Cloud - A builder’s guide" - This talk will provide insight in how to build a highly available OpenStack cloud together with Ceph in a classical highly available data centers with e.g. two fire compartments and redundant infrastructure. The focus will be on failure scenarios and their impact on OpenStack and Ceph components, quorum devices you have to consider, strategies on how to ensure quorums and keep the cloud running, pitfalls and solutions.
  • "NFV orchestration powered by OpenStack" - This talk would be about existing OpenStack orchestration projects and how they can be used to manage a NFV Cloud, how they integrate, what is missing, and how to map these projects on the ETSI-NFV model.
You can vote, if you are interested to see my talks [1][2] at the summit, every vote is highly welcome. You can find a full abstract at the voting page.

My colleague Ralf Trezeciak submitted also a NFV related talk. He will appreciate your votes for sure, if you are interested in the presentation.

There is a long list of interesting Ceph related talks, simply use the search field on the voting page. I may provide a list in an additional post later.

Thursday
23 July, 2015


face

TumbleweedLeap’s milestone is inching ever so close to being released. The milestone is very close to being released, but it won’t come out today.

The timeline for the development of these milestones is never concrete, and while the first milestone was looking close to being released today, there was a decision to jump from a 3-series Linux kernel that was planned for developing the first milestone to a 4.1 kernel that is planned for the official Leap release.

People interested in the build and how soon it will be released can track the progress of Leap’s first milestone at https://openqa.opensuse.org/group_overview/7. When everything is green, the Leap milestone is a go. Anyone wanting to help with the following in Leap is more than welcome:

xfce – missing package to complete the pattern (fix submitted)
zdup-13.2 – missing package (bit complex)
sysauth – text needs to be reworked
rescue system – seems the CD does not boot
lxde – does not do autologin (should be using lxdm instead of xdm)

While Leap has been progressing extensively throughout the day, Tumbleweed needed some items debugged, and a snapshot was released at 1600 UTC.

There were some fixes for NFS. Few packages were added in snapshot 20150722  but several were removed. Mozilla Firefox updated to its next major release 39.0, which  enables safe browsing malware detection. Apache2 added a patch. A bash patch for a perl 5.22 fix was added. GNOME had a version update to 3.16.3 and the default kernel updated to 4.1.2.


Wednesday
22 July, 2015


Jos Poortvliet: Link

12:35 UTCmember

face
The Washington Post again demanded that tech companies create special 'golden keys' for authorities to keep and use for access to private communication. Protected by a warrant, of course. For the benefit of this discussion (which is really getting old), I just put together the reasons why it is a dumb idea.

First of all. It is a pure fantasy, an entirely unrealistic wish of the Pink Unicorn variety that it is possible to create a key which only the US goverment (and other sanctioned agencies) would have access to. It is technically not possible. Ever. I explained that before so let me now just quote Bruce Schneier:
"We have one infrastructure. We can't choose a world where the US gets to spy and the Chinese don't. We get to choose a world where everyone can spy, or a world where no one can spy. We can be secure from everyone, or vulnerable to anyone. And I'm tired of us choosing surveillance over security."
And let's be clear - we've been over this, the Clinton government wanted a similar thing with the Clipper chip and as security researcher Matthew Green pointed out:
Clipper is only one of several examples of 'government access' mechanisms that failed and blew back on us catastrophically.
A second issue with the proposal is that it doesn't do anything. Just like all the spying programs that came before in this and previous decade. Here's Bruce talking about that, here the Guardian, the Newyorker, Wired and Washingtonsblog. Whatever these spy programs do - from spying on German Chancellor Merkel to US congress (that's the Washington Post itself!) to the United Nations and Unicef - the government spying programs certainly don't target or are helpful against terrorism or pedophilia or any of the other stuff they are claimed to be for. And neither will these 'golden keys' be used to catch terrorists.

Last, and this should already be blindingly clear if you see the list above of some of the targets of surveillance, you should doubt if the government agencies will abide by the rules - they haven't in the past.

I also want to point out that the very reason we're having this conversation in the first place is because we're idiots.

face

t-shirt-motiv1A job announcement for a Release Engineer for openSUSE was published today and it offers a unique challenge, which sounds pretty cool. The optional bonus challenges to be included in the candidates’ application are:

1. Being a regular contributor to a community distribution? Point us to your work!

2. Using a programming language of your choice, write a small program that extracts all CVE identifiers from a given set of RPMs, and creates a sort index mapping CVEs to packages.

Bonus points if you can do it in 10 lines of perl. Extra bonus points if our perl experts scratch their head and ask “how does he do that?!” :)

3. Find out what changed in the minimal text installation between 13.2 and current TW and try to find the reasoning behind the changes.

Providing answers to the challenge really give people applying for the position an opportunity to stand out among other candidates.

There are many smart people in the openSUSE Community and taking part in the openSUSE Project every day constantly reminds me of how many brilliant people I work with here in Germany and elsewhere.

If you are going to apply for this position, be sure to bring your “A Game” because to make our perl experts scratch their head is quite the challenge.


Monday
20 July, 2015


Michael Meeks: 2015-07-20 Monday.

14:21 UTCmember

face
  • Mail chew, 1:1 with Kendy, Niall, lunch with H. team call. Mail chew, booked LibreOffice conference travel - thank God for RyanAir direct Stansted to Arhus; wow.

Sunday
19 July, 2015


Michael Meeks: 2015-07-19 Sunday.

21:00 UTCmember

face
  • Off to NCC, tried to help the older kidlets understand Good Shepherds; home for a pizza lunch, got singing our quartet surprisingly well in harmony. Tried to replicate that with other music - not so easy.
  • Advanced slugging, read books, lazed, Yes Minister in the evening. Bed.

Saturday
18 July, 2015


Michael Meeks: 2015-07-18 Saturday.

21:00 UTCmember

face
  • Drove to Bruce & Anne's for a combined 80th and 45th birthday party celebration; a lovely time had by all, fine food, weather, wider family company etc. Babes played a quartet or two to celebrate. Chewed mail on the way home in the car, undid some data-loss, filed an easy-hack, etc.

Friday
17 July, 2015


Michael Meeks: 2015-07-17 Friday.

21:00 UTCmember

face
  • Up early; train into Cambridge not running, struck by lightning overnight or somesuch. Drove 5x stranded others into Cambridge. Battled with awful Windows machines & hardware.
  • Meeting with Philippe & Tracie; quick lunch, back to battling hardware. Unbelievably broken Windows 7 - blue-screen and auto-re-booting with a totally generic crash-dump despite a full Acer BIOS & Intel driver upgrade, endless disk manager fiddling etc.. Attempted to install Windows 8 - after struggling to disable the horrendous anti-Linux 'secure-boot' foo - then external USB CD drive refused to play with the BIOS; irritating. Attempted to debug other thermal issues fruitlessly.
  • Home via picking up kids, relaxed watched Yes Minister with them; bit more hackery before bed.

face

Adding more to the Raspberry Pi Having already basically created a thermostat using a Raspberry Pi and a temperature monitor in conjunction with the WiFi power socket I was wondering what functionality I could add. Having looked around for a bit I found that there is a camera module available which can pick up infra-red […]


face

Running Unfortunately, it’s more running without heart rate monitoring earphones, as the fifth pair have now failed. I make that just about 5 pairs failed inside 5 months. I am not going to warranty replace these ones – there is quite clearly a flaw and I don’t really see the point in continuing to trek […]


Jonathan Ervine: Loops

06:51 UTC

face

Running in circles Another run without earphones was completed last night – I’ve reverted to using a Polar chest strap hear rate monitor whilst the Jabras are in their non-working state. Relatively faster and slow interval running last night – at over 30C and high humidity it’s not much fun. Jabra have offered to check […]


face

TV Struggles Watching live sport in Hong Kong can always be a bit of a challenge. There’s generally two providers of many things pay TV, and sometimes it feels like it’s all a bit of a stitch up. When I first arrived in Hong Kong (8+ years ago!) I signed up for nowTV with the […]


Thursday
16 July, 2015


Michael Meeks: 2015-07-16 Thursday.

21:00 UTCmember

face
  • Mail chew, ESC call, Advisory Board call, worked on financials, misc. ranking bits.

face

TumbleweedSince our last update on news.opensuse.org about Tumbleweed, a lot has happened. The rolling release now uses GCC 5 for the compiler. There was a large chunk of bugfixes and powerpc backports. The list for the July 2 snapshot was lengthy and quite a few packages were removed from that snapshot. Apparmor and many libraries a had extensive work done, but the real story about that snapshot is how GCC 5 was tested extensively in openQA and before being released as a Tumbleweed snapshot.

“Better tested/failed in openQA than tested/failed on your own machine, right?” wrote Dominique Leuenberger, the Factory master.

This proves the environmental care and trust people have with using Tumbleweed.

The next big thing coming in Tumbleweed will be Perl updates.

The July 11 snapshot focused primarily on KDE Plasma updating to 5.3.2 and providing bugfixes.

The last Tumbleweed snapshot on July 13 had minimal updates, but there is a reason. Why? Leap!

Leap’s milestone is being tested in openQA and receiving attention. People involved within Factory may want to check and submit the packages, for example xfce.

Polishing patterns will advance the release of the Leap milestone and some incomplete packages need attention.

The snapshot released 15 minutes ago just updated the Linux Kernel from 4.0.5 to 4.1.1.


Jonathan Ervine: Progress?

08:26 UTC

face

New earphones! Yep – a new set of Jabra earphones turned up yesterday. As promised by Jabra, they’ve sent me a pair of Sport Coach earphones, which are supposedly the next development from the Sport Pulse ones I was previously using and breaking wearing out in rapid time. Unfortunately, this model of earphones do not […]


Wednesday
15 July, 2015


Michael Meeks: 2015-07-15 Wednesday.

21:00 UTCmember

face
  • Spammed people wrt. regression testing ideas and started collating votes. Mail chew, poked at configmgr write noise, and odd effects around inlining in Calc.
  • Miriam returned from Thorpe Woodlands having a great time, with lots of frenetic exercise .

face

SUSE Linux Enterprise 11 Service Pack 4 was released today. It contains lots of software updates and features. For more information have a look at the release notes of our Server and Desktop version.


SUSE Linux Enterprise 11 SP4 templates

SUSE Studio supports the new SUSE Linux Enterprise release from day one. Just click on the Create appliance link after you log in and select the template you'd like to start with.


As always you can configure, build, testdrive and publish your appliance.

Configure SUSE Linux Enterprise 11 SP4 GNOME desktop

Testdriving SUSE Linux Enterprise 11 SP4 GNOME desktop

Updates

SUSE Linux Enterprise SP4 includes a lot of updates like new versions for openSSH and zypper. OpenSSH is constantly improving and gaining new and more secure cipher suites. The newest SUSE Linux Service pack ships with version 6.6p1 of openSSH which includes modern elliptic curve ciphers based on the elliptic curve Curve25519, resulting in public key types Ed25519. Also the new transport cipher "chacha20-poly1305@openssh.com" was added, using the ChaCha20 stream cipher and Poly1305 MAC developed by Dan Bernstein.

SUSE Linux Enterprise Server 11 SP4 updates also PostgreSQL to Version 9.4 which includes the new JSONB data type for PostgreSQL. With the new data type users no longer have to choose between relational and non-relational data stores: they can have both at the same time. JSONB supports fast lookups and simple expression search queries using Generalized Inverted Indexes (GIN). For more information have a look at the PostgreSQL Wiki.

Upgrade

As usual you can upgrade previous SUSE Linux Enterprise versions to the new Service Pack 4. Just go to the start tab of your appliance and click the Upgrade button at the top bar.

Different than previously, we implemented a step-wise-upgrade. That means, if you currently run on SLES11 SP3 and you want to upgrade to SLES12 you need two steps (SLES11 SP3 -> SLES11 SP4 -> SLES12) and we won't upgrade to the latest version automatically.

First step: Upgrade to SUSE Linux Enterprise 11 SP4

Second step: Upgrade to SUSE Linux Enterprise 12

In case you are not satisfied with the upgrade you can also rollback to your old appliance version. Just click on Undo upgrade at the bottom of the appliance start tab.

Rollback to SUSE Linux Enterprise 11 SP4

Happy building :)

face

Screenshot from 2015-07-15 15:11:21Developing Leap 42.1 is happening quickly and it was announced yesterday that the milestone was being built.The first milestone will hopefully be released this week. Leap is going through its testing and the importance of openQA (Quality Assurance) in this development process can not be understated.

openQA is used for testing an operating system, finding and files bugs and provides fully automated testing to ensure a distribution work correctly with clean functionality.

The wonders of openQA determine if a build is good and triggered errors allow testers and developers to see errors quickly and determine a cause.

Feel free to look at the test of the Leap milestone and use the hints below to navigate through openQA.

See what Richard Brown, openSUSE chairman, had to say about Leap and openQA on Reddit.

How To: Use openQA to find and file bugs

  • Click on one of the Red or Green dots that represent a finished test
  • You’re at the ‘Test Results’ page, this is where you can see the results of this openQA test. By default you’re taken to the ‘Default’ tab, which shows you each test module and all the screenshots taken during that test
  • Look at the screenshots, do they all make sense to you? Pay attention especially to any screenshots in rows that are marked Red/Failed..they’re probably bad and broken. Don’t always assume the Green ones are perfect, sometimes we make mistakes with our automated tests :)
  • File bugs accordingly, good bug reports should always have logs attached, luckily openQA includes many logs in it’s “Logs & Assets” Tab
  • Alternatively just skip step the last step and fix the problems right away

How To: Get the ISO used in the Tests

  • Click on one of the Red or Green dots that represent a finished test
  • You’re at the ‘Test Results’ page, this is where you can see the results of this openQA test. By default you’re taken to the ‘Default’ tab, which shows you each test module and all the screenshots taken during that test
  • Click the ‘Logs & Assets’ tab. This is where openQA keeps its logs for that test, as well as a Video recording, and it’s ‘Assets’ (aka ISO’s and HDD Disk Images)
  • Click on the ISO you want to download, in this case openSUSE-42.1-DVD-x86_64-Build0002-Media.iso
  • Congratulations, you now have the same ISO that openQA is using for testing openSUSE Leap 42.1

How To: See tests that are running

  • Click on any Yellow dots, these are the tests that are running
  • Congratulations, you’re now able to see the test running in openQA in Real Time

face

“Since when has the world of computer software design been about what people want? This is a simple question of evolution. The day is quickly coming when every knee will bow down to a silicon fist, and you will all beg your binary gods for mercy.” Bill Gates

For the sake of the users, let’s assume Bill was either wrong or (||) sarcastic.

Let’s say that we want to deliver Freedom and privacy to the users and that we want to be more effective at that. We plan to do that through quality software products and communication — that’s how we reach new users and keep them loving our software.

We can’t get away with half-assed software that more or less always shows clear signs of “in progress”, we need to think our software through from a users point of view and then build the software accordingly. We need to present our work at eye-level with commercial software vendors, it needs to be clear that we’re producing software fully reliable on a professional level. Our planning, implementation, quality and deployment processes need to be geared towards this same goal.

We need processes that allow us to deliver fixes to users within days, if not hours. Currently in most end-user scenario, it often takes months and perhaps even a dist-upgrade for a fix for a functional problem with our software.

The fun of all this lies in a more rewarding experience of making successful software, and learning to work together across the whole stack (including communication) to work together on this goal.

So, with these objectives in mind, where do we go from here? The answer is of course that we’re already underway, not at a very fast speed, but many of us have good understanding of many of the above structural goals and found solutions that work well.

Take tighter and more complete quality control, being at the heart of the implementation, as an example. We have adopted better review processes, more unit testing, more real-world testing and better feedback cycles with the community, especially the KDE Frameworks and Plasma stacks are well maintained and stabilized at high speeds. We can clearly say that the Frameworks idea worked very well technically but also from an organizational point of view, we have spread the maintainership over many more shoulders, and have been able to vastly simplify the deployment model (away from x.y.z releases). This works out because we test especially the Frameworks automatically and rather thoroughly through our CI systems. Within one year of Frameworks 5, our core software layer has settled into a nice pace of stable incremental development.

On the user interaction side, the past years have accompanied our interaction designers with visual artists. This is clearly visible when comparing Plasma 4 to Plasma 5. We have help from a very active group of visual designers now for about one and a half year, but have also adopted stricter visual guidelines in our


Tuesday
14 July, 2015


Michael Meeks: 2015-07-14 Tuesday.

21:00 UTCmember

face
  • Mail chew; calls, fixed a 'base' crasher nasty; built ESC agenda - chased slideshow horrors; wow the slideshow presenter code has just some amazing things in it - its own timer thread, queues of idle handlers and user event posting to poke other idle queueing of screen rendering bits, un-necessary UNO interfaces and much more.

face
The next OpenStack Summit will take place in Tokyo, Japan from 27-30 October 2015. The Call for Speaker period is open since some days and will close on July 15th, 2015, 11:59 PM PDT (July 16th, 08:59 CEST).

You can submit your presentations here. I myself work currently on a proposal to speak about OpenStack and Ceph HA aspects.

Monday
13 July, 2015


Michael Meeks: 2015-07-13 Monday.

21:00 UTCmember

face
  • Mail chew, 1:1 calls, lunch, dropped J to school. Team meeting. Into Cambridge, lots of fooling around with servers, swapping RAM banks, tweaking SSDs, several windows 7 blue-screens trying to format and partition a disk; eventually had to do that using Linux; DHCP mending with Vivek.
  • Philippe arrived, then Guy & Katia - lovely to meet her; out for a fine dinner all together in town; quickly back via the office, train home, bed late.

Older blog entries ->