UDS Day 3

Today Sessions :

Defect Analyst Bug Review Dashboard

http://summit.ubuntu.com/uds-p/meeting/19483/other-p-bug-dashboard/

https://blueprints.launchpad.net/ubuntu/+spec/other-p-bug-dashboard

This session was to create a way to monitor bugs across several packages and in an efficient way. Currently, most people who want to work on bugs of multiple packages create a team and subscribe all packages to this team. It’s working to get information, but nothing exist to summarize statistics about the bugs (status, severity, in progress …).

 

Ask Ubuntu for the experts

http://summit.ubuntu.com/uds-p/meeting/19717/community-askubuntu-experts/

https://blueprints.launchpad.net/ubuntu/+spec/community-askubuntu-experts

Presentation of Askubuntu.com, and some advanced features to use it (edit, tag, bounty, votes …), and possible integration with Loco teams. It still sad that it’s only in English, so not easy to do support, in counties which don’t speak English.

 

Calendar Integration

http://summit.ubuntu.com/uds-p/meeting/19450/desktop-p-calendar-integration/

https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-calendar-integration

This session was to discuss the use of a calendar application, because with the switch to Thunderbird, there is no calendar in 11.10.

There is different solutions :

– Adding extension to TB to handle calendar features. But some people express the wish to have no extension by default on TB.

– Adopting Maya, the calendar application of Elementary OS. But this application is not finished, and it needs help to be functional.

– Write a new application. But it needs time and resources, + it will probably be dropped once Gnome have it’s own calendar application, or if Maya is finished and works well.

Discussion followed in the Default application session, and probably nothing will happen this cycle to add a calendar solution (unless a drop-in solution is found).

 

12.04 LTS (Precise Pangolin) Release Planning

http://summit.ubuntu.com/uds-p/meeting/19548/other-p-release-lts-planning/

https://blueprints.launchpad.net/ubuntu/+spec/other-p-release-lts-planning

This one was about the schedule of the release, the different milestones etc … It’s a review of the current roadmap, and adjustments of it. For example, the DebianImportFreeze (the date when automatic imports from Debian testing stopped) was moved later in the cycle due to Christmas break. Also, it was confirmed that there will be no RC official images, but a period when images will be declared as “release candidate”.

Also, the status of derivatives was discussed. Finally, something was written about the status of derivatives, how you can achieve this status, what support is provided by Canonical … It was something always blurry, and we suffer it when Lubuntu tried to be official.

See details on :

https://wiki.ubuntu.com/RecognizedDerivatives

 

The plenaries was about ARM technology and patents. There was also the traditional group photos after.

 

GNOME Version

https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-gnome-version

http://summit.ubuntu.com/uds-p/meeting/19454/desktop-p-gnome-version/

This session was to discuss which version of GNOME will be shipped, 3.2 (the actual stable one) or 3.4 (the next stable one).

For the 2 main parts of the platform (GTK and glib), the plan is to update them to 3.4. It may have problems with multitouch support which is now included in GTK. It may conflict with Ubuntu multitouch implementation. There was also a discussion about the idea to have some sort of LTS version for GTK (discussion to be continued with GNOME people).

The plan for the rest of the applications is to stay by default on 3.2, and pickup components from 3.4 in some cases. Nautilus (and gvfs), Evolution for example should stay with 3.2, like empathy. For other small applications, it will be discuss case by case.

 

Default Apps Discussion

https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-default-apps

http://summit.ubuntu.com/uds-p/meeting/19442/desktop-p-default-apps/

This is the usual session to discuss applications by default. Many topics was discussed :

– Inclusion of Boot-repair in the Live-CD : probably yes if there is no stopper.

– Inclusion of FreeRDP : to be check with security.

– Video editor : No (not needed by default)

– Rhythmbox / Banshee :

This subject was a bit of surprise for me, I didn’t expect such discussion will happen. However, the 2 applications have problems :

– Banshee : Problem on ARM (doesn’t work), no GTK3 support, and removing Banshee will remove Mono from the CD (good for the space) and probably from main (which make Security team happy, not having to maintain Mono stack for 5 years)

– RB : U1 store need to be updated, Music lense needs to be updated, it needs a release from upstream.

A quick vote on usage of both applications in the room makes approximately a 50 / 50 result (maybe a bit more for RB).

