Planet Debian Derivatives

Ubuntu developers: Andres Rodriguez: Getting Started with MAAS and Juju: MAAS Overview

Ubuntu developers — 2013-05-21T16:31:51+00:00

For a while, I have been wanting to write about MAAS and how it can easily deploy workloads (specially OpenStack) with Juju, and the time has finally come. This will be the first of a series of posts where I’ll provide an Overview of how to quickly get started with MAAS and Juju.

What is MAAS?

I think that MAAS does not require introduction, but if people really need to know, this awesome video will provide a far better explanation than the one I can give in this blog post.

http://youtu.be/J1XH0SQARgo

Components and Architecture

MAAS have been designed in such a way that it can be deployed in different architectures and network environments. MAAS can be deployed as both, a Single-Node or Multi-Node Architecture. This allows MAAS to be a scalable deployment system to meet your needs. It has two basic components, the MAAS Region Controller and the MAAS Cluster Controller.

Region Controller

The MAAS Region Controller is the component the users interface with, and is the one that controls the Cluster Controllers. It is the place of the WebUI and API. The Region Controller is also the place for the MAAS meta-data server for cloud-init, as well as the place where the DNS server runs. The region controller also configures a rsyslogd server to log the installation process, as well as a proxy (squid-deb-proxy) that is used to cache the debian packages. The preseeds used for the different stages of the process are also being stored here.

Cluster Controller

The MAAS Cluster Controller only interfaces with the Region controller and is the one in charge of provisioning in general. The Cluster Controller is the place the TFTP and DHCP server(s) are located. This is the place where both the PXE files and ephemeral images are being stored. It is also the Cluster Controller’s job to power on/off the managed nodes (if configured).

The Architecture

As you can see in the image above, MAAS can be deployed in both a single node or multi-node. The way MAAS has being designed makes MAAS highly scalable allowing to add more Cluster Controllers that will manage a different pool of machines. A single-node scenario can become in a multi-node scenario by simply adding more Cluster Controllers. Each Cluster Controller has to register with the Region Controller, and each can be configured to manage a different Network. The way has this is intended to work is that each Cluster Controller will manage a different pool of machines in different networks (for provisioning), allowing MAAS to manage hundreds of machines. This is completely transparent to users because MAAS makes the machines available to them as a single pool of machines, which can all be used for deploying/orchestrating your services with juju.

How Does It Work?

MAAS has 3 basic stages. These are Enlistment, Commissioning and Deployment which are explained below:

Enlistment

The enlistment process is the process on which a new machine is registered to MAAS. When a new machine is started, it will obtain an IP address and PXE boot from the MAAS Cluster Controller. The PXE boot process will instruct the machine to load an ephemeral image that will run and perform an initial discovery process (via a preseed fed to cloud-init). This discovery process will obtain basic information such as network interfaces, MAC addresses and the machine’s architecture. Once this information is gathered, a request to register the machine is made to the MAAS Region Controller. Once this happens, the machine will appear in MAAS with a Declared state.

Commissioning

The commissioning process is the process where MAAS collects hardware information, such as the number of CPU cores, RAM memory, disk size, etc, which can be later used as constraints. Once the machine has been enlisted (Declared State), the machine must be accepted into the MAAS in order for the commissioning processes to begin and for it to be ready for deployment. For example, in the WebUI, an “Accept & Commission” button will be present. Once the machine gets accepted into MAAS, the machine will PXE boot from the MAAS Cluster Controller and will be instructed to run the same ephemeral image (again). This time, however, the commissioning process will be instructed to gather more information about the machine, which will be sent back to the MAAS region controller (via cloud-init from MAAS meta-data server). Once this process has finished, the machine information will be updated it will change to Ready state. This status means that the machine is ready for deployment.

Deployment

Once the machines are in Ready state, they can be used for deployment. Deployment can happen with both juju or the maas-cli (or even the WebUI). The maas-cli will only allow you to install Ubuntu on the machine, while juju will not only allow you to deploy Ubuntu on them, but will allow you to orchestrate services. When a machine has been deployed, its state will change to Allocated to <user>. This state means that the machine is in use by the user who requested its deployment.

Releasing Machines

Once a user doesn’t need the machine anymore, it can be released and its status will change from Allocated to <user> back to Ready. This means that the machine will be turned off and will be made available for later use.

But… How do Machines Turn On/Off?

Now, you might be wondering how are the machines being turned on/off or who is the one in charge of that. MAAS can manage power devices, such as IPMI/iLO, Sentry Switch CDU’s, or even virsh. By default, we expect that all the machines being controlled by MAAS have IPMI/iLO cards. So if your machines do, MAAS will attempt to auto-detect and auto-configure your IPMI/iLO cards during the Enlistment and Commissioning processes. Once the machines are Accepted into MAAS (after enlistment) they will be turned on automatically and they will be Commissioned (that is if IPMI was discovered and configured correctly).. This also means that every time a machine is being deployed, they will be turned on automatically.

Note that MAAS not only handles physical machines, it can also handle Virtual Machines, hence the virsh power management type. However, you will have to manually configure the details in order for MAAS to manage these virtual machines and turn them on/off automatically.

Ubuntu developers: Timo Jyrinki: Network from laptop to Android device over USB

Timo Jyrinki — 2013-05-21T12:20:00+00:00

If you're running an Android device with GNU userland Linux in a chroot and need a full network access over USB cable (so that you can use your laptop/desktop machine's network connection from the device), here's a quick primer on how it can be set up.

When doing Openmoko hacking, one always first plugged in the USB cable and forwarded network, or like I did later forwarded network over Bluetooth. It was mostly because the WiFi was quite unstable with many of the kernels.

I recently found out myself using a chroot on a Nexus 4 without working WiFi, so instead of my usual WiFi usage I needed network over USB... trivial, of course, except that there's Android on the way and I'm a Android newbie. Thanks to ZDmitry on Freenode, I got the bits for the Android part so I got it working.

On device, have eg. data/usb.sh with the following contents.

#!/system/xbin/sh
CHROOT="/data/chroot"

ip addr add 192.168.137.2/30 dev usb0
ip link set usb0 up
ip route delete default
ip route add default via 192.168.137.1;
setprop net.dns1 8.8.8.8
echo 'nameserver 8.8.8.8' >> $CHROOT/run/resolvconf/resolv.conf

On the host, execute the following:

adb shell setprop sys.usb.config rndis,adb
adb shell data/usb.sh
sudo ifconfig usb0 192.168.137.1
sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.137.0/24
echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward 
sudo iptables -P FORWARD ACCEPT

This works at least with Ubuntu saucy chroot. The main difference in some other distro might be whether the resolv.conf has moved to /run or not. You should be now all set up to browse / apt-get stuff from the device again.

Update: Clarified that this is to forward the desktop/laptop's network connection to the device so that network is accessible from the device over USB.

Blankon developers: Sokhibi: Daftar Isi Artikel Inkscape

Istana Media — 2013-05-21T09:46:26+00:00

Karena tulisan blog saya sudah lumyan banyak dan bercampur aduk antara artikel satu dan lainnya, maka untuk memudahkan pencarian artikel tertentu maka saya membuat daftar isi secara sederhana. Halaman ini hanya berisi daftar isi tautan dari beberapa artikel yang berkaitan langsung dengan desain grafis terutama Inkscape, untuk menuju artikel sesungguhnya, klik pada salah satu judul artikel

Blankon developers: Sokhibi: Membuka, Menyimpan, dan Menutup Project pada Inkscape

Istana Media — 2013-05-21T09:43:34+00:00

Sambungan dari Mengenal Antarmuka Inkscape Membuat Halaman Baru Klik File => New => pilih jenis canvas yang akan dipakai, atau tekan tombol Ctrl+N pada keyboard, cara lainnya klik ikon New pada Command Bar Membuka File Klik File => Open, tombol Ctrl+O pada keyboard, kemudian lakukan pencarian file atau project yang akan Anda buka Untuk melihat tampilan gambar yang akan

Blankon developers: Sokhibi: Mengatur Canvas dan Halaman Kerja pada Inkscape

Istana Media — 2013-05-21T09:41:40+00:00

Sambunagan dari Membuka, Menyimpan, dan Menutup Project pada Inkscape Mengatur Canvas Agar saat membuat gambar lebih mudah sebaiknya kita melakukan pengaturan halaman kerja terlebih dulu, untuk melakukan pengaturan Canvas (area kerja) lakukan langkah berikut: klik File => Document Properties (Shift+Ctrl+D) Setelah jendela pengaturan halaman tampil di layar,

ZevenOS-Neptune: Neptune 3.1 is ready

leszek — 2013-05-21T08:51:13+00:00

The Neptune team is proud to announce the release of Neptune 3.1 (Codename “Brotkasten”).
We worked hard and spend a lot of effort in creating this service release for Neptune 3.0. So if you like it please consider donating to us a small amount of money so we can further develop and strenghtens our efforts.
You can donate via paypal:

This release features the linux kernel 3.9.2 and is exclusively meant to run on 64bit CPUs. The Debian base system was updated to the released version 7.0 wheezy to provide a stable user experience. The KDE Plasma Desktop ships with version 4.10.3. Chromium was updated to version 26, Kdenlive 0.9.6, Amarok 2.7.1 and LibreOffice to version 4.0.3. We ship with the latest and greatest multimedia codecs preinstalled aswell as the flashplayer. For wireless diagnosis we ship Wireshark, Aircrack-ng and kismon.

We a lot effort in adding some new applications and fixing of bugs.
We now include the brandnew Ardour 3.1 audio editing suite including the jackd audio daemon. We added the disk-manager as an graphical application to manage your /etc/fstab mount options. We also added the easy to use knetworkmounter which uses fuse and mount to directly mount remote folders. You can call run the program with the hotkey Super+K (Win+K). We added apper as the new default software center. For the first time we also support the usage of zram in the kernel which creates a compressed swap file in memory for low memory computers. It can be activated by installing the neptune-zram-config package.

Default Desktop

Upgrade notice:
To upgrade Neptune 3.0 to 3.1 just perform an normal system update. This will upgrade the system except for LibreOffice which must be updated manually by performing the instructions in the forum. To Upgrade KDE please enable the Neptune KDE Repository.
Adding new applications like disk-manager, knetworkmounter, apper needs to be done manually.

DOWNLOAD

The changes in an overview:

New kernel 3.9.2
KDE SC 4.10.3 with customized notification center
updated Debian base to 7.0 Wheezy
Added f2fs filesystem support
Upgraded Gparted to handle new filesystems and load faster
fixed zevenos-hardwaremanager
Updated LibreOffice to version 4.0.3
Added knetworkmounter
Added Apper as default software center
Updated Amarok to version 2.7.1
Updated Kdenlive to version 0.9.6
Downgraded muon to a working version of 1.4
Enabled Multiarch
ISO is now build as hybridiso so it can be dd’ed onto a usb stick

Blankon developers: Budiwijaya: Varnish – tips trick #1

Blankon developers — 2013-05-21T08:11:05+00:00

Here’s varnish tips trick number 1

How to check varnish rule? Create a file (ie: check-varnish.sh) with this content:
#!/bin/bash varnishd -C -f /etc/varnish/default.vcl

How to check top domain on multi domain varnish configuration? Create a file (ie: check-top-domain.sh) with this content:
#!/bin/bash varnishtop -i RxHeader -C -I ^Host

Ubuntu developers: Bryce Harrington: pingssh

Ubuntu developers — 2013-05-21T03:37:51+00:00

For graphics testing on Ubuntu I typically ssh into one or more test machines, fiddle with them, reboot them, and then re-ssh into them. Since the machine won’t accept ssh connections until it’s pretty far along in boot, I often have to re-ssh multiple times. Instead, I made a script that retries ssh until it succeeds.

#!/bin/bash

# pingssh

if [ -z "${1}" ]; then
    echo "Usage: pingssh "
fi
host=$1

while : ; do
    count=50
    while ! ping -qc1 -W1 $host > /dev/null; do
	echo -n "?"
	sleep 0.2
	count=$(( count - 1 ))
    done
    echo

    ssh ${host}
    ret=$?
    if [ $ret = 0 ]; then
	exit 0
    elif [ $ret = 255 ]; then
	sleep 0.5
    fi

    echo -n "!"
done

Ubuntu developers: Valorie Zimmerman: Why we do this crazy thing we do

Valorie Zimmerman — 2013-05-21T03:36:42+00:00

Looking through a nice blog by Andreas Schilling, I found this classic linked:

It catches very well why we're here, and perhaps why you are reading this blog.

Also, if you are mentoring in GSoC or Season of KDE this year, remind yourself what motivates you and your students, both. We all want to make the world a better place.

Ubuntu developers: Scott Kitterman: We have a winner (actually three) – Kubuntu Council 2013 elections

Ubuntu developers — 2013-05-21T02:21:42+00:00

The results are in. The Kubuntu Council is selected from among and by Kubuntu members. There are six council members. Each serves a two year term, so we elect half the council each year. The winners are:

Philip Muskovac (yofel)
Rohan Garg (shadeslayer)
Valorie Zimmerman (valorie)

