Most recent items from Ubuntu feeds:
Didier Roche: Ubuntu GNOME Shell in Artful: Day 4 from Planet Ubuntu

Let’s continue on our journey on transforming the current default session in Ubuntu Artful with a small change today. For more background on this, you can refer back to our decisions regarding our default session experience as discussed in my blog post.

Day 4: Status icons and multiple sessions

Let’s focus today on a very small detail, but that still show up we are looking at those nitpicks before delivering ubuntu 17.10.

As I teased yesterday, can you spot what’s wrong in that picture?

Sure, there is some french involved, but I wasn’t talking about that. :) What’s happening is that the battery icon is squished on a non HiDPI display. This is coming from the fact that the icon isn’t square, and GNOME-Shell is expecting square icons, contrary to our Unity indicator power implementation. Consequently, our battery icons from our ubuntu-mono icon theme aren’t compatible in their current form with the Shell.

As we can’t separate easily the icon theme, and this one is containing a bunch of other monochrome icons we want to use by default in our ubuntu session for various applications, the “simple” fix was to prepend those special icons with unity- and having only indicator-power reading them, still being backward compatible as Ubuntu MATE is using this indicator with their own theme. (Actually, I had to quickly write a small script to rename everything in batch, as there is a bunch of symlinks in between of all those files).

The result is that now both the ubuntu and GNOME vanilla session shows up the upstream battery icon, alongside other default status icons:

And our unity session (available in universe) will display our desired set of icons:

Even if this seems a trivial issue, attention to details is always important and a crucial value we always have. Especially if we can, easily, prevent breakage on other part of the distribution and archive.

As every day, if you are eager to experiment with these changes before they migrate to the artful release pocket, you can head over to our official Ubuntu desktop team transitions ppa to get a taste of what’s cooking!

And we’ll attack tomorrow the big piece: introducing the new Ubuntu Dock!

about 5 hours ago

Ubuntu Insights: How to set up Kubernetes on any cloud and monitor your apps with Weave from Planet Ubuntu

On August 2, Luke Marsden (Weaveworks) and Marco Ceppi (Canonical) presented a webinar on how to Speed up your software development lifecycle with Kubernetes. In the session they described how you can use conjure-up and Weave Cloud to set up, manage and monitor an app in Kubernetes. In this tutorial we’re going to show you how to set up Kubernetes on any cloud, the conjure-up way. Once the cluster is spun up, you’ll use Weave Cloud to deploy an application, explore the microservices and monitor the app as it runs in the cluster.
Why Canonical & Weaveworks?
Canonical’s conjure-up makes it easy to deploy and operate Kubernetes in production, using a neat, easy-to-use CLI installer. Weave Cloud fills in the gaps missing with a Kubernetes install and provides the tools necessary for a full development lifecycle:

Deploy – plug output of CI system into cluster so that you can ship features faster
Explore – visualize and understand what’s happening so that you can fix problems faster
Monitor – understand behavior of running system so that you can fix problems faster using Prometheus

Weave Cloud Development Lifecycle
Installing Kubernetes with conjure-up

Use conjure-up to install Kubernetes on your cloud infrastructure (LXD provider is not currently supported by Weave Cloud)

Run the following script to enable privileged containers & set up RBAC properly:

juju config kubernetes-master allow-privileged=true juju config kubernetes-worker allow-privileged=true juju ssh kubernetes-master/0 -- 'sudo snap set kube-apiserver authorization-mode=RBAC' sleep 120 juju ssh kubernetes-master/0 -- '/snap/bin/kubectl create clusterrolebinding root-cluster-admin-binding --clusterrole=cluster-admin --user=admin && /snap/bin/kubectl create clusterrolebinding kubelet-node-binding --clusterrole=system:node --user=kubelet'

export KUBECONFIG=<path-to-kubeconfig>
find the path from e.g.
cat ~/bin/kubectl.conjure<tab>
You may wish to make this permanent by adding the export command to your ~/.bash_profile or equivalent shell startup script. Once you have the environment variable in place, you can run kubectl commands against the cluster. Try it out with
kubectl get nodes

