I Use This!
Activity Not Available


Analyzed 3 months ago. based on code collected 10 months ago.
Posted 5 days ago
Hi guys! Again… Long time, no see you :-). As you surely know, in the past weeks Ubuntu took the hard decision of stopping the development of Unity desktop environment, focusing again in shipping GNOME as default DE, and joining the upstream efforts. ... [More] While, in a personal note, after more than 6 years of involvement in the Unity development, this is a little heartbreaking, I also think that given the situation this is the right decision, and I’m quite excited to be able to work even closer to the whole opensource community! Most of the aspects of the future Ubuntu desktop have to be defined yet, and I guess you know that there’s a survey going on I encourage you to participate in order to make your voice count… One important aspect of this, is the visual appearance, and the Ubuntu Desktop team has decided that the default themes for Ubuntu 17.10 will continue to be the ones you always loved! Right now some work is being done to make sure Ambiance and Radiance look and work good in GNOME Shell. In the past days I’ve released a  new version of ‘light-themes‘ to fix several theming problems in GNOME Shell. This is already quite an improvement, but we can’t fix bugs we don’t know about… So this is where you can help make Ubuntu better! Get Started If you haven’t already, here’s how I recommend you get started. Install the latest Ubuntu 17.10 daily image (if not going wild and trying this in 17.04). After installing it, install gnome-shell. Install gnome-tweak-tool if you want an easy way to change themes. On the login screen, switch your session to GNOME and log in. Report Bugs Run this command to report bugs with Ambiance or Radiance: ubuntu-bug light-themes Attach a screenshot to the Launchpad issue. Other info Ubuntu’s default icon theme is ubuntu-mono-dark (or -light if you switch to Radiance) but most of Ubuntu’s customized icons are provided by humanity-icon-theme. Helping with Themes development If you want to help with the theming itself, you’re very welcome. Gtk themes are nowadays using CSS, so I’m pretty sure that any Web designer out there can help with them (these are the supported properties). All you have to do, is simply use the Gtk Inspector that can be launched from any Gtk3 app, and write some CSS rules and see how they get applied on the fly. Once you’re happy with your solution, you can just create a MP for the Ubuntu Themes. Let’s keep ubuntu, look ubuntu! PS: thanks to Jeremy Bicha for the help in this post. [Less]
Posted 5 days ago
I’ve been running Artful aka 17.10 on my laptop for maybe a month now with no real issues and thats thanks to the awesome Kubuntu developers we have and our testers!   My Current layout has Latte Dock running with a normal panel (yes a bit Mac-y I ... [More] know). I had to build Latte Dock for myself in Launchpad[1] so if you want to use it on 17.10 with the normal PPA/testing warning, I also have it built for 17.04 if anyone wants that as well[2]. I’m also running the new Qt music player Babe-Qt. I also have the Uptime widget and a launcher widget in the Latte Dock as it can hold widgets just like a normal panel. Oh and the wallpaper is from awesome game Firewatch (it’s on Linux!) [1] https://launchpad.net/~aaronhoneycutt/+archive/ubuntu/artful [2] https://launchpad.net/~aaronhoneycutt/+archive/ubuntu/kubuntu-zetsy [Less]
Posted 6 days ago
This week we concentrated on polishing up our region and credentials selection capabilities. Initially, we wanted people deploying big software as fast as possible without it turning into a "choose your own adventure" book. This has been hugely ... [More] successful as it minimized time and effort to getting to that end result of a usable Kubernetes or OpenStack. Now fast forward a few months and feature requests were coming in wanting to expand on this basic flow of installing big software. Our first request was to add the ability to specify regions where this software would live, that feature is complete and is known as region selections: Region Selections Region selection is supported in both Juju as a Service (JAAS) and as a self hosted controller. In this example we are using JAAS to deploy Canonical Distribution of Kubernetes to the us-east-2 region in AWS: conjure-up will already know what regions are available and will prompt you with that list: Finally, input your credentials and off it goes to having a fully usable Kubernetes cluster in AWS. The credentials view leads us into our second completed feature. Multiple user credentials are supported for all the various clouds and previously conjure-up tried to do the right thing if an existing credential for a cloud was found. Again, in the interest of getting you up and running as fast as possible conjure-up would re-use any credentials it found for the cloud in use. This worked well initially, however, as usage increased so did the need for being able to choose from a list of existing credentials or create your own. That feature work has been completed and will be available in conjure-up 2.2. Credential Selection This screen shows you a list of existing credentials that were created for AWS or gives you the option of creating additional ones: Trying out the latest As always we keep our edge releases current with the latest from our code. If you want to help test out these new features simply run: sudo snap install conjure-up --classic --edge conjure-up That's all for this week, check back next week for more conjure-up news! [Less]
Posted 6 days ago
Welcome to the first ever Ubuntu OpenStack development summary! This summary is intended to be a regular communication of activities and plans happening in and around Ubuntu OpenStack, covering but not limited to the distribution and deployment of ... [More] OpenStack on Ubuntu. If there is something that you would like to see covered in future summaries, or you have general feedback on content please feel free to reach out to me (jamespage on Freenode IRC) or any of the OpenStack Engineering team at Canonical! OpenStack Distribution Stable Releases Ceph 10.2.7 for Xenial, Yakkety, Zesty and Trusty-Mitaka UCA: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1684527 Open vSwitch updates (2.5.2 and 2.6.1) for Xenial and Yakkety plus associated UCA pockets: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1673063 https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1641956 Point releases for Horizon (9.1.2) and Keystone (9.3.0) for Xenial and Trusty-Mitaka UCA: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1680098 And the current set of OpenStack Newton point releases have just entered testing: https://bugs.launchpad.net/cloud-archive/+bug/1688557 Development Release OpenStack Pike b1 is available in Xenial-Pike UCA (working through proposed testing in Artful). Open vSwitch 2.7.0 is available in Artful and Xenial-Pike UCA. Expect some focus on development previews for Ceph Luminous (the next stable release) for Artful and the Xenial-Pike UCA in the next month. OpenStack Snaps Progress on producing snap packages for OpenStack components continues; snaps for glance, keystone, nova, neutron and nova-hypervisor are available in the snap store in the edge channel – for example: sudo snap install --edge --classic keystone Snaps are currently Ocata aligned; once the team have a set of snaps that we’re all comfortable are a good base, we’ll be working towards publication of snaps across tracks for OpenStack Ocata and OpenStack Pike as well as expanding the scope of projects covered with snap packages. The edge channel for each track will contain the tip of the associated branch for each OpenStack project, with the beta, candidate and release channels being reserved for released versions. These three channels will be used to drive the CI process for validation of snap updates. This should result in an experience something like: sudo snap install --classic --channel=ocata/stable keystone or sudo snap install --classic --channel=pike/edge keystone As the snaps mature, the team will be focusing on enabling deployment of OpenStack using snaps in the OpenStack Charms (which will support CI/CD testing) and migration from deb based installs to snap based installs. Nova LXD Support for different Cinder block device backends for Nova-LXD has landed into driver (and the supporting os-brick library), allowing Ceph Cinder storage backends to be used with LXD containers; this is available in the Pike development release only. Work on support for new LXD features to allow multiple storage backends to be used is currently in-flight, allowing the driver to use dedicated storage for its LXD instances alongside any use of LXD via other tools on the same servers. OpenStack Charms 6 monthly release cycle The OpenStack Charms project is moving to a 6 monthly release cadence (rather than the 3 month cadence we’ve followed for the last few years); This reflects the reduced rate of new features across OpenStack and the charms, and the improved process for backporting fixes to the stable charm set between releases. The next charm release will be in August, aligned with the release of OpenStack Pike and the Xenial Pike UCA. If you have bugs that you’d like to see backported to the current stable charm set, please tag them with the ‘stable-backport’ tag (and they will pop-up in the right place in Launchpad) – you can see the current stable bug pipeline here. Ubuntu Artful and OpenStack Pike Support Required changes into the OpenStack Charms to support deployment of Ubuntu Artful (the current development release) and OpenStack Pike are landing into the development branches for all charms, alongside the release of Pike b1 into Artful and the Xenial-Pike UCA. You can consume these charms (as always) via the ~openstack-charmers-next team, for example: juju deploy cs:~openstack-charmers-next/keystone IRC (and meetings) You can participate in the OpenStack charm development and discussion by joining the #openstack-charms channel on Freenode IRC; we also have a weekly development meeting in #openstack-meeting-4 at either 1000 UTC (odd weeks) or 1700 UTC (even weeks) – see http://eavesdrop.openstack.org/#OpenStack_Charms for more details. EOM [Less]
Posted 7 days ago by nore...@blogger.com (Marcos Costales)
Segundo capítulo del podcast Ubuntu y otras hierbas.En esta ocasión: Paco Molinero Francisco Javier Teruelo Marcos Costales Charlaremos sobre estos temas: Migración a GNOME 3 UBPorts mantendrá Unity y Ubuntu Phone El podcast está disponible para ... [More] escuchar en: Youtube Ivoox Podcast en Youtube Links relacionados al podcast: Banda sonora del podcast bajo licencia CC BY-NC 4.0. Vídeo de Marius en la Ubucon sobre UBPorts.Todos los capítulos del podcast 'Ubuntu y otras hierbas' disponibles aquí. [Less]
Posted 7 days ago
I just got a new Raspberry Pi Zero W (the wireless version) and didn’t feel like hooking it up to a monitor and keyboard to get started. I really just wanted a serial console for starters. Rather than solder in a header, I wanted to be really lazy ... [More] , so decided to use the USB OTG support of the Pi Zero to provide a console over USB. It’s pretty straightforward, actually. Install Raspbian on MicroSD Mount the /boot partition Edit /boot/config.txt Edit /boot/cmdline.txt Mount the root (/) partition Enable a Console on /dev/ttyGS0 Unmount and boot your Pi Zero Connect via a terminal emulator Conclusion Install Raspbian on MicroSD First off is a straightforward “install” of Raspbian on your MicroSD card. In my case, I used dd to image the img file from Raspbian to a MicroSD card in a card reader. 1 dd if=/home/david/Downloads/2017-04-10-raspbian-jessie-lite.img of=/dev/sde bs=1M conv=fdatasync Mount the /boot partition You’ll want to mount the boot partition to make a couple of changes. Before doing so, run partprobe to re-read the partition tables (or unplug and replug the SD card). Then mount the partition somewhere convenient. 1 2 partprobe mount /dev/sde1 /mnt/boot Edit /boot/config.txt To use the USB port as an OTG port, you’ll need to enable the dwc2 device tree overlay. This is accomplished by adding a line to /boot/config.txt with dtoverlay=dwc2. 1 2 vim /mnt/boot/config.txt (append dtoverlay=dwc2) Edit /boot/cmdline.txt Now we’ll need to tell the kernel to load the right module for the serial OTG support. Open /boot/cmdline.txt, and after rootwait, add modules-load=dwc2,g_serial. 1 2 vim /mnt/boot/cmdline.txt (insert modules-load=dwc2,g_serial after rootwait) When you save the file, make sure it is all one line, if you have any line wrapping options they may have inserted newlines into the file. Mount the root (/) partition Let’s switch the partition we’re dealing with. 1 2 umount /mnt/boot mount /dev/sde2 /mnt/root Enable a Console on /dev/ttyGS0 /dev/ttyGS0 is the serial port on the USB gadget interface. While we’ll get a serial port, we won’t have a console on it unless we tell systemd to start a getty (the process that handles login and starts shells) on the USB serial port. This is as simple as creating a symlink: 1 ln -s /lib/systemd/system/getty@.service /mnt/root/etc/systemd/system/getty.target.wants/getty@ttyGS0.service This asks systemd to start a getty on ttyGS0 on boot. Unmount and boot your Pi Zero Unmount your SD card, insert the micro SD card into a Pi Zero, and boot with a Micro USB cable between your computer and the OTG port. Connect via a terminal emulator You can connect via the terminal emulator of your choice at 115200bps. The Pi Zero shows up as a “Netchip Technology, Inc. Linux-USB Serial Gadget (CDC ACM mode)”, which means that (on Linux) your device will typically be /dev/ttyACM0. 1 screen /dev/ttyACM0 115200 Conclusion This is a quick way to get a console on a Raspberry Pi Zero, but it has downsides: Provides only console, no networking. File transfers are “difficult”. [Less]
Posted 8 days ago
After some internal bikeshedding, we decided to rework the tooling that the Server Team has been working on for git-based source package management. The old tool was usd (Ubuntu Server Dev), as it stemmed from a Canonical Server sprint in Barcelona ... [More] last year. That name is confusing (acronyms that aren’t obvious are never good) and really the tooling had evolved to be a git wrapper. So, we renamed everything to be git-ubuntu. Since git is awesome, that means git ubuntu also works as long as git-ubuntu is in your $PATH. The snap (previously usd-nacc) has been deprecated in favor of git-ubuntu (it still exists, but if you try to run, e.g., usd-nacc.usd you are told to install the git-ubuntu snap). To get it, use: sudo snap install --classic git-ubuntu We are working on some relatively big changes to the code-base to release next week: Empty directory support (LP: #1687057). My colleague Robie Basak implemented a workaround for upstream git not being able to represent empty directories. Standardizing (internal to the code) how the remote(s) work and what refspecs are used to fetch from them. Along with those architectural changes, one big functional shift is to using git-config to store some metadata about the user (specifically, the Launchpad user name to use, in ~/.gitconfig) and the command used to create the repository (specifically, the source package name, in /.git/config). I think this actually ends up being quite clean from an end-user perspective, and it means our APIs and commands are easier to use, as we can just lookup this information from git-config when using an existing repository. As always, the latest code is at: https://git.launchpad.net/usd-importer [Less]
Posted 8 days ago by david....@canonical.com (Ubuntu Insights)
There is a new desktop snap in the Snap store: Visual Studio Code. A versatile and open source code editor Launched in 2015 by Microsoft, Visual Studio Code has imposed itself as one of the preferred code editors in the developer community. ... [More] Cross-platform (powered by Electron), it features a marketplace of more than 3000 extensions where any language can find its linters, debuggers and test runners. To install Visual Studio Code as a snap: sudo snap install --classic vscode How has VS Code made such a splash in the development world? After barely two years, this editor has found a place in a lot of tool belts, on Linux too. To explain this success, here are some notable highlights: smart completion based on types and functions a versatile integrated debugger git built-in support with an approachable user interface for git commands and of course, extensions support Git integration in Visual Studio Code features delightful commit (and reverts!) management. To make the experience more familiar, you can emulate keyboard shortcuts of other editors by installing alternative keymaps, such as Vim, Emacs, Sublime, etc. Available as a snap for an agile release process It’s not the first code editor featured in this Electron snaps blog series, and if you have been reading the other entries, you already know why snaps are a good fit for Electron distribution on Linux: auto-updates, ease of installation and dependency bundling. This snap makes the latest version of Visual Studio Code easily installable and auto-updatable on Ubuntu 14.04, 16.04 and newer supported releases, goodbye 3rd party PPAs and general package hunting! Releases for everyone and releases for testers Snaps allow developers to release software in different “channels”, that users subscribe to (defaulting to the stable channel), in order to receive automated updates. Four channels are available, with names hinting at the stability users can expect: edge is for QA, testers and adventurous adopters beta is where versions from the edge channel are moved to when they pass some level of testing and QA candidate is commonly used for freezed pre-release versions stable is what users install by default (the snap install command without any options) and is expected to only contain stable software. This is also the channel that enables snaps to appear in search results of the snap find command. For a primer on using the snap command-line, this tutorial will show you the way. [Less]
Posted 9 days ago
I personally stopped blogging a while ago, but I kinda feel this is a necessary blog post. A while ago, a professor used the term Community Manager interchangeably with Social Media Manager. I made a quick comment about them not being the same, and ... [More] later some friends started questioning my reasoning. Last week during OSCON, I was chatting with a friend about this same topic. A startup asked me to help them as a community manager about a year ago. I gladly accepted, but then they just started assigning me social media work. And these are not the only cases. I have seen several people use both terms interchangeably, which they are not. I guess it’s time for me to burst the bubble that has been wrapped around both terms. In order to do that, let’s explain, in very simple words, the job of both of them. Let’s start with the social media managers. Their job is, as the title says, to manage social media channels. Post on Facebook, respond to Twitter replies, make sure people feel welcome when they visit any of the social media channels, and automatically represent the brand/product through social media. Community managers, on the other side, focus on building communities around a product or service. To put it simpler, they make sure that there’s people that care about the product, that contribute to the ecosystem, that work with the provider to make it better. Social media management is a part of their job. It is a core function, because it is one of the channels that allow them to communicate with people to hear their concerns and project the provider’s voice about the product. However, it is not their only job. They also have to go out and meet with people, in real life. Talk with higher-ups to voice the concerns. Hear how the product is impacting people’s life in order to make a change, or continue on the same good path. With this, I’m not trying to devalue the work of social media managers. On the other hand, they are have a very valuable job. Imagine all those companies with social media profiles, without the funny comments. No message replies if you had a question. Horrible, right? Managing these channels is as important, so brands/products are ‘alive’ on the interwebs. Being a community manager is not only managing a channel. Therefore, they are not comparable jobs. Each of the positions is different, even though they complement each other pretty well. But I hope that with this post you can understand a little bit more about the inside job of both community managers and social media managers. In a fast-paced world like ours today, these two can make a huge difference between having a presence online, or not. So, next time, if you’re looking for a community manager, don’t expect them to do only social media work. And viceversa – if you’re looking for a social media manager, don’t expect them to build community out of social media. [Less]
Posted 9 days ago
Hot on the heels of landing Cockpit in Debian unstable and Ubuntu 17.04, the Ubuntu backport request got approved (thanks Iain!), which means that installing cockpit on Ubuntu 16.04 LTS or 16.10 is now also a simple apt install cockpit away. I updated the installation instructions accordingly. Enjoy, and let us know about problems!