Congratulations and welcome. All three are first time council members.

The Kubuntu Council is the governing body of Kubuntu. The Kubuntu Council has three primary roles:

Approve development plans for future Kubuntu releases
Approve Kubuntu membership applications
Resolve disputes within the Kubuntu project

Fortunately, we had our own mini vUDS today so we’ve now got a good idea what we want to have the new council approve.

Ubuntu developers: The Fridge: Ubuntu Weekly Newsletter Issue 317

Ubuntu developers — 2013-05-20T22:59:08+00:00

Welcome to the Ubuntu Weekly Newsletter. This is issue #317 for the week May 13 – 19, 2013, and the full version is available here.

In this issue we cover:

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

Elizabeth Krumbach Joseph
Paul White
John Kim
Benjamin Kerensa
David Morfin
Amber Graner
The Alpaca Herder
Jim Connett
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

Ubuntu developers: Jono Bacon: New Song

Ubuntu developers — 2013-05-20T22:50:58+00:00

Since Jack was born my music has taken something of a back seat. Recently I got the itch to write a new song and here is my first metal tune since he was born. It is an instrumental named after his onesie with chimp feet. I wanted to enjoy writing a song that spins around a little bit without the need to make it radio-length. As such it weighs in at just under 7 1/2 minutes. Anyone want to make a music video for it.

I wrote and recorded this in my home studio and played the guitars and bass; drums are programmed this time around. Licensed as CC-BY-SA.

Download It Here

Ubuntu developers: Tony Whitmore: Otherwise engaged

Ubuntu developers — 2013-05-20T21:27:00+00:00

It’s been a manically busy few weeks so I’m not going to write much today, just share some photos from some of the engagement sessions that I’ve photographed recently. In no particular order.

Rachel and Dan are getting married later this year in Cambridge. We went to a nature reserve near Basingstoke for their photo session.

Sarah and Marcus are getting married next month. For their photo session we revisited the site of their first date, and where Marcus had proposed. Right there on that very bench!

Andrew and Callum are getting married this week. When I went into their flat and saw the rows of Doctor Who DVDs on their shelves I knew we were going to get along. We went to a Doctor Who location for this photo session.

Lucy and James got married at the Tithe Barn in Petersfield, but we went to the Queen Elizabeth Country Park for their engagement photo session. The morning sun poured through the mist and created some rather special lighting.

Pin It

Ubuntu developers: Ubuntu Classroom: Ubuntu Open Week for Raring: Almost Here!

Ubuntu developers — 2013-05-20T17:44:54+00:00

In just nine years, Ubuntu has become one of the most popular Linux distributions in the world with millions of users and a thriving community. Ever wondered what all the fuss is about? How have we achieved such a great feat in such a short space of time? Here’s where you can find out. Ubuntu Open Week is a week of IRC tuition and Q+A sessions all about getting involved in the rock-and-roll world that is the Ubuntu community. We organise this week for the beginning of a new release cycle to help new contributors get involved.

Ubuntu Open Week takes place in #ubuntu-classroom on irc.freenode.net (#ubuntu-classroom-chat for questions), on May 20th-21st, from 13 to 18 UTC each day. We will be having people from different teams in, such as the Quality team, the Development team, the News team, and more! We are also going to have an “Ask Mark!” session with Mark Shuttleworth, the Ubuntu Community founder!

During the “Ask Mark!” session, community members are invited to ask Mark Shuttleworth (sabdfl) questions about the Ubuntu project. You will ask your questions in #ubuntu-classroom-chat with the prefix QUESTION: and philipballew will be selecting specific questions to pass along to Mark in the main #ubuntu-classroom channel.

To check out the full schedule and learn more about the event, visit the Ubuntu Open Week page on the Ubuntu wiki (we’re finishing to nail the schedule!)

We hope to see you there! But if not, as always, logs will be available after each session, and linked to the schedule at the end of each day.

Blankon developers: Sokhibi: Mengenal Antarmuka Inkscape

Istana Media — 2013-05-20T14:58:04+00:00

Antarmuka Inkscape Antarmuka Inkscape terdiri dari, nama aplikasi, menu dan command bar, control bar, kanvas, toolbox, pallete, status bar, dan lain-lain. Sebelum menggunakan program pengolah gambar Inkscape sebaiknya kita mengenal dulu beberapa menu penting yang ada pada Inkscape, karena dengan mengenal menu-menu penting tersebut akan mempermudah dalam penggunaan program ini:

Ubuntu developers: Adam Stokes: python-salesforce on pypi

Ubuntu developers — 2013-05-20T14:04:34+00:00

I've got a project going to utilize Salesforce.com api over json and oauth rather than soap. Today I uploaded the package to the cheeseshop in hopes to pull in some interest from the community.

Right now the library contains authorization over OAuth 1.0a and client methods for retrieving basic Account, Case, and Asset information. My goal is to be api complete by the end of the year.

I would love to have contributors join the project in order to shape this young project into a well documented, tested, and easy to use library. As far as I can tell there isn't another python library like this that doesn't utilize SOAP for its endpoints.

Using the library is pretty straight forward, currently, I have 2 scripts that provide a simple way to authorize yourself and communicate with the endpoints.

sf-exchange-auth provides a local ssl enabled web server for going through the OAuth process and storing your token/secret.

sf-cli provides some arguments for pulling in rudimentary account and case information. Usage documentation is provided for this script.

The current focus is to stick to the YAGNI principles and utilize OO when it makes sense. This may or may not be the way to go so I am open to ideas and patches :D.

You can currently install python-salesforce through pip

  $ pip install python-salesforce

The project page is located at

http://python.salesforce.astokes.org

Looking forward to hearing from you.

Ubuntu developers: Adam Stokes: python-salesforce on pypi

Ubuntu developers — 2013-05-20T14:04:34+00:00

I've got a project going to utilize Salesforce.com api over json and oauth rather than soap. Today I uploaded the package to the cheeseshop in hopes to pull in some interest from the community.

Right now the library contains authorization over OAuth 1.0a and client methods for retrieving basic Account, Case, and Asset information. My goal is to be api complete by the end of the year.

Using the library is pretty straight forward, currently, I have 2 scripts that provide a simple way to authorize yourself and communicate with the endpoints.

sf-exchange-auth provides a local ssl enabled web server for going through the OAuth process and storing your token/secret.

sf-cli provides some arguments for pulling in rudimentary account and case information. Usage documentation is provided for this script.

The current focus is to stick to the YAGNI principles and utilize OO when it makes sense. This may or may not be the way to go so I am open to ideas and patches :D.

You can currently install python-salesforce through pip

  $ pip install python-salesforce

The project page is located at

http://python.salesforce.astokes.org

Looking forward to hearing from you.

Ubuntu developers: Ralph Janke: Respect is a Bi-Directional Proposition

Ubuntu developers — 2013-05-20T04:51:37+00:00

Jono has written a very good post on his blog about respect in the community. I agree with the importance of respect in a community. It was also important to clarify that having different opinions or perspectives are not a sign of disrespect and are very important in a community even if consent cannot always be found. That is life, but not issuing different perspectives will disadvantage a community.

However, respect is a two-directional proposition. It is difficult to maintain respect, if every time there is a disagreement and passion creates tension, it is the fault of the community. In particular the vast differences in power create different points of breaking points and hence it sometimes may be far too easy to make comparisons on an equal level, or use objective tests to try to rationalise or use relativism. Pontifications of cult leaders rarely lead to respect, more often it is rather dissension or fear that are the result. This post is not supposed to in any way contradict the points Jono made in his blog post, but rather add another perspective to it.

Ubuntu developers: Ubuntu Ohio - Burning Circle: Burning Circle Episode 113

Ubuntu developers — 2013-05-20T03:35:36+00:00

This week's episode is brief and is the first after the close of the production suspension. A rough transcript is presented below for the avoidance of doubt.

Download here (MP3) (ogg) (FLAC), or subscribe to the podcast (MP3) to have episodes delivered to your media player. We suggest subscribing by way of a service like gpodder.net.

This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/.

And we're back...

Welcome to the Burning Circle. The production suspension has now concluded. For release on Monday, May 20th, this is episode 113.

I have sent to the e-mail list and posted elsewhere a notes update to bring everybody up to speed as to what is going on. I will not reiterate it here. If you need a link to it you will be able to find such in Ubuntu Weekly Newsletter 317. You are subscribed to the Ubuntu Weekly Newsletter, aren't you?

We've had three folks attempt to join our community. I have disapproved two already and one remains in the pool. As a rule of thumb, I do ask that if I e-mail you that you please respond to me within a week. Within that amount of time, even a postcard can reach me via the United States Postal Service. Two people seeking to join did not contact me within a week's time and after multiple e-mails greeting them. One person remains in the queue with four day left to say something even if it is to tell me to go away. As a local community we have to be about more than just collecting a stylized Ohio flag logo on your Launchpad page. My biggest fear is that that has been the case a couple hundred times already.

We're heading into the Saucy Salamander cycle. We're way, way too quiet across the state. We have a mailing list. We have an IRC channel. We have a voicemail drop box to contact the leader. We need to speak up more as a community.

From the south shores of Lake Erie in the border port community of Ashtabula Township, this program has been brought to you over the facilities of the Internet Archive and Ubuntu Ohio by Erie Looking Productions. Our producer, Gloria "The Half Million Dollar Woman" Kellat, remains on medical leave. Our owner and engineer is Mike Kellat. I am the head writer, Stephen Michael Kellat. This program is released under a Creative Commons Attribution Share-Alike 3.0 United States license.

Thank you for joining us.

Ubuntu developers: John Baer: Ubuntu 13.04 – Enable Google Music All Access

Ubuntu developers — 2013-05-20T01:42:49+00:00

There may not be a native solution, but Google Music All Access is available in Ubuntu 13.04 today as a web app.

Turn On Notifications

To fully enjoy the Google music experience, notifications should be present. I am only going to turn on notifications within Chrome but you may explore a more intimate integration at this webupd8 blog post.

The first step is to load Google Music using the Chrome browser. I am using the beta version 27.0.1453.81. Press the setting button located in the upper right quadrant of the browser window and select Music Labs.

Find Desktop Notifications from the list and click enable.

Add Google Music as a Web App

Although you may run this directly from the Chrome browser, the secret to an enhanced user experience is adding Google Music as a Ubuntu web app. For the details on how to accomplish this see; Ubuntu – A Replacement for Chrome OS.

Enroll In Google Music All Access

You can stream music in your library to any device or computer via a browser on which you’re signed in. You can also download music in your library to any authorized device or computer. You can authorize up to a total of ten (10) devices or computers at any one time. At this time, only two Google accounts per computer can be used to add music with the Google Play Music Manager.

Click the Try It Free for 30 Days button to begin your registration. For your awareness a list of Authorized devices will be displayed for your consideration and you will be prompted to enter credit card payment info.

Start Playing Music

Ubuntu Integration

Enjoy : )

The post Ubuntu 13.04 – Enable Google Music All Access appeared first on j-Baer.

Ubuntu developers: Jono Bacon: Respect in Community Discussion and Debate

Ubuntu developers — 2013-05-19T23:30:19+00:00

Recently there was yet another storm in a teacup that distracted us from creating and sharing Ubuntu and our flavors with others. I am not going to dive into the details of this particular incident…it has been exhaustively documented elsewhere…but at the heart of this case was a concern around the conduct in which some folks engaged around something they disagreed with. This is not the first time we have seen disappointing conduct in a debate, and I wanted to share some thoughts on this too.

In every community I have worked in I have tried to build an environment in which all view points that challenge decisions or decision makers are welcome with the requirement that they are built on a platform of respectful discourse; this is the essence of our Code Of Conduct. Within the context of an Open Source community we also encourage this engagement around differences to be expressed as solutions with a focus on solving problems; this helps us to be productive and move the project forward. This is why we have such a strong emphasis on blueprints, specs, bugs, and other ways of expressing issues and exploring solutions.

Within the context of this most recent issue I saw three problems (problems I have seen present in other similar arguments too):

Irrespective of the voracity or content of an opinion we must never forget to be respectful and polite in the way we express and engage with others, irrespective of whether you are a volunteer, Canonical employee, or otherwise. Respect must always be present in our discourse, irrespective of the content of our opinions; without it we become a barbaric people and lose the magic that brought this wonderful set of minds together in the first place. There is simply no excuse for rudeness, and inflammatory FUD that has no evidence to back it up other than presumed ill-intent serves nothing but to demotive folks and ratchet up the flames, as opposed to resolve the issue and make things better.
Trust needs to be earned, but trust should always be built within the wider context of a set of contributions and conduct. Unfortunately some folks consider decisions they disagree with to be a basis for (a) entering into a paranoid debate about the “real reason” the individual or company made that decision (and typically not believing the rationale provided by said decision-maker) and (b) seemingly forgetting about all the other positive contributions that the person or company has contributed. I can assure you there is no nefarious scheme at place at Canonical; our goals are well known in the community. If I felt Canonical was fundamentally trying to demote and shut the community out, I wouldn’t work here; I have no interest in working for a company that doesn’t understand the value of community, and I am not worried about finding suitable employment elsewhere. I work at Canonical because I believe our goals with Ubuntu are just and the company’s commitment to our community is sincere.
Ubuntu is not a consensus-based community. Consensus communities rarely work, and I am not aware of any Open Source project that bases their work on wider consensus in the community. It would be impossible and impractical to notify our community of every decision we make, let alone try to base a decision on a majority view, but we do try to ensure that major changes are communicated to our leaders first (this is something we have been driving improvements in recently). We always need to find the right balance between transparency and JFDI, and sometimes the balance isnt’t quite there, but that does not mean there is some kind of illuminati-ish scheme going on behind the scenes.