Connecting your conjured up cluster to Weave Cloud

Next you will visualize the Kubernetes cluster in Weave Cloud. Sign up for Weave Cloud. Select Setup → Kubernetes → Generic Kubernetes and then cut and paste the Kubernetes command from the Weave Cloud UI into your terminal:

Weave Cloud Token and command location
For example, you would run:
kubectl apply -n kube-system -f \ "[CLOUD-TOKEN]&k8s-version=$(kubectl version | base64 | tr -d '\n')"

[CLOUD-TOKEN] is the Weave Cloud token.

The cluster should now appear in Weave Cloud. Check Explore → Hosts to see all five hosts:

Deploy the Sock Shop by first creating the namespace, checking it out of Git and then changing the kubernetes deploy directory:

kubectl create namespace sock-shop git clone cd microservices-demo kubectl apply -n sock-shop -f deploy/kubernetes/manifests
Now you should be able to see the Sock Shop in Weave Cloud Explore (click Controllers and select the sock-shop namespace filter from the bottom left):

And you should be able to access the shop in your browser, using the IP address of one of your Kubernetes nodes at port :30001.

Once the app is loaded, try out the Monitoring tool in Weave Cloud to observe the latencies between services in the cluster. Click Monitor and then run the following query:

You should see all the different requests latencies for all the services in the sock shop. This is possible because the sock shop is instrumented with the Prometheus client libraries.
In this post, we showed you how to get from nothing to a Kubernetes cluster using Canonical’s conjure-up. We then showed you how to install the Weave Cloud agents and just scratched the surface of what you can do with Weave Cloud: monitoring the request latencies on a Prometheus-instrumented app, the sock shop.
Next steps

Watch the webinar on-demand
Learn more about Canonical Distribution of Kubernetes
Get started with Weave Cloud or sign up for a free trial

about 5 hours ago

Ubuntu Insights: Ubuntu Foundations Development Summary – August 16, 2017 from Planet Ubuntu

This newsletter is to provide a status update from the Ubuntu Foundations Team. There will also be highlights provided for any interesting subjects the team may be working on. If you would like to reach the Foundations team, you can find us at the #ubuntu-devel channel on freenode.

Updated cloud images have been released with fix for CVE-2017-7533 has been released, to lint jenkins-job-builder output

The State of the Archive

After no small amount of effort, the perl 5.26 and gcc-7 transitions migrated to artful on the 10th, unblocking many of the packages that had been stuck in -proposed.
As GCC 7 is now the default compiler in artful, the build failures reported at now apply to 17.10. Please help us resolve these failing packages for the release.
Next in line we have the Qt 5.9 transition. Look for more news about this next week!

Upcoming Ubuntu Dates

17.10 Feature Freeze – August 24, 2017

Weekly Meeting

IRC Log:

about 19 hours ago

Ross Gammon: My Debian & Ubuntu work from April to mid-August 2017 from Planet Ubuntu

Okay, so I have been slack with my blogging again. I have been travelling around Europe with work quite a bit, had a short holiday over Easter in Denmark, and also had 3 weeks of Summer Holiday in Germany.

