[00:20] <desrt> robert_ancell: hey
[00:25] <robert_ancell> desrt, hey
[00:25] <desrt> robert_ancell: still interested in dconf-editor? :)
[00:26] <robert_ancell> desrt, sure
[00:26]  * RAOF returns a non-wardrobe to Freedom while mesa builds
[00:27] <desrt> nice
[00:27] <desrt> going to start making a dconf API for it, then
[00:27] <desrt> UI question for you:
[00:27] <robert_ancell> desrt, got step-by-step instructions to getting d-conf to work on Maverick?
[00:27] <robert_ancell> :)
[00:27] <desrt> robert_ancell: step 1: wait until seb wakes up
[00:27] <desrt> robert_ancell: step 2: install some .debs :)
[00:27] <robert_ancell> nice
[00:28] <desrt> in seriousness, though... you could download the glib and dconf releases that i made today
[00:28] <desrt> that's all you need to do
[00:28] <robert_ancell> how is dconf started? on demand?
[00:28] <desrt> on first write
[00:28] <desrt> but unless you have some really fancy setup going on, that's not going to work out at all
[00:30] <robert_ancell> desrt, you want dconf-editor in the dconf git?
[00:31] <desrt> it makes sense i guess
[00:31] <desrt> hmm.
[00:31] <desrt> ya.  let's do that.
[00:32] <desrt> so my UI question is this:
[00:32] <desrt> when you go to edit your user settings
[00:32] <desrt> should you also see the defaults?
[00:32] <desrt> or -just- the ones that you explicitly setup for yourself
[00:32] <desrt> also: how well-integrated should our GSettings support be?
[00:32] <desrt> i can imagine two different views: one you navigate by tree and the other that you navigate by schema
[00:33] <robert_ancell> I think you should see the value you would get if you did a read, but it should indicate if that value is the default (and show the default if it is not).  gconf-editor didn't do this well and it was annoying
[00:33] <robert_ancell> show the default *as well*
[00:33] <desrt> ya.  i specifically ask because of how bad gconf-editor is here
[00:33] <desrt> ok.  that means that we will need an API to determine this
[00:33] <robert_ancell> are the schemas in the same namespace as they were in gconf?
[00:33] <desrt> no
[00:33] <desrt> schemas are very much out of band
[00:34] <desrt> and organised quite differently
[00:34] <robert_ancell> well, then I would consider a "schema view" but I don't think it's a high priority
[00:34] <desrt> you will have to open /usr/share/glib-2.0/schemas/ and parse a bunch of xml
[00:34] <robert_ancell> np
[00:35] <desrt> i guess another interesting question is if we should show schema values
[00:35] <robert_ancell> schema values = default value, limits?
[00:35] <robert_ancell> name, description
[00:35] <desrt> so there are several layers
[00:36] <desrt> as it is, it will be extremely rare for default values to be in dconf
[00:36] <desrt> unless you have a sysadmin, essentially
[00:36] <desrt> vendor defaults are handled via the schemas
[00:37] <TheMuso> 8/c
[00:42] <mclasen> desrt: you have to parse the schemas anyway, to get at the key docs
[00:43] <Amaranth> man, compiz is really hating me
[00:43] <Amaranth> when I build in pbuilder all the schemas are completely empty files
[00:55] <desrt> mclasen: right... not sure if that information ought to be visibile in the tree view or not...
[00:56] <desrt> mclasen: since you could go the GSettings view route to get it...
[00:56] <mclasen> desrt: in my view, a tree of keys without any documentation is pretty useless
[00:56] <desrt> i agree
[00:57] <desrt> which is why i think people should use the schema-based view
[00:57] <desrt> ie: pick your schema, do your changes
[00:57] <desrt> could almost build it directly on GSettings itself if we add the introspection support you've been asking about :)
[01:10] <robert_ancell> desrt, any idea what package name seb128 was going to use for dconf?  dconf is already used by another package
[01:14]  * TheMuso guesses that gnome-dconf would be used. :p
[01:15] <TheMuso> Orca was in a similar position a few years back. At the time, there was already an package called orca in Debian, so gnome-orca was used.
[02:04] <RAOF> Who wants to sponsor a mesa upload?
[02:06] <TheMuso> RAOF: how big an upload is it?
[02:06] <RAOF> ~30MB
[02:06] <RAOF> Or big as in changes?
[02:06] <TheMuso> changes wise
[02:07] <RAOF> It's a merge from debian, going from 7.7.1 → 7.8.1.  It's pretty big, changes wise.
[02:08] <TheMuso> ah ok. If you have everything committed to the various branches, just let me know where I need to pull from and I'll have a look.
[02:08] <RAOF> git.debian.org/git/pkg-xorg/lib/mesa - branch ubuntu.  You'll need to grab Debian's .orig.tar.gz, because it's created from multiple upstream tarballs.
[02:11] <TheMuso> ok sounds fun.
[02:11] <TheMuso> Does the MoM archive have that tarball?
[02:12] <TheMuso> RAOF: and since you are building from git, what command do you use to build the package?
[02:13] <RAOF> git-buildpackage
[02:13] <TheMuso> RAOF: any particular arguments I need to use?
[02:13] <RAOF> Or, rather, git-buildpackage -S
[02:13] <TheMuso> ok thanks
[02:54] <RAOF> TheMuso: Hey, have you uploaded mesa yet?  If not, we can drop a couple of packages from it; there's no longer any point in building -i686 versions :)
[03:00] <TheMuso> RAOF: not uploaded yet, just had to build a fresh maverick chroot, so go ahead and mke more changes, let me know, and I'll pull.
[03:21] <desrt> robert_ancell: i guess libdconf
[03:23] <TheMuso> desrt: ah if its a library only, then that makes sense.
[03:23] <desrt> well
[03:23] <desrt> it's not just a library
[03:23] <desrt> *shrug*
[03:24] <desrt> maybe i should just rename dconf
[03:24] <TheMuso> heh
[03:24] <desrt> what's in a name?
[03:25] <desrt> econf!
[03:25] <desrt> cconf!
[03:26] <TheMuso> yeah I know.
[03:26] <TheMuso> c
[03:27] <RAOF> aoeuconf.  I guarantee no one else will have that name!
[03:27] <chrisccoulson> uconf!
[03:28] <RAOF> I-conf u-conf we all… conf for i-conf?
[03:28] <chrisccoulson> lol
[03:29] <chrisccoulson> right, bed time for me. i'm meant to be waking up again in 3 hours
[03:31] <TheMuso> RAOF: I am building amd64 of mesa, and wow it takes a while, and this is on a quad core 3GHz penryn CPU.
[03:33] <Amaranth> gah it takes so long for a pbuilder run
[03:34] <chrisccoulson> Amaranth - dpkg ;)
[03:34] <Amaranth> eh?
[03:34] <chrisccoulson> it's probably dpkg taking ages to unpack things isn't it?
[03:34] <chrisccoulson> that's a known issue
[03:34] <Amaranth> oh, I suppose so
[03:35] <Amaranth> It takes like 15 minutes to install all the packages before it can start building
[03:35] <Amaranth> Then again it is installing 700MB worth of stuff
[03:35] <RAOF> TheMuso: May I steal your computer? :)
[03:36] <RAOF> Yeah, it takes ages, at least in part because it builds everything five different ways.
[03:36] <TheMuso> heh lovely
[03:36] <TheMuso> RAOF: heh
[03:36] <chrisccoulson> Amaranth, see bug 570805
[03:36] <ubot2> Launchpad bug 570805 in dpkg (Ubuntu Lucid) (and 3 other projects) "[regression] dpkg fsync cause massive regression in Ubuntu Server and Alternate installation times (affects: 10) (dups: 1) (heat: 80)" [High,Triaged] https://launchpad.net/bugs/570805
[03:36] <Amaranth> my penryn is a lousy 2Ghz dual core
[03:37] <RAOF> i386 will now be *slightly* faster, because it won't build swrast twice with identical options.
[03:37] <TheMuso> There is a plan to cretae a command-line flag for dpkg to turn that off, so we could set things up such that its turned off for sbuild/pbuilder.
[03:37] <Amaranth> wow ubot2 got rather verbose
[03:37] <chrisccoulson> i need a machine like the one TheMuso has
[03:37] <TheMuso> RAOF: right
[03:38]  * TheMuso got this box as an all-rounder back in 2008. Good for audio, video, VMs, compiling, etc.
[03:38] <TheMuso> When I updated my desktop and notebook, I wanted penryn so I had the SSE4 instructino set available to apps I wanted to use.
[03:38] <TheMuso> instruction
[03:41] <TheMuso> RAOF: so just let me know when you have updated git with your changes that you want included.
[03:41]  * RAOF needs to find his LCD so that his (c2006 - athlon64, baby!) desktop box can be used again.
[03:41] <RAOF> TheMuso: Once mesa has test-built on i386… :)
[03:41] <TheMuso> RAOF: heh ok.
[03:42] <Amaranth> I wonder if I could convince pbuilder to use libeatmydata for dpkg
[03:43] <RAOF> TheMuso: Everything's pushed and ready, if you'd like to try and beat my core2 duo laptop in an i386 build-off :)
[03:44] <TheMuso> RAOF: heh ok
[03:44] <TheMuso> let me fetch
[03:45] <Amaranth> Need to get 0B/199MB of archives. After unpacking 805MB will be used.
[03:45] <Amaranth> I dunno if I've mentioned this before but Compiz depends on _everything_
[03:45] <RAOF> That's a pretty impressive compression ratio
[03:45]  * TheMuso builds mesa for i386.
[03:46] <RAOF> BAh.  One final change - UNRELEASED → maverick in changelog.  Won't affect the build, though.
[03:48] <TheMuso> right
[03:55] <TheMuso> RAOF: any reason why you are not merging with the unreleased changes in the debian-experimental branch, one of which looks useful with package stripping?
[03:56]  * TheMuso notes he regularly does this with alsa packages, due to the useful changes that exist, and the infrequency at times of updates in terms of package uploads in Debian.
[04:01] <RAOF> TheMuso: Probably because those changes weren't there at the time.  I'll incorporate them.
[04:03] <TheMuso> RAOF: ah ok
[04:04] <RAOF> Hm.  How should that get changelogd?
[04:05] <TheMuso> RAOF: Good question. You could add them as extra changes for Ubuntu, stating that they are unreleased changes from the Debian git branch
[04:05] <RAOF> That's what I was going to do.  Is that what you do for alsa?
[04:05] <TheMuso> No I don't, but its something I should do differently in the future, now that I've thought about it.
[04:06] <TheMuso> It hasn't bitten me in a bad way as yet, but is tidier.
[04:06] <TheMuso> sorry, is not as tidy
[04:11] <TheMuso> So for mesa on i386:
[04:11] <TheMuso> Finished at 20100520-1309
[04:11] <TheMuso> Build needed 00:23:42, 1758288k disc space
[04:12] <Amaranth> How do you get those stats?
[04:13] <RAOF> sbuild
[04:13] <RAOF> Build needed 00:45:48, 1950392k disc space
[04:13] <RAOF> Your machine appears to be roughly twice as fast as mine for building mesa.  Damn.
[04:13] <Amaranth> sbuild apparently lets you make -j5
[04:15] <RAOF> TheMuso: Changes merged & pushed.  Feel free to use your awesome powers of CPU to test build again, but it *should* be trivially safe.
[04:15] <TheMuso> RAOF: ok thanks
[04:16] <RAOF> I'm test-building i386 because I'm paranoid; if you want to test-build, amd64 will be useful.
[04:17] <TheMuso> ok great
[04:21] <TheMuso> Give the flexibility of sbuild, if the slightly higher learning curve, I've never looked back.
[04:21] <TheMuso> given
[04:22] <Amaranth> RAOF: Is there a setup guide for using sbuild this way? The one on the wiki seems to be from hardy
[04:22] <RAOF> mk-sbuild, basically.
[04:23] <RAOF> From ubuntu-dev-tools
[04:23] <RAOF> It does all you want and you don't even need lvm.
[04:33] <Amaranth> sbuild maverick chroot building
[04:40] <Amaranth> I've _got_ to figure out how to get libeatmydata into these chroots
[04:40] <RAOF> Mount them on a tmpfs
[04:40] <Amaranth> *facepalm*
[04:40] <RAOF> Quick, easy fsync :)
[04:40] <Amaranth> Although I don't think I have enough memory
[04:41] <RAOF> It's a bit easier with sbuild, since you won't need the memory for the base chroot.
[04:41] <Amaranth> still, 800MB of data before I even start building :/
[04:41] <RAOF> Well, 1000MB - you also need the .debs :)
[04:41] <Amaranth> d'oh
[04:42] <Amaranth> right
[04:42] <Amaranth> Also, I don't see a way to tell sbuild to do that
[04:42] <RAOF> mount a tmpfs on /var/lib/sbuild/overlay
[04:42] <Amaranth> ah, nice
[04:43] <TheMuso> Ok, I'll just have a quick squiz at the diff for this mesa upload, and if all looks good, then I'll upload.
[04:43] <TheMuso> amd64 built fine BTW.
[04:44] <RAOF> Sweet.  Once that's available xserver + a hojillion drivers is open for business :).
[04:45] <TheMuso> RAOF: hrm could you please confirm something for me? You said using git buildpackage -S to build the package, however the debdiff is creating a .gitignore, when I compare 7.8.1-1 to 7.8.1-2
[04:45] <TheMuso> s/-2/-1ubuntu1/
[04:46] <TheMuso> So I wonder whether I am building it incorrectly...
[04:49] <Amaranth> ooh, cjwatson already fixed the dpkg suckage
[04:51]  * TheMuso tries with a more refined buildpackage command.
[04:51] <RAOF> TheMuso: Hm.  I don't see any .gitignore changes in the git diff.  I'll check against my locally built packages.
[04:51] <TheMuso> ok
[04:52] <TheMuso> RAOF: do you have perhaps have another git buildpackage config file other than whats in debian/
[04:53] <Amaranth> hmm, sbuild doesn't seem to be using /var/lib/sbuild/overlay
[04:54] <Amaranth> sbuild -Asd maverick foo.dsc certainly seems to be installing stuff somewhere though
[04:55] <TheMuso> schroot puts chroots in /var/lib/schroot/mount
[04:55] <Amaranth> yep, that's the spot
[04:55] <RAOF> TheMuso: No, you're right.  My build also seems to remove all the .gitignore, but the debian package doesn't.
[04:56] <Amaranth> So I guess I need to make /var/lib/schroot/mount a tmpfs?
[04:56] <TheMuso> RAOF: ah right that confirms what I am seeing now, the diff.gz for the Ubuntu version doesn't have .gitattributes or .gitignore
[04:56] <TheMuso> RAOF: but thats not all bad.
[04:57] <TheMuso> The package is more lintian clean in that way
[04:57] <TheMuso> RAOF: I'm willing to disregard that then
[04:57] <TheMuso> unless you would rather not...
[04:58] <RAOF> I'm not sure why they're not being stripped in Debian, but they should be (by dpkg-source -i -I, I believe).  I'm happy to disregard that.
[04:59] <TheMuso> ok fine by me
[05:00] <Amaranth> Weird split
[05:01] <TheMuso> RAOF: I see that Ubuntu is using debhelper 7 for packaging. Is that going to be pushed to the Debian branches at all by yourself or the Debian X guys?
[05:01] <Amaranth> Actually whatever sbuild is doing seems unaffected by the fsync stuff
[05:01] <Amaranth> It's chewing CPU processing the unpacking so quickly
[05:02] <TheMuso> Amaranth: Interesting. Did you use the script from ubuntu-dev-tools to set it up?
[05:02] <Amaranth> yeah
[05:02] <TheMuso> hrm. I still do mine by hand. I'll have to see what that script does these days.
[05:02] <Amaranth> oh, it's aufs+unionfs
[05:03] <Amaranth> or wait, just aufs?
[05:03] <RAOF> TheMuso: Where - in mesa?  No, the bump for debhelper 7.2.something is for dh_strip --remaining-packages, and that came from Debian.
[05:03] <RAOF> Just aufs, unless you switch it to unionfs
[05:03] <TheMuso> RAOF: oh right, of course, thanks.
[05:03] <Amaranth> I dunno, I don't keep up with filesystem stuff
[05:03] <Amaranth> Anyway, it's much faster than pbuilder
[05:03] <TheMuso> That seems icky IMO.
[05:04]  * TheMuso would prefer LVM snapshots.
[05:04] <TheMuso> s/would prefer/preferrs/
[05:04] <RAOF> That makes it harder to build in a tmpfs, though :)
[05:05] <TheMuso> True, but easier to manage chroots etc.
[05:05]  * RAOF should really publish his building-on-tmpfs pbuilder benchmarks.
[05:05] <Amaranth> oh you're kidding
[05:05] <Amaranth> It doesn't cache build deps?
[05:08]  * TheMuso pats his local mirror.
[05:09] <Amaranth> I'm half tempted to just upload this to my PPA to see if it works
[05:20] <TheMuso> RAOF: One last question. Is the fix that was uploaded in lucid-proposed for mesa in maverick yet?
[05:23] <RAOF> TheMuso: Yes.  That was a cherrypick from upstream, and the new version contains it.
[05:27] <TheMuso> RAOF: Ok then, thanks.
[05:27] <TheMuso> RAOF: just needed to know in relation to what changelog entries should be included in the changes file.
[05:29] <RAOF> Just the last two.
[05:33] <TheMuso> you mean prior to your changelog entry? Yeah thats what I've done.
[05:33] <TheMuso> Strike that, I know what you mean, the last two including yours.
[05:35] <TheMuso> RAOF: Are you aware that the .diff.gz files for both debian and this proposed Ubuntu package have files directly modified in the source tree, and the ubuntu package also has debian/patches files?
[05:35] <TheMuso> ah its not so bad, Debian has that too. Kind of a mess, but anyway.
[05:35]  * TheMuso uploads.
[05:37] <RAOF> Yes.  Thanks!
[05:37] <TheMuso> np
[05:37]  * TheMuso is glad he won't be the one cleaning that up.
[05:40] <TheMuso> Ouch, the diff alone is ~2MB.
[05:40] <TheMuso> 2.5MB even
[05:40] <TheMuso> RAOF: uploaded.
[05:44] <RAOF> Sweet.  Thanks again.
[05:45] <TheMuso> np
[05:46] <RAOF> A surprising amount of that diff is ChangeLog, at 7.8MB uncompressed :)
[05:46] <TheMuso> Yeah I can imagine.
[06:10] <ccheney> is there a list of tags posted somewhere, like all the apport-* related tags?
[06:10] <ccheney> i'm trying to write a bug automation script to ask for apport-collect info for bugs but it seems there are at least several apport related tags
[06:11] <ccheney> it looks like there are 4 of them
[06:41] <robert_ancell> TheMuso, can you sponsor GTK+ (in bzr)
[06:45] <TheMuso> robert_ancell: Sure. You got all the X bits you needed through the NEW queue yet?
[06:45] <robert_ancell> TheMuso, yup, they were there by this morning (don't know what the delay was in the end)
[06:46] <TheMuso> robert_ancell: ok then will take a look.
[06:49] <robert_ancell> hey does anyone know why the recent build of libffi puts its header files in a strange place? http://packages.debian.org/squeeze/i386/libffi-dev/filelist
[06:49] <robert_ancell> I'm guessing it's a bug in their build system?
[07:22]  * ccheney likes arsenal, much easier to triage with it :)
[07:26] <TheMuso> robert_ancell: I am test building gtk now.
[07:27] <robert_ancell> TheMuso, thanks
[07:42] <TheMuso> robert_ancell: you have left out all the previous ubuntu changelog entries.
[07:42] <TheMuso> robert_ancell: i.e only  your merge changelog is present.
[07:49] <robert_ancell> TheMuso, yes, that's the best way to do it - the previous entries aren't relevant anymore
[07:51] <robert_ancell> I'm trying to think who said it was ok to do it that way...
[07:51] <TheMuso> robert_ancell: hrm ok. Generally if its a merge, we keep all the other changelog entries in the merge so people can go back and see when perticular additions to the Ubuntu package were made.
[07:52] <robert_ancell> TheMuso, what use is that?  The patch headers contain the metadata about the patches and link to the bug reports with this information
[07:54] <TheMuso> robert_ancell: Very well, I see thats how it was done previously.
[07:54] <mvo> its seems that its slightly different in different teams
[07:55] <TheMuso> mvo: More than that, its different between package groups, i.e X and GTK/GNOME is different. :)
[07:55] <mvo> yeah :)
[07:56] <mvo> I tend to preserve the changelogs, but I can see that having all the metadata in the patches is valid and the merge can be a bit painful with the changelog
[07:56] <robert_ancell> well, I like to remove them because it makes future merging harder and it's confusing to read the changelog
[07:57] <TheMuso> fair enough.
[07:57] <robert_ancell> especially when you do a few merges in a row and end up with very large "Ubuntu changes" changelog entries
[07:57]  * TheMuso is building i386 of gtk now. Amd64 was fine but wil wait till this is built and upload.
[07:57] <mvo> yep, fair enough from me too
[07:58] <robert_ancell> mvo, hey btw :)
[07:58] <mvo> I guess its a good afternoon for you :)
[07:58] <mvo> funny, I'm still having my wake-up tea (and I'm not yet fully woken up)
[07:58] <TheMuso> The only thing I don't like about this time of year, is that it gets dark too early. :)
[07:59] <TheMuso> The weather on the other hand, is great!
[07:59] <robert_ancell> TheMuso, depends on your preferred weather!
[07:59] <robert_ancell> has anyone ever tried solang?
[07:59] <TheMuso> robert_ancell: Thats true. I refer to the mid to late autumn Sydney weather, pleasant days, cool nights.
[08:02] <mvo> TheMuso: oh, nice. we have really bad weather here, its supposed to be summer, but all we get currently is rain and grey skys
[08:05] <robert_ancell> TheMuso, GTK+ sure takes a long time to compile :)  Took me at least 30 mins on my Maverick build box which is unfortunately a netbook
[08:05] <TheMuso> Does indeed.
[08:06] <TheMuso> robert_ancell: Yeah took me 29 mins for i386 and 27 mins for amd64.
[08:06] <didrocks> good morning
[08:07] <TheMuso> robert_ancell: uploading
[08:08] <TheMuso> Wow. Gtk is slightly bigger tarball wise than mesa was.
[08:09] <robert_ancell> didrocks, hey
[08:10] <robert_ancell> didrocks, do you know much about gobject introspection?  I noticed you did the GTK+ work.  I'm trying to get PyGI working...
[08:12] <didrocks> robert_ancell: hey o/ I don't know "much", but I've used a little bit the pygi for clutter and it didn't really work as well as expected
[08:13] <robert_ancell> didrocks, I've got a package for it but there's nothing in gi.repository.  Was wondering if you had any debugging tips
[08:14] <didrocks> robert_ancell: hum, not really, sorry :/, but gi repository is deprecated, no?
[08:14] <robert_ancell> didrocks, i'm not sure, but I haven't got my head fully around gi yet.  Still seems quite fluid
[08:15] <asac> o/
[08:15] <robert_ancell> o/
[08:15] <didrocks> hey asac
[08:15] <RAOF> TheMuso: And if we built GTK 5 times I'm sure it'd take as long to build, too :)
[08:16] <asac> hi didrocks, robert_ancell !
[08:16] <didrocks> robert_ancell: I still have on my "TOREAD" stuff the blog posts from yesterday on pygi :)
[08:19] <pitti> Good morning
[08:19] <didrocks> Guten Morgen pitti, how are you?
[08:24] <TheMuso> RAOF: heh
[08:24] <pitti> bonjour didrocks, I'm great! how are you?
[08:25] <didrocks> pitti: I'm fine, thanks ;)
[08:29] <mvo> hm, I had a dialog this morning that my stadnard folders need new names. but all it want to change is "Desktop" to "Downloads". that does not look right
[08:42] <robert_ancell> later all
[08:45] <didrocks> see you robert_ancell
[11:42] <seb128> ok
[11:42] <seb128> versions tracking maverick now
[11:48] <didrocks> seb128: cool \o/
[12:07] <vish> seb128: hi.. how do i get an upload to lucid-proposed ? [for SRU]
[12:09] <pitti> vish: it's technically no different than uploading to maverick, except that the nature of changes needs to match the SRU requirements, and it needs to link to an SRU bug
[12:09]  * pitti lunch &
[12:10] <vish> seb128: pitti: ex: Bug #566996 i think i filled the description appropriately..
[12:10] <ubot2> Launchpad bug 566996 in humanity-icon-theme (Ubuntu) "Humanity in KDE does not display volume icons. (affects: 1) (heat: 7)" [Low,Fix committed] https://launchpad.net/bugs/566996
[12:15] <pitti> vish: ah, so KDE doesn't get along with the .png -> .svg symlink hack?
[12:15] <pitti> approved the lucid task
[12:15] <vish> pitti: yeah , thanks..
[12:30] <seb128> vish, I was away for lunch, what pitti said
[12:31] <seb128> you just need the upload to go to lucid-proposed in the changelog
[12:31] <seb128> with a bug which has the debdiff and has a testcase
[12:32] <vish> seb128: oh , ok so the changelog for the lp:~ubuntu-art-pkg/humanity/release branch should mention "lucid-proposed" , on it
[12:32] <vish> thanks..
[12:33] <seb128> yes
[12:41] <vish> seb128: fixed the changelog to lucid-proposed :  lp:~ubuntu-art-pkg/humanity/release , could you upload it to -proposed..
[12:43] <seb128> vish, I will have a look later when I do some SRU round
[12:43] <vish> seb128: neat thanks..
[12:43] <seb128> you're welcome, thanks for working on the change!
[12:43] <vish> np..  :)
[13:04] <kenvandine> seb128, when does the tracker update?
[13:05] <kenvandine> WI tracker that is?
[13:07] <seb128> kenvandine, once a day or when pitti kicks an update I think
[13:07] <seb128> pitti, ^
[13:08] <kenvandine> ok
[13:08] <pitti> it updates WIs hourly
[13:08] <pitti> and team members/milestones daily
[13:08] <seb128> pitti, thanks
[13:08] <seb128> kenvandine, is that anything you miss there?
[13:10] <kenvandine> i fixed something
[13:10] <kenvandine> removed the leading *
[13:10] <kenvandine> so now my WI count is a perfect 16 :)
[13:12] <seb128> pitti, do you have any suggestion about who would know about zip and encoding or could take responsability for this change out of you?
[13:12] <pitti> seb128: bug 580961?
[13:12] <ubot2> Launchpad bug 580961 in unzip (Debian) (and 2 other projects) "unzip fails to deal correctly with filename encodings (affects: 84) (dups: 19) (heat: 582)" [Unknown,Confirmed] https://launchpad.net/bugs/580961
[13:12] <seb128> pitti, yes, it seems to be high on the user annoyance list looking at duplicates
[13:13] <seb128> pitti, and since you are not going to work on it I'm trying to figure where to bounce it
[13:13] <pitti> I haven't looked at it at all yet
[13:13] <seb128> well you shouldn't ;-)
[13:13] <pitti> I never actually touched that patch, so I'm afraid I know nothing more than anyone else
[13:14] <seb128> ok, good, thanks
[13:14] <pitti> but oh well, we don't even support non-UTF8 file names, locales, etc.
[13:14] <seb128> I will add it on my list of things to look at
[13:14] <pitti> so I don't consider it a major issue TBH
[13:14] <pitti> merci
[13:15] <pitti> and this is not the kind of change that I like us to carry permanently
[13:15] <seb128> it has quite some duplicate, I would like to have that sorted still ;-)
[13:15] <seb128> you're welcome
[13:15] <pitti> that patch is ancient, and if it never made it upstream, there's something fishy
[13:16] <pitti> doko originally applied it, but apparently got the idea wrong what it actually does
[13:16] <pitti> but this was in feisty, so he might not remember the details any more
[13:17] <seb128> I will try to understand what is going on and talk to doko about it a bit later
[13:17] <seb128> thanks!
[13:17]  * pitti hugs seb128
[13:18]  * seb128 hugs pitti
[13:18] <kenvandine> seb128, got a few to review my blueprints?
[13:18] <seb128> kenvandine, yes, did the track picked your updates yet?
[13:20] <kenvandine> probably not, but it is obvious
[13:20] <kenvandine> basically my number is 16, not 22
[13:20] <kenvandine> the ones with [segphault] were getting counted for me
[13:20] <seb128> ok
[13:20] <seb128> so let's review those
[13:20] <seb128> you have 3 specs right?
[13:21] <kenvandine> yeah
[13:21] <seb128> desktop-maverick-empathy-indicator
[13:21] <seb128> desktop-maverick-gwibber-test-suite
[13:21] <seb128> desktop-maverick-social-api
[13:21] <seb128> + some items on dx specs
[13:21] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team.html says you have 49 items for the cycle
[13:22] <pitti> ?!
[13:22] <seb128> what was item per week count?
[13:22] <pitti> two hours ago it was 4
[13:22] <kenvandine> my target is 16 for a2
[13:22] <seb128> pitti, ? I'm talking to kenvandine
[13:22] <pitti> seb128: I can do one per week
[13:22] <pitti> seb128: argh, sorry; got the hightlight due to the /~pitti/
[13:22] <seb128> pitti, sorry seems there is some confusion
[13:22] <kenvandine> hehe
[13:22] <seb128> pitti, kenvandine can't make it to the meeting today, we are review his items
[13:23] <seb128> reviewing
[13:23]  * seb128 hugs pitti
[13:23] <kenvandine> weekly target is 3
[13:23] <kenvandine> so actually my a2 target is 18
[13:23] <seb128> ok
[13:23] <kenvandine> i have 16 so far for my specs
[13:23] <seb128> so let's start with
[13:23] <seb128> http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-1.html
[13:23] <kenvandine> which only gives me room for 2 more :)
[13:23]  * pitti should have put them into a role account
[13:23] <kenvandine> only other item i know about is indicator-network plus my usually package wrangling
[13:24] <seb128> ok
[13:24] <seb128> alpha1 has the indicator-appmenu items
[13:24] <desrt> seb128, pitti, kenvandine; good morning
[13:24] <seb128> do you know if that's on track to land in the next 2 weeks?
[13:24] <seb128> desrt, hey
[13:24] <pitti> hey desrt, how are you?
[13:24] <desrt> pretty decent
[13:24] <kenvandine> yes
[13:24] <kenvandine> seb128, those should be thursday
[13:24] <kenvandine> next week
[13:24] <seb128> ok, good
[13:24] <seb128> so alpha1 on track
[13:25] <seb128> looking to http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html now
[13:25] <desrt> seb128: there are some new packages :)
[13:25] <seb128> desrt, no time for dconf this week sorry ;-)
[13:25] <kenvandine> yay tracker refreshed
[13:25] <desrt> it's fine :p
[13:25] <seb128> but maybe robert_ancell will pick it up, he did the glib 2.25 update
[13:25] <desrt> was wondering if maybe we can get the 'dconf' package dropped from universe though
[13:26] <desrt> otherwise i will be forced to rename it to seb128conf
[13:26] <seb128> I doubt it
[13:26] <seb128> namespace clash suck
[13:26] <kenvandine> hehe
[13:26]  * desrt installed epiphany-game during the default browser selection session >:(
[13:27] <chrisccoulson> i've done that before too ;)
[13:27] <kenvandine> seb128, so for a2 my target is 18 and i have 16, i think the indicator-network stuff should have WIs for me, so that will max me out
[13:27] <kenvandine> but it should be doable
[13:27] <desrt> chrisccoulson: i think every living being has done that at some point
[13:27] <kenvandine> 2 of the a2 WIs are almost done already
[13:27] <seb128> kenvandine, right, I'm reviewing your a2 items right now, seems good
[13:27] <kenvandine> actually 3
[13:27] <seb128> desrt, yeah...
[13:28] <desrt> ok
[13:28] <desrt> seb128conf it is
[13:28] <seb128> kenvandine, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-empathy-indicator do we still need an empathy change or the preference?
[13:28] <desrt> i will let the gnome admins know to rename the module in git and bugzilla
[13:28] <desrt> :)
[13:28] <seb128> desrt, lol
[13:28] <kenvandine> seb128, yeah, small one
[13:28] <kenvandine> to enable or disable use of the indicator
[13:28] <kenvandine> we'll read the pref from gconf
[13:28] <kenvandine> i don't want any UI in the service
[13:29] <seb128> I'm wondering if we need an UI
[13:29] <kenvandine> and empathy will need to know if it needs to use the StatusIcon or not
[13:29] <seb128> the service will be a new binary?
[13:29] <kenvandine> yes
[13:29] <seb128> can't we just be smart about it depending on whether the service is installed or not
[13:29] <seb128> and maybe have a gconf key for tweaking but without ui
[13:29] <kenvandine> we could... but makes it a little harder for users to go back and forth
[13:30] <kenvandine> either way requires a patch to empathy
[13:30] <seb128> ok, fair enough
[13:30] <kenvandine> so empathy doesn't use the status icon
[13:30] <kenvandine> trying to keep it simple
[13:30] <kenvandine> we already have the UI patch in place and is tiny
[13:31] <seb128> right
[13:32] <ArneGoetje> seb128: I have one blueprint, which doesn't show up in the burndown chart. Can you please take a look? https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector-code-changes
[13:32] <seb128> your list seems good, you have quite some items but tasks are reasonable amount of work and it seems doable
[13:32] <kenvandine> good :)
[13:32] <seb128> kenvandine, who is in charge or porting the indicator to libgwibber, dx or you?
[13:33] <kenvandine> me
[13:33] <seb128> kenvandine, you seem to have no work items for those tasks?
[13:33] <kenvandine> well the indicator won't be in libgwibber
[13:33] <kenvandine> that won't change actually
[13:33] <kenvandine> that is driven by gwibber-service
[13:33] <seb128> ok, so indicator change required?
[13:34] <kenvandine> no
[13:34] <seb128> ArneGoetje, done
[13:34] <seb128> ArneGoetje, it needed the serie goal to be accepted
[13:34] <kenvandine> libgwibber is just for other apps besides gwibber
[13:34] <seb128> ArneGoetje, should be there on next refresh
[13:34] <seb128> kenvandine, ok, good
[13:34] <ArneGoetje> seb128: ok, thanks
[13:35] <seb128> kenvandine, is there any item for the indicator-clock packaging somewhere?
[13:35] <kenvandine> that packaging is done
[13:35] <seb128> I guess it will need to get uploaded and promoted this cycle
[13:35] <kenvandine> the only thing needed would be to drop the existing one
[13:35] <kenvandine> just needs to land in main
[13:36] <seb128> should we track that?
[13:36] <kenvandine> didrocks might already be
[13:36] <kenvandine> since that is already in UNE
[13:36] <kenvandine> if not it would be good to track it
[13:36] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-indicator-clock
[13:36] <didrocks> kenvandine: I guess there is a dx spec for it
[13:36] <didrocks> ok, seb128 found it :)
[13:36] <seb128> didrocks, kenvandine: ^ can you coordinate to get 2 items there
[13:37] <seb128> one for getting it uploaded
[13:37] <seb128> one mir
[13:37] <seb128> decide between you who takes the actions
[13:37] <didrocks> I was thinking all indicators stuff was on kenvandine, hence the fact I didn't check
[13:37] <seb128> it should not be lot of work anyway ;-)
[13:38] <seb128> kenvandine, can you get it in universe?
[13:38] <seb128> didrocks, can you get the mir done and une to pull it in?
[13:38] <kenvandine> i can
[13:38] <seb128> thanks
[13:38] <seb128> kenvandine, ok, you are on track for your specs it seems, thanks for the review
[13:38] <kenvandine> thank you
[13:38] <seb128> good luck for getting all that done now ;-)
[13:39] <kenvandine> hehe
[13:41] <seb128> desrt, so dconf, we don't have good way to handle renames
[13:41] <desrt> *ahem* drop? :)
[13:41] <seb128> users who have current dconf installed would receive something different on upgrade replacing what they use
[13:41] <desrt> i guess the upgrade question is pretty pointless when the new package is default-installed
[13:41] <seb128> we would need to convince debian too since it comes from there
[13:42] <kenvandine> seb128, can you sponsor lp:~ubuntu-desktop/indicator-application/ubuntu
[13:42] <kenvandine> to lucid-proposed?
[13:42] <seb128> kenvandine, will do, thanks to ted and you for working on it
[13:42] <kenvandine> it got rejected for me
[13:42] <pitti> seb128: I don't understand? wouldn't it be enough to have the new packages conflicts/replaces: dconf?
[13:42] <seb128> pitti, which new packages?
[13:43] <kenvandine> and subscribe ubuntu-sru to bug 569273
[13:43] <ubot2> Launchpad bug 569273 in indicator-application (Ubuntu) "memory leak in gnome-power-manager on lucid (affects: 11) (heat: 50)" [Medium,New] https://launchpad.net/bugs/569273
[13:43] <seb128> pitti, there is a dconf already which is something else
[13:43]  * kenvandine needs to head out now... be back in a few hours
[13:43] <pitti> seb128: aah, right; this is not _that_ dconf, sorry
[13:43] <seb128> kenvandine, I will let you handle the bug subscribing etc side
[13:43] <seb128> pitti, yeah, confusing...
[13:44] <pitti> seb128: the binary might be libdconf1 and libdconf-bin?
[13:44] <seb128> they might, I didn't look at it yet
[13:44] <didrocks> seb128: I've added that to the WI "MIR for UNE components"
[13:44] <seb128> didrocks, thanks
[13:45] <kenvandine> ok
[13:45] <seb128> desrt, how are the applications ported to gsettings working right now without dconf?
[13:46] <desrt> they use a backend inside of glib that stores the settings in a GHashTable local to the program
[13:46] <seb128> it means you loose your config when you close the software?
[13:46] <desrt> yes
[13:46] <seb128> ok, we don't want to package 2.31 yet :p
[13:47] <desrt> just package dconf first :p
[13:47] <seb128> yeah, will try to get that done next week
[13:47] <desrt> i guess dconf should be Recommends: of libglib
[13:47] <seb128> right
[13:47] <seb128> slomo, hey
[13:48] <seb128> slomo, will you work on packaging dconf for debian?
[13:48] <slomo> seb128: probably not, too busy with other stuff
[13:49] <slomo> seb128: same goes for gtk3 :(
[13:49] <seb128> ok
[13:49] <seb128> you started on glib 2.25 so I was wondering
[13:49] <seb128> thanks
[13:49] <pitti> seb128: you could upload it to debian as well?
[13:50] <seb128> pitti, right, I was just checking before we start and duplicate work
[13:50] <seb128> I will get it in debian
[13:50] <seb128> though I guess Debian will not do anything with it in the next month
[13:50] <seb128> they will freeze soon
[13:51] <pitti> they probably won't mind having it in experimental
[13:51] <seb128> right, I will get it there
[13:53] <desrt> seb128: yes.
[13:53] <desrt> er.  ignore me.
[14:01] <ccheney> good morning
[14:24] <seb128> hey tedg, rickspencer3
[14:25] <seb128> tedg, rickspencer3: slightly going back on your local timezones it seems? ;-)
[14:26] <rickspencer3> hi seb128
[14:26] <rickspencer3> yes, I went to bed and woke up at normal times for the first time since back!
[14:26] <tedg> seb128, Trying ;)
[14:26] <rickspencer3> I am very happy
[14:28] <pitti> hey rickspencer3
[14:29] <rickspencer3> hi pitti
[14:29] <seb128> pitti, do you plan do your merges during your distro time or should we try to take over those?
[14:29] <pitti> seb128: I did a few, but I might not get to all of them
[14:29] <seb128> I guess we can ask tremolux to help on those
[14:29] <seb128> would be some good training for distro work
[14:29] <rickspencer3> seb128, is there an invite for the bp review meeting?
[14:30] <rickspencer3> does everyone know when it is?
[14:30]  * tremolux waves
[14:30] <pitti> rickspencer3: I got one
[14:30] <seb128> rickspencer3, I sent a reminder this morning, let me know if that didn't work
[14:30] <seb128> rickspencer3, I use the launchpad "contact team members"
[14:30] <seb128> hey tremolux
[14:30] <seb128> hey ccheney too
[14:30] <tremolux> seb128: hiya seb128
[14:31] <ccheney> seb128: hi
[14:46]  * tremolux reaches out for seb128 but catches only air
[14:46] <DASPRiD> tremolux, so you got him?
[14:46] <DASPRiD> :)
[14:47] <tremolux> DASPRiD: haha
[15:23] <rickspencer3> seb128, fyi ... I'm going to take a swap day tomorrow
[15:24] <seb128> rickspencer3, ok, enjoy it!
[15:24] <seb128> rickspencer3, will you drive the eastern edition for specs btw?
[15:24] <seb128> specs -> workitems
[15:24] <rickspencer3> seb128, yeah
[15:24] <rickspencer3> I'll do my best
[15:24] <rickspencer3> maybe tomorrow you can check them over, though
[15:26] <seb128> will do
[15:26] <seb128> at what time is the eastern edition?
[15:29] <seb128> rickspencer3, is desktop-maverick-desktop-application-selection worth tracking or are the only plan of record tracked by other specs?
[15:30] <seb128> ie shotwell by default
[15:30] <seb128> gobby has some notes about getting new screensavers, etc
[15:31] <seb128> tremolux, don't forget to define your work items for the meeting in 1h58
[15:31] <seb128> tremolux, desktop-maverick-software-center-front-end still has none
[15:32] <seb128> TheMuso, should desktop-maverick-gnome3-accessibility-readiness be tracked for maverick or not? it has no work items but is on the maverick serie
[15:32] <rickspencer3> seb128, I think not
[15:33] <rickspencer3> same with the UNE one
[15:33] <tremolux> seb128: yep, actually, I apologize but didn't know about https://wiki.ubuntu.com/DesktopTeam/10.10/WorkItemProcess until this morning
[15:33] <seb128> rickspencer3, ok, should I mark it informational?
[15:33] <tremolux> seb128: I'm working right now with mvo to coordinate our work items
[15:34] <seb128> tremolux, oh ok, thanks, you didn't get the "Blueprints and Work Items" email 3 days ago from rick?
[15:34] <tremolux> seb128: nope  :(
[15:34] <seb128> tremolux, you should be in the team and it has been sent to team member on launchpad
[15:34] <tremolux> I think I was added this week
[15:34] <seb128> tremolux, do you have a launchpad filter which could have sent that in your flood or bug emails?
[15:35] <seb128> tremolux, you were added 6 days ago according to my emails
[15:35] <tremolux> seb128: hrm
[15:35] <seb128> tremolux, you should have received it...did you get the one I sent today about the meeting reminder?
[15:36] <tremolux> seb128: yep, I did get the reminder, which is when I found out about it
[15:36] <seb128> tremolux, ok, let's assume things are working now
[15:36] <seb128> tremolux, thanks for working on getting the list done, don't worry if you are a bit late that's not an issue
[15:37] <tremolux> seb128: thanks seb128, sorry about that!
[15:37] <seb128> no worry!
[15:37] <seb128> pitti, could you kick a workitems update in 1.5hours?
[15:37] <seb128> pitti, I would like to have an updated summary for the meeting
[15:37] <pitti> seb128: in 1.5 hours it'll trigger automatically anyway
[15:38] <pitti> it's :05 past the hour
[15:38] <rickspencer3> I love seeing seb128 cracking the whip
[15:38] <seb128> rickspencer3, ;-)
[15:38] <pitti> yeah, he learned that quickly :)
[15:38]  * pitti hugs seb128
[15:38] <seb128> lol
[15:38]  * rickspencer3 leans back on marble couch while getting fed grapes
[15:38]  * seb128 hugs pitti
[15:38] <pitti> rickspencer3: sounds ... stressful :)
[15:38] <seb128> lol
[15:38] <rickspencer3> you guys make my job so hard
[15:41]  * tremolux is mumbling with mvo..
[15:49] <seb128> mvo, do you think there is an actual lp team on launchpad you could use rather than "lp team" in your specs?
[15:49] <seb128> mvo, or pick somebody on the launchpad side
[15:51] <mvo> seb128: soyuz is the one that I can think of that is closest
[15:52] <seb128> mvo, I guess the soyuz team doesn't do workitems charts anyway so there is no real point to match their team there...
[15:52] <seb128> mvo, is somebody in charge of checking that things are being done on the server side?
[15:52] <rickspencer3> seb128, mvo can we not just assign work items to bigjools on the white board?
[15:53] <mvo> oh, that is a good idea, we can just use his name instead of the team
[15:53] <mvo> seb128: its there to show that its a dependency for some of our functionality
[15:54] <seb128> or to whoever on the distro side is tracking those changes
[15:54] <seb128> soon mvo will have half of ubuntu workitems assigned to him ;-)
[15:54]  * seb128 hugs mvo
[16:02]  * DASPRiD pets seb128 
[16:07] <rickspencer3> tremolux, I'm not seeing the bug report for that weird PPA issue we saw yesterday
[16:11] <Amaranth> hmm, I think I might need to get some help from the KDE guys on this compiz packaging issue
[16:13] <Amaranth> compiz generates a pot file during the build which is then used to generate translated xml files and gconf schemas from those xml files but I think since the pot file is going in to the srcdir instead of the builddir this is failing silently in pbuilder and sbuild
[16:16] <tremolux> rickspencer3: yep, still need to write it, unfortunately, looks like that ppa (ppa:nisshh/ppa) has been deleted?
[16:17] <rickspencer3> hmm
[16:17] <rickspencer3> weird
[16:17] <rickspencer3> tremolux, I'll ask nisshh what's up
[16:17] <tremolux> rickspencer3: k, thanks
[17:29] <seb128> hey there
[17:29] <seb128> meeting in 1 minute
[17:30] <ccheney> here
[17:30] <ArneGoetje> o/
[17:30] <seb128> ArneGoetje, ccheney, didrocks, chrisccoulson, Riddell, rickspencer3: hey
[17:31] <seb128> did I forget anybody?
[17:31] <chrisccoulson> hey
[17:31] <seb128> pitti, not sure if you join
[17:31] <pitti> I'll lurk
[17:31] <didrocks> o/
[17:31]  * chrisccoulson waves at pitti
[17:31] <pitti> hey chrisccoulson
[17:31] <seb128> hey everybody
[17:31] <Riddell> hi
[17:31] <seb128> I hope everybody travelled back safely
[17:32] <seb128> and got over jetlag without ubufly
[17:32] <seb128> ubuflu
[17:32] <pitti> on that front it was surprisingly quiet indeed
[17:32] <chrisccoulson> is ubufly a new airline? ;)
[17:32] <pitti> seems we finally exchanged enough germs around the world :)
[17:32] <seb128> lol
[17:33] <seb128> pitti, it seems lool and dholbach got it
[17:33] <ccheney> i was surprised i didn't get sick this time
[17:33] <seb128> not sure about other people
[17:33] <seb128> so let's get started
[17:33] <chrisccoulson> i didn't get sick either
[17:33] <seb128> everybody did some good work on registering blueprints and workitems, so thanks!
[17:34] <seb128> pitti, want to start? since you don't really have to stay for the meeting and have only 4 items should be quick then you are free to go enjoy your evening ;-)
[17:34] <pitti> please :)
[17:34] <seb128> I guess you can manage those 4 items during the cycle during your 20% distro time?
[17:34] <pitti> absolutely
[17:34] <pitti> the two vfat-noexec ones are by and large done
[17:34] <pitti> just waiting for an ack from davidz
[17:35] <pitti> "Add apport.hookutils.add_video_info" sounds easy
[17:35] <pitti> and I don't know about the gpu hang detection
[17:35] <seb128> ok, matches what I though too
[17:35] <pitti> I'll talk to RAOF
[17:35] <seb128> I don't see any special issue or anything to discuss
[17:36] <seb128> thanks pitti ;-)
[17:36] <pitti> that was quick :)
[17:36] <seb128> indeed!
[17:36]  * pitti hugs seb128 for organizing everything so well
[17:36]  * seb128 hugs pitti
[17:36] <seb128> hope your enjoy your rotation ;-)
[17:36] <seb128> ok, let's keep going
[17:36] <seb128> ArneGoetje, hey
[17:36] <ArneGoetje> seb128: hi
[17:36] <seb128> ArneGoetje, so you have 2 specs about language selector
[17:37] <ArneGoetje> seb128: yup
[17:37] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector
[17:37] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector-code-changes
[17:37] <seb128> ArneGoetje, did you calculate your workitem number by week for previous cycle?
[17:37] <ArneGoetje> seb128: those 2 are not related, that's why I separated them
[17:37] <seb128> ArneGoetje, how much was it? what does it give you for a2?
[17:38] <ArneGoetje> seb128: I didn't calculate that, but I'll try to get as many done as possible for a2
[17:38] <seb128> the idea was to use that as a metric to know how much you can aim at for a2
[17:39] <seb128> could you try to calculate it later and let us know the number as it was described on the wikipage rick mentions some day ago in his email?
[17:39] <seb128> https://wiki.ubuntu.com/DesktopTeam/10.10/WorkItemProcess
[17:39] <seb128> ArneGoetje, ^
[17:39] <ArneGoetje> seb128: las cycle I had lots of extra stuff to do, so I figured the 11 items I have now are feasable
[17:40] <seb128> ok, still do it for the record if you can
[17:40] <seb128> so no alpha1 items so far
[17:40] <seb128> and only one for alpha2
[17:40] <seb128> is that correct?
[17:40] <ArneGoetje> seb128: sure... just need to go digging for the old blueprints again
[17:40] <seb128> just use the lucid team summary
[17:41] <seb128> you have the count there
[17:41] <seb128> by people
[17:41] <seb128> divide by the number of weeks
[17:41] <seb128> so let's go back to maverick
[17:41] <seb128> ArneGoetje, you should probably target some extra items for alpha-2
[17:41] <ArneGoetje> seb128: yes, I hope I can get the design mockups next week so that I can start right away
[17:41] <seb128> you have only one according to http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html
[17:42] <ArneGoetje> seb128: depends on how fast I can get the design mockups
[17:42] <seb128> who is working on the design?
[17:43] <ArneGoetje> michael forrest. I have contacted him already
[17:43] <seb128> ok good
[17:43] <seb128> do you have other things to work on until you get the design?
[17:43] <seb128> or other non-spec work for this cycle?
[17:43] <ArneGoetje> regarding the code changes I'll have a mini sprint with mvo next week, so that'l get me started too
[17:44] <seb128> ok good
[17:44] <seb128> your list of work items seem reasonable otherwise
[17:44] <seb128> if you are blocked to get going on that maybe review lucid bugs on language selector and look if there is some sru required there
[17:44] <ArneGoetje> I'm currently reading documentation about dbus and aptdeamon, and keep looking at bug reports which came in in the meantime.
[17:44] <seb128> or try helping on merges for maverick if you think you can do some
[17:45] <seb128> ok, seems good
[17:45] <seb128> ArneGoetje, also is ubiquity using language selector for langpacks handling?
[17:45] <ArneGoetje> seb128: yes, should be
[17:45] <seb128> just checking if that should be something to take in account when you do the changes
[17:45] <seb128> you have no work item about that
[17:45] <seb128> could you add one about making sure ubiquity gets updated if required?
[17:45] <seb128> or at least tested
[17:46] <ArneGoetje> not sure how much changes I will have to do... hope the mini sprint with mvo clarifies that... so, expect some more work items to appear on that spec.
[17:46] <seb128> ok, good
[17:46] <seb128> thanks ArneGoetje
[17:46] <seb128> good luck for the sprint ;-)
[17:46] <ArneGoetje> thanks
[17:47] <seb128> ccheney, hi
[17:47] <ccheney> seb128, hi
[17:47] <seb128> ccheney, do you still have some desktop team time this cycle or are you helping the server time full time now?
[17:47] <ccheney> seb128, yes 20%
[17:48] <seb128> do you have any spec for those 20%?
[17:48] <seb128> or just regular openoffice updates and cleaning?
[17:48] <ccheney> seb128, https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-openoffice
[17:48] <seb128> oh, it has no serie goal
[17:48]  * seb128 fixes that
[17:48] <ccheney> seb128, cleaning/updating OOo and working with dx team on paper cuts/menu integration
[17:49] <ccheney> ah sorry about that, forgot to tag it
[17:49] <seb128> ccheney, no worry, I've done it
[17:49] <seb128> the list of workitems there seems reasonable for a 20% time
[17:49] <seb128> ccheney, thanks
[17:50] <ccheney> ok
[17:50] <seb128> chrisccoulson, hi
[17:50] <chrisccoulson> hi seb128
[17:50] <seb128> chrisccoulson, did you calculate your workitems by week count?
[17:50] <seb128> not sure if you have been in the team long enough in lucid to do that though
[17:51] <seb128> you pretty much worked on getting on speed with firefox I guess
[17:51] <rickspencer3> chrisccoulson, work item/week count = infinity + 1
[17:51] <chrisccoulson> yeah, i don't really have any historical data to do that yet
[17:51] <rickspencer3> ;)
[17:51] <seb128> lol
[17:51] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-chromium
[17:51] <chrisccoulson> lol
[17:51] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-user-accounts-dialog
[17:51] <seb128> I see those specs on your list
[17:51] <seb128> somewhat it seems to low I must be missing something? ;-)
[17:52] <chrisccoulson> yeah, there is also https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-mozilla-team-discussion, which doesn't have a series goal just yet
[17:52] <seb128> joke aside, you are quite busy with browser and n-m maintainship I guess
[17:52] <chrisccoulson> but most of the WI's on there are not mine ;)
[17:52] <seb128> should I set it now?
[17:52] <seb128> the serie goal
[17:52] <chrisccoulson> yes please :)
[17:52] <chrisccoulson> yeah, i'm generally quite busy with browser maintenance atm ;)
[17:53] <seb128> ok, serie goal accepted
[17:53] <chrisccoulson> thanks
[17:53] <seb128> so I guess your priority for now is to sort up quickly chromium and if it's doable for UNE this cycle
[17:53] <chrisccoulson> yeah, i can do that
[17:53] <seb128> should you have some alpha-1 or alpha-2 items about that?
[17:54] <seb128> the technicals packaging changes can wait a bit
[17:54] <seb128> but we should try to sort early what we need
[17:54] <seb128> and if upstream is wanting to help getting there this cycle
[17:55] <chrisccoulson> yeah. so, i think the big things are security updates and translations aren't they?
[17:55] <seb128> yes
[17:55] <seb128> + sorting what users issues we will need to get sorted
[17:56] <seb128> ie dx indicator-menu integration
[17:56] <seb128> csd
[17:56] <seb128> somebody mentioned during the session also that printing was quite broken
[17:56] <seb128> could you try to coordinate with bratsche_ maybe to talk to upstream about the menu and csd
[17:57] <chrisccoulson> yeah, no problem
[17:57] <seb128> + try to get the security updates discussion going and see what we can do for translations?
[17:57] <seb128> thanks
[17:57] <seb128> otherwise your useraccount spec seems reasonable
[17:57] <seb128> chrisccoulson, anything else to add?
[17:58] <chrisccoulson> i don't think i've got anything else to add
[17:58] <seb128> ok, seems you are in shape and going to be busy again this cycle
[17:58] <seb128> thanks chrisccoulson ;-)
[17:58] <seb128> dunno what we would do without you
[17:58] <seb128> don't forget to sleep and don't overwork yourself too much ;-)
[17:58] <seb128> next
[17:59] <seb128> didrocks, hey
[17:59] <didrocks> yes o/
[17:59] <didrocks> my magical number is 5 WI a week
[17:59] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-une-app-selection
[17:59] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-quickly
[17:59] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-oneconf
[17:59] <seb128> didrocks, nice, somebody who reply before being asked, thanks ;-)
[17:59] <didrocks> y/w :-)
[17:59] <seb128> you have those on your list for now
[18:00] <seb128> is there any spec missing or not listed yet?
[18:00] <didrocks> no, I've gathered some part of other specs on thoses
[18:00] <seb128> you will be busy maintaining UNE too
[18:00] <didrocks> I guess… ^^
[18:00] <Riddell> is UNE going to be the old UNE or Unity?
[18:00] <seb128> unity
[18:01] <seb128> didrocks, your list seems quite detailed and in shape
[18:01] <seb128> you have a lot of alpha-2 items
[18:02] <didrocks> seb128: yeah, I think some WI are quite small, but it's more like a TODO reminder :)
[18:02] <seb128> right
[18:02] <seb128> it seems doable if you don't get too much sidetracked if maintaining other things
[18:02] <seb128> or doing merges and updates
[18:02] <didrocks> right, I've worked on the last two days to be able to close 3/4 WI :)
[18:02] <seb128> let me know if you feel you need to reschedule some items during the next weeks
[18:02] <didrocks> so, I think it's doable
[18:03] <seb128> seems you are up for a busy cycle too but should manage
[18:03]  * seb128 hugs didrocks
[18:03] <didrocks> some WI can be postponed to alpha3 if it's short
[18:03]  * didrocks hugs seb128
[18:03] <seb128> keep rocking ;-)
[18:03] <didrocks> thanks :-)
[18:03] <seb128> right, it seems you targetted almost all your items for alpha-2
[18:03] <seb128> we can probably delay some quickly one to alpha-3 if required
[18:04] <didrocks> sure
[18:04] <seb128> didrocks, thanks
[18:04] <seb128> Riddell, hey
[18:04] <didrocks> thanks to you for the review :)
[18:04] <seb128> Riddell, not sure if you want to do a kubuntu summary for us there
[18:04] <Riddell> hi seb128
[18:04] <seb128> or if you have something ready
[18:04] <Riddell> we have lots of specs and todo items listed at https://wiki.kubuntu.org/Kubuntu/Todo
[18:05] <seb128> indeed
[18:05]  * seb128 looks to the list
[18:05] <seb128> seems a good list
[18:05] <seb128> I trust you and the kubuntu team to be well organized and know what you have to do
[18:06] <seb128> I've no special comment I think, anything you would like to mention or discuss with the team today?
[18:06] <Riddell> as a mostly community project it's hard to pin down deadlines to milestones so I'm unsure if it's useful to mark items for alpha 2 or not
[18:06] <seb128> I would say it's always good to write some goals
[18:06] <seb128> it might help you to focus
[18:06] <seb128> but there is no strong need for it
[18:07] <seb128> you can also reshuffle later if required
[18:07] <seb128> but it's up to you ;-)
[18:07] <Riddell> yes, I'll mark some as being for alpha 2, see if it works or no
[18:07] <seb128> seems good
[18:07] <seb128> anything else?
[18:08] <seb128> Riddell, thanks!
[18:08] <seb128> next
[18:08] <Riddell> just usual reminder that if anyone is working on cross desktop bits to let me know when anything is liable to break
[18:08] <seb128> right, good point
[18:08] <seb128> seems people are taking that into account, I've seen ArneGoetje have specific items to test the kde backend for the language selector changes
[18:08] <Riddell> ooh good
[18:08] <seb128> but we will make sure to let you know about the coming changes
[18:09] <seb128> thanks Riddell ;-)
[18:09] <seb128> next
[18:09] <seb128> rickspencer3, hello
[18:09] <rickspencer3> seb128, still otp
[18:09] <rickspencer3> sorry
[18:09] <seb128> ok
[18:09] <seb128> no problem
[18:09] <seb128> kenvandine is not there but I did review his items with it on the channel earlier
[18:10] <seb128> those who are interested can read the log from 5 hours ago
[18:10]  * kenvandine is actually here now :)
[18:10] <kenvandine> but glad to be done
[18:10] <seb128> ;-)
[18:10] <seb128> seems there is only me left now
[18:10] <seb128> https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-gnome
[18:10] <seb128> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-overriding-defaults-on-upgrade
[18:10] <seb128> I've those on my list
[18:11] <seb128> I didn't take on too many items for this cycle, doing techlead work is going to take some of my time and I want some free slot to handle GNOME changes coming
[18:12] <seb128> well robert will be in charge mostly
[18:12] <seb128> but still there might be need for some extra hands to sort some of the changes
[18:13] <seb128>  
[18:13] <seb128> anybody has a comment about my specs?
[18:13] <seb128> I guess not, let's move on ;-)
[18:13] <seb128> I will catchup with rickspencer3 for his blueprints later on the channel
[18:13] <seb128> and we will have an eastern edition tonight too
[18:14] <seb128> some reminders before we end the meeting though
[18:14] <seb128> - there will be lucid .1 in july
[18:14] <seb128> (10.04.1)
[18:14] <seb128> so keep fixing bugs you think are worth fixing there by doing sru updates
[18:14] <seb128> don't spend too much time trying to fix every single bug though
[18:15] <seb128> the maverick cycle will be short and we have lot to do
[18:15] <seb128> - maverick is open
[18:15] <seb128> lot of merges to do, help from everybody is welcome on those
[18:15] <seb128> - it's review time
[18:15] <seb128> by review I mean performance review
[18:15] <chrisccoulson> does that apply to me too?
[18:15] <seb128> so take some time to do that in the next week
[18:16] <didrocks> chrisccoulson: only for people who began before February, from what I read on the wiki (need checking again)
[18:16] <seb128> "Everyone who joined on or before 01 February 2010 is in scope for this
[18:16] <seb128> review."
[18:16] <seb128> chrisccoulson, when did you start?
[18:16] <seb128> later than that I guess?
[18:17] <seb128> anyway
[18:17] <seb128> that's all from me I think
[18:17] <seb128> rickspencer3, anything to add that I overlooked?
[18:18] <seb128> rickspencer3, I know you are busy, it's just in case
[18:18] <ccheney> i wanted to note that i will be gone the most of next week for a server sprint
[18:18] <seb128> let's say it's a no, we can catch up later if required
[18:18] <seb128> ccheney, ok, good luck
[18:18] <seb128> thanks everybody
[18:18] <ccheney> i will be available via email but probably won't be at keyboard on irc much
[18:19] <kenvandine> thx seb128
[18:19] <didrocks> thanks seb128 and everyone
[18:19] <ArneGoetje> thanks
[18:19] <chrisccoulson> seb128 - i started in march
[18:19] <kenvandine> chrisccoulson, when do you think you'll get conman uploaded to maverick?
[18:19] <seb128> on which note it seems monday is a national holiday there
[18:19] <chrisccoulson> kenvandine, i could do it now
[18:19] <kenvandine> chrisccoulson, it would be appreciated :)
[18:19] <chrisccoulson> it's already uploaded to the lucid PPA
[18:19] <kenvandine> i saw
[18:19] <kenvandine> chrisccoulson, i am doing indicator-network now
[18:20] <kenvandine> will get it into the lucid ppa first
[18:25] <didrocks> going out for some errands, see you guys
[18:25]  * ccheney off to late lunch, bbia 1h
[18:29] <seb128> didrocks, have fun
[18:29]  * seb128 going for dinner
[18:35] <ArneGoetje> seb128: FYI, my WI/week for Lucid was 1.7
[18:37] <Amaranth> nice, using a tmpfs for pbuilder is _fast_
[18:37] <Amaranth> and I'm almost out of RAM :P
[18:37] <Amaranth> oops, ran out
[18:41] <chrisccoulson> hmmm, connman needs an upstart job
[18:41] <chrisccoulson> and it needs porting to polkit-1
[19:22]  * ccheney back
[19:22] <ccheney> brb, have to reboot machine running irc client
[19:25] <ccheney> back
[21:07]  * ccheney found out today his wife might not actually have our son until June 18th, heh
[21:39] <pitti> good night everyone
[23:54] <rickspencer3> hey RAOF, robert_ancell, tremolux
[23:55] <tremolux> howdy!
[23:55] <robert_ancell> rickspencer3, hello
[23:55] <rickspencer3> I guess time to review blueprints in 5 minutes?
[23:55] <rickspencer3> TheMuso,  too
[23:55]  * rickspencer3 feels like we are missing someone
[23:57] <robert_ancell> good timing RAOF_!
[23:57] <TheMuso> Morning folks.
[23:57] <robert_ancell> [8:55] rickspencer3 feels like we are missing someone
[23:57] <RAOF_> Morning all.
[23:58] <tremolux> heya everyone
[23:59] <rickspencer3> I guess we'll start here:
[23:59] <rickspencer3> https://blueprints.edge.launchpad.net/ubuntu/maverick?searchtext=desktop-maverick
[23:59] <rickspencer3> sort by assignee, and go through?
[23:59] <rickspencer3> no bryce :,(