Ubuntu is a community filled with passionate people, and I love that we have folks who are critical of our direction and decisions. If everyone agreed with what we are doing, we would not always make the right decisions, and our diversity is what makes Ubuntu and our flavors such a great place to participate.

As I said at the beginning of this post, it is important that all viewpoints are welcome, but we have to get the tone and conduct of some of these debates under control. The sheer level of sensationalist and confrontational language that is often in place in these disagreements doesn’t serve anyone but hungry journalists looking for page hits.

Now, I am not suggesting here that anyone should change any of their viewpoints. If you vehemently disagree with an aspect of what we are doing in Ubuntu or at Canonical, that is fine and of course, welcome. What I am appealing to everyone though is to treat others like you wish to be treated, with respect and dignity, and lets keep the sensationalism out of our community and focus on what we do best…building a world-class Free Software platform and its rich ecosystem of flavors.

Grml developers: Evgeni Golov: powerdyn – a dynamic DNS service for PowerDNS users

Grml developers — 2013-05-19T21:45:55+00:00

You may not know this, but I am a huge PowerDNS fan. This may be because it is so simple to use, supports different databases as backends or maybe just because I do not like BIND, pick one.

I also happen to live in Germany where ISPs usually do not give static IP-addresses to private customers. Unless you pay extra or limit yourself to a bunch of providers that do good service but rely on old (DSL) technology, limiting you to some 16MBit/s down and 1MBit/s up. Luckily my ISP does not force the IP-address change, but it does happen from time to time (once in a couple of month usually). To access the machine(s) at home while on a non-IPv6-capable connection, I have been using my old (old, old, old) DynDNS.com account and pointing a CNAME from under die-welt.net to it.

Some time ago, DynDNS.com started supporting AAAA records in their zones and I was happy: no need to type hostname.ipv6.kerker.die-welt.net to connect via v6 — just let the application decide. Well, yes, almost. It’s just DynDNS.com resets the AAAA record when you update the A record with ddclient and there is currently no IPv6 support in any of the DynDNS.com clients for Linux. So I end up with no AAAA record and am not as happy as I should be.

Last Friday I got a mail from DynDNS:

Starting now, if you would like to maintain your free Dyn account, you must now log into your account once a month. Failure to do so will result in expiration and loss of your hostname. Note that using an update client will no longer suffice for this monthly login. You will still continue to get email alerts every 30 days if your email address is current.
Yes, thank you very much…

Given that I have enough nameservers under my control and love hacking, I started writing an own dynamic DNS service. Actually you cannot call it a service. Or dynamic. But it’s my own, and it does DNS: powerdyn. It is actually just a script, that can update DNS records in SQL (from which PowerDNS serves the zones).

When you design such a “service”, you first think about user authentication and proper information transport. The machine that runs my PowerDNS database is reachable via SSH, so let’s use SSH for that. You do not only get user authentication, server authentication and properly crypted data transport, you also do not have to try hard to find out the IP-address you want to update the hostname to, just use $SSH_CLIENT from your environment.

If you expected further explanation what has to be done next: sorry, we’re done. We have the user (or hostname) by looking at the SSH credentials, and we have the IP-address to update it to if the data in the database is outdated. The only thing missing is some execution daemon or … cron(8). :)

The machine at home has the following cron entry now:

*/5 * * * * ssh -4 -T -i /home/evgeni/.ssh/powerdyn_rsa powerdyn@ssh.die-welt.net

This connects to the machine with the database via v4 (my IPv6 address does not change) and that’s all.
As an alternative, one can add the ssh call in /etc/network/if-up.d/, /etc/ppp/ip-up.d/ or /etc/ppp/ipv6-up.d (depending on your setup) to be executed every time the connection goes up.

The machine with the database has the following authorized_keys entry for the powerdyn user:

no-agent-forwarding,no-port-forwarding,no-pty,no-X11-forwarding,no-user-rc,\ 
command="/home/powerdyn/powerdyn/powerdyn dorei.kerker.die-welt.net" ssh-rsa AAAA... evgeni@dorei

By forcing the command, the user has no way to get the database-credentials the script uses to write to the database and neither cannot update a different host. That seems secure enough for me. It won’t scale for a setup as DynDNS.com and the user-management sucks (you even have to create the entries in the database first, the script can only update them), but it works fine for me and I bet it would for others too :)

Update: included suggestions by XX and Helmut from the comments.

Ubuntu developers: Benjamin Mako Hill: The Cost of Inaccessibility at the Margins of Relevance

Ubuntu developers — 2013-05-19T16:00:05+00:00

I use RSS feeds to keep up with academic journals. Because of an undocumented and unexpected feature (bug?) in my (otherwise wonderful) free software newsreader NewsBlur, many articles published over the last year were marked as having been read before I saw them.

Over the last week, I caught up. I spent hours going through abstracts and downloading papers that looked interesting or relevant to my research. Because I did this for hundreds of articles, it gave me an unusual opportunity to reflect on my journal reading practices in a systematic way.

On a number of occasions, there were potentially interesting articles in non-open access journals that neither MIT nor Harvard subscribes to and that were otherwise not accessible to me. In several cases where the research was obviously important to my work, I made an interlibrary request, emailed the papers’ authors for copies, or tracked down a colleague at an institution with access.

Of course, articles that look potentially interesting from the title and abstract often end up being less relevant or well executed on closer inspection. I tend to cast a wide net, skim many articles, and put them aside when it’s clear that the study is not for me. This week, I downloaded many of these possibly relevant papers to, at least, give a skim. But only if I could download them easily. On three or four occasions, I found inaccessible articles at this margin of relevance. In these cases, I did not bother trying to track down the articles.

Of course, what appear to be marginally relevant articles sometimes end up being a great match for my research and I will end up citing and building on the work. I found several suprisingly interesting papers last week. The articles that were locked up have no chance at this.

When people suggest that open access hinders the spread of scholarship, a common retort is that the people who need the work have or can finagle access. For the papers we know we need, this might be true. As someone with access to two of the most well endowed libraries in academia who routinely requests otherwise inaccessible articles through several channels, I would have told you, a week ago, that locked-down journals were unlikely to keep me from citing anybody.

So it was interesting watching myself do a personal cost calculation in a way that sidelined published scholarship — and that open access publishing would have prevented. At the margin of relevance to ones research, open access may make a big difference.

Maemo developers: SeriesFinale for BlackBerry

Joaquim Rocha — 2013-05-19T09:51:24+00:00

I would like to share with you this port of SeriesFinale for Blackberry.

Unlike the other versions, I was not involved in the development of this one. It was developed by Micke Prag, who also started the Meego/N9 port back in the day.
I developed the first version of SeriesFinale in 2009 for the defunct Maemo system and released also a version for the N9/Meego in 2011 (there was also a version for GNOME but I never finished it…). It is very good to see that it continues its life even if I am not involved this time.

I don’t own a BlackBerry so I am not able to try it but judging from this video, it definitely looks good so if you’re a BB user, check it out!

Judging from the success that a clone for Android and a similar online service have, it seems like I could have started a whole business out of it…

0 0

Blankon developers: Iang: Improvisasi

Fajran Iman Rusadi — 2013-05-19T08:15:20+00:00

Salah satu fitur yang ada di OS X adalah penyuaraan tulisan alias "Text to Speech". OS X menyediakan sebuah aplikasi command line yang memungkinkan kita untuk meyuarakan tulisan apa saja yang kita masukkan

$ say "How are you?"

Dari sekian penyuara yang tersedia, salah satunya adalah Damayanti yang bisa menyuarakan Bahasa Indonesia

$ say -v Damayanti "Apa kabar?"

Ternyata si Damayanti ini bisa berimprovisasi menambahkan kata yang tidak kita tuliskan di sana. Coba saja jalankan perintah berikut.

$ say -v Damayanti "Sudah 5 hari aku berdiri selama 5 menit dan 5 detik setiap 5 jam"

Blankon developers: Sokhibi: Daftar Isi Artikel Libre Office

Istana Media — 2013-05-19T04:20:12+00:00

Halaman ini hanya berisi daftar isi tautan dari beberapa artikel yang berkaitan langsung dengan Libreoffice, untuk menuju artikel sesungguhnya, klik pada salah satu judul artikel atau klik kanan judul artikel kemudian pilih "Open Link in New Tab" untuk membuka pada tab baru. Fungsi tombol Papan Tik pada LibreOffice Writer Mengenal Ikon pada LibreOffice Writer Membuat Surat

Blankon developers: Sokhibi: Backup Aplikasi yang sudah terpasang di BlankOn

Istana Media — 2013-05-19T03:19:07+00:00

Kemarin di Group Facebook BlankOn ada salah satu anggota group yang tanya begini "mas , cara backup aplikasi di blankon bagaimana?" Kemudain dijawab oleh beberapa anggota lainnya seperti yang tampak pada gambar diatas Jawaban diatas memang benar bisa dilakukan dengan syarat User belum melakukan perintah "apt-get-clean" dan sejenisnya, jika sudah melakuan perintah tersebut tentu saja pada

Ubuntu developers: Adolfo Jayme Barrientos: Interesting reads today

Ubuntu developers — 2013-05-19T02:40:07+00:00

“Open source is not a warzone. Not every man is a dick.” A lovely essay from Perl girls, I truly enjoyed reading it.
“The water we swim in.” Valorie has nailed it with this: “most of the people discussing the issue seem to be talking past the folks they are hoping to connect with.” FWIW, I just think this whole shitstorm over the Community link is too overblown, too melodramatic, a whole tornado was created inside a small glass of water. The Hitler comparisons were ridiculous, unnecessary and embarrasing for the rest of us.

Emdebian developers: pybit 1.0.0 - distributed, scalable builds direct from VCS or archives

Neil Williams — 2013-05-19T00:02:28+00:00

PyBit is a distributed build system able to build packages in response to VCS commits or other triggers, across multiple architectures, multiple clients and multiple build environments with automated uploads to a nominated repository.

Support is included in 1.0.0 for building Debian packages using sbuild in response to subversion commits or changes in debian-devel-changes@lists.debian.org (by using apt as a version control handler) for any architecture and build environment which sbuild can support. There is also an example git commit template. Pybit has been designed to be fully extensible, so support for RPM or other package formats can be added as well as other version control handlers, other build environments and other architectures. Pybit is also scalable, when one type of client is struggling with the workload, another machine of the same architecture can be added to the pool to share the load. Pybit can also build a package for any number of architectures and build environments at the same time. The Pybit web interface provides an at-a-glance summary of all current builds as well as options to blacklist certain combinations, cancel and retry specific jobs and add monitor each pybit client. Current use cases include:

Rapidly changing VCS - one or more subversion repositories with lots of Debian packages, built automatically for any number of build environments and architectures every time the debian/changelog is modified. Clean chroot builds provide continuous integration testing of the every package.

Rebuilding the archive with different compilers or flags - a dedicated email account subscribed to debian-devel-changes@lists.debian.org feeding messages through procmail to the changes-debian hook, passing build requests to the apt handler to rebuild each package in your own sbuild chroots, using whatever environments, suites and build options can be configured within those chroots.

something else we haven't thought of yet ... there is scope for a lot more hooks, package formats, chroot tools and handler plugins.

arrived in Debian unstable

https://freecode.com/projects/pybit

http://nicholasdavidson.github.io/pybit/

https://github.com/nicholasdavidson/pybit

Ubuntu developers: Valorie Zimmerman: The water we swim in

Valorie Zimmerman — 2013-05-18T23:03:30+00:00

Healthy relationships. I've been thinking about them not in my personal life, but in terms of teams in free software. When I first began contributing, it was within a team creating an application (Amarok), so rather small. Then I became active in Ubuntu-Women, which is larger, but still not huge. Then Kubuntu, then the larger Ubuntu community, and now KDE, which is truly enormous.

In all of these projects, communication and trust are paramount. Dialog which fosters creativity and progress is only possible when people enlarge their trust in one another. Along the way to the highest trust levels, many barriers will come down, as people allow them. Sometimes these barriers are invisible, until someone points them out.

I thought I'd seen a cartoon illustrating this story, but a web search tells me it's a story by David Foster Wallace:

Two young fish meet an older fish, who asks them “How’s the water?” The younger fish look at each other and say, “What the hell is water?”

I was reminded of this story recently while observing the various reactions to the removal of the Community link on Ubuntu.com, the portal to the Ubuntu project. The link is coming back, so I'm not complaining. However, what I've noticed is that most of the people discussing the issue seem to be talking past the folks they are hoping to connect with. The emotions expressed range from puzzlement, to shock and outrage, with little understanding on the other "side" on the perceptions causing these reactions.