Tidied up the packaging and tried building the latest version of libdrumstick, but tests had been added to the package by upstream which were failing. I still need to get back and investigate that.
Updated node-seq (targeted at experimental due to the Debian Stretch release freeze) and asked for sponsorship (as I did not have DM rights for it yet).
Uploaded the latest version of abcmidi (also to experimental), and again.
Updated node-tmp to the latest version and uploaded to experimental.
Worked some more on bluebird RFP, but getting errors when running tests. I still haven’t gone back to investigate that.
Updated node-coffeeify to the latest version and uploaded to experimental.
Uploaded the latest version of node-os-tmpdir (also to experimental).
Uploaded the latest version of node-concat-stream (also to experimental).
After encouragement from several Debian Developers, I applied to become a full Debian Developer. Over the summer months I worked with Santiago as my Application Manager and answered questions about working in the Debian Project.
A web vulnerability was identified in node-concat-stream, so I prepared a fix to the version in unstable, uploaded it to unstable, and submitted a unblock request bug so that it would be fixed in the coming Debian Stretch release.
Debian 10 (Stretch) was released! Yay!
Moved abcmidi from experimental to unstable, adding an autopkgtest at the same time.
Moved node-concat-stream from experimental to unstable. During the process I had to take care of the intermediate upload to stretch (on a separate branch) because of the freeze.
Moved node-tmp to unstable from experimental.
Moved node-os-tmpdir from experimental to unstable.
Filed a removal bug for creepy, which seems to be unmaintained upstream these days. Sent my unfinished Qt4 to Qt5 porting patches upstream just in case!
Uploaded node-object-inspect to experimental to check the reverse dependencies, then moved it to unstable. Then a new upstream version came out which is now in experimental waiting for a retest of reverse dependencies.
Uploaded the latest version of gramps (4.2.6).
Uploaded a new version of node-cross-spawn to experimental.
Discovered that I had successfully completed the DD application process and I was now a Debian Developer. I celebrated by uploading the Debian Multimedia Blends package to the NEW queue, which I was not able to do before!
Tweaked and uploaded the node-seq package (with an RC fix) which had been sitting there because I did not have DM rights to the package. It is not an important package anyhow, as it is just one of the many dependencies that need to be packaged for Browserify.
Packaged and uploaded the latest node-isarray directly to unstable, as the changes seemed harmless.
Prepared and uploaded the latest node-js-yaml to experimental.
Did an update to the Node packaging Manual now that we are allowed to use “node” as the executable in Debian instead of “nodejs” which caused us to do a lot of patching in the past to get node packages working in Debian.


Did a freeze exception bug for ubuntustudio-controls, but we did not manage to get it sponsored before the Ubuntu Studio Zesty 17.04 release.
Investigated why Ardour was not migrating from zesty-proposed, but I couldn’t be sure of what was holding it up. After getting some help from the Developer’s mailing list, I prepared “no change rebuild” of pd-aubio which was sponsored by Steve Langasek after a little tweak. This did the trick.
Wrote to the Ubuntu Studio list asking for support for testing the Ubuntu Studio Zesty release, as I would be on holiday in the lead up to the release. When I got back, I found the release had gone smoothly. Thanks team!
Worked on some blueprints for the next Ubuntu Studio Artful release.
As Set no longer has enough spare time to work on Ubuntu Studio, we had a meeting on IRC to decide what to do. We decided that we should set up a Council like Xubuntu have. I drafted an announcement, but we still have not gone live with it yet. Maybe someone will have read this far and give us a push (or help).
Did a quick test of Len’s ubuntustudio-controls re-write (at least the GUI bits). We better get a move on if we want this to be part of Artful!
Tested ISO for Ubuntu Studio Xenial 16.04.3 point release, and updated the release notes.
Started working on a merge of Qjackctl using git-ubuntu for the first time. Had some issues getting going, so I asked the authors for some advice.

about 22 hours ago

Didier Roche: Ubuntu GNOME Shell in Artful: Day 3 from Planet Ubuntu

After introducing yesterday a real GNOME vanilla session, let’s see how we are using this to implement small behavior differences and transforming current Ubuntu Artful. For more background on this, you can refer back to our decisions regarding our default session experience as discussed in my blog post.

Day 3: a story of sound and collaboration…

Some devices have very low volume even when pushed at their maximum. One example for this is the x220 when most of videos on youtube, or listening to music in rhythmbox doesn’t give great results even at maximum volume.

Pulseaudio can amplify some of those sound devices (detecting if amplification is available on those output sources). Doing it, at the price of sound quality, makes at least the embedded speakers usable.

There are 3 components involved:
* gnome-control-center, which has a slider to push volume for supported device upper than 100%.
* gnome-settings-daemon, detecting multimedia keys, for volume up and down.
* gnome-shell, showing up a slider in the volume menu.

