{"id":1319,"date":"2006-06-24T12:29:32","date_gmt":"2006-06-24T10:29:32","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2006\/06\/ubuntu-dev-summit-in-paris\/"},"modified":"2006-06-24T12:29:32","modified_gmt":"2006-06-24T10:29:32","slug":"ubuntu-dev-summit-in-paris","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2006\/06\/ubuntu-dev-summit-in-paris\/","title":{"rendered":"Ubuntu Dev Summit in Paris."},"content":{"rendered":"

\"Drafting<\/a><\/p>\n

\n\tSo this release cycle’s Ubuntu Dev Summit has ended. 60 people from the wider Ubuntu community
\ngathered in Paris to draft the next release, Edgy Eft — and it will be rocking (although probably
\nedgy, as its name says). Some highlights are an event-based replacement for the init system, SysV
\ninit does not fit today’s use cases very well anymore, a system nowadays is almost never booted with
\nall kinds of pluggable hardware, suspend and resume functionality. Speaking of
\nsuspend<\/strong>, I’ve talked to Ben Collins, Ubuntu’s kernel maintainer about integrating
\nsuspend2<\/a> in Edgy’s kernel. He had a quick look at the patches
\nand was quite surprised by the improved quality. Nigel Cunningham, suspend2’s main developer has put
\nquite some work in making the patches less intrusive and more mergeable. Last week, I benchmarked
\nboth, suspend2 and vanilla’s software suspend. The results were simply amazing: swsusp needs 45
\nseconds to bring the machine back up, whereas suspend2 does that in 25s (mainly caused by image
\ncompression). suspend2 also adds a nice userinterface (framebuffer splash, textmode progress bar —
\npick your poisoln) and is much<\/strong> more reliable under high memory load. The least
\nthing you want is a system not suspending when you run away in a hurry and drop your laptop in a
\ntrain. That’s definitely a big plus. Hope Ubuntu will be the first distro shipping this cutting edge
\ntechnology by default.\n\t<\/p>\n

\n\tWe also talked about the benefits and disadvantages of decoupling Ubuntu’s and Kubuntu’s
\nrelease schedules<\/strong>. It would make sense from a branding point of view. Putting out a press
\nrelease of Ubuntu and Kubuntu at the same time doesn’t make sense, it’d only harm the clarity of the
\nmessage to the outside. That is mainly why Kubuntu didn’t have a separate press release. To create a
\nstronger brand, however, it’d make sense to have a real opportunity to notify the public. From a
\ntechnical point of view, releasing for example 3 weeks after a Ubuntu release makes it possible to
\nget the first wave of bugfixes onto the CD, so one might expect to be of higher quality. I talked
\nabout that with Jonathan of Kubuntu fame, and also with a couple of guys that’d probably be affected
\nby it, notably Daniel Silverstone from the Soyuz team (package archives infrastructure), and Colin
\nWatson and Matt Zimmerman from the release team. They were not directly opposed and certainly see
\nthat it’d add benefit. The details however need to be sorted out first.\n\t<\/p>\n

\n\tOne thing I’m really excited about is the level of cross-desktop collaboration<\/strong>
\nI was confronted with last week. On Thursday, we had a BoF that was called gst-umbrella. We talked
\nabout how GNOME system tools could be improved, and how we can share more code between the three
\ndesktops living in the Ubuntu world — KDE, GNOME and XFCE. The atmosphere was really relaxed and we
\nwere very much on the same line. There is quite an opportunity to use the same configuration
\nmanipulation backends for all those desktops. Currently, according to the GNOME guys, the GNOME
\nsystem tools source package is a tarball of 12MB of perl backends, C frontends and XML-based GUI
\nfiles. Feel the pain. There is a common understanding that it makes sense to move that stuff to
\nPython in the future. Those issues have to be checked back with GNOME-upstream. We might even have
\nthe first results of that ready for edgy, which has a pretty tight release schedule — feature
\nfreeze in 11 weeks.\n\t<\/p>\n

\n\tThe people that might worry about me after Ken’s
\nreport from wednesday night in Paris<\/a> : I’m fine. Only have to wear my (prescribed)
\nsun<\/strong>glasses now all day (and night!) which makes me look a bit stupid. Can’t say I’m
\nunhappy with that acutally, people should basically never expect me to be too serious. :P Still a
\ngood thing that it’s really summer here in Western Europe.
\n\t
Myriam from the FSFE was kind enough to take me to Germany, we had a nice chat in the car
\nabout Freedom, messaging, the Free Software world in general, buy in from other organisations,
\npolitical stuff …<\/p>\n

\tThat’s about it for now, I’ll probably blog some about FrOSCon<\/a> more later on. Ow, thanks to \\sh<\/a> (who’s also here at FrOSCon) and it seems I’m now also
\naggregated on Planet Kubuntu<\/a>, so hi there!\n\t<\/p>\n","protected":false},"excerpt":{"rendered":"

So this release cycle’s Ubuntu Dev Summit has ended. 60 people from the wider Ubuntu community gathered in Paris to draft the next release, Edgy Eft — and it will be rocking (although probably edgy, as its name says). Some highlights are an event-based replacement for the init system, SysV init does not fit today’s… Continue reading Ubuntu Dev Summit in Paris.<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1319","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1319","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1319"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1319\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}