So how is the water? To me, the drama played out completely predictably, because any time you have one company selling a product, and volunteers working in that same project, you will have class issues, and class is like the water fish swim in. People are often not aware of it, and thus have difficulty dealing with their emotions around it, because they have been taught to ignore it, or even that it doesn't exist. So when the designers removed the link, it was felt as a slap to the face of community members, while the designers see it as just a step to a clean, functional design. The conversation about this change at the recent vUDS clearly betrays this lack of understanding of the other on all sides. http://summit.ubuntu.com/uds-1305/meeting/21740/community-1305-ubuntu-website-planning/

There is no such thing as a culture without class. There are always power imbalances, and privileges. However, that doesn't mean that class is the death of the Ubuntu project, or that volunteers and companies can't happily co-exist. They can, but the fact of class must be acknowledged, and those with privilege and power must realize what they have, and use them on behalf of the project.

A healthy culture has hierarchy, but not one based on domination. In fact, in FOSS that is part of what we are attempting to dislodge, right? We want our hierarchies to be constructed for function, not to rule over us. For instance, those who demonstrate their skill in packaging or coding are given the right to upload to the repositories. And those who grant them that right are those who already have built their reputations by using their skill and trustworthiness in that domain.

Recently there has been a breakdown -- or an apparent breakdown -- in that hierarchy of function in Ubuntu. And I think that both those inside Canonical and those outside, perceive that the other is the one causing that break. So, some repair is needed.

All of our differences can be overcome as we build (or re-build) trust. However, all sides of the issue will need to think about, process emotion about, and finally discuss openly what has gone on. The replacement of the Community link alone will not mend this breach, nor will brief virtual UDS sessions. In fact, I think the lack of in-person face-to-face interaction is allowing this divide to grow.

Folks, we don't want resentment and suspicion to grow, so we are all going to need to work on this if the Ubuntu project is going to continue to thrive as a free software enterprise. In my opinion, thinking about and discussing class issues are fundamental to that effort.

This blog appears on the Linuxchix, KDE and Ubuntu planets, and these issues of class appear in all teams. Health and progress are the goal, and honest dialog is the means. I propose we look one another in the eye and start a conversation. These are difficult dialogs, but our health is at stake.

Ubuntu developers: Elizabeth Krumbach Joseph: Adopt a Salamander

Ubuntu developers — 2013-05-18T21:47:19+00:00

For each Ubuntu release I spend a little time finding a toy or other representation of the codename animal to use at booths, Ubuntu Hours and other events. I wrote about Quetzals and Pangolins here and you may have seen Raring here.

When the salamander came up I was confident that a toy would be easy to find, and indeed they were! Even better, I found that the World Wildlife Fund offers a $50 Hellbender Salamander Adoption Kit that ships with 2 plush salamanders! Mine arrived yesterday, I’ll be keeping one to use at our events and will find a way to give away the other (perhaps as part of the Ubuntu Women contest we’re planning? Or at some LoCo event?).

Event decoration + helping to save the actual animal, hooray!

Oh, and it is a release late, but while I was in Mérida, Mexico we stopped in to Miniaturas where I picked up some adorable quetzal earrings:

I think I’ll wear them to our San Francisco Ubuntu Hour on June 12th, and bring along the salamander!

Ubuntu developers: Seif Lotfy: Globaleaks 0.2 Alpha

Ubuntu developers — 2013-05-18T21:25:46+00:00

Globaleaks 0.2 Alpha is out.

Globaleaks is an open source project aimed at creating a worldwide, anonymous, censorship-resistant, distributed whistle-blowing platform. It enables organizations interested in running whistle-blowing initiatives to setup their own safe zone, where whistle-blowers and recipients can exchange data.

2 Years ago I helped out with the development of Globaleaks 0.1. And although I am not active anymore, I really support the initiative behind it. Now with the HERMES Center for Transparency and Digital Human Rights backing it up, it has grown a lot and shaped up to be a very organized and thought through project.

TL;DR:

Full rewrite
More flexible and extensible
Linux ready-made system and network hardened installation
Written in python using twisted
New Frontend

Try it out:

Try out the demo. It is pretty straight forward.

Help out:

As young project, Globaleaks can use some help fixing bugs. Just head to the wiki and read through it. It is pretty straight forward, and explains the modules, security concepts and set up instructions.

Globaleaks already has Debian and Ubuntu ready packages. An easy way to help out is to set up a PPA for us on Launchpad.

Get in touch:

You can contact the Globaleaks team at info () globaleaks org or on IRC on #globaleaks at irc.oftc.net

Here are some screenshots of the new frontend

Congratulations you are using Tor

Receiver selection page

The submission receipt

Configuring a receiver

Configuring a context

Blankon developers: Budiwijaya: Book Review: Mastering NGINX

Blankon developers — 2013-05-18T19:26:48+00:00

Mastering Nginx
by Dimitri Aivaliotis

Chapter 1 – Installing Nginx and Third party modules

This is a first step you need to do before doing any nginx things.
It’s includes the most easiest way to install nginx a.k.a installing from package manager for major distro.

apt-get for debian
yum for redhat
pkg_install for freebsd

And also step by step to make a custom install of nginx a.k.a compiling from source.

Chapter 2 – A configuration guide

Here’s the most important parts of nginx. The configurations.
The author writes in an easy to follow, where this is the most complicated part for beginner.

Chapter 3 – Using the mail module

Proxying mail service with nginx is one of nginx features. Eventhough I never use nginx with mail proxying, the author write clearly and easy to understand so I can imagine how it works.

In the end of chapter, there’s a sample of authentication program to use with mail proxy using ruby programming language.

Chapter 4 – NGINX as a Reverse Proxy

Reverse proxy is also a killer feature of nginx. Here’s alot example with various backends such as apache and memcache.

Chapter 5 – Reverse Proxy Advanced Topics

Here, an advanced use of nginx as reverse proxy is discussed.
Nginx as ssl-accelerator, security based on ip address, fine tuning reverse proxy and caching.

Chapter 6 – The NGINX HTTP Server

HTTP Server is the core of nginx function. A detailed discussion about nginx as http server.

Chapter 7 – NGINX for the Developer

Eventough the title says “for the Developer”, its helped me alot as a sysadmin to configure the behaviour of nginx. For example, the caching is discussed more detail in this chapter, how caching helps legacy applications.

Some important discussion are caching on memcache, caching on static files, changing content on-the-fly, SSI and generating secure links.

Chapter 8 – Troubleshooting techniques

This is what I love about this book. Here discussed how to troubleshoot most common error and common mistakes on configuring nginx.

The most simple troubleshoot is look at the log files, here explained inside-out about an error on log-files. Also there’s an advanced logging to make our lives as sysadmin easier. And some tips and trick about operating systems specific limits.

Conclusion

For me, this book is helped me alot how to configure and troubleshoot an nginx configuration. This book is suitable for newbie and advanced nginx users. What I loved most of this book is Appendix A: Directive Reference and Appendix B: Rewrite Rule Guide, it helps me alot on explanation of a directives and what is the default entry of that directive.

Overall, this book is a great books. The author is well written this book. You should buy this book if you serious onto nginx configuration.

Ubuntu developers: Scott Kitterman: Polls Closing Soon – Kubuntu Council Elections 2013

Ubuntu developers — 2013-05-18T19:20:08+00:00

As I’ve mentioned before, the 2013 Kubuntu Council elections are underway. You’ve got just over two days left to vote, so if you’ve been procrastinating, mission accomplished, now go vote.

Blankon developers: Sokhibi: Menambahkan menu Satuan pada LibreOffice Calc

Istana Media — 2013-05-18T16:19:56+00:00

Tadi siang karena sedang tidak ada kerjaan saya bongkar-bongkar kardus dan mengumpulkan barang-barang bekas yang sudah tidak terpakai untuk dijual ke tukang rongsok secara kiloan, seperti biasa saya berusaha membuat pembukuan apa yang dijual hari ini, karena dalam pembukuan tersebut harus membuat data dengan satuan kilogram (kg) sedangkan di LibreOffice Calc tidak tersedia menu satuan tersebut,

Ubuntu developers: Rafael Carreras: Raring Party in Barcelona

Ubuntu developers — 2013-05-18T10:04:52+00:00

Last Saturday, the Catalan LoCo Team did its Ubuntu Raring Ringtail Party at the Escola del Clot of Barcelona with some 80 people present in the different speeches and installs.

The day started with a little presentation about Ubuntu and Catalan LoCo Team. After that, there were two lectures from Sergi Grau: HTML5 and Android 4.2.

Simultaneously, on other room, it was the speech about the Free & Open Source Software Outreach for Women Program with Mònica Ramírez, Debian Developer.

After that, there were the talks about Metadistributions based on Ubuntu using Remastersys with Jordi Binefa and ChameleonPI (a Raspbian versions with games emulators for the Raspberry Pi) with its author Carles Oriol.

Joan de Gràcia presented the Linkat Edu 12.04, the official Catalan public school GNU/Linux distro, for the first time based on Ubuntu, and Jordi Binefa showed Free hardware with Ubuntu.

Meanwhile, on the install room, people worked on installations and clarification of doubts and we sold some LoCo Team T-shirts and gave away some Ubuntu installation and using guides.

As always, we ended the party with a draw of some T-shirts and an Ubuntu Handbook.

As you can see, after the party was completed, some of us went to lunch.

Tails: Tails 0.18 is out

Tails — 2013-05-18T09:23:45+00:00

Tails, The Amnesic Incognito Live System, version 0.18, is out.

All users must upgrade as soon as possible.

Changes

Notable user-visible changes include:

New features
- Support obfs3 bridges.
- Automatically install a custom list of additional packages chosen by the user at the beginning of every working session, and upgrade them once a network connection is established (technology preview).
Iceweasel
- Upgrade to Iceweasel 17.0.5esr-0+tails2~bpo60+1.
- Update Torbrowser patches to current maint-2.4 branch (567682b).
- Torbutton 1.5.2, and various prefs hacks to fix breakage.
- HTTPS Everywhere 3.2
- NoScript 2.6.6.1-1
- Isolate DOM storage to first party URI, and enable DOM storage.
- Isolate the image cache per url bar domain.
- Update prefs to match the TBB's, fix bugs, and take advantage of the latest Torbrowser patches.
- Make prefs organization closer to the TBB's, and generally clean them up.
Bugfixes
- Linux 3.2.41-2+deb7u2.
- All Iceweasel prefs we set are now applied.
- Bring back support for proxies of type other than obfsproxy.
Minor improvements
- Set kernel.dmesg_restrict=1, and make /proc/<pid>/ invisible and restricted for other users. It makes it slightly harder for an attacker to gather information that may allow them to escalate privileges.
- Install gnome-screenshot.
- Add a About Tails launcher in the System menu.
- Install GNOME accessibility themes.
- Use Getting started... as the homepage for the Tails documentation button.
- Disable audio preview in Nautilus.
Localization: many translation updates all over the place.

See the online Changelog for technical details.

Known issue

The web browser default search engine is Google, instead of the intended localized Startpage. You may select Startpage HTTPS in the search engine menu next to the Google icon.

I want to try it / to upgrade!

See the Getting started page.

As no software is ever perfect, we maintain a list of problems that affects the last release of Tails.

What's coming up?

The next Tails release is scheduled for June 27.

Have a look to our roadmap to see where we are heading to.

Would you want to help? As explained in our "how to contribute" documentation, there are many ways you can contribute to Tails. If you want to help, come talk to us!

Ubuntu developers: Elizabeth Krumbach Joseph: Virtual Ubuntu Developer Summit 1305

Ubuntu developers — 2013-05-18T03:42:03+00:00

Since I left for my wedding and honey moon a bunch of things happened! Ubuntu 13.04 was released, 13.10 was given the code name “Saucy Salamander” and Debian 7.0 Wheezy came out. Plus lots of exciting OpenStack development discussion that came out following the Summit (I left right after it). When I got back into the country on the 12th I had a lot to catch up on! I did my best to cram before sessions and certainly had to limit involvement to a handful of sessions that I was particularly keen on attending and so could get up to speed with quickly.

This was the first virtual UDS I was able to participate in, so it was all new to me. Essentially the the “fish bowl” (as seen here, I took this photo from my spot in the wider attendee seating) is replaced by a Google Hangout and the “wider attendee seating” is an IRC channel. For the 4 sessions I participated in this worked very well, session leads were pro-active about asking who wished to participate in the Hangout so everyone who wanted to was able to. A great deal of attention in all these sessions was given to the IRC channel, which is a contrast with in person UDS where the channel can sometimes get a bit left behind (even though it’s being projected, it was easy to forget once you get talking). I didn’t use the summit.ubuntu.com page for anything aside reference, preferring to pop out the etherpad and use my standard IRC client, but I appreciated it all being there as a resource (and I’m sure it was super helpful for newcomers to follow along!).

Cheri Francis and others in the Ubuntu Women session