However, this brings some issues in the current design: if you set the volume above 100% in GNOME Control Center, and then press the multimedia key up, the volume is reset to 100%, and you can’t go further using only keys. A similar behavior is observable using GNOME Shell slider which reset the sound below what you did set in GNOME Control Center.

As a video will explain it better than words:

This behavior gets a little bit annoying when using it day to day on such hardware (you set the volume greater than 100%, then press the multimedia key “up” and it’s back to unhearable state) and not that consistent as the sliders between the OSD, GNOME Shell and GNOME Control Center aren’t in sync.

What we did few cycles ago in Ubuntu, was to introduce the idea to be able to set the volume above 100% from all of those, but conditionally. This was done in unity control center, Ubuntu settings daemon and unity for 14.04.

When the switch is off, which is the default, we removed any possibility to amplify and set the sound volume above 100%, being from GNOME control center, multimedia keys or any Shell visible slider to keep consistency. The option appears only though if any output source supports amplified volume. It’s disabled otherwise. If it’s available and you then switch it on, all of those methods enables amplifying the volume, syncing the sliders in a consistent manner.

We talked about it at GUADEC with Allan who needed a little bit more context and time to think about it (it might be a little bit late for this GNOME 3.26 cycle anyway). However, we didn’t want to keep Ubuntu 17.10 with the current behavior, so we reimplemented that design, but made it fully conditional to the XDG_CURRENT_DESKTOP variable we talked about yesterday. Consequently, the GNOME vanilla session is showing off the behavior you can see in the above video, and nothing in the upstream experience is impacted. However, the Ubuntu session, conditioned by this variable (as for any gsetting keys override), will show off the modifications we made in gnome settings daemon, GNOME Shell and GNOME Control Center, using our own gsettings key that we seeded back under the com.ubuntu settings namespace so that we don’t abuse the org.gnome one until this is blessed upstream. People who enabled that settings in previous Unity session will thus be automatically transitioned.

Here is a video illustrating this behavior:

For people who want to see the discussion we’re having with the GNOME design team to get something similar to this (maybe it won’t be completely the same, but in the same vein), you can head over to the corresponding bug.

We are trying to use these conditional per-session patches to keep the upstream vanilla session as vanilla as possible when it makes sense (meaning, when it’s not about integrating with a debian package based distro for instance). That enables us to deliver the desired and current upstream look and feel, while still be able to propose and implement slightly subtle changes we think are important for our user base.

As yesterday, if you are eager to experiment with these changes before they migrate to the artful release pocket, you can head over to our official Ubuntu desktop team transitions ppa to get a taste of what’s cooking!

There is still something in the GNOME vanilla session which is different from upstream, can you spot it? (Hint: it’s an icon). It feels as well a little bit out of place in the Ubuntu one. We are going to fix it tomorrow :)

1 day ago

Valorie Zimmerman: Repugnant from Planet Ubuntu

I grew up in a right-wing, Republican family. As I grew to adulthood and read about the proud history of the Republican party, beginning with Lincoln, I embraced that party, even as racism began to be embraced as a political strategy during Nixon's campaign for president. I overlooked that part, because I didn't want to see it. Besides, the Democrats were the party of racists.However, as I heard about the crimes that President Nixon seemed to be excusing, and that people around me also seemed to excuse, I began to think long and hard about party versus principle. Within a few years, I left that party, especially as I saw the Democrats, so long the party steeped in racism, begin to attempt to repair that damage done to the country. It took me many years to admit that I had changed parties, because my beliefs have not changed that much. I just see things more clearly now, after reading a lot more history.Today I've seen a Republican president embrace racism, support of the Confederacy, and support racists, neo-Nazis, white nationalists, and the Ku Klux Klan party -- a party his father supported in Queens, New York. Fred Trump was arrested for marching publicly in full regalia, masked, hooded and robed. I've seen no report that he was convicted, although there are pictures of the march and the arrest report in the local newspaper.Make no mistake about it; today's statement was deliberate. Trump's entry into the political fray was as a leader of the so-called birthers, questioning Barack Obama's citizenship. His announcement of candidacy was a full-throated anti-immigrant stance, which he never moderated and has not changed.Yes, previous American presidents have been racist, some of them proudly so. But since the Civil War we have not seen -- until today -- a president of the United States throw his political lot in with white nationalists and neo-Nazis. Good people voted for this man, hoping that he would shake things up in Washington. Good people cannot stand by statements such as Trump made today.It is time for the Congress to censure this President. The statements made today are morally bankrupt, and are intolerable. Good people do not march with neo-Nazis, and good people cannot let statements such as those made today, stand.

