Again early wake up… This time 4:44 but I think that today will be better then yesterday because 6h of sleep is often my default amount. Few minutes ago room mate woke up and said: you will never convert to this timezone if you will not sleep longer. But why do I have to? In few days I will be back home.

After “let’s do nothing” Sunday it is time to start doing UDS things. I have quite long list of sessions to attend and for few I will need to select which one to go:

Monday:

• 11:00 Linaro@UDS roundtable
• 12:00 Xdeb cross-compilation environment
• 15:00 Current state of Linaro toolchain
• 16:15 Package development tools
• 17:10 Future Linaro toolchain areas

Tuesday:

• 09:00 Toolchain consumption models
• 11:00 Design a safe and stable build cluster for public ARM PPAs based on the OMAP4 Pandaboard
• 11:00 Using QEMU for demonstrations
• 12:00 Integrate gdbserver support in Linaro
• 15:00 Kexec
• 16:15 Improve detection of device class at install time
• 16:15 Current and future GDB for ARM plans

Wednesday:

• 09:00 Create minimal preinstalled developer images
• 11:00 The Multi-Monitor User Experience multimedia
• 12:00 State of ARM developer tools
• 12:00 Kubuntu Natty and X.org
• 15:00 Provide ARM cross-compiler packages for Ubuntu Natty
• 16:15 Linaro toolchain integration in Ubuntu Natty
• 17:00 Cross-Compilation Environment

Thursday:

• 10:00 Git for Bzr users
• 11:00 Kernel version and flavours
• 11:00 Performance inside of GCC
• 12:00 ARM specific library tuning
• 15:00 Produce an image suitable for set-top boxes for armel

Friday:

• 09:00 Provide a Linaro image with a set of developer-oriented tools installed by default
• 10:00 More stable VM solution for running armel VMs
• 11:00 Multiarch Support for gcc, binutils, dpkg, and apt
• 12:00 Discuss the way forward with the 2D ARM netbook UI
• 15:00 Provide solutions for netbooting and minimally installed Thin Clients on ARM boards

For now this is a list of sessions which I will attend or consider to. Some of them are required for me, some I will lead, some are for curiosity and few I will attend to check what is going on and maybe provide some hints. Compared to UDS-M this one will be rather busy for me. And I have to catch Jamie to grab my PandaBoard from him :)

BTW — if you are interested in checking something on PandaBoard then catch me. Maybe it will be possible to organize some kind of hacking session (but note that I do not have any of required things for board — no psu, no cables/keyboard/mouse/etc).

All rights reserved © Marcin Juszkiewicz
UDS-N: Monday was originally posted on Marcin Juszkiewicz website

Share/Bookmark

Related posts:

1. UDS continues
2. Ubuntu cross compilers
3. PandaBoard: Beagleboard XM killer?

It’s less than a week before the Ubuntu Developer Summit kicks off in Orlando, Florida, from the 25th-29th Oct, and everyone is getting ready to plan all the sessions and put all of the pieces in place for what will be once more an amazing schedule for an exciting development cycle: Ubuntu 11.04, the Natty Narwhal.

As usual, we’re going to have a solid representation of Ubuntu Translations, and I’d like to take the opportunity to let you know bit more about the sessions we’ve got in store for this UDS.

Main Sessions

These will constitute the roadmap for next cycle, and were based on the great feedback from community members during the call for proposals for the Ubuntu 11.04 Translations Plans.

Everyone should feel welcome to participate in the discussions and collaborate in completing these goals.

Ubuntu Translations Portal

A web portal to unify all the available content on Ubuntu translations such as stories, announcements, language teams, documentation, etc. (read more…)

Language Pack Updates Schedule

A clear policy on language pack updates for stable releases, stating for which releases and when they will be published. (read more…)

Translations Stories

A coordinated effort to publish stories about the work of translation teams throughout the cycle. (read more…)

Introductory Video to Ubuntu Translations

Production of an introductory video on Ubuntu translations, which will ultimately appear on the Translations Portal. (read more…)

Translations Training Sessions

A set of translations training sessions to help new translators getting started using Launchpad Translations and contributing to Ubuntu. (read more…)

Additional Sessions

Translatable Ubuntu Code of Conduct and Leadership Code of Conduct

We want to provide the Code of Conduct (CoC) and the Leadership Code of Conduct (LCoC) in anyone’s own language, and we want to enable the community to translate it. (read more…)

Internationalization of Launchpad Answers

We’d like to have an open discussion about the scope of work and the steps involved in enabling internationalization and localization of the Launchpad Answers application’s web UI. (read more…)

Roundtables

Ubuntu Translations Community Roundtable

A roundtable to discuss anything related to the Ubuntu Translations community, and to Launchpad Translations as a tool. (read more…)