Conclusion, RB will probably be back on the CD, if no problem is raised by the other teams not present during the session. The decision was not easy, but IMO it makes sense in the context of an LTS. And, well, Banshee will still be available in the archive, will at least the same level of integration than in 11.10.

Publicités

UDS Day 2

Today sessions:

Shrink the image build pipeline

http://summit.ubuntu.com/uds-p/meeting/19533/foundations-p-image-build-pipeline/

https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-image-build-pipeline

This session was to reduce the time to build ISOs. It’s important during testing time, when we need to rebuild many ISOs. For example, if ubiquity is broken, and it’s fixed during ISO testing, many ISOs need to be rebuild to re-do testing. By reducing this time, you speed up testing and reduce the risk to delay a release.

 

Identify build breaks on daily ISOs

http://summit.ubuntu.com/uds-p/meeting/19409/other-p-builds-smoke-testing/

https://blueprints.launchpad.net/ubuntu/+spec/other-p-builds-smoke-testing

This one was about automated testing and to generate a report into a central place, to ensure daily ISO are in good shape enough to be tested (booting, installation OK …). It’s useful to ensure people are aware of the  state of the daily builds, and if it’s broken, they don’t need to download it (and don’t loose time to download something broken). It will be only available for Ubuntu and Ubuntu server, but as some pieces are common across the distributions (like ubiquity),it’s also useful for all derivative.

 

Lubuntu user experience

http://summit.ubuntu.com/uds-p/meeting/19473/other-lubuntu-p-users-experience/

https://blueprints.launchpad.net/ubuntu/+spec/other-lubuntu-p-users-experience

First session for Lubuntu, it was to discuss improvements like new features, new applications by default. There was not so many people on the room, but some had the possibility to participate on IRC. Basically, I presented the items I’ll be working on for this cycle :

– Lightdm enable by default for Alpha 1

– Multi-screen configuration : not easy to configure with lxrandr. Solution : Extend lxsession to accept configuration from other utility like arandr.

– Lxsession options / services : Add possibility to configure applications by default, and to enable them or not (screensaver, power-management …)

– lubuntu-software-center : Add it by default, but keep synaptic.

 

FreeRDP

http://summit.ubuntu.com/uds-p/meeting/19614/desktop-p-freerdp/

https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-freerdp

Presentation of FreeRDP and Remmina. There is another session this week to discuss inclusion of FreeRDP and Remmina by default on Ubuntu (to replace vinaigre, tsclient …). We had also a demo on the features. Upstream is pretty active, and starts integration into Ubuntu (port to GTK3, indicator support …).

 

Plenaries were about Openstack and Rackspace, applications development, and Qt. ecosystem (how is it organized, achievements, and future plan with Qt 5.0).

 

Piloting a new test case management tool

https://blueprints.launchpad.net/ubuntu/+spec/other-p-qa-test-case-management-tool

http://summit.ubuntu.com/uds-p/meeting/19416/other-p-qa-test-case-management-tool/

This session was to discuss the use of a test cases management tool, to replace the current wiki pages. No decision was made, but people was able to discussed features they want in the next tool.

 

Optimization in Lubuntu

http://summit.ubuntu.com/uds-p/meeting/19472/other-lubuntu-p-optimizations/

https://blueprints.launchpad.net/ubuntu/+spec/other-lubuntu-p-optimizations

The second session of Lubuntu was not very useful,as many items were discuss on the other session.Discussion will probably move to the mailing when it’s needed. The only important thing is that we will kept GTK2 for most of our applications, as we will not have the resources to migrate them all.

 

Improving weekly release meeting

https://blueprints.launchpad.net/ubuntu/+spec/other-p-release-meeting

http://summit.ubuntu.com/uds-p/meeting/19547/other-p-release-meeting/

The last session was about the weekly release meetings we have with many other teams to share what happened last week, what are the plans for next week, current issues …We discuss some improvements to make it more interactive (because currently, it’s often a copy / paste of a wiki page during the meeting). Status of each team will be asked 1 day before the meeting, so people will have time to prepare the meeting, and it should reduce the time needed for this meeting. We also have a quick presentation on what tools are available (status.ubuntu.com for example).

 

That’s all fort today 🙂

UDS Day 1