1 day ago

The Fridge: Ubuntu Weekly Newsletter Issue 516 from Planet Ubuntu

Welcome to the Ubuntu Weekly Newsletter. This is issue #516 for the week of August 8 – 14, 2017, and the full version is available here.
In this issue we cover:

Ubuntu Artful Desktop Fit and Finish Sprint
Ubuntu Stats
LoCo Events
Alan Pope: Ubuntu Community Hub Proposal
Canonical News
In The Blogosphere
Featured Audio and Video
Weekly Ubuntu Development Team Meetings
Upcoming Meetings and Events
Updates and Security for 14.04, 16.04, and 17.04
And much more!

The issue of The Ubuntu Weekly Newsletter is brought to you by:

Simon Quigley
Chris Guiver
And many others

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License

1 day ago

Canonical Design Team: Vanilla Framework has a new website from Planet Ubuntu

We’re happy to announce the long overdue Vanilla Framework website, where you can find all the relevant links and resources needed to start using Vanilla.
The homepage of
When you visit the new site, you will also see the new Vanilla logo, which follows the same visual principles as other logos within the Ubuntu family, like Juju, MAAS and Landscape.
We wanted to make sure that the Vanilla site showcased what you can do with the framework, so we kept it nice and clean, using only Vanilla patterns.
We plan on extending it to include more information about Vanilla and how it works, how to prototype using Vanilla, and the design principles that are behind it, so keep tuned.
And remember you can follow Vanilla on Twitter, ask questions on Slack and file new pattern proposals and issues on GitHub.

3 days ago

Costales: Folder Color now has emblem file support from Planet Ubuntu

New release 0.0.85 of folder color! Now you can select a file and set an emblem! Enjoy it! :)File emblemHow to install?

3 days ago

Jono Bacon: Sous Vide For Nerds (With Limited Cooking Experience) from Planet Ubuntu

Something a little different to share today, but important if you are (a) not especially gifted/interested in cooking, (b) love great food, and (c) are a bit of a nerd. Sous vide is the technique, and the Joule is the solution.

Sous vide is a method of cooking that involves putting food in a bag and submerging it in a water pan that is kept at a regulated temperature. You then essentially slow-cook the food, but because the water that the food is in is so consistent in temperature, it evenly cooks the food.

The result of this is phenomenal food. While I am still fairly new to sous vide, everything we have tried has been a significant improvement compared to regular methods (e.g. grilling).

As an example, chicken is notoriously difficult to cook well. When I sous vide the chicken and then sear it on the grill (to get some delicious char), you get incredible tender and juicy chicken with the ideal grilled texture and flavor.

Steak is phenomenal too. I use the same technique: sous vide it to a medium-rare doneness and then sear it at high heat on the grill. Perfectly cooked steak.

A particular surprise here are eggs. When you sous vide an egg, the yolk texture is undeniably better. It takes on an almost custard like texture and brings the flavor to life.

So, sous vide is an unquestionably fantastic method of cooking. The big question is, particularly for the non-cooks among you, is it worth it?

Sous vide is great for busy (or lazy) people

Part of why I am loving sous vide is that it matches the formula I want to experience in cooking:

Easy + Low Effort + Low Risk + Minimal Cleanup = Great Food

Here’s the breakdown:

Easy – you can’t really screw it up. Put the food in a bag, set the right temperate, come back after a given period of time and your food is perfectly cooked.
+ Low Effort – it takes a few minutes to start the cooking process and you can do other things while it cooks. You never need to babysit it.
+ Low Risk – with sous vide you know it is cooked evenly. As an example, with chicken, it is common to get a cooked outer core (from grilling) and it be uncooked in the middle. As such people overcook it to prevent the risk. With sous vide you just have to ensure you cook it to a safe level and it is consistently cooked.
+ Minimal Cleanup – you put the food in a bag, cook it, and then throw the bag away. The only pan you use is a bowl with water in it (about as easy to clean as possible). Perfect!

Thus, the result is great food and minimal fuss.

One other benefit is reheating for later eating.

As an example, right now I am ‘sous vide’ing’ (?) a pan full of eggs. These will be for breakfast every day this week. When the eggs are done, we will pop them in the fridge to keep. To reheat, we simply submerge the eggs in boiling water and it raises the internal temperature back up. The result is the incredible sous vide texture and consistency, but it takes merely (a) boiling the kettle, (b) submerging the eggs, and (c) waiting a little bit to get the benefits of sous vide later.

The gadget

This is where the nerdy bit comes in, but it isn’t all that nerdy.

For Christmas, Erica and I got a Joule. Put simply, it is white stick that plugs into the wall and connects to your phone via bluetooth.

You fill a pan with water, pop the Joule in, and search for the food you want to cook. The app will then recommend the right temperate and cooking time. When you set the time, the Joule turns on and starts circulating the water in the pan until it reaches the target temperate.

Next, you put the food in in the bag and the app starts the timer. When the timer is done your phone gets notified, you pull the food out and bingo!

The library of food in the app is enormous and even helps with how to prepare the food (e.g. any recommended seasoning). If though you want to ignore the guidance and just set a temperature and cooking time, then you can do that too.

When you are done cooking, throw the bag you cooked the food in away, empty the water out of the pan, and put the Joule back in the cupboard. Job done.

Now, to be clear, there are many other sous vide gadgets, none of which I have tried. I have tried one, the Joule, and it has been brilliant.

So, that’s it: I just wanted to share this recent discovery. Give it a try, I think you will dig it as much as I do.
The post Sous Vide For Nerds (With Limited Cooking Experience) appeared first on Jono Bacon.

3 days ago

Sebastian Schauenburg: IPv6 Unique Local Address from Planet Ubuntu

Since IPv6 is happening, we should be prepared. During the deployment of a new accesspoint I was in need of a Unique Local Address. IPv6 Unique Local Addresses basically are comparable to the IPv4 private address ranges.
Some sites refer to, but that is offline nowadays. Others refer to generator, which is open source and still available yay.

But wait, there must be an offline method for this right? There is! subnetcalc (nowadays available here apparently) to the rescue:
subnetcalc fd00:: 64 -uniquelocal | grep ^Network

Profit :-)

5 days ago

Valorie Zimmerman: Akademy; at 20, KDE reaches out from Planet Ubuntu

Some of the talks, initiatives, conversations, and workshops that inspired me at Akademy. Thanks so much for the e.V. for sponsoring me.A. Wikidata  - We have some work to do to get our data automatically uploaded into Wikidata. However, doing so will help us keep our Wikipedia pages up-to-date.B. Looking for Love, Paul Brown's talk and workshop about Increasing your audience's appreciation for your project. Many of the top Google results for our pages don't address what people are looking for:What can your project do for me? What does your application or library do?Paul highlighted one good example: That crucial information is above the fold, with no scrolling. Attractive, and exactly the approach we should be taking in all our public-facing pages.My offer to all projects: I will help with the text on any of your pages. This is a serious offer! Just ask in IRC or send an email to valorie at kde dot org for editing.C. The Enterprise list for people with large KDE deployments, an under-used resource for those supporting our users in huge numbers, in schools, governments and companies. If you know of anyone doing this job who is not on the list, hand along the link to them.D. Goalposts for KDE - I was not at this "Luminaries" Kabal Proposals BoF, but I read the notes. I'll be happy to see this idea develop on the Community list.E. UserBase revival -- This effort is timely! and brings the list of things I'm excited about full circle. For many teams, UserBase pages are their website. We need to clean up and polish UserBase! Join us in #kde-wiki in IRC or the Telegram channel and where we'll actually be tracking and doing the work. I'm so thankful that Claus is taking the leadership on this.If you are a project leader and want help buffing your UserBase pages, we can help!In addition to all of the above ideas, there is still another idea floating around that needs more development. Each of our application sites, at least, should have a quality metric box, listing things like code testing, translation/internationalization percentage, number of contributors, and maybe more. These should be picked up automatically, not generated by hand. No other major projects seem to have this, so we should lead. When people are looking for what applications they want to run on their computers, they should choose by more than color or other incidentals. We work so much on quality -- we should lead with it. There were many informal discussions about this but no concrete proposals yet.

