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.
Note that you may use those keys with or without pressing the alt key.
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.
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.
I cut out the shield shape by first sawing the straight sections, and then using a coping saw on the curved ones.
I used a spokeshave to smooth the convex curves on the sides.
The curves on the top are concave, and the spokeshave doesn't fit. I used a drawknife for those.
This gives us crisp corners and smooth curves throughout.
On to planing the face flat! I sharpened my plane irons...
... and planed carefully. The cutoff from the top of the shield was useful as a support against the planing stop.
The foot shows through once the paper is planed away...
Check out the 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.
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.
Here is the first coat of boiled linseed oil after sanding. When it dries I'll add some coats of shellac.
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.
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 …
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.
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.
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.
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.
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.
Finally, I clamped everything against another board to distribute the pressure. Let's hope for the best.
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.
The 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 .
“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,
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.
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:
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.
Leap’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:
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.
"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.
A 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?!” :)
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.
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 […]
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 […]
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 […]
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 […]
Since 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.
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 […]
“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 …