I found the sessions I participated in to be productive and focused and when applicable resulted in a solid list of action items. I hope that the event also lessened the experience gap that was always present for in person vs. remote participants, we all got the same experience. Now I have to admit to not being a fan of using Google Hangouts for this (I like Google, but it is still a proprietary, closed-source tool that we have no control over), but I understand that the ease of use and immediate availability of videos on YouTube makes a compelling case. Perhaps my only other complaint is lack of cohesiveness that comes from an online event, I didn’t watch the introduction or the wrap up. I also didn’t participate in the “beer hangout” – I didn’t even know it was happening, and sitting in front of my computer with a beer in the middle of the day wasn’t particularly interesting to me. I only attended a few specific sessions and there was no “wandering into something that looks interesting” (instead I just went back to work) or the regular social down time we get to relax or sit down to hack on things. I do hope we can find some kind of replacement for the in-person events, it would be great to see something on the LoCo team level at conferences where we seek to have an expanded Ubuntu presence focused on contributors (perhaps an Ubucon with a participant track?).

And the venue… it was at home! In order to participate in the hangout I did feel the need to leverage my multiple monitors.

My desk is a bit chaotic

Now the sessions themselves…

– Planning for Ubuntu Community presence on the Ubuntu Website –

This was not a particularly productive session as far as action items were concerned, but it turns out that while I was gone the removal of the “Community” link from ubuntu.com took on a life of its own (and boy was I surprised to see my name end up in a recent Datamation article about it). Personally I was satisfied with Daniel Holbach’s blog post on the subject a day after the change was made, but it was nice to speak with with some folks from the Design team and allow everyone to confirm that no ill will was intended and that plans for a new and improved community site were moving forward. The session was kept short given the more structured session about the community site specifically planned for the following day.

YouTube video of the session here

– Ubuntu Women UDS-1305 Goals –

Huge thanks to Silvia Bindelli and Cheri Francis for doing all of the leg work for this session while I was gone, I felt very comfortable reviewing their pre-session notes and found a really great, collaborative environment upon joining in. The discussion began talking about an information scavenger-hung competition that the team will be doing in the coming months, seeking volunteers to assist. It then moved into a topic that I was really happy to see on the agenda – a user poll to see how the team could be most effective in serving our audience of women interested in Ubuntu. I find that the project needs a bit of an adjustment every couple of years to refocus on our current targets as Ubuntu and the open source ecosystem evolves, so I’m excited that we’re doing this. Finally, much of the session was spent discussing our intention to further collaborate with other groups seeking to encourage women in open source (and in technology in general).

YouTube video of the session here and I uploaded session notes here

– Revamping ubuntu.com/community –

Picking up from where discussion left off the previous day, this session was a focused on on concrete things that need to be done to get the proposed community website that was under development reviewed and published. I admit that job change + wedding planning had my attention diverted this past cycle so I wasn’t able to contribute to this project, but I made sure to spend time the night before to do a review of the content so I’d be prepared. I was able to go through some of my suggestions during the meeting and took a few action items to continue with a more thorough review and to collect some quotes and photos from the community to make the site more personal and approachable.

YouTube video of the session here and I uploaded session notes here

– Shaping a plan for the future of Ubuntu Documentation Team –

I can’t begin to say how pleased I was to see this session land on the agenda. The Ubuntu Doc team has been a very small team for a long time, and new contributors have struggled to participate as the docs for writing the docs got stale to a point where they were not useful. We’re at a very exciting time now where we have limited support from a couple of the (very busy!) former drivers of this team and at least two strong contributors who have committed to moving the project forward. The first thing on the agenda was addressing the updating of docs so that more contributors can get on-boarded. I was able to pitch in with a couple action items to nudge things along a bit, but I’m hopeful that this is the beginning of an exciting new phase for the team.

YouTube video of the session here and I uploaded session notes here

A Slimy Salamander (wait, you said Saucy?)

– Xubuntu –

Since the event was online, the Xubuntu team took advantage of the flexibility and ended up pulling their sessions from UDS proper and scheduling our sessions for the hour after UDS each day to tackle a series of blueprints designed for the coming months. I was able to use my YouTube account + Hangouts to replicate that portion of what main UDS was doing.

Discussion of most interest to me centered around our testing+release plans (should we do alphas? betas? which ones?) and documentation, but discussion of our limited developer force (want to grow it!), a proposal for a shortcut overlay and default applications also were discussed. A much better summary was posted on the Xubuntu website yesterday: Looking towards Xubuntu 13.10. Pasi Lallinaho also wrote bullet-point style summaries of Night 1 and Night 2 which include links to their respective YouTube videos.

In all, a productive UDS for me, I have a lot of work to do… :)

Blankon developers: Sokhibi: Mencetak Satu Tulisan Panjang ke beberapa Kertas

Istana Media — 2013-05-18T03:05:06+00:00

Pernah membuat tulisan besar-besar dan ingin di cetak secara bersambung dalam beberapa kertas, misal ingin membuat tulisan pengumuman dengan ukuran 100 x 50cm namun printer hanya mendukung untuk kertas dengan lebar maksimal 21,5 cm dan kertas yang tersedia hanya ukuran A4 (21,00 x 29,70 cm) Tidak tahu caranya?, tidak usah galau, baca tulisan ini sampai selesai dan ikuti caranya Buka

Blankon developers: Sokhibi: Benarkah Menggunakan Linux itu Sulit?

Istana Media — 2013-05-18T02:52:06+00:00

Dari beberapa obrolan dengan teman-teman baik obrolan secara nyata maupun lewat jejaring sosial banyak bilang jika memakai Linux itu Sulit, biasanya akan saya jawab “memang Linux itu sulit, saya aja gak bisa memakainya”, biasanya mereka akan tanya lagi “lha katanya gak pakai Windows, tapi gak pakai Linux juga” kalau mau tahu jawabannya, baca tulisan ini sampai selsesai :D Open Source

Whonix developers: looking for someone to create a graphic to explain Whonix's stream isolation feature

adrelanos — 2013-05-18T02:48:39+00:00

The details behind that feature will be explained and you will be hand over a draft.

Please contact me by mail:
adrelanos at riseup dot net

Ubuntu developers: Paul Tagliamonte: Hy: recent developments and some work from doctormo

Ubuntu developers — 2013-05-18T01:58:04+00:00

Thanks to DoctorMo for the hilarious photo. It’s just so good.

We’ve got Classes working, the usual fixes from the ‘crew, and native macros. Huzzah!

I’ve had to take the site down for now (well, stop updating it) because of a vulnerability I introduced (macros allow arbitrary code to run), which means, if anyone’s keen, they should add the sandboxing code to the Hy Site as well!

More coming soon!

Ubuntu developers: Stephen Michael Kellat: An Update in Notes

Ubuntu developers — 2013-05-18T00:00:01+00:00

Ubuntu Ohio Leader Notes for 2013-05-17

Continuing Attacks on freenode

Prior to the start of the recently concluded Ubuntu Developer Summit many saw freenode become subject to Denial of Service attacks. I first noticed such on May 11th. There recently has been a blog post made explaining the situation on freenode's administrative side.

As a bit of a contingency I am encouraging members of Ubuntu Ohio to update their Launchpad profiles by editing their listed Jabber (otherwise known as XMPP) IDs so that we have a bit of a roster there. We may end up considering a fall-back XMPP Conference Room if freenode hits heavier pockets of turbulence. For now the implementation of that conundrum is left as something for us as an interesting hypothetical to consider for the moment. Anybody who has ideas about how to implement such an XMPP Conference Room is encouraged to edit https://wiki.ubuntu.com/OhioTeam/XMPP on the Ubuntu Wiki Infrastructure to further collaboration.

Podcast Resumption

The two week suspension of Burning Circle should be wrapping up this week and a new episode is expected to be released on Monday, May 20th.

Ubuntu Developer Summit May 2013

The proceedings of Ubuntu Developer Summit May 2013 have concluded and I urge you to view the resulting YouTube videos created from the various Google Hangouts. One thing that was noted was that having this happen at the same time as Google I/O was a bad thing. The Xubuntu folks held some parallel sessions and published a blog post with summaries and an outline of their work plan for the Saucy Salamander cycle.

If this scheduling pattern continues the next summit should be held in August 2013. That will place it one month before Ohio Linux Fest 2013.

Ohio Linux Fest 2013

I have received a communication from Robert Ball concerning getting a table at Ohio Linux Fest 2013. I would like to deputize someone in our community located outside Ashtabula County to sign the contract for such and to handle that matter. Please contact me directly at skellat@ubuntu.com and we can discuss the matter.

An offer was received from Jorge Castro during a UDS session to bring in some people to assist with presenting an UbuCon. I still encourage members of our community to think of what they would like to present as we will get close to my issuing a call for topics. I do not currently have confirmation that space is available yet for us to do this but will be following up with Ohio Linux Fest organizers.

Ubuntu Ohio Projects For The Saucy Salamander Cycle

As a community we have three or four projects to consider during the Saucy Salamander cycle.

Consider the creation of a fall-back XMPP Conference Room
Prepare for Ohio Linux Fest 2013
The Ubuntu Advocacy Kit
Mentoring & Shepherding Community Members To Become Ubuntu Members

The first two items have been dealt with above. Jono Bacon and I engaged in a colloquy during an Ubuntu Developer Summit session about our community perhaps assisting in the development of the Ubuntu Advocacy Kit. Jono discussed further on his blog about the need for help with bringing the kit to version 1.0 and provides some basic instructions on how to get started. If there are community members who are interested in participating please follow the directions and dig in. If we need to spend time going over the mechanics of contributing using Bazaar, please let me know so that I can schedule an educational session.

The last project matter is one that I am taking on which is to help mentor and shepherd members of our community through the process of attaining Ubuntu Membership. Across the planet there are only 784 Ubuntu Members in the relevant Launchpad group at the time this is written. I want to help people grow in the community and become increasingly responsible for its growth and maintenance. This is an important step.

AND FINALLY...

NewsChannel 5 WEWS in Cleveland reports that the State of Ohio's average unemployment rate dropped by one-tenth of one percentage point to seven percent. The Ohio Department of Job and Family Services has a press release posted which provides a break-down of where employment shifted between March 2013 and April 2013. A table showing the changes by industrial group is also posted.

Ubuntu developers: Jono Bacon: Dogfooding the Ubuntu Phone: My (Early) Experience

Ubuntu developers — 2013-05-17T22:38:11+00:00

As many of you will know, our goal is to get the Ubuntu phone in a state where it can be used on a daily basis for testing, and importantly, finding bugs, UI issues, and other details that help us to refine the overall Ubuntu Touch experience. Progress is on-track for the end of May.

I decided to start dogfooding a little early (please remember, we are shooting for the beginning of July to be broadly in shape for dogfooding, so if you try, don’t expect things to be ready right now), so today I put my SIM card in my Galaxy Nexus with Ubuntu Touch and things are working pretty well so far. It seems that my data is no longer getting wiped on image updates, which helps testing significantly, so I am regularly upgrading with the daily images.

As ever, if you decide to test, you are doing so at your own risk…don’t be surprised to see bugs, crashes, and potential data loss (although I have not seen any data loss so far).

Some notes about my experience dogfooding:

Making and recieving phone calls works well. I am using T-Mobile as my network.
Sending and recieving texts works well too. Messages appear chronologically.
Contact syncing is not in place but Sergio blogged about how to sync your contacts from Google. This has made my phone infinitely more useful and rather nicely, it pulls in the avatars too so I can see who is calling me.
Browsing and connecting to wireless networks works well.
The browser works well overall, although currently requires wifi (3G browsing coming soon).
Camera works well (for still photos, video not implemented yet) and I can browse my pictures in the gallery.
Many of the community-written core apps are present and working. Calendar lets me save and browse calendar events (although syncing with a calendar service is not there yet). Weather shows me the weather for my area right now and a week long forcast. Calculator is working and largely feature-complete. Other core apps are on their way to the daily image soon.
Overall the core Unity UI is working well. I can search for apps, load them, quit them, multi-tasting works well, and the indicators work (for adjusting volume etc).

The primary blockers in my way right now for normal use out and about are:

The screen does not auto shut-off. This means if the screen gets turned on in my pocket it never turns off and the battery dies.
Speakerphone not wired into the UI yet.
Can’t set the time on the phone yet. Also, the alarm feature in the clock doesn’t work; I need this to get me up in the morning.
Not so much a blocker, but the phone is still filled with example material and contacts. They need to be removed.

All of these are on the TODO list for completion by the end of the month.

I have been filing bugs for a bunch of the issues I am seeing on a day to day basis and the team are working hard to hit the end of May goal. Overall progress is looking good.

Although I have been using the daily images for quite some time on a phone without a SIM card, using as an actual phone is even more motivating than before. I can feel the phone coming together and when we get many of these issues fixed, it is going to deliver a far superior experience than the Android phone I was using before.

Lihuen: ¡Lihuen 5 beta 1 publicada!

Lihuen — 2013-05-17T21:19:45+00:00

18:08 17 may 2013 (ART)~

Escritorio Cinnamon con el tema Bluebird