How to participate

• Go to the blueprint. Click on the session you’re interested in, either in this overview (using the read more.. links) or in the UDS schedule. This will take you to the blueprint in Launchpad.
• Subscribe to it. Subscribe to the blueprint, optionally ticking the “Participation essential” checkbox.
• Add feedback. If you like, add feedback to the blueprint’s whiteboard.
• Join in! Remember that if you are participating remotely, there’s IRC projected in all rooms and sound is streamed, so you can interact with those in the session. Check out the remote participation documentation for detailed instructions on how to participate from home or anywhere else.

Looking forward to seeing everyone next week!

We’ve been talking a lot about UDS but some of you out there might not know what it is. Duncan McGregor, one of my colleagues, has had this very conversation with a speaker who will be attending this UDS. He took some time to compose a blog post explaining what the summit is all about.

It’s well worth a read

Just a reminder that the sponsorship application deadline is 8th September if you haven’t already applied! For more information please see this page: http://uds.ubuntu.com/participate/sponsorship/

(There is a bug in the summit system that is telling people that the deadline is March 26, this is incorrect!)

The Ubuntu Hams team was started a year ago, and has seen a lot of membership growth since then. We just finished the first BOF session we’ve ever had at an Ubuntu Developer’s Summit, and it was a lot of fun. As soon as I can I’ll email a summary to the team mailing list. The discussion was wide-ranging, from enabling translation of amateur radio packages, to increasing the number of upstream maintainers that we engage with.

We decided to begin having monthly meetings on IRC for Ubuntu-hams, as well as starting to have some HF nets. If you’re interested in following this, join the team and subscribe to the mailing list. We’ll be having followup discussions there.

Engines are warming up for the next Ubuntu Developer Summit next week in Brussels, and on the Community track we’ve got a rich set of sessions to discuss a lot of topics around Translations. These will help shaping up the roadmap for the next version of Ubuntu, the Maverick Meerkat.

We discussed the sessions in the last translations meeting and they have now all been scheduled. You can also see the overview on the wiki, although they will all be tracked from the linked blueprints. Here they are:

1. Translations community roundtable
   • Unstructured session to discuss and gather feedback on all around the Ubuntu translations community
     • Proposed topic: QA of language packs (GaborKelemen) – asking translators to test each updated package before release may be too much. With on-demand updates, it may be unnecessary to withhold untested updates.
2. Launchpad Translations roundtable
   • Unstructured session to discuss and gather feedback on all around Launchpad Translations as a tool
3. Desktop and Translations roundtable
   • Roundtable with members of the desktop team to discuss everything related to translations. Proposed topics:
     • Overview of Launchpad Translations changes in Maverick: automatic generation of translation templates, import of translations from upstream bzr branches and translation sharing. This will also be explained in a plenary.
     • Implementing gettext support to PolicyKit
     • Firefox and OpenOffice.org translations
     • Common approach for building POT template on non-desktop packages using plain gettext instead of intltool, e.g. mountall, in the same way as CDBS GNOME packages use langpack.mk
     • Could langpack-o-matic build the translated XML files for documentation to be shipped in language packs? Even if we cannot get it to build for all packages, even if only for ubuntu-docs would be a big improvement.
     • Enabling keyboard indicator applet by default on users with a non-Latin alphabet keyboard layout (see bug 550704)?
     • Evaluate the use of mlterm instead of VTE for RTL locales?
4. Kubuntu Translations roundtable
   • Unstructured session to discuss and gather feedback on all around Kubuntu translations.
5. Translations Community Advocacy
   • Session to discuss how to rise awareness on the global Ubuntu Translations community, both within and outside the Ubuntu community.
6. Translations Community Learning Content
   • Session to discuss ways of providing content to ease start contributing to translations.
7. Translations Community Events
   • Discuss a series of events throughout the cycle to help promoting the Ubuntu Translations project and increase participation in translating Ubuntu.
8. Extend the translations reporting site
   • Continuation of the Lucid blueprint on how to improve how we report translation status for Ubuntu
9. Translation teams health check
   • A session on an effort to get in touch with all of the translations teams for a health check. Make sure to understand their needs and if they need help in any area. Raise awareness on the new team policies, especially on having information on the team’s communication channel on their Launchpad page, along with info on how to join the team.
10. Launchpad Translations Reporting API
    • Discuss the current status and implementation of the Launchpad Translations reporting API, as per the specification Adi is working on.
11. Developer education on localization
    • Get feedback on the creation of a resource with developer reference on localization, extending the internationalization guide.
12. Universe is translatable in Launchpad
    • Session to assess if it’s desirable to make all localized applications from universe also translatable in Launchpad, not only those from the main repository.
    • Previous spec