6 days ago

Stephan Ruegamer: Looking for a Release Engineer, Berlin from Planet Ubuntu

Release Engineer (Berlin, Germany), Sony Interactive Entertainment
Do you want to be part of an engineering team that is building a world class cloud platform that scales to millions of users? Are you excited to dive into new projects, have an enthusiasm for automation, and enjoy working in a strong collaborate culture? If so, join us!
Design and development of Release Engineering projects and tools to aid in release pipeline.
Work in cross-functional development teams to build and deploy new software systems.
Work with team and project managers to deliver quality software within schedule constraints.
Demonstrable knowledge of distributed architectures, OOP and Python
BS or a minimum of 5 years of relevant work experience
Skills & Knowledge

Expert level knowledge of Unix/Linux
Advanced skills in Python
Kubernetes experience is a huge plus
Programming best practices including unit testing, integration testing, static analysis, and code documentation
Familiarity with build systems
Familiarity with continuous integration and delivery

Additional Attributes

Contributor to open source projects
Version control systems (preferably Git)
Gamer is a plus
Enjoys working in a fast-paced environment
Strong communication skills

Interested? Use this link

6 days ago

David Tomaschik: Review of HackerBoxes 0021: Hacker Tracker from Planet Ubuntu

HackerBoxes is a monthly subscription service for hardware hackers and makers.
I hadn’t heard of it until I was researching DEF CON 25 badges, for which they
had a box, at which point I was amazed I had missed it. They were handing out
coupons at DEF CON and BSidesLV for 10% off your first box, so I decided to give
it a try.

First thing I noticed upon opening the box was that there’s no fanfare in the
packaging or design of the shipping. You get a plain white box shipped USPS
with all of the contents just inside. I can’t decide if I’m happy they’re not
wasting material on extra packaging, or disappointed they didn’t do more to make
it feel exciting. If you look at their website, they show all the past boxes
with a black “Hacker Boxes” branded box, so I don’t know if this is a change, or
the pictures on the website are misleading, or the influx of new members from
hacker summer camp has resulted in a box shortage.

I unpacked the box quickly to find the following:

Arduino Nano Clone
Jumper Wires
Small breadboard
MicroSD Card (16 GB)
USB MicroSD Reader
MicroSD Breakout Board
u-blox NEO 6M GPS module
Magnetometer breakout
PCB Ruler
MicroUSB Cable
Hackerboxes Sticker
Pinout card with reminder of instructions (aka h4x0r sk00l)

If you’ve been trying to do the math in your head, I’ll save you the trouble.
In quantity 1, these parts can be had from AliExpress for about $30. If you’re
feeling impatient, you can do it on Amazon for about $50. Of course, the value
of the parts alone isn’t the whole story: this is a curated set of components
that builds a project, and the directions they provide on getting started are
part of the product. (I just know everyone wanted to know the cash value.)

Compared to some of their historical boxes, I’m a little underwhelmed. Many of
their boxes look like something where I could do many things with the kit or
teach hardware concepts: for example, “0018: Circuit Circus” is clearly an effort to
teach analog circuits. “0015 - Connect Everything” lets you connect everything
to WiFi via the ESP32. Even when not multi-purpose, previous kits have included
reusable tools like a USB borescope or a Utili-Key. Many seem to have an
exclusive “fun” item, like a patch or keychain, in addition to the obligatory
HackerBoxes sticker.