Ya está disponible en el área de descargas la primer versión beta de Lihuen 5 (basada en Debian Wheezy).

Al igual que la versión anterior hay ediciones para 32 y 64bits y múltiples variantes. En esta versión estrenamos el escritorio Cinnamon (originalmente de Linux Mint) como reemplazo para Gnome 2 y como siempre seguimos teniendo LXDE para equipos no tan potentes o para usuarios que quieren un entorno de escritorio rápido y sencillo.

Ubuntu developers: James Hunt: A simple two-player QML game for Ubuntu Touch using the Ubuntu SDK: noughts and crosses (aka tic-tac-toe)!

James Hunt — 2013-05-17T18:37:15+00:00

Inspired by Rick's recent blog posts, and keen to write a blog post with a ridiculously long title, I've been reading up on QML recently. Still bearing the scars from the XML horrors of working with J2EE in the early days, that 3-byte acronym ending in "ML" initially subconsciously somewhat filled me with trepidation. However, as soon as I actually saw some QML, I could see these fears were unfounded (! :-) And in fact I now love QML. It's clean, elegant, powerful, declarative and (OMG YAY!) you can even "%-bounce" on the braces in vim! :-) That said, the qtcreator IDE is extremely good, managing to provide just enough of what you want without requiring endless additional configuration.

But it doesn't stop there. The Design Team have done some incredible work in creating the Ubuntu SDK components: not only do they look fantastic (if you have the ubuntu-ui-toolkit-examples package installed, try running /usr/lib/ubuntu-ui-toolkit/demos/launch_componentshowcase), they are also extremely flexible and powerful.

As Rick has mentioned, it does take a while to grok the "QML-ish" way of doing things. And if like me you spend most of your time writing in imperative languages, initially you just think "all this QML is wonderful, but where do I actually put the code?". But then you have the epiphany moment when you realise you're already writing "the code" - in many cases, you don't need anything beyond the declarative QML itself.

I Need an Itch to Scratch

The only real way to learn a new language is to use it. But what to do? I wanted to code something simple and fun, like a game. There are already few games on the Collections page so I needed to think of a really simple one that is also fun to play. How about a game that even children can appreciate? Of course - Noughts and Crosses (aka tic-tac-toe)!

https://github.com/jamesodhunt/qml-noughts-and-crosses (GPLv3)

Note that the code is pretty rudimentary right now, but it's just about usable ;-)

Design

This is a simple game so we only need a few objects: Cell, Game and MainView.

The MainView is the container for the application and includes a Page and the actual Game object. The only property we specify for the game is the boardSize of 3 giving us a 3x3 board. Technically, we don't actually even need to specify this since -- as we're about to see -- 3x3 is the default board size anyway. So, the Game object could be specified minimally as "Game {}". However, I've left it specified as a reminder to myself that ultimately I'd like to pass a variable to allow the board size to be specified at game creation time.

Here is a slightly simplified version of the MainView (noughts-and-crosses.qml):

import QtQuick 2.0
import Ubuntu.Components 0.1

MainView {
       
    Page {
        title: "Noughts and Crosses"

        id: page

        Game {
            // change this to whatever value you want for an NxN-sized board
            boardSize: 3
        }
    }
}

The Game object is a Column and comprises a Label, to show some text relating to the game, and a Grid to actually represent the game. There is some magic going on in the grid as it uses the very cool Repeater object to make laying out the grid easy: for a 3x3 board it creates 9 Cell objects and packs them into the grid. Here's a cut-down version of the Game object:

Column {

    property alias boardSize: gameGrid.boardSize

    Label {
        id: text
        text: "Noughts goes first"
    }

    Grid {
        id: gameGrid

        // Default to a 3x3 board (we only support square boards).
        property real boardSize: 3

        // toggled between "O" and "X". The value specified below denotes
        // which side goes first.
        property string player: "O"

        columns: boardSize
        rows: boardSize

        // layout the appropriate number of cells for the board size
        Repeater {
            id: gridRepeater
            model: boardSize * boardSize

            Cell {
                width: 100
                height: width
            }
        }
    }
}

Note the property alias for boardSize in the Column object - it exposes a boardSize variable which is just a way to access the real variable of the same name within the Grid object. Note too that we tell the Grid object its dimensions by setting its columns and rows properties.

The Game object also contains a chunk of Javascript in the form of the checkForWin() function to determine whether a move resulted in the game being won.

The Cell object is the most interesting object. A Cell represents an individual location on the board. It is constructed from a Rectangle and comprises a Text value. The text value is either a middle-dot (to denote the cell has not yet been selected), a "O" or a "X". It also includes a MouseArea that specifies the new cell state to apply when the cell is clicked. Initially, the state is middle-dot but when the cell is clicked, the state is changed to the value of the parent (Game) objects player property. The Cell object specifies 3 states to represent every possible value a Cell can display. What's neat here is that changing the cells state also toggles the parent (Game) objects player property which allows the game to proceed with each player taking a turn. Clicking a cell also calls the checkForWin()function to determine if a particular turn results in the game being won. Here's the complete Cell object:

Rectangle {
    id: cell
    state: gameGrid.defaultText

    property alias textColor: cellText.color

    Text {
        id: cellText
        text: parent.state
        color: "silver"
        anchors.horizontalCenter: parent.horizontalCenter
        anchors.verticalCenter: parent.verticalCenter
        font.pointSize: 48
    }

    states: [
        State {
            name: cell.parent.defaultText
            PropertyChanges { target: gameGrid; player: "" }
        },
        State {
            name: "O"
            PropertyChanges { target: gameGrid; player: cell.state }
        },
        State {
            name: "X"
            PropertyChanges { target: gameGrid; player: cell.state }
        }
    ]

    // when clicked,
    MouseArea {
        anchors.fill: parent
        onClicked: {
            cell.state = (gameGrid.player == "O" ? "X" : "O");
            gameGrid.numberTurns += 1
            gameGrid.checkForWin();
        }
    }
}

Winning Algorithm