13. Improve Translations Packaging for Help in Ubuntu Applications
    • Development of a strategy to provide translatable documentation for Ubuntu applications.
    • This will also allow OEM projects to use documentation and its translations from Ubuntu, installed independently from the monolithic ubuntu-docs package.
    • Ideally the translated documentation should be shipped in language packs.
14. Proactive bug detection
    • Discuss the possibilities of proactive bug detection: this would need more and earlier testing of packages for translation problems (lack of i18n infrastructure, untranslatable files/strings, needs-pot-on-build, needs-desktop-entry-i18n…)
    • We also need to devote more manpower to fix bugs in time, and reducing the average lifespan of bugs. Goal: 0 translation bugs at release time
    • Rejecting string changing uploads that do not close a string exception tagged bug? (TimoJyrinki)
15. Fixed schedule for translation updates
    • Predictable translation updates could help scheduling work
    • Not only language packs, but DDTP, (k)ubuntu-docs, and whatnot too
    • Perhaps we could introduce on-demand updates, so that a language can get an update when it needs it the most
    • “Supported release” should mean not only security fixes, but translation updates too!
16. Creating a localized help.ubuntu.com
    • help.ubuntu.com should detect my browsers locale settings and show the content on my language
    • Asking teams to create localized versions of that site makes no sense: we duplicate the infrastructure and the work to maintain it for nothing.
17. Improving communication with translators in Launchpad
    • (From the Ubuntu Manual Team)

How to participate

• Go to the blueprint. Click on the session you’re interested in, either in this overview or in the UDS schedule. This will take you to the blueprint in Launchpad.
• Subscribe to it. Subscribe to the blueprint, optionally ticking the “Participation essential” checkbox.
• Add feedback. If you like, add feedback to the blueprint’s whiteboard.
• Join in! Remember that if you are participating remotely, there’s IRC projected in all rooms and sound is streamed, so you can interact with those in the session. Check out Jorge’s Ubuntu Open Week IRC session next Friday at 18:00 UTC on #ubuntu-classroom

I have been busy with the release of Ubuntu 10.04 LTS and, although it may seem that Mago activity has decreased, there are some news related to the project that I want to share before UDS.

Ubuntu 10.04 LTS has been released with Mago 0.2, which is the release of Mago compatible with LDTP 2.0. Earlier this year, LDTP team released a complete rewrite of the testing framework in Python. After LDTP 2.0. arrived in Lucid, Mago suffered some weeks of instability, until it was working again with the new API. Also, I gained upload rights for ldtp and mago packages last week and, hopefully, this will be reflected in more activity during the Maverick cycle.

There is going to be work related to GUI testing during Maverick cycle, and some of them have been already reflected as blueprints for discussion during UDS:

Mago internationalization:
Mago works only with “C” locale applications. We need to modify it in order to make it work with different locales. This will be useful for local Ubuntu derivatives and to test language packs.

Mago Daily:
We aim to be running Mago tests on a daily basis. One of the biggest challenges to achieve this is having perfect integration of Mago with Checkbox. We will be discussing previous problems and will try to find a solution.

Roundtable: GUI Testing:
We will be discussing the different solutions for GUI testing available, their advantages and disadvantages. Sikuli, Mago, kvm-autotest, among others.

So, if you are coming to UDS (or want to participate remotely) and are interested in automated GUI testing, feel free to subscribe to those blueprints and participate in the discussion. See you all there!

Update:
James Tatum, a Mago contributor who is also coming to UDS, points me to another blueprint for discussion.

Simplify the creation of tests in Mago:
Adding applications to the Mago library is cumbersome. To foster the creation of more test cases, we will discuss ways to make this easier.

If you’re attending the Ubuntu Developer Summit in Brussels May 10-14, you’re welcome to participate in the openPGP keysigning party on Wednesday evening.

when you go to dinner in a car^Wtank^Wbattleship^Wrazy something like this:

I savely arrived in our hotel in Dallas, Texas this afternoon, after a rather uneventful 14 hour trip from Dresden via Frankfurt. On the way I emptied my laptop battery with some small hacking and catching up on bug report email, and did a lot of reading. I also tried to watch Harry Potter 6, but the headphones they give you were so hideous that I hardly understood anything, so I gave up after some ten minutes.

In the early evening a small group of us went to the center to have a light Mexican style dinner (yummy), and someone came up with the monster above. Was quite an experience, veeery comfortable interior with leather couches and champagner glasses. Almost as comfortable as on my bicycle at home.

Naturally I feel the jetlag and are pretty groggy now, but I still managed to stay conscious until now, after having a beer and two hours of chatting in the bar. It’s so great to see everyone again!

I’m looking forward to the Ubuntu Developer Summit next week.