1st day to the UDS, and as usual, it began with an introduction by Jono Bacon. It’s a quick introduction on how the UDS is working, some advices, and how to use the schedule and the blueprints. It’s followed by the Keynote by Mark Shuttleworth. This time, he talks a lot on the achievements of the last cycle (developer.ubuntu.com, Software-Center, Lightdm …). No big announcement for the next release (as expected, the 12.04 need to focus on polishing). The main announcement was the goal for 14.04 : Ubuntu on everything (Tablets, TV, phones …). And to finish, there was a quick speech about Linaro (introduction to the project, achievements, etc …).

 

Today Sessions :

As usual, the schedule was quite unstable for sessions I would like to follow (sessions were moving all the time on the schedule, even during UDS itself), but hopefully some doesn’t move 🙂

 

Build images :

http://summit.ubuntu.com/uds-p/meeting/19546/ubuntu-arm-p-image-build-tools/

https://blueprints.launchpad.net/ubuntu/+spec/ubuntu-arm-p-image-build-tools

This session was about how ISO can be build without using the main Ubuntu infrastructure. Progress was made to achieve this goal, like using live-build and ubuntu-defaults-builder. They are used to produce localized ISO (such as the Chinese one, or the French one). But this system lacks some features of the official infrastructure, and doesn’t solve the problem of ARM cases (which use specific file systems on each hardware).

 

Software-center roadmap

https://blueprints.launchpad.net/ubuntu/+spec/consumer-p-software-center-enhancements

http://summit.ubuntu.com/uds-p/meeting/19743/consumer-p-software-center-enhancements/

It was a general session about software-center, and some ideas how to improve it :

* Performance : Devs are aware of the performance issues (like startup time), and they planned to improve the situation.

* Unit testing : How to improve unit testing coverage (which is good, but not complete enough)

* Code reviews and documentation : devs will try to improve the documentation for new contributors.

* Improving the integration with Unity (lens)

* Recommendations : Add automatic recommendations of packages that people would probably want to install.

It’s IMO a good balance between new features and quality improvement plan for a LTS

After the lunch, there are plenaries with various topics. There was one about Cloud Foundry, and a more interesting for me, on the relationship between Debian and Ubuntu, made by the Debian Leader. The situation seems to have improved since 2 years ago, and I’m agree that in general, Debian devs seems to be more friendly about Ubuntu contributions. I think current problems are mostly not project-wide, but when people from the different projects have different points of view. It can’t be easily fixed, and certainly not project-wide, but case by case.

 

Release Process Improvements

https://blueprints.launchpad.net/ubuntu/+spec/other-p-release-process-improvements

http://summit.ubuntu.com/uds-p/meeting/19545/other-p-release-process-improvements/

This one was about  how the release process can be improved. One of the most discussed item was the release candidate images. For oneiric cycle, there was not an official RC ISO, just a moment when images was declared “release candidate”, but without a real milestone. It will be improved in the next cycle (more communication about it). Also, there would be improvements on ISO tracker, when a respin[1] is necessary.

 

Control panel cleanup

https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-control-center-cleanup

http://summit.ubuntu.com/uds-p/meeting/19451/desktop-p-control-center-cleanup/

This session was about improving integration of Ubuntu applications to the gnome control center, such as ubuntu one preferences, the language settings (language-selector), additional drivers support (jockey) …  The goal is to have them embedded in the control center window, instead of launching another window.

Supporting package to team mappings effectively

http://summit.ubuntu.com/uds-p/meeting/19664/other-p-package-mapping/

https://blueprints.launchpad.net/launchpad/+spec/other-p-package-mapping

The last one was to implement a feature in launchpad to link a package to a team which will be responsible of. The main goal is to have a single point of contact when there is critical bugs, and for statitics. It’s useful for the release team, to be able to affect bugs to the right team (the one which will be in charge to fix it). One of the solution proposed was to used packagesets (group packages used in Launchpad) to achieve it.

That’s all for today, tomorrow there will be the 2 Lubuntu sessions planned for UDS, it’s time to prepare them 🙂

[1] Currently, you do ISO testing during several days before the day of the release of a milestoned ISO (Alpha, Beta …). To validate an ISO (saying it’s OK to release this ISO), yu need to do some manual tests (like testing the installation). When a bug is fixed on some specific packages (like ubiquity, the installer), you need to rebuild the ISO to include the fix. After this, you need to do again all the tests to validate the ISO. So, if there are 3 respins, all the tests you have done on the 2 previous ISO are useless, and need to be done again.

UDS -2

UDS is approaching, only 2 days before the start. It’s usually the period when community members arrive from all over the world (Canonical folks are usually here 1 week before).