The approach I've taken is very simplistic: just scan each row, column and diagonal looking for a winning run. This isn't particularly efficient (we're scanning the board multiple times) but that's not a problem for small board sizes. However, it has two fairly compelling attributes:

It's simple to understand
It works for arbitrary-sized boards.

My favourite alternative algorithm is to make use of the properties of Magic Squares. Using these, you can scan the board a single time to determine if a player has one. This is achieved by determining if a cell has been selected by a player and if so incrementing their counter based on the magic square value for that index. For a 3x3 board, if a players total equals 15, they win!

Screenshots

So, what does it look like at this early beta stage...?

Start of a new game:

We have a winner!

Another winner on a 7x7 board (the person playing crosses needs more practice me thinks :-):

What's Next

The javascript code is currently horrid and needs to be refactored with dynamite.
Add ability to play "the computer".
Config option to allow variable-sided playing grids.
Once the game is stopped, we need to disallow further board clicks.
Leverage more QML facilities to simplify the code further.
Visual improvements (animation for a winning run maybe?)
Ability to change player that starts.
Score-keeping and "best of 'n' games " support (particularly useful when the kids beat you repeatedly ;-)
Menu to start new game.

The code is on github, so get forking!

In Conclusion

My "clean-room" implementation is far from perfect at the moment, but it's been a fantastic learning exercise so far and a lot of fun!

There are of course other QML noughts-and-crosses games out there. They come with varying licenses, some use C++ for the game logic, and most -- if not all -- are hard-coded to produce a 3x3 board only. Additionally, they generally use graphical representations for the noughts and crosses whereas here, I'm just using styled text. If you're interested, compare my github code with, for example, the Qt version to see the different approaches taken:

http://qt-project.org/doc/qt-4.8/declarative-toys-tic-tac-toe.html

Ubuntu developers: Rick Spencer: Dogfood Update

Rick Spencer — 2013-05-17T18:07:44+00:00

At the end of April, we set the goal to have Ubuntu Touch be dogfoodable on the Nexus and Nexus 4 phones. By that we mean, the goal is to make it so that we can use our phones exclusively as our phones. Today I chatted with some of the engineering managers involved to see how much progress we have made towards that. I am happy to say that it looks like we are still on track for this goal. However, there do appear to be some risky parts, so I am keeping my fingers crossed.

You can make and receive phone calls: Done!
You can make and receive sms messages: Done!
You can browse the web on 3g data: Tony had been blocked on some technical issues, but thinks he's through them, so is in the debugging phase. He expects to have this done by end of May as per the dogfooding goal. For me, personally, this is the only missing part for me to be able to use the phone as my main phone around town. So, if Tony cracks this nut, then I will put away my old phone and start using my Ubuntu Phone exclusively.
You can browse the web on wifi: Done! This has actually been done for quite a while.
You can switch between wifi and 3g data: There are 2 parts to this work. There is low level networking code to get done, and then there is UI to enable it. That means that the Phone Foundations team and the Desktop team both have work to do. Both teams expect to get it done for May, but the work is not started yet.
The proximity sensore dims the screen when you lift the phone to talk on it: There are two parts to this also. Gather the sensor data and then making the phone app use the sensor data. Work has not started for this part either.
You can import contacts from somewhere, and you can add and edit contacts: There is some work done on this that imports from a *.csv file. I expect there will be some crude support for this in time for the May goal. It might be fun for someone to try out a more elegant implementation. Ubuntu Phone is using Evolution Data Server for the contacts store, so there may be folks out there who already have the experience to do this easily.
When you update your phone your user data is retained, even if updating with phablet-flash: Done! This part being done makes the contacts import less important to me because as I add contacts they won't get blown away. On the other hand, it means it is worth it to import contacts, since you won't have to re-important as you update your phone each day (while it is in development).

Ubuntu developers: Colin King: Kernel tracing using lttng

Colin Ian King — 2013-05-17T14:47:03+00:00

LTTng (Linux Trace Toolkit - next generation) is a highly efficient system tracer that allows tracing of the kernel and userspace. It also provides tools to view and analyse the gathered trace data. So let's see how to install and use LTTng kernel tracing in Ubuntu. First, one has to install the LTTng userspace tools:

 sudo apt-get update  
 sudo apt-get install lttng-tools

LTTng was already recently added into the Ubuntu 13.10 Saucy kernel, however, with earlier releases one needs to install the LTTng kernel driver using lttng-modules-dkms as follows:

 sudo apt-get install lttng-modules-dkms

It is a good idea to sanity check to see if the tools and driver are installed correctly, so first check to see the available kernel events on your machine:

 sudo lttng list -k

And you should get a list similar to the following:

 Kernel events:  
 -------------  
    mm_vmscan_kswapd_sleep (loglevel: TRACE_EMERG (0)) (type: tracepoint)  
    mm_vmscan_kswapd_wake (loglevel: TRACE_EMERG (0)) (type: tracepoint)  
    mm_vmscan_wakeup_kswapd (loglevel: TRACE_EMERG (0)) (type: tracepoint)  
    mm_vmscan_direct_reclaim_begin (loglevel: TRACE_EMERG (0)) (type: tracepoint)  
    mm_vmscan_memcg_reclaim_begin (loglevel: TRACE_EMERG (0)) (type: tracepoint)  
 ..

Next, we need to create a tracing session:

 sudo lttng create examplesession

..and enable events to be traced using:

 sudo lttng enable-event sched_process_exec -k

One can also specify multiple events as a comma separated list. Next, start the tracing using:

 sudo lttng start

and to stop and complete the tracing use:

 sudo lttng stop  
 sudo lttng destroy

and the trace data will be saved in the directory ~/lttng-traces/examplesession-[date]-[time]/. One can examine the trace data using the babeltrace tool, for example:

 sudo babeltrace ~/lttng-traces/examplesession-20130517-125533

And you should get a list similar to the following:

 [12:56:04.490960303] (+?.?????????) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/bin/firefox", tid = 4892, old_tid = 4892 }  
 [12:56:04.493116594] (+0.002156291) x220i sched_process_exec: { cpu_id = 0 }, { filename = "/usr/bin/which", tid = 4895, old_tid = 4895 }  
 [12:56:04.496291224] (+0.003174630) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/lib/firefox/firefox", tid = 4892, old_tid = 4892 }  
 [12:56:05.472770438] (+0.976479214) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/lib/libunity-webapps/unity-webapps-service", tid = 4910, old_tid = 4910 }  
 [12:56:05.478117340] (+0.005346902) x220i sched_process_exec: { cpu_id = 2 }, { filename = "/usr/bin/ubuntu-webapps-update-index", tid = 4912, old_tid = 4912 }  
 [12:56:10.834043409] (+5.355926069) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/top", tid = 4937, old_tid = 4937 }  
 [12:56:13.668306764] (+2.834263355) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/bin/ps", tid = 4938, old_tid = 4938 }  
 [12:56:16.047191671] (+2.378884907) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/sudo", tid = 4939, old_tid = 4939 }  
 [12:56:16.059363974] (+0.012172303) x220i sched_process_exec: { cpu_id = 3 }, { filename = "/usr/bin/lttng", tid = 4940, old_tid = 4940 }

The LTTng wiki contains many useful worked examples and is well worth exploring.

As it stands, LTTng is relatively light weight. Research by Romik Guha Anjoy and Soumya Kanti Chakraborty shows that LTTng describes how the CPU overhead is ~1.6% on a Intel® CoreTM 2 Quad with four 64 bit Q9550 cores. With measurements I've made with oprofile on a Nexus 4 with 1.5 GHz quad-core Snapdragon S4 Pro processor shows a CPU overhead of < 1% for kernel tracing. In flight recorder mode, one can generate a lot of trace data. For example, with all tracing enabled running multiple stress tests I was able to generate ~850K second of trace data, so this will obviously impact disk I/O.

Blankon developers: Sokhibi: Menyisipkan Obyek Pada Presentasi

Istana Media — 2013-05-17T14:07:00+00:00

Tulisan ini merupakan lanjutan dari tulisan saya sebelumnya berjudul "Mengenal Perangkat Lunak Untuk Presentasi", pada tulisan tersebut kita sudah mengenal aplikasi untuk presentasi dan sedikit cara menggunakannya. Menyisipkan Obyek Buat presentasi seperti yang saya tulis pada artikel sebelumnya, kemudian sisipkan salindia baru dengan cara melakukan klik "Sisip ->> Salindia Tulis Judul

Blankon developers: Sokhibi: Menulis Karakter Khusus di Inkscape

Istana Media — 2013-05-17T12:56:26+00:00

Untuk Anda pemakai aplikasi Open Source dan yang hoby menggambar tentunya tidak asing lagi dengan yang namanya Inkscape, ya Inkscape memang salah satu aplikasi untuk menggambar Vektor dari yang sederhana sampai yang rumit, selain untuk menggambar kita juga dapat membuat tulisan dengan apliaksi ini dengan menggunakan menu Text Tool yang berada pada menu Tool Box, selain untuk membuat tulisan

Ubuntu developers: Valorie Zimmerman: Tea and cookies for your new team members

Valorie Zimmerman — 2013-05-17T09:42:35+00:00

What does every development team want? New contributors!

I'd like to suggest a simple process that can turn visitors to your website, list or IRC channel into a successful part of the development team. When people actually contribute, they quickly feel like a valuable part of the group. New people bring fresh energy, and new ideas.

At your next sprint or meeting, start dreaming. Is your user documentation well-written and up-to-date? Do you need promotion, or video guides? How about art or diagrams for your website? Speaking of your website, when was the last time all the links were tested, and it was checked for spelling and grammar? Create a nice, friendly list of tasks for your newcomers.

Could your codebase use some grooming, for common misspellings, for instance? (EBN is a great source for these). When you run across a bit of code which needs pruning or refactoring, or normalizing signal-slot stuff, the easy thing is to fix it while it's in front of your eyes. Instead, consider which of these small tasks can be filed as a "Junior Job", created for the purpose of getting those knowledgeable people to move from faithful user, to part of the team.

The Bugsquad and Quality Control teams can likely suggest more ideas, too.

KDE Junior Jobs can be easily found: http://kde.org/jj. Teams can create their own shortcut links too, such as Amarok has done, listed in the #amarok IRC channel topic: http://tinyurl.com/amarokjjs. Other tasks can be blogged about, posted on a trello, on the Community wiki; whatever your team likes to use. For more ideas, see http://community.kde.org/Getinvolved.

The Kubuntu team has a list of tasks in Trello, which works well.

So, when you feel like not fixing a little issue, don't feel lazy. Feel responsible! File a bug, make it a JJ, and call attention to those issues when new folks show up and ask, how can I help?

PS: Thanks to the #kde-www team for suggesting this blog. Einar77, neverdingo, mamarok; you are wonderful.

PPS: How LibreOffice does it: https://wiki.documentfoundation.org/Development/Easy_Hacks

Ubuntu developers: Xubuntu: Looking towards Xubuntu 13.10

Ubuntu developers — 2013-05-16T23:45:42+00:00

After three Nights of Xubuntu, the Xubuntu team is able to present you a quick overview of some of the planned features and improvements for Xubuntu 13.10. Enjoy!

Software and development

On the software side, apt-offline will be included in our default installation after a few cycles of preparing and writing documentation for it. This will help our users who have impaired-bandwidth situations and usage documentation is already present in the 13.04 offline documentation. The team is also considering the possibility to add a keyboard shortcuts overlay to help new (and why not old) users with their shortcuts-fu. Finally, the team is looking to improve the Pavucontrol user interface to make it more intuitive.

The team also discussed if a heads-up display (HUD) would fit to the Xubuntu paradigm and if it would be viable to implement. The team decided that including or working with one should be postponed until after the long-term support (LTS) release since there isn’t a proof of concept of a HUD suitable for Xubuntu ready and developing one would take a lot of developer time. Further inquiry can take place, though.

Besides the additions and improvements to software, the team roughly discussed including a Xubuntu core meta package which would include only a basic system without various applications seen in the current default installation. Some team members are working on drafts for the contents for the package as you read this article. The meta package would be installable instead of the Xubuntu desktop package during installation.

Documentation

The team is keeping the pressure up on the documentation improvements. The team is looking to extend the re-written Xubuntu documentation from a few releases ago even further as well as to get the infrastructure rights to enable translations for the documentation.

In addition, another goal is to get started with the 12.04 documentation review to supply a more up-to-date version via a stable release update for the LTS users as well.

Community

As with the previous cycles, we will keep on focusing on community. One of our targets this cycle is to get several people new upload rights to the Xubuntu package set. We also hope the prospective developers can help create processes with the newly appointed QA team lead to help reinforce the QA team as well as help with their testing duties.

Milestone participation

As usually, Xubuntu is following the Ubuntu release schedule. While the release schedule is far from final, the Xubuntu team is planning to release one alpha and both betas. At the moment the alpha participation looks pretty certain but the details depend on the Xfce 4.12 release. We will keep sending updates as soon as we have any news.

Summary

In the end, this is a final tune-up before we head into developing the LTS release that is expected to be unleashed in April 2014. Xubuntu presents a conservative desktop choice among the Ubuntu flavours. As we head into the Saucy Salamander development cycle, we will be striving for excellence once more.

To read the full notes from the three meetings, refer to the following URLs: night 1, night 2, night 3. If you are interested in the original agenda for the nights, refer to the following URLs: development and milestone participation, forward-looking issues, software.

Ubuntu developers: Rick Spencer: Feel Like Friday (post-vUDS)

Rick Spencer — 2013-05-16T21:21:17+00:00

It feels like Friday! Why? I think it's because I am tired. I am tired because Virtual UDS turns out to be surprisingly intense.

Power to People

So, that is to say, the second Virtual UDS is over. After experience my second vUDS, I think vUDS is really a boost for the transparency of the Ubuntu Project for a few reasons.

Frequency. We can do it every 3 months instead of every 6 months. As I mentioned in the opening plenary, this is important because we don't actually plan only every 6 months anymore. Like any modern software project, we are continuously planning. The 3 month cadence for vUDS means that there will be less time between detecting a need to change plans and discussion about how to make those necessary changes. I pushed very hard to have the first vUDS quickly, because there was a lot of planning for Ubuntu Touch that was backed up and needed proper discussion. If we waited until now, a lot of the work would have started without a good opportunity for discussion.
Access. Folks don't have to travel to wherever UDS is. People with specific interests can rock those interests with a laser focus, without having to dedicate a whole week away from home. Let's face it, traveling for 2 weeks a year to participate in UDS is something that only a few privileged people can swing. Many many more people can join a hangout.
Persistence. The sessions are streamed live, but then instantly available for reviewing, along with the white board, links to blueprints, etc... Try it. Go to Summit for the UDS that just ended. Find a session. Click on the session. It's like you are there live. Discussions that used to exist only in the memories of a select few with some written traces are now persisted and available.

Personal Faves

I won't go into a run down of the results, because that job is taken. However, here are some of my personal favorite discussions at this vUDS. These are my favorites based only on personal interests of mine. These are by no means the most important decisions or discussions. Just things that interest me a lot personally.

Rolling Release

After the unfortunate kerfufle last cycle when I pushed hard to move Ubuntu to a model of LTSs with rolling releases in between, it was niceto close in on one nice outcome. Namely, Colin has a technical solution that will allow users to subscribe to essentially the tip of development. Instead of using "raring" or "saucy" in your sources lists, you'll subscribe to a new name which is symlinked to whatever is the current development release. In this way, each day you will be on the latest. Even the day after a development release becomes a stable release, because the symlink will just point to the next development release.

I ended up with a couple of action items from this session. Mostly, to come up with a name and bring it to the next Tech Board meeting for approval. I'm very much leaning to "rolling", but I am open to discussion ;) This would mean you could say "I am on Raring", or "I am on Precise", or "I am on Rolling". "I am on Rolling" means that you are on the tip of development. Fun!

Touch Image Testing

I've been very keen to get Ubuntu Touch out of "preview" mode and into our standard development processes so that they inherit all of the daily quality tools that we have in place. This means moving all the code of out PPAs and into the real archives, so that we get the benefits of all the efforts we have put into place around -proposed and archive maintenance. It also means getting smoke testing and regression testing automated on the Touch images. I loved hearing from the Phone Foundations team and the QA team about their vision for "not accepting regressions". We should have dog-foodable touch images as early as the end of this month. Then if we can keep the images fully usable with minimal regressions each day, we will go very fast towards completion.

Ubuntu Status Stracker

I am partial to this topic because the status tracker started out as a labor of love for me. The first real bit of code that I wrote after joining canonical was to render my version of burndown charts. If I am not mistaken this code is still in use. In any case, status.ubuntu.com is critical to maintaining our planning, and ensuring that the status of the project is visible to all.

Unity 8 in 13.10

While 13.10 is very very focused on Ubunty Touch for phones, we all know that the real prize is the fully converged client OS. With that in mind, I think it's important to get the code up on as many device types as possible as soon as possible. There was a rich discussion about the steps to offer Unity 8 on top of Mir as an option in 13.10. Now, keep in mind that the result will only be the Phone UI on the desktop, and the default will be the Unity that we know and love today (with Smart Scopes and other enhancements of course!). Still in all, I am betting that basing Unity 8 on QML means that it will be surprisingly functional on a desktop even though it won't have any real desktop support in terms of things like workspace switching, etc..

Ubuntu developers: Scott Kitterman: New ipaddress module in python3.3

Ubuntu developers — 2013-05-16T20:43:14+00:00

Back in 2010 I packaged Google’s ipaddr module because I needed a light weight IP address manipulation library that supported both IPv4 and IPv6 and (at the time) python-subnettree was IPv4 only. Well, ipaddr is all grown up now and included in python3.3 as the ipaddress manipulation module in the standard library. You can find details, as well as some description of the differences, in PEP 3144.

I just converted one package that I’m upstream for to use either ipaddr (for python2.6/2.7/3.2) or ipaddress instead of some custom code. It turned out to be pretty easy to make it work with either. Other than the name, the only difference I ran into was the removal of the common, generic IPAddress and IPNetwork functions that are replaced by ip_address and ip_network.

…
-import ipaddr
+try:
+    import ipaddress
+except ImportError:
+    import ipaddr as ipaddress
…
-    address = ipaddr.IPAddress(ip)
-    if isinstance(address, ipaddr.IPv4Address):
+    try:
+        address = ipaddress.ip_address(ip)
+    except AttributeError:
+        address = ipaddress.IPAddress(ip)
+    if isinstance(address, ipaddress.IPv4Address):
…

Currently, python3-ipaddr has no reverse-dependencies in the archive (python-ipaddr does). Once python3.2 is dropped from Jessie, I think I’ll drop the python3-ipaddr binary on the assumption people newly coding for python3.3 should use ipaddress. The python-ipaddr module will stick around for use with python2.7.

Ubuntu developers: Laura Czajkowski: June HacknTalk event – London

Ubuntu developers — 2013-05-16T20:03:44+00:00

Following on from the first event in March of this year where we had a great day of talks covering varying topic I am very happy to announce the next HacknTalk will take place on the 29th June at the Google Campus again in London.

For those who missed it we had a great turn out and had talk on “Documenting tools for Tech Events“, “How to get kids more involved in open source in Education“,” Exceptional Money“, “Using MVC in Game Design” and we learned about STEMNET. There were other talks, lots of demonstrations and hands on help from members of the community helping one another with their questions.

We hope to reproduce the fun and informative day again in June. Learn about more great projects that are happening in the varying open source communities and meet new people. Since HacknTalk is an unconference, the speaking/demo schedule will be set on the day and everyone is free to propose a talk themselves. You are of course free to come along, sit back and listen to other people’s talks but we’d like to encourage everyone to take part and talk on something they are passionate about in technology. There is lots of space, wifi, and power sockets to go around. Break out areas to work on your hacking or demoing and hanging out with people.

If you want to come along please do remember places are limited so you need to sign up. If you can’t make the event, let other people in your community know about it and remember there will be another event in 3-4 months again. You can follow @hackntalk for more updates.

Ubuntu developers: Ubuntu Podcast from the UK LoCo: S06E12 – Django Ubuntu

Ubuntu developers — 2013-05-16T18:29:38+00:00

We’re back with the twelfth episode of Season Six of the Ubuntu Podcast from the UK LoCo Team! Alan Pope, Mark Johnson, Tony Whitmore, Laura Cowen and The Podcats are all set in Studio A with cake and an interview.

Download OGG

Download MP3

In this week’s show:-

We interview Rick Spencer, VP of Ubuntu Engineering at Canonical, about engineering Ubuntu.
We share some Command Line Lurve:
```
gpg --multifile
```
We chat about attending an Ubuntu development sprint in Oakland, more Doctor Who stuff at the British Film Institute (it is the 50th anniversary year!), and going to watch the Reduced Shakespeare Company reducing Shakespeare to 90 mins (including an interval).
And, of course, we go over your marvellous feedback.

Please send your comments and suggestions to: podcast@ubuntu-uk.org
Join us on IRC in #ubuntu-uk-podcast on Freenode
Leave a voicemail via phone: +44 (0) 203 298 1600, sip: podcast@sip.ubuntu-uk.org and skype: ubuntuukpodcast
Follow our twitter feed http://twitter.com/uupc
Find our Facebook Fan Page
Follow us on Google Plus
Leave us some segment ideas on the Etherpad

Ubuntu developers: Canonical Design Team: System Settings for Ubuntu Phone

Ubuntu developers — 2013-05-16T14:30:52+00:00

In late 2008, I sketched initial designs for what became Gnome’s System Settings utility. This centralized most operating system settings in a single window, without the need to reopen menus or switch between multiple windows if you didn’t find the setting you were looking for the first time. It made Ubuntu, and other Gnome-based systems, much easier to configure.

Five years later, we’re building a phone operating system. So once again, we need a centralized system settings interface.

What other phone OSes do

The first step in designing this was a competitor evaluation of how other phone systems present system settings.

iOS 6.1.4.

iOS is highly consistent in using a hierarchy of list items for Settings. But their design is rather awkward in three ways. First, the top-level Settings screen is very long, usually containing 30 or more top-level categories. Second, Apple originally tried to include application-specific settings inside the system-wide Settings, which made them hard to find while using the app. Some apps (including nearly all the default ones) still do that, but nowadays most put settings in their own UI. And third, the top-level “General” settings category is a bit of a junk drawer — containing subcategories for everything from auto-lock to accessibility, software updates to Siri.

Android 4.2: Tapping “Set mobile data limit” checks the checkbox. Tapping “Mobile data” flashes the switch label, but does nothing else. Tapping “⋮” opens a menu of more settings.

Android’s Settings similarly uses a hierarchy of lists, though some sections use dialogs instead. It has other consistency problems, too. Sometimes checkboxes are on the left, sometimes on the right. Tapping a checkbox label toggles the checkbox, but tapping a switch label doesn’t toggle the switch — sometimes it navigates to a different screen, other times it does nothing at all. Sometimes a screen’s heading contains a Back button, sometimes it doesn’t. Sometimes it contains a “⋮” dropdown menu of more settings, and sometimes it doesn’t. All this shows the importance of system settings having, if not a single designer, at least strong design guidelines.

An impressive aspect of Android’s Settings is that they can display in either portrait or landscape mode.

Windows Phone 8.

The Windows Phone design emphasizes typography and visual simplicity. It’s a bit rough around the edges: for example, the “photos+camera” settings screen uses ten font variations, and the main heading doesn’t fit on the screen. Windows Phone also groups “system” and “applications” settings on separate screens, but the separation needs work: for example, the voicemail sound effect is set in one of the “system” screens, while the voicemail number is set in one of the “applications” screens.

A nice detail in Windows Phone’s Settings is the use of summary values. The row you would tap, to navigate to a settings screen, often contains a line of small text summarizing the current settings values. This can save you from having to visit the other screen at all.

Learning from others

This competitor evaluation revealed three main issues. First, the difficulty of organizing system settings versus application settings. Apple tried to group them all together in iOS, but that lacks in-app discoverability. Microsoft used “system” and “applications” categories in Windows Phone, but suffers from poor sorting. It seems more likely that we can solve the sorting problem than the discoverability problem. So, as with Ubuntu for PC, Ubuntu Phone will have “System Settings”, not just “Settings”. Applications will be responsible for presenting their own settings.

Second, there is a tension between categorizing settings, and promoting frequent or urgently used settings. Categorizing by itself is tricky enough: different people might look for the same setting in different places. (For example, iOS sometimes mirrors subcategories of settings inside multiple categories.) A search function may help, but is not a complete answer, because people still need to know what settings are available in the first place. Categorization becomes even trickier when trying to provide quick access to settings like flight mode or orientation lock. Indicators at the top of the screen may help with this, by providing quick access to frequently used functions, like they do on Ubuntu for PC.

Third, it can be useful to reveal current state of settings as part of the navigation to those settings. This is usually done in text, with summary values, but an icon could work too. For example, a Bluetooth settings icon might be dull when Bluetooth is off, bright when it is on, and have an emblem when it is paired to any device.

User journeys

Two user journeys influenced the design of the System Settings interface.

The primary journey is someone wanting to solve a problem. Maybe their Internet connection is not working. Maybe they’re wondering if they can save battery. Maybe a cabin attendant has asked them to put the phone into flight mode. Maybe a friend has been messing around with their phone and they want to stop it from happening again. This person usually will be in a hurry, and sometimes irritated. They’ll want to get in and out as quickly as possible.

The secondary journey is an adventurous new owner, starting out with their phone, wanting to explore what it is capable of. They have more time to read explanations, and to explore cross-references between categories.

Designing the overview

Next, I sketched out nine possible layouts for the overview screen — the first thing people would see when they entered System Settings.

Selecting the most promising elements from each of the nine layouts, I passed them on to one of our visual designers, Rosie Zhu. She produced mockups of three possibilities, and with help from Marcus Haslam we decided on one final layout.

The design promotes frequently- and urgently-needed settings at the top, categorizes other settings compactly, and places bureaucratic stuff (“About This Phone” and “Reset Phone”) right at the bottom.

This is far from a final mockup. We need to finalize the icon style, and fine-tune control sizes, use of color, use of lines, and so on. But the basic layout is in place for engineers to start work. (Contact Sebastien Bacher if you’d like to help out with the code.)

Designing individual screens

Meanwhile, I have been busy designing individual settings screens. This has helped reveal missing controls in the UI toolkit, so they can be implemented for app developers to use them too.

Links to designs for the individual screens, as well as the design for the overview screen, are on the System Settings wiki page. Your feedback on any of the designs is welcome, either here, or on the ubuntu-phone@ mailing list.

Ubuntu developers: Ralph Janke: Why is there this never ending discussion of what an Ubuntu team is?

Ubuntu developers — 2013-05-16T13:58:06+00:00

For several years, Randall Ross has been now on the war path about the structure of Ubuntu LoCo teams.

However, everything that is raised in his post seems nothing more than a storm in the teapot.

Ubuntu developers: Ralph Janke: Update about Brainstorm

Ubuntu developers — 2013-05-16T13:26:26+00:00

As can be read from Jono's blog, Brainstorm has basically effectively been discontinued. It strikes odd, that this decision was made seemingly so rapidly, and it seems without a lot of community input, despite it was a community tool.

Of particular interest seems to be the reasons given for retiring this tool.

Ubuntu developers: Ubuntu App Developer Blog: App Development sessions at UDS, final day

Ubuntu developers — 2013-05-16T13:18:14+00:00

Time does fly, and we’re alread on the last day of the Ubuntu Developer Summit. Lots of content covered and still lots of interesting discussions to be had. We’re thrilled to bring you the summary on what’s on today on the App Development track.

Here’s the list of app development sessions for today at UDS:

At 14:00 UTC: App Development Roundtable
At 14:00 UTC: SDK UI Toolkit Responsive Layouting
At 15:05 UTC: Core Apps plans for 13.10
At 15:05 UTC: Contact Service for Ubuntu Touch
At 16:05 UTC: LoCo Team Coding Challenge
At 16:05 UTC: Refocus the Ubuntu App Developer site to go mobile
At 18:05 UTC: Building a set tutorials for App Developers
At 19:00 UTC: Closing Plenary and Track Summaries

Hope to see you there!

Planet Debian Derivatives

Ubuntu developers: Andres Rodriguez: Getting Started with MAAS and Juju: MAAS Overview

Ubuntu developers: Timo Jyrinki: Network from laptop to Android device over USB

Blankon developers: Sokhibi: Daftar Isi Artikel Inkscape

Blankon developers: Sokhibi: Membuka, Menyimpan, dan Menutup Project pada Inkscape

Blankon developers: Sokhibi: Mengatur Canvas dan Halaman Kerja pada Inkscape

ZevenOS-Neptune: Neptune 3.1 is ready

DOWNLOAD

Blankon developers: Budiwijaya: Varnish – tips trick #1

Ubuntu developers: Bryce Harrington: pingssh

Ubuntu developers: Valorie Zimmerman: Why we do this crazy thing we do

Ubuntu developers: Scott Kitterman: We have a winner (actually three) – Kubuntu Council 2013 elections

Ubuntu developers: The Fridge: Ubuntu Weekly Newsletter Issue 317

Ubuntu developers: Jono Bacon: New Song

Ubuntu developers: Tony Whitmore: Otherwise engaged

Ubuntu developers: Ubuntu Classroom: Ubuntu Open Week for Raring: Almost Here!

Blankon developers: Sokhibi: Mengenal Antarmuka Inkscape

Ubuntu developers: Adam Stokes: python-salesforce on pypi

Ubuntu developers: Adam Stokes: python-salesforce on pypi

Ubuntu developers: Ralph Janke: Respect is a Bi-Directional Proposition

Ubuntu developers: Ubuntu Ohio - Burning Circle: Burning Circle Episode 113

Ubuntu developers: John Baer: Ubuntu 13.04 – Enable Google Music All Access

Turn On Notifications

Add Google Music as a Web App

Enroll In Google Music All Access

Start Playing Music

Ubuntu Integration

Ubuntu developers: Jono Bacon: Respect in Community Discussion and Debate

Grml developers: Evgeni Golov: powerdyn – a dynamic DNS service for PowerDNS users

Ubuntu developers: Benjamin Mako Hill: The Cost of Inaccessibility at the Margins of Relevance

Maemo developers: SeriesFinale for BlackBerry

Blankon developers: Iang: Improvisasi

Blankon developers: Sokhibi: Daftar Isi Artikel Libre Office

Blankon developers: Sokhibi: Backup Aplikasi yang sudah terpasang di BlankOn

Ubuntu developers: Adolfo Jayme Barrientos: Interesting reads today

Emdebian developers: pybit 1.0.0 - distributed, scalable builds direct from VCS or archives

Ubuntu developers: Valorie Zimmerman: The water we swim in

Ubuntu developers: Elizabeth Krumbach Joseph: Adopt a Salamander

Ubuntu developers: Seif Lotfy: Globaleaks 0.2 Alpha

Blankon developers: Budiwijaya: Book Review: Mastering NGINX

Ubuntu developers: Scott Kitterman: Polls Closing Soon – Kubuntu Council Elections 2013

Blankon developers: Sokhibi: Menambahkan menu Satuan pada LibreOffice Calc

Ubuntu developers: Rafael Carreras: Raring Party in Barcelona

Tails: Tails 0.18 is out

Changes

Known issue

I want to try it / to upgrade!

What's coming up?

Ubuntu developers: Elizabeth Krumbach Joseph: Virtual Ubuntu Developer Summit 1305

Blankon developers: Sokhibi: Mencetak Satu Tulisan Panjang ke beberapa Kertas

Blankon developers: Sokhibi: Benarkah Menggunakan Linux itu Sulit?

Whonix developers: looking for someone to create a graphic to explain Whonix's stream isolation feature

Ubuntu developers: Paul Tagliamonte: Hy: recent developments and some work from doctormo

Ubuntu developers: Stephen Michael Kellat: An Update in Notes

Ubuntu Ohio Leader Notes for 2013-05-17

Continuing Attacks on freenode

Podcast Resumption

Ubuntu Developer Summit May 2013

Ohio Linux Fest 2013

Ubuntu Ohio Projects For The Saucy Salamander Cycle

AND FINALLY...

Ubuntu developers: Jono Bacon: Dogfooding the Ubuntu Phone: My (Early) Experience

Lihuen: ¡Lihuen 5 beta 1 publicada!

Ubuntu developers: James Hunt: A simple two-player QML game for Ubuntu Touch using the Ubuntu SDK: noughts and crosses (aka tic-tac-toe)!

I Need an Itch to Scratch

Design

Winning Algorithm

Screenshots

What's Next

In Conclusion

See Also

Ubuntu developers: Rick Spencer: Dogfood Update

Ubuntu developers: Colin King: Kernel tracing using lttng

Blankon developers: Sokhibi: Menyisipkan Obyek Pada Presentasi

Blankon developers: Sokhibi: Menulis Karakter Khusus di Inkscape

Ubuntu developers: Valorie Zimmerman: Tea and cookies for your new team members

Ubuntu developers: Xubuntu: Looking towards Xubuntu 13.10

Software and development

Documentation

Community