In contrast, the “Hacker Tracker” box feels like a unitasker: receive
GPS/magnetometer readings and log them to a MicroSD card. Furthermore, there’s
not much hardware education involved: all of the components connect directly via
jumper wires to the provided Arduino Nano clone, so other than “connect the
right wire”, there’s no electronics skillset to speak of. On the software side,
while there are steps along the way showing how each component is used, a
fully-functional Arduino sketch is provided, so you don’t have to know any
programming to get a functional GPS logger.

Overall, I feel like this kit is essentially “paint-by-numbers”, which can
either be great or disappointing. If you’re introducing a teenager to
electronics and programming, a “paint-by-numbers” approach is probably a great
start. Likewise, if this is your first foray into electronics or Arduino, you
should have no trouble following along. On the other hand, if you’re more
experienced and just looking for inspiration of endless possibilities, I feel
like this kit has fallen short.

There’s one other gripe I have with this kit: there are headers on the Arduino
Nano clone and the MicroSD breakout, but the headers are not soldered on the
accelerometer or GPS module. At least if you’re going to make a simple kit,
make it so I don’t have to clean off the soldering station, okay?

So, am I keeping my subscription? For the moment, yes, at least for another
month. Like I said, I’ve been impressed by past kits, so this might just be an
off month for what I’m looking for. I don’t think this kit is bad, and I’m not
disappointed, just not as excited as I’d hoped to be. I might have to give
Adabox a try though.

As for the subscription service itself: it looks like their web interface makes
it easy to skip a month (maybe you’re travelling and won’t have time?) or cancel
entirely. I’m not advocating cancelling, but I absolutely hate when
subscription services make you contact customer service to cancel (just so they
can try to talk you into staying longer, like AOL back in the 90s). The site
has a nice clean feel and works well.

If anyone from HackerBoxes is reading this, I’ll consolidate my suggestions to
you in a few points:

Hook us up with patches & more stickers! Especially a sticker that won’t take
1/4 of a laptop. (I love the sticker from #0015 and the patch from #0018.)
Don’t have the only soldering be two tiny header strips. Getting out the
soldering iron just to do a couple of SPI connections is a bit of a drag.
Either do a PCB like #0019, #0020, etc., or provide modules with headers in
place. (If it wasn’t for the soldering, you could take this kit on vacation
and play with just the kit and a laptop!)
Instructables with more information on why you’re doing what you’re doing
would be nice. Mentioning that there’s a level shifter on the MicroSD
breakout because MicroSD cards run at 3.3V, and not the 5V from an Arduino
Nano, for example.
Including a part that requires a warning about you (the experts) having had a
lot of problems with it in an introductory kit seems like a poor choice. A
customer with flaky behavior won’t know if it’s their setup, their code, or
the part.

Overall, I’m excited to see so much going into STEM education and the maker
movement, and I’m happy that it’s still growing. I want to thank HackerBoxes
for being a part of that and wish them success even if I don’t turn out to be
their ideal demographic.

6 days ago

Scarlett Clark: Another successful Akademy! Neon team BoF, snappy and more. from Planet Ubuntu

Akademy 2017
This years akademy held in Almeria, Spain was a great success.
We ( the neon team ) have decided to move to using snappy container format for KDE applications in KDE Neon.
This will begin in the dev/unstable builds while we sort out the kinks and heavily test it. We still have some roadblocks to overcome, but hope to work with the snappy team to resolve them.
We have also begun the transition of moving Plasma Mobile CI over to Neon CI. So between mobile (arm), snap and debian packaging, we will be very busy!
I attended several BoFs that brought great new ideas for the KDE community.
I was able to chat with Kubuntu release manager ( Valorie Zimmerman ) and hope to work closer with the Kubuntu and Debian teams to reduce duplicate work. I feel this
is very important for all teams involved.
We had so many great talks, see some here:
Akademy is a perfect venue for KDE contributors to work face to face to tackle issues and create new ideas.
Please consider donating:
As usual, it was wonderful to see my KDE family again! See you all next year in Vienna!

7 days ago