It’s also my case, arriving from France today, with some difficulties (Air France’s strike).

This year is a bit different than last UDS (it will be my 5th UDS), because I’m sponsored by Canonical this time (thanks to them !). It will also be the first UDS with Lubuntu officially in the Ubuntu family, and with our first official release with this status. So, I decide to blog a bit more this time. I’ll try to summarized the session I’ll follow. I’ll also try to add quick introductions to some concepts of the UDS (blueprints, schedule …) for people who discover the UDS.

Usually, it’s time for me to select the sessions I want to follow. The best thing to do is to subscribe to the corresponding blueprints [1]. Actually, subscribing doesn’t mean you want to assist to the session, but by doing this :

– The schedule [2] will try to adapt itself, to arrange the sessions so you can participate at most of the blueprints you subscribed. But it’s limited, and if you subscribed to many sessions, it may be conflicts, and you will have to choose. But be careful, the schedule changes every-time during UDS 🙂

– You will be notified for each modification made to the blueprint, such as the whiteboard which containing tasks for developers related to this blueprint, or some notes about the topics of this blueprint.

1 important thing, is that you can participate to the sessions, even if you are not physically here. Each rooms have also a specific IRC channel, so you can ask questions and participate remotely. the sound of all sessions are also available, so you can also hear people talking, and react on IRC 🙂 If you plan to do so, be sure to subscribe to blueprints you want to follow, and also to register to the UDS page [3], so the schedule will also try to be nice with you 🙂

Personally, I’ll follow many desktop sessions (to be sure they don’t mess up things which affect Lubuntu :)) and also some related to the release team.

That’s all for today 🙂

PS : If you don’t know me, you can find information on my wiki page [4], it will show you what are my interests on Ubuntu / Lubuntu and so the sessions I will probably follow and report 🙂 I’ll try also to use my twitter account a bit more this time 🙂

[1] https://blueprints.launchpad.net/sprints/uds-p

[2] http://summit.ubuntu.com/uds-p/

[3] https://launchpad.net/sprints/uds-p/+attend

[4] http://wiki.ubuntu.com/gilir

Lubuntu 11.10 released

Lubuntu 11.10 is now available :

http://cdimage.ubuntu.com/lubuntu/releases/11.10/release/

 

== What is Lubuntu ? ==

Lubuntu 11.10 is a brand new flavor of Ubuntu based on the Lightweight X11 Desktop Environment (LXDE), as its default GUI. The goal is to provide a very lightweight distribution, with all the advantages of the Ubuntu world (repositories, support, etc.). Lubuntu is targeted at « normal » PC and laptop users running on low-spec hardware. Such users may not know how to use command line tools, and in most cases they just don’t have enough resources for all the bells and whistles of the « full-featured » mainstream distributions.

With many LXDE components, Lubuntu also uses well-known applications, such as Chromium, Openbox, Pidgin, to name a few. The Lubuntu project wiki contains more information on the project and the applications used available.

== Features ==

* Based on the lightweight LXDE desktop environment.
* Pcmanfm 0.9.9, a fast and lightweight files manager using gio/gvfs.
* Lxdm, a lightweight GTK display manager.
* Chromium, the open-source version of Google Chrome.
* … and, of course, based on Ubuntu 11.10.

See the complete list of applications on
https://wiki.ubuntu.com/Lubuntu/Applications

== Improvements since Lubuntu 11.04 ==

* ISOs are now build with Ubuntu official build system.
* Alternate ISOs are available.
* Many updates from LXDE (most components had official releases).
* Build with recommended packages by default.
* Use recommends instead of depends for most of components of lubuntu-desktop meta-package.
* Register correctly LXDE as a desktop environment by xdg tools.
* Switch to xfce4-power-manager for power management.
* Add a microblog client : pidgin-microblog.
* New theme made by Rafael Laguna.

== Releases notes and known issues ==

The release notes, with a list of known problems are available on
https://wiki.ubuntu.com/Lubuntu/ReleaseNotes/OneiricOcelot

== Reporting bugs ==

You can find information on how to report bug on this wiki page :
https://wiki.ubuntu.com/Lubuntu/ReportingBugs

== Thanks ==

I would like to thanks all people involved in the development of Lubuntu
during this past 6 months : LXDE developers, people helping on IRC, testing ISOs, reporting bugs, making documentation and artwork …
It was a pleasure to work with all of you.

== Links ==

* Website : http://lubuntu.net/
* Documentation : https://wiki.ubuntu.com/Lubuntu
* LXDE website : http://lxde.org/
* Announcement: https://wiki.ubuntu.com/Lubuntu/Announcement/11.10

Lubuntu 10.10 is released

Lubuntu 10.10 is now available :

What is Lubuntu ?

Lubuntu is an Ubuntu derivated using the LXDE desktop. It’s designed to be a lightweight and easy-to-use desktop environment.
Lubuntu is actually not part of the Ubuntu family, and not build with the current Ubuntu infrastructure. This release is considered as a « stable beta », a result that could be a final and stable release if we was included in the Ubuntu family.

Features

  • Based on the lightweight LXDE desktop environment.
  • Pcmanfm 0.9.7, a fast and lightweight files manager using gio/gvfs.
  • Lxdm, a lightweight GTK display manager.
  • Chromium, the open-source version of Google Chrome.
  • … and, of course, based on Ubuntu 10.10

See the complete list of applications on https://wiki.ubuntu.com/Lubuntu/Applications

Improvements since Lubuntu 10.04

Applications by default

Programs installed by default have been updated

  • Added :

Update-notifier, to get notification for available updates.
Xpad, to create quick notes (similar to Tomboy).
Ace-of-penguins, to provide some games

  • Removed

Parcellite, which is not maintained upstream, is less useful since most of copy/paste bugs was gone with pcmanfm 0.9.X.
Pyneighborhood was replaced by gvfs support of pcmanfm.

  • Changes

LXtask replace Xfce4-taskmanager for tasks monitoring.
Evince is now used for reading PDF, ePDFview have some serious memory leaks.

New theme

A new and fresh theme, made by Rafael Laguna, is available.

Installer slideshow

New slideshow is available during the installation, to describe Lubuntu and its features.

Indicators supports

Lxpanel now support Ubuntu indicators applets. This feature is turn off by default, but you can activate it by adding the « Indicators applet”.

New extras packages

  • A new meta-package (lubuntu-core) is available to install only core packages of Lubuntu.
  • A new meta-package (lubuntu-restricted-extras) is available to install restricted packages for Lubuntu (such as flash, java and extra codecs for Chromium)

LXDE updates

  • LXDE is now HAL-free. Lubuntu still depends on HAL for CD-burner, but by removing it, you can obtain a HAL-free system.
  • New lxappareance from LXDE git (without Openbox integration)
  • And the usual updates of LXDE and Ubuntu packages included in Lubuntu.

Releases notes and known issues

The release notes, with a list of known problems are available on https://wiki.ubuntu.com/Lubuntu/ReleaseNotes/MaverickMeerkat

Reporting bugs

You can find information on how to report bug on this wiki page : https://wiki.ubuntu.com/Lubuntu/ReportingBugs

Links

Lubuntu 10.04

Lubuntu 10.04 is now available :

== What is Lubuntu ? ==

Lubuntu is a project to make a Ubuntu variant using the LXDE desktop. It’s designed to be a lightweight and easy-to-use desktop environment. Lubuntu is currently not part of the Ubuntu family, and not build with the current Ubuntu infrastructure. This release is considered as a « stable beta », a result that could be a final and stable release if it was included in the Ubuntu family. Please note also that Lubuntu 10.04 is not a LTS version.

== Features ==

  • Based on the lightweight LXDE desktop environment.
  • Pcmanfm 0.9.5, the rewrite of pcmanfm using gio/gvfs.
  • Lxdm, a new and lightweight GTK display manager.
  • Chromium, the open-source version of Google Chrome.
  • … and, of course, based on Ubuntu 10.04

See the complete list of applications on the wiki.

The release notes are available also on the wiki.

== Specific Lubuntu changes ==

Lubuntu still contains modifications not available in the official repository, you can see them in the Lubuntu PPA [1] :

  • New pcmanfm2 and libfm (LP: #523433)
  • lubuntu-default-settings with pcmanfm2 support
  • Fix for blurry shutdown-icon from elementary-icons (LP: #527345)
  • Autologin support in ubiquity (LP: #546445)

== Roadmap for Maverick ==

A roadmap for the next version is available on the wiki :

https://wiki.ubuntu.com/Lubuntu/Developers#Maverick

== Screenshot ==

== Links ==

[1] : https://launchpad.net/~lubuntu-desktop/+archive/