/srv/irclogs.ubuntu.com/2010/05/20/#ubuntu-desktop.txt

desrtrobert_ancell: hey00:20
robert_ancelldesrt, hey00:25
desrtrobert_ancell: still interested in dconf-editor? :)00:25
robert_ancelldesrt, sure00:26
* RAOF returns a non-wardrobe to Freedom while mesa builds00:26
desrtnice00:27
desrtgoing to start making a dconf API for it, then00:27
desrtUI question for you:00:27
robert_ancelldesrt, got step-by-step instructions to getting d-conf to work on Maverick?00:27
robert_ancell:)00:27
desrtrobert_ancell: step 1: wait until seb wakes up00:27
desrtrobert_ancell: step 2: install some .debs :)00:27
robert_ancellnice00:27
desrtin seriousness, though... you could download the glib and dconf releases that i made today00:28
desrtthat's all you need to do00:28
robert_ancellhow is dconf started? on demand?00:28
desrton first write00:28
desrtbut unless you have some really fancy setup going on, that's not going to work out at all00:28
robert_ancelldesrt, you want dconf-editor in the dconf git?00:30
desrtit makes sense i guess00:31
desrthmm.00:31
desrtya.  let's do that.00:31
desrtso my UI question is this:00:32
desrtwhen you go to edit your user settings00:32
desrtshould you also see the defaults?00:32
desrtor -just- the ones that you explicitly setup for yourself00:32
desrtalso: how well-integrated should our GSettings support be?00:32
desrti can imagine two different views: one you navigate by tree and the other that you navigate by schema00:32
robert_ancellI 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 annoying00:33
robert_ancellshow the default *as well*00:33
desrtya.  i specifically ask because of how bad gconf-editor is here00:33
desrtok.  that means that we will need an API to determine this00:33
robert_ancellare the schemas in the same namespace as they were in gconf?00:33
desrtno00:33
desrtschemas are very much out of band00:33
desrtand organised quite differently00:34
robert_ancellwell, then I would consider a "schema view" but I don't think it's a high priority00:34
desrtyou will have to open /usr/share/glib-2.0/schemas/ and parse a bunch of xml00:34
robert_ancellnp00:34
desrti guess another interesting question is if we should show schema values00:35
robert_ancellschema values = default value, limits?00:35
robert_ancellname, description00:35
desrtso there are several layers00:35
desrtas it is, it will be extremely rare for default values to be in dconf00:36
desrtunless you have a sysadmin, essentially00:36
desrtvendor defaults are handled via the schemas00:36
TheMuso8/c00:37
mclasendesrt: you have to parse the schemas anyway, to get at the key docs00:42
Amaranthman, compiz is really hating me00:43
Amaranthwhen I build in pbuilder all the schemas are completely empty files00:43
desrtmclasen: right... not sure if that information ought to be visibile in the tree view or not...00:55
desrtmclasen: since you could go the GSettings view route to get it...00:56
mclasendesrt: in my view, a tree of keys without any documentation is pretty useless00:56
desrti agree00:56
desrtwhich is why i think people should use the schema-based view00:57
desrtie: pick your schema, do your changes00:57
desrtcould almost build it directly on GSettings itself if we add the introspection support you've been asking about :)00:57
robert_ancelldesrt, any idea what package name seb128 was going to use for dconf?  dconf is already used by another package01:10
* TheMuso guesses that gnome-dconf would be used. :p01:14
TheMusoOrca 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.01:15
RAOFWho wants to sponsor a mesa upload?02:04
TheMusoRAOF: how big an upload is it?02:06
RAOF~30MB02:06
RAOFOr big as in changes?02:06
TheMusochanges wise02:06
RAOFIt's a merge from debian, going from 7.7.1 → 7.8.1.  It's pretty big, changes wise.02:07
TheMusoah 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
RAOFgit.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:08
TheMusook sounds fun.02:11
TheMusoDoes the MoM archive have that tarball?02:11
TheMusoRAOF: and since you are building from git, what command do you use to build the package?02:12
RAOFgit-buildpackage02:13
TheMusoRAOF: any particular arguments I need to use?02:13
RAOFOr, rather, git-buildpackage -S02:13
TheMusook thanks02:13
RAOFTheMuso: 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 :)02:54
TheMusoRAOF: 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:00
desrtrobert_ancell: i guess libdconf03:21
TheMusodesrt: ah if its a library only, then that makes sense.03:23
desrtwell03:23
desrtit's not just a library03:23
desrt*shrug*03:23
desrtmaybe i should just rename dconf03:24
TheMusoheh03:24
desrtwhat's in a name?03:24
desrteconf!03:25
desrtcconf!03:25
TheMusoyeah I know.03:26
TheMusoc03:26
RAOFaoeuconf.  I guarantee no one else will have that name!03:27
chrisccoulsonuconf!03:27
RAOFI-conf u-conf we all… conf for i-conf?03:28
chrisccoulsonlol03:28
chrisccoulsonright, bed time for me. i'm meant to be waking up again in 3 hours03:29
TheMusoRAOF: I am building amd64 of mesa, and wow it takes a while, and this is on a quad core 3GHz penryn CPU.03:31
Amaranthgah it takes so long for a pbuilder run03:33
chrisccoulsonAmaranth - dpkg ;)03:34
Amarantheh?03:34
chrisccoulsonit's probably dpkg taking ages to unpack things isn't it?03:34
chrisccoulsonthat's a known issue03:34
Amaranthoh, I suppose so03:34
AmaranthIt takes like 15 minutes to install all the packages before it can start building03:35
AmaranthThen again it is installing 700MB worth of stuff03:35
RAOFTheMuso: May I steal your computer? :)03:35
RAOFYeah, it takes ages, at least in part because it builds everything five different ways.03:36
TheMusoheh lovely03:36
TheMusoRAOF: heh03:36
chrisccoulsonAmaranth, see bug 57080503:36
ubot2Launchpad 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/57080503:36
Amaranthmy penryn is a lousy 2Ghz dual core03:36
RAOFi386 will now be *slightly* faster, because it won't build swrast twice with identical options.03:37
TheMusoThere 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
Amaranthwow ubot2 got rather verbose03:37
chrisccoulsoni need a machine like the one TheMuso has03:37
TheMusoRAOF: right03:37
* TheMuso got this box as an all-rounder back in 2008. Good for audio, video, VMs, compiling, etc.03:38
TheMusoWhen 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
TheMusoinstruction03:38
TheMusoRAOF: 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
RAOFTheMuso: Once mesa has test-built on i386… :)03:41
TheMusoRAOF: heh ok.03:41
AmaranthI wonder if I could convince pbuilder to use libeatmydata for dpkg03:42
RAOFTheMuso: Everything's pushed and ready, if you'd like to try and beat my core2 duo laptop in an i386 build-off :)03:43
TheMusoRAOF: heh ok03:44
TheMusolet me fetch03:44
AmaranthNeed to get 0B/199MB of archives. After unpacking 805MB will be used.03:45
AmaranthI dunno if I've mentioned this before but Compiz depends on _everything_03:45
RAOFThat's a pretty impressive compression ratio03:45
* TheMuso builds mesa for i386.03:45
RAOFBAh.  One final change - UNRELEASED → maverick in changelog.  Won't affect the build, though.03:46
TheMusoright03:48
TheMusoRAOF: 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:55
* 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.03:56
RAOFTheMuso: Probably because those changes weren't there at the time.  I'll incorporate them.04:01
TheMusoRAOF: ah ok04:03
RAOFHm.  How should that get changelogd?04:04
TheMusoRAOF: Good question. You could add them as extra changes for Ubuntu, stating that they are unreleased changes from the Debian git branch04:05
RAOFThat's what I was going to do.  Is that what you do for alsa?04:05
TheMusoNo I don't, but its something I should do differently in the future, now that I've thought about it.04:05
TheMusoIt hasn't bitten me in a bad way as yet, but is tidier.04:06
TheMusosorry, is not as tidy04:06
TheMusoSo for mesa on i386:04:11
TheMusoFinished at 20100520-130904:11
TheMusoBuild needed 00:23:42, 1758288k disc space04:11
AmaranthHow do you get those stats?04:12
RAOFsbuild04:13
RAOFBuild needed 00:45:48, 1950392k disc space04:13
RAOFYour machine appears to be roughly twice as fast as mine for building mesa.  Damn.04:13
Amaranthsbuild apparently lets you make -j504:13
RAOFTheMuso: Changes merged & pushed.  Feel free to use your awesome powers of CPU to test build again, but it *should* be trivially safe.04:15
TheMusoRAOF: ok thanks04:15
RAOFI'm test-building i386 because I'm paranoid; if you want to test-build, amd64 will be useful.04:16
TheMusook great04:17
TheMusoGive the flexibility of sbuild, if the slightly higher learning curve, I've never looked back.04:21
TheMusogiven04:21
AmaranthRAOF: Is there a setup guide for using sbuild this way? The one on the wiki seems to be from hardy04:22
RAOFmk-sbuild, basically.04:22
RAOFFrom ubuntu-dev-tools04:23
RAOFIt does all you want and you don't even need lvm.04:23
Amaranthsbuild maverick chroot building04:33
AmaranthI've _got_ to figure out how to get libeatmydata into these chroots04:40
RAOFMount them on a tmpfs04:40
Amaranth*facepalm*04:40
RAOFQuick, easy fsync :)04:40
AmaranthAlthough I don't think I have enough memory04:40
RAOFIt's a bit easier with sbuild, since you won't need the memory for the base chroot.04:41
Amaranthstill, 800MB of data before I even start building :/04:41
RAOFWell, 1000MB - you also need the .debs :)04:41
Amaranthd'oh04:41
Amaranthright04:42
AmaranthAlso, I don't see a way to tell sbuild to do that04:42
RAOFmount a tmpfs on /var/lib/sbuild/overlay04:42
Amaranthah, nice04:42
TheMusoOk, 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
TheMusoamd64 built fine BTW.04:43
RAOFSweet.  Once that's available xserver + a hojillion drivers is open for business :).04:44
TheMusoRAOF: 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-204:45
TheMusos/-2/-1ubuntu1/04:45
TheMusoSo I wonder whether I am building it incorrectly...04:46
Amaranthooh, cjwatson already fixed the dpkg suckage04:49
* TheMuso tries with a more refined buildpackage command.04:51
RAOFTheMuso: Hm.  I don't see any .gitignore changes in the git diff.  I'll check against my locally built packages.04:51
TheMusook04:51
TheMusoRAOF: do you have perhaps have another git buildpackage config file other than whats in debian/04:52
Amaranthhmm, sbuild doesn't seem to be using /var/lib/sbuild/overlay04:53
Amaranthsbuild -Asd maverick foo.dsc certainly seems to be installing stuff somewhere though04:54
TheMusoschroot puts chroots in /var/lib/schroot/mount04:55
Amaranthyep, that's the spot04:55
RAOFTheMuso: No, you're right.  My build also seems to remove all the .gitignore, but the debian package doesn't.04:55
AmaranthSo I guess I need to make /var/lib/schroot/mount a tmpfs?04:56
TheMusoRAOF: ah right that confirms what I am seeing now, the diff.gz for the Ubuntu version doesn't have .gitattributes or .gitignore04:56
TheMusoRAOF: but thats not all bad.04:56
TheMusoThe package is more lintian clean in that way04:57
TheMusoRAOF: I'm willing to disregard that then04:57
TheMusounless you would rather not...04:57
=== lifeless_ is now known as lifeless
RAOFI'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:58
TheMusook fine by me04:59
AmaranthWeird split05:00
TheMusoRAOF: 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
AmaranthActually whatever sbuild is doing seems unaffected by the fsync stuff05:01
AmaranthIt's chewing CPU processing the unpacking so quickly05:01
TheMusoAmaranth: Interesting. Did you use the script from ubuntu-dev-tools to set it up?05:02
Amaranthyeah05:02
TheMusohrm. I still do mine by hand. I'll have to see what that script does these days.05:02
Amaranthoh, it's aufs+unionfs05:02
Amaranthor wait, just aufs?05:03
RAOFTheMuso: Where - in mesa?  No, the bump for debhelper 7.2.something is for dh_strip --remaining-packages, and that came from Debian.05:03
RAOFJust aufs, unless you switch it to unionfs05:03
TheMusoRAOF: oh right, of course, thanks.05:03
AmaranthI dunno, I don't keep up with filesystem stuff05:03
AmaranthAnyway, it's much faster than pbuilder05:03
TheMusoThat seems icky IMO.05:03
* TheMuso would prefer LVM snapshots.05:04
TheMusos/would prefer/preferrs/05:04
RAOFThat makes it harder to build in a tmpfs, though :)05:04
TheMusoTrue, but easier to manage chroots etc.05:05
* RAOF should really publish his building-on-tmpfs pbuilder benchmarks.05:05
Amaranthoh you're kidding05:05
AmaranthIt doesn't cache build deps?05:05
* TheMuso pats his local mirror.05:08
AmaranthI'm half tempted to just upload this to my PPA to see if it works05:09
TheMusoRAOF: One last question. Is the fix that was uploaded in lucid-proposed for mesa in maverick yet?05:20
RAOFTheMuso: Yes.  That was a cherrypick from upstream, and the new version contains it.05:23
TheMusoRAOF: Ok then, thanks.05:27
TheMusoRAOF: just needed to know in relation to what changelog entries should be included in the changes file.05:27
RAOFJust the last two.05:29
TheMusoyou mean prior to your changelog entry? Yeah thats what I've done.05:33
TheMusoStrike that, I know what you mean, the last two including yours.05:33
TheMusoRAOF: 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
TheMusoah its not so bad, Debian has that too. Kind of a mess, but anyway.05:35
* TheMuso uploads.05:35
RAOFYes.  Thanks!05:37
TheMusonp05:37
* TheMuso is glad he won't be the one cleaning that up.05:37
TheMusoOuch, the diff alone is ~2MB.05:40
TheMuso2.5MB even05:40
TheMusoRAOF: uploaded.05:40
RAOFSweet.  Thanks again.05:44
TheMusonp05:45
RAOFA surprising amount of that diff is ChangeLog, at 7.8MB uncompressed :)05:46
TheMusoYeah I can imagine.05:46
ccheneyis there a list of tags posted somewhere, like all the apport-* related tags?06:10
ccheneyi'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 tags06:10
ccheneyit looks like there are 4 of them06:11
robert_ancellTheMuso, can you sponsor GTK+ (in bzr)06:41
TheMusorobert_ancell: Sure. You got all the X bits you needed through the NEW queue yet?06:45
robert_ancellTheMuso, yup, they were there by this morning (don't know what the delay was in the end)06:45
TheMusorobert_ancell: ok then will take a look.06:46
robert_ancellhey 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/filelist06:49
robert_ancellI'm guessing it's a bug in their build system?06:49
* ccheney likes arsenal, much easier to triage with it :)07:22
TheMusorobert_ancell: I am test building gtk now.07:26
robert_ancellTheMuso, thanks07:27
TheMusorobert_ancell: you have left out all the previous ubuntu changelog entries.07:42
TheMusorobert_ancell: i.e only  your merge changelog is present.07:42
robert_ancellTheMuso, yes, that's the best way to do it - the previous entries aren't relevant anymore07:49
robert_ancellI'm trying to think who said it was ok to do it that way...07:51
TheMusorobert_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:51
robert_ancellTheMuso, what use is that?  The patch headers contain the metadata about the patches and link to the bug reports with this information07:52
TheMusorobert_ancell: Very well, I see thats how it was done previously.07:54
mvoits seems that its slightly different in different teams07:54
TheMusomvo: More than that, its different between package groups, i.e X and GTK/GNOME is different. :)07:55
mvoyeah :)07:55
mvoI 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 changelog07:56
robert_ancellwell, I like to remove them because it makes future merging harder and it's confusing to read the changelog07:56
TheMusofair enough.07:57
robert_ancellespecially when you do a few merges in a row and end up with very large "Ubuntu changes" changelog entries07:57
* TheMuso is building i386 of gtk now. Amd64 was fine but wil wait till this is built and upload.07:57
mvoyep, fair enough from me too07:57
robert_ancellmvo, hey btw :)07:58
mvoI guess its a good afternoon for you :)07:58
mvofunny, I'm still having my wake-up tea (and I'm not yet fully woken up)07:58
TheMusoThe only thing I don't like about this time of year, is that it gets dark too early. :)07:58
TheMusoThe weather on the other hand, is great!07:59
robert_ancellTheMuso, depends on your preferred weather!07:59
robert_ancellhas anyone ever tried solang?07:59
TheMusorobert_ancell: Thats true. I refer to the mid to late autumn Sydney weather, pleasant days, cool nights.07:59
mvoTheMuso: oh, nice. we have really bad weather here, its supposed to be summer, but all we get currently is rain and grey skys08:02
robert_ancellTheMuso, GTK+ sure takes a long time to compile :)  Took me at least 30 mins on my Maverick build box which is unfortunately a netbook08:05
TheMusoDoes indeed.08:05
TheMusorobert_ancell: Yeah took me 29 mins for i386 and 27 mins for amd64.08:06
didrocksgood morning08:06
TheMusorobert_ancell: uploading08:07
TheMusoWow. Gtk is slightly bigger tarball wise than mesa was.08:08
robert_ancelldidrocks, hey08:09
robert_ancelldidrocks, do you know much about gobject introspection?  I noticed you did the GTK+ work.  I'm trying to get PyGI working...08:10
didrocksrobert_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 expected08:12
robert_ancelldidrocks, I've got a package for it but there's nothing in gi.repository.  Was wondering if you had any debugging tips08:13
didrocksrobert_ancell: hum, not really, sorry :/, but gi repository is deprecated, no?08:14
robert_ancelldidrocks, i'm not sure, but I haven't got my head fully around gi yet.  Still seems quite fluid08:14
asaco/08:15
robert_ancello/08:15
didrockshey asac08:15
RAOFTheMuso: And if we built GTK 5 times I'm sure it'd take as long to build, too :)08:15
asachi didrocks, robert_ancell !08:16
didrocksrobert_ancell: I still have on my "TOREAD" stuff the blog posts from yesterday on pygi :)08:16
pittiGood morning08:19
didrocksGuten Morgen pitti, how are you?08:19
TheMusoRAOF: heh08:24
pittibonjour didrocks, I'm great! how are you?08:24
didrockspitti: I'm fine, thanks ;)08:25
mvohm, 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 right08:29
robert_ancelllater all08:42
didrockssee you robert_ancell08:45
seb128ok11:42
seb128versions tracking maverick now11:42
didrocksseb128: cool \o/11:48
vishseb128: hi.. how do i get an upload to lucid-proposed ? [for SRU]12:07
pittivish: 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 bug12:09
* pitti lunch &12:09
vishseb128: pitti: ex: Bug #566996 i think i filled the description appropriately..12:10
ubot2Launchpad 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/56699612:10
pittivish: ah, so KDE doesn't get along with the .png -> .svg symlink hack?12:15
pittiapproved the lucid task12:15
vishpitti: yeah , thanks..12:15
=== cking is now known as cking-afk
seb128vish, I was away for lunch, what pitti said12:30
seb128you just need the upload to go to lucid-proposed in the changelog12:31
seb128with a bug which has the debdiff and has a testcase12:31
vishseb128: oh , ok so the changelog for the lp:~ubuntu-art-pkg/humanity/release branch should mention "lucid-proposed" , on it12:32
vishthanks..12:32
seb128yes12:33
vishseb128: fixed the changelog to lucid-proposed :  lp:~ubuntu-art-pkg/humanity/release , could you upload it to -proposed..12:41
=== cking-afk is now known as cking
seb128vish, I will have a look later when I do some SRU round12:43
vishseb128: neat thanks..12:43
seb128you're welcome, thanks for working on the change!12:43
vishnp..  :)12:43
kenvandineseb128, when does the tracker update?13:04
kenvandineWI tracker that is?13:05
seb128kenvandine, once a day or when pitti kicks an update I think13:07
seb128pitti, ^13:07
kenvandineok13:08
pittiit updates WIs hourly13:08
pittiand team members/milestones daily13:08
seb128pitti, thanks13:08
seb128kenvandine, is that anything you miss there?13:08
kenvandinei fixed something13:10
kenvandineremoved the leading *13:10
kenvandineso now my WI count is a perfect 16 :)13:10
seb128pitti, 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
pittiseb128: bug 580961?13:12
ubot2Launchpad 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/58096113:12
seb128pitti, yes, it seems to be high on the user annoyance list looking at duplicates13:12
seb128pitti, and since you are not going to work on it I'm trying to figure where to bounce it13:13
pittiI haven't looked at it at all yet13:13
seb128well you shouldn't ;-)13:13
pittiI never actually touched that patch, so I'm afraid I know nothing more than anyone else13:13
seb128ok, good, thanks13:14
pittibut oh well, we don't even support non-UTF8 file names, locales, etc.13:14
seb128I will add it on my list of things to look at13:14
pittiso I don't consider it a major issue TBH13:14
pittimerci13:14
pittiand this is not the kind of change that I like us to carry permanently13:15
seb128it has quite some duplicate, I would like to have that sorted still ;-)13:15
seb128you're welcome13:15
pittithat patch is ancient, and if it never made it upstream, there's something fishy13:15
pittidoko originally applied it, but apparently got the idea wrong what it actually does13:16
pittibut this was in feisty, so he might not remember the details any more13:16
seb128I will try to understand what is going on and talk to doko about it a bit later13:17
seb128thanks!13:17
* pitti hugs seb12813:17
* seb128 hugs pitti13:18
kenvandineseb128, got a few to review my blueprints?13:18
seb128kenvandine, yes, did the track picked your updates yet?13:18
kenvandineprobably not, but it is obvious13:20
kenvandinebasically my number is 16, not 2213:20
kenvandinethe ones with [segphault] were getting counted for me13:20
seb128ok13:20
seb128so let's review those13:20
seb128you have 3 specs right?13:20
kenvandineyeah13:21
seb128desktop-maverick-empathy-indicator13:21
seb128desktop-maverick-gwibber-test-suite13:21
seb128desktop-maverick-social-api13:21
seb128+ some items on dx specs13:21
seb128http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team.html says you have 49 items for the cycle13:21
pitti?!13:22
seb128what was item per week count?13:22
pittitwo hours ago it was 413:22
kenvandinemy target is 16 for a213:22
seb128pitti, ? I'm talking to kenvandine13:22
pittiseb128: I can do one per week13:22
pittiseb128: argh, sorry; got the hightlight due to the /~pitti/13:22
seb128pitti, sorry seems there is some confusion13:22
kenvandinehehe13:22
seb128pitti, kenvandine can't make it to the meeting today, we are review his items13:22
seb128reviewing13:23
* seb128 hugs pitti13:23
kenvandineweekly target is 313:23
kenvandineso actually my a2 target is 1813:23
seb128ok13:23
kenvandinei have 16 so far for my specs13:23
seb128so let's start with13:23
seb128http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-1.html13:23
kenvandinewhich only gives me room for 2 more :)13:23
* pitti should have put them into a role account13:23
kenvandineonly other item i know about is indicator-network plus my usually package wrangling13:23
seb128ok13:24
seb128alpha1 has the indicator-appmenu items13:24
desrtseb128, pitti, kenvandine; good morning13:24
seb128do you know if that's on track to land in the next 2 weeks?13:24
seb128desrt, hey13:24
pittihey desrt, how are you?13:24
desrtpretty decent13:24
kenvandineyes13:24
kenvandineseb128, those should be thursday13:24
kenvandinenext week13:24
seb128ok, good13:24
seb128so alpha1 on track13:24
seb128looking to http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html now13:25
desrtseb128: there are some new packages :)13:25
seb128desrt, no time for dconf this week sorry ;-)13:25
kenvandineyay tracker refreshed13:25
desrtit's fine :p13:25
seb128but maybe robert_ancell will pick it up, he did the glib 2.25 update13:25
desrtwas wondering if maybe we can get the 'dconf' package dropped from universe though13:25
desrtotherwise i will be forced to rename it to seb128conf13:26
seb128I doubt it13:26
seb128namespace clash suck13:26
kenvandinehehe13:26
* desrt installed epiphany-game during the default browser selection session >:(13:26
chrisccoulsoni've done that before too ;)13:27
kenvandineseb128, 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 out13:27
kenvandinebut it should be doable13:27
desrtchrisccoulson: i think every living being has done that at some point13:27
kenvandine2 of the a2 WIs are almost done already13:27
seb128kenvandine, right, I'm reviewing your a2 items right now, seems good13:27
kenvandineactually 313:27
seb128desrt, yeah...13:27
desrtok13:28
desrtseb128conf it is13:28
seb128kenvandine, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-empathy-indicator do we still need an empathy change or the preference?13:28
desrti will let the gnome admins know to rename the module in git and bugzilla13:28
desrt:)13:28
seb128desrt, lol13:28
kenvandineseb128, yeah, small one13:28
kenvandineto enable or disable use of the indicator13:28
kenvandinewe'll read the pref from gconf13:28
kenvandinei don't want any UI in the service13:28
seb128I'm wondering if we need an UI13:29
kenvandineand empathy will need to know if it needs to use the StatusIcon or not13:29
seb128the service will be a new binary?13:29
kenvandineyes13:29
seb128can't we just be smart about it depending on whether the service is installed or not13:29
seb128and maybe have a gconf key for tweaking but without ui13:29
kenvandinewe could... but makes it a little harder for users to go back and forth13:29
kenvandineeither way requires a patch to empathy13:30
seb128ok, fair enough13:30
kenvandineso empathy doesn't use the status icon13:30
kenvandinetrying to keep it simple13:30
kenvandinewe already have the UI patch in place and is tiny13:30
seb128right13:31
ArneGoetjeseb128: 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-changes13:32
seb128your list seems good, you have quite some items but tasks are reasonable amount of work and it seems doable13:32
kenvandinegood :)13:32
seb128kenvandine, who is in charge or porting the indicator to libgwibber, dx or you?13:32
kenvandineme13:33
seb128kenvandine, you seem to have no work items for those tasks?13:33
kenvandinewell the indicator won't be in libgwibber13:33
kenvandinethat won't change actually13:33
kenvandinethat is driven by gwibber-service13:33
seb128ok, so indicator change required?13:33
kenvandineno13:34
seb128ArneGoetje, done13:34
seb128ArneGoetje, it needed the serie goal to be accepted13:34
kenvandinelibgwibber is just for other apps besides gwibber13:34
seb128ArneGoetje, should be there on next refresh13:34
seb128kenvandine, ok, good13:34
ArneGoetjeseb128: ok, thanks13:34
seb128kenvandine, is there any item for the indicator-clock packaging somewhere?13:35
kenvandinethat packaging is done13:35
seb128I guess it will need to get uploaded and promoted this cycle13:35
kenvandinethe only thing needed would be to drop the existing one13:35
kenvandinejust needs to land in main13:35
seb128should we track that?13:36
kenvandinedidrocks might already be13:36
kenvandinesince that is already in UNE13:36
kenvandineif not it would be good to track it13:36
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/dx-m-indicator-clock13:36
didrockskenvandine: I guess there is a dx spec for it13:36
didrocksok, seb128 found it :)13:36
seb128didrocks, kenvandine: ^ can you coordinate to get 2 items there13:36
seb128one for getting it uploaded13:37
seb128one mir13:37
seb128decide between you who takes the actions13:37
didrocksI was thinking all indicators stuff was on kenvandine, hence the fact I didn't check13:37
seb128it should not be lot of work anyway ;-)13:37
seb128kenvandine, can you get it in universe?13:38
seb128didrocks, can you get the mir done and une to pull it in?13:38
kenvandinei can13:38
seb128thanks13:38
seb128kenvandine, ok, you are on track for your specs it seems, thanks for the review13:38
kenvandinethank you13:38
seb128good luck for getting all that done now ;-)13:38
kenvandinehehe13:39
seb128desrt, so dconf, we don't have good way to handle renames13:41
desrt*ahem* drop? :)13:41
seb128users who have current dconf installed would receive something different on upgrade replacing what they use13:41
desrti guess the upgrade question is pretty pointless when the new package is default-installed13:41
seb128we would need to convince debian too since it comes from there13:41
kenvandineseb128, can you sponsor lp:~ubuntu-desktop/indicator-application/ubuntu13:42
kenvandineto lucid-proposed?13:42
seb128kenvandine, will do, thanks to ted and you for working on it13:42
kenvandineit got rejected for me13:42
pittiseb128: I don't understand? wouldn't it be enough to have the new packages conflicts/replaces: dconf?13:42
seb128pitti, which new packages?13:42
kenvandineand subscribe ubuntu-sru to bug 56927313:43
ubot2Launchpad bug 569273 in indicator-application (Ubuntu) "memory leak in gnome-power-manager on lucid (affects: 11) (heat: 50)" [Medium,New] https://launchpad.net/bugs/56927313:43
seb128pitti, there is a dconf already which is something else13:43
* kenvandine needs to head out now... be back in a few hours13:43
pittiseb128: aah, right; this is not _that_ dconf, sorry13:43
seb128kenvandine, I will let you handle the bug subscribing etc side13:43
seb128pitti, yeah, confusing...13:43
pittiseb128: the binary might be libdconf1 and libdconf-bin?13:44
seb128they might, I didn't look at it yet13:44
didrocksseb128: I've added that to the WI "MIR for UNE components"13:44
seb128didrocks, thanks13:44
kenvandineok13:45
seb128desrt, how are the applications ported to gsettings working right now without dconf?13:45
desrtthey use a backend inside of glib that stores the settings in a GHashTable local to the program13:46
seb128it means you loose your config when you close the software?13:46
desrtyes13:46
seb128ok, we don't want to package 2.31 yet :p13:46
desrtjust package dconf first :p13:47
seb128yeah, will try to get that done next week13:47
desrti guess dconf should be Recommends: of libglib13:47
seb128right13:47
seb128slomo, hey13:47
seb128slomo, will you work on packaging dconf for debian?13:48
slomoseb128: probably not, too busy with other stuff13:48
slomoseb128: same goes for gtk3 :(13:49
seb128ok13:49
seb128you started on glib 2.25 so I was wondering13:49
seb128thanks13:49
pittiseb128: you could upload it to debian as well?13:49
seb128pitti, right, I was just checking before we start and duplicate work13:50
seb128I will get it in debian13:50
seb128though I guess Debian will not do anything with it in the next month13:50
seb128they will freeze soon13:50
pittithey probably won't mind having it in experimental13:51
seb128right, I will get it there13:51
desrtseb128: yes.13:53
desrter.  ignore me.13:53
ccheneygood morning14:01
seb128hey tedg, rickspencer314:24
seb128tedg, rickspencer3: slightly going back on your local timezones it seems? ;-)14:25
rickspencer3hi seb12814:26
rickspencer3yes, I went to bed and woke up at normal times for the first time since back!14:26
tedgseb128, Trying ;)14:26
rickspencer3I am very happy14:26
pittihey rickspencer314:28
rickspencer3hi pitti14:29
seb128pitti, do you plan do your merges during your distro time or should we try to take over those?14:29
pittiseb128: I did a few, but I might not get to all of them14:29
seb128I guess we can ask tremolux to help on those14:29
seb128would be some good training for distro work14:29
rickspencer3seb128, is there an invite for the bp review meeting?14:29
rickspencer3does everyone know when it is?14:30
* tremolux waves14:30
pittirickspencer3: I got one14:30
seb128rickspencer3, I sent a reminder this morning, let me know if that didn't work14:30
seb128rickspencer3, I use the launchpad "contact team members"14:30
seb128hey tremolux14:30
seb128hey ccheney too14:30
tremoluxseb128: hiya seb12814:30
ccheneyseb128: hi14:31
* tremolux reaches out for seb128 but catches only air14:46
DASPRiDtremolux, so you got him?14:46
DASPRiD:)14:46
tremoluxDASPRiD: haha14:47
rickspencer3seb128, fyi ... I'm going to take a swap day tomorrow15:23
seb128rickspencer3, ok, enjoy it!15:24
seb128rickspencer3, will you drive the eastern edition for specs btw?15:24
seb128specs -> workitems15:24
rickspencer3seb128, yeah15:24
rickspencer3I'll do my best15:24
rickspencer3maybe tomorrow you can check them over, though15:24
seb128will do15:26
seb128at what time is the eastern edition?15:26
seb128rickspencer3, is desktop-maverick-desktop-application-selection worth tracking or are the only plan of record tracked by other specs?15:29
seb128ie shotwell by default15:30
seb128gobby has some notes about getting new screensavers, etc15:30
seb128tremolux, don't forget to define your work items for the meeting in 1h5815:31
seb128tremolux, desktop-maverick-software-center-front-end still has none15:31
seb128TheMuso, should desktop-maverick-gnome3-accessibility-readiness be tracked for maverick or not? it has no work items but is on the maverick serie15:32
rickspencer3seb128, I think not15:32
rickspencer3same with the UNE one15:33
tremoluxseb128: yep, actually, I apologize but didn't know about https://wiki.ubuntu.com/DesktopTeam/10.10/WorkItemProcess until this morning15:33
seb128rickspencer3, ok, should I mark it informational?15:33
tremoluxseb128: I'm working right now with mvo to coordinate our work items15:33
seb128tremolux, oh ok, thanks, you didn't get the "Blueprints and Work Items" email 3 days ago from rick?15:34
tremoluxseb128: nope  :(15:34
seb128tremolux, you should be in the team and it has been sent to team member on launchpad15:34
tremoluxI think I was added this week15:34
seb128tremolux, do you have a launchpad filter which could have sent that in your flood or bug emails?15:34
seb128tremolux, you were added 6 days ago according to my emails15:35
tremoluxseb128: hrm15:35
seb128tremolux, you should have received it...did you get the one I sent today about the meeting reminder?15:35
tremoluxseb128: yep, I did get the reminder, which is when I found out about it15:36
seb128tremolux, ok, let's assume things are working now15:36
seb128tremolux, thanks for working on getting the list done, don't worry if you are a bit late that's not an issue15:36
tremoluxseb128: thanks seb128, sorry about that!15:37
seb128no worry!15:37
seb128pitti, could you kick a workitems update in 1.5hours?15:37
seb128pitti, I would like to have an updated summary for the meeting15:37
pittiseb128: in 1.5 hours it'll trigger automatically anyway15:37
pittiit's :05 past the hour15:38
rickspencer3I love seeing seb128 cracking the whip15:38
seb128rickspencer3, ;-)15:38
pittiyeah, he learned that quickly :)15:38
* pitti hugs seb12815:38
seb128lol15:38
* rickspencer3 leans back on marble couch while getting fed grapes15:38
* seb128 hugs pitti15:38
pittirickspencer3: sounds ... stressful :)15:38
seb128lol15:38
rickspencer3you guys make my job so hard15:38
* tremolux is mumbling with mvo..15:41
seb128mvo, do you think there is an actual lp team on launchpad you could use rather than "lp team" in your specs?15:49
seb128mvo, or pick somebody on the launchpad side15:49
mvoseb128: soyuz is the one that I can think of that is closest15:51
seb128mvo, I guess the soyuz team doesn't do workitems charts anyway so there is no real point to match their team there...15:52
seb128mvo, is somebody in charge of checking that things are being done on the server side?15:52
rickspencer3seb128, mvo can we not just assign work items to bigjools on the white board?15:52
mvooh, that is a good idea, we can just use his name instead of the team15:53
mvoseb128: its there to show that its a dependency for some of our functionality15:53
seb128or to whoever on the distro side is tracking those changes15:54
seb128soon mvo will have half of ubuntu workitems assigned to him ;-)15:54
* seb128 hugs mvo15:54
* DASPRiD pets seb128 16:02
rickspencer3tremolux, I'm not seeing the bug report for that weird PPA issue we saw yesterday16:07
Amaranthhmm, I think I might need to get some help from the KDE guys on this compiz packaging issue16:11
Amaranthcompiz 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 sbuild16:13
tremoluxrickspencer3: yep, still need to write it, unfortunately, looks like that ppa (ppa:nisshh/ppa) has been deleted?16:16
rickspencer3hmm16:17
rickspencer3weird16:17
rickspencer3tremolux, I'll ask nisshh what's up16:17
tremoluxrickspencer3: k, thanks16:17
seb128hey there17:29
seb128meeting in 1 minute17:29
ccheneyhere17:30
ArneGoetjeo/17:30
seb128ArneGoetje, ccheney, didrocks, chrisccoulson, Riddell, rickspencer3: hey17:30
seb128did I forget anybody?17:31
chrisccoulsonhey17:31
seb128pitti, not sure if you join17:31
pittiI'll lurk17:31
didrockso/17:31
* chrisccoulson waves at pitti17:31
pittihey chrisccoulson17:31
seb128hey everybody17:31
Riddellhi17:31
seb128I hope everybody travelled back safely17:31
seb128and got over jetlag without ubufly17:32
seb128ubuflu17:32
pittion that front it was surprisingly quiet indeed17:32
chrisccoulsonis ubufly a new airline? ;)17:32
pittiseems we finally exchanged enough germs around the world :)17:32
seb128lol17:32
seb128pitti, it seems lool and dholbach got it17:33
ccheneyi was surprised i didn't get sick this time17:33
seb128not sure about other people17:33
seb128so let's get started17:33
chrisccoulsoni didn't get sick either17:33
seb128everybody did some good work on registering blueprints and workitems, so thanks!17:33
seb128pitti, 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
pittiplease :)17:34
seb128I guess you can manage those 4 items during the cycle during your 20% distro time?17:34
pittiabsolutely17:34
pittithe two vfat-noexec ones are by and large done17:34
pittijust waiting for an ack from davidz17:34
pitti"Add apport.hookutils.add_video_info" sounds easy17:35
pittiand I don't know about the gpu hang detection17:35
seb128ok, matches what I though too17:35
pittiI'll talk to RAOF17:35
seb128I don't see any special issue or anything to discuss17:35
seb128thanks pitti ;-)17:36
pittithat was quick :)17:36
seb128indeed!17:36
* pitti hugs seb128 for organizing everything so well17:36
* seb128 hugs pitti17:36
seb128hope your enjoy your rotation ;-)17:36
seb128ok, let's keep going17:36
seb128ArneGoetje, hey17:36
ArneGoetjeseb128: hi17:36
seb128ArneGoetje, so you have 2 specs about language selector17:36
ArneGoetjeseb128: yup17:37
seb128https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector17:37
seb128https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-language-selector-code-changes17:37
seb128ArneGoetje, did you calculate your workitem number by week for previous cycle?17:37
ArneGoetjeseb128: those 2 are not related, that's why I separated them17:37
seb128ArneGoetje, how much was it? what does it give you for a2?17:37
ArneGoetjeseb128: I didn't calculate that, but I'll try to get as many done as possible for a217:38
seb128the idea was to use that as a metric to know how much you can aim at for a217:38
seb128could 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
seb128https://wiki.ubuntu.com/DesktopTeam/10.10/WorkItemProcess17:39
seb128ArneGoetje, ^17:39
ArneGoetjeseb128: las cycle I had lots of extra stuff to do, so I figured the 11 items I have now are feasable17:39
seb128ok, still do it for the record if you can17:40
seb128so no alpha1 items so far17:40
seb128and only one for alpha217:40
seb128is that correct?17:40
ArneGoetjeseb128: sure... just need to go digging for the old blueprints again17:40
seb128just use the lucid team summary17:40
seb128you have the count there17:41
seb128by people17:41
seb128divide by the number of weeks17:41
seb128so let's go back to maverick17:41
seb128ArneGoetje, you should probably target some extra items for alpha-217:41
ArneGoetjeseb128: yes, I hope I can get the design mockups next week so that I can start right away17:41
seb128you have only one according to http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html17:41
ArneGoetjeseb128: depends on how fast I can get the design mockups17:42
seb128who is working on the design?17:42
ArneGoetjemichael forrest. I have contacted him already17:43
seb128ok good17:43
seb128do you have other things to work on until you get the design?17:43
seb128or other non-spec work for this cycle?17:43
ArneGoetjeregarding the code changes I'll have a mini sprint with mvo next week, so that'l get me started too17:43
seb128ok good17:44
seb128your list of work items seem reasonable otherwise17:44
seb128if you are blocked to get going on that maybe review lucid bugs on language selector and look if there is some sru required there17:44
ArneGoetjeI'm currently reading documentation about dbus and aptdeamon, and keep looking at bug reports which came in in the meantime.17:44
seb128or try helping on merges for maverick if you think you can do some17:44
seb128ok, seems good17:45
seb128ArneGoetje, also is ubiquity using language selector for langpacks handling?17:45
ArneGoetjeseb128: yes, should be17:45
seb128just checking if that should be something to take in account when you do the changes17:45
seb128you have no work item about that17:45
seb128could you add one about making sure ubiquity gets updated if required?17:45
seb128or at least tested17:45
ArneGoetjenot 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
seb128ok, good17:46
seb128thanks ArneGoetje17:46
seb128good luck for the sprint ;-)17:46
ArneGoetjethanks17:46
seb128ccheney, hi17:47
ccheneyseb128, hi17:47
seb128ccheney, do you still have some desktop team time this cycle or are you helping the server time full time now?17:47
ccheneyseb128, yes 20%17:47
seb128do you have any spec for those 20%?17:48
seb128or just regular openoffice updates and cleaning?17:48
ccheneyseb128, https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-openoffice17:48
seb128oh, it has no serie goal17:48
* seb128 fixes that17:48
ccheneyseb128, cleaning/updating OOo and working with dx team on paper cuts/menu integration17:48
ccheneyah sorry about that, forgot to tag it17:49
seb128ccheney, no worry, I've done it17:49
seb128the list of workitems there seems reasonable for a 20% time17:49
seb128ccheney, thanks17:49
ccheneyok17:50
seb128chrisccoulson, hi17:50
chrisccoulsonhi seb12817:50
seb128chrisccoulson, did you calculate your workitems by week count?17:50
seb128not sure if you have been in the team long enough in lucid to do that though17:50
seb128you pretty much worked on getting on speed with firefox I guess17:51
rickspencer3chrisccoulson, work item/week count = infinity + 117:51
chrisccoulsonyeah, i don't really have any historical data to do that yet17:51
rickspencer3;)17:51
seb128lol17:51
seb128https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-chromium17:51
chrisccoulsonlol17:51
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-user-accounts-dialog17:51
seb128I see those specs on your list17:51
seb128somewhat it seems to low I must be missing something? ;-)17:51
chrisccoulsonyeah, there is also https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-mozilla-team-discussion, which doesn't have a series goal just yet17:52
seb128joke aside, you are quite busy with browser and n-m maintainship I guess17:52
chrisccoulsonbut most of the WI's on there are not mine ;)17:52
seb128should I set it now?17:52
seb128the serie goal17:52
chrisccoulsonyes please :)17:52
chrisccoulsonyeah, i'm generally quite busy with browser maintenance atm ;)17:52
seb128ok, serie goal accepted17:53
chrisccoulsonthanks17:53
seb128so I guess your priority for now is to sort up quickly chromium and if it's doable for UNE this cycle17:53
chrisccoulsonyeah, i can do that17:53
seb128should you have some alpha-1 or alpha-2 items about that?17:53
seb128the technicals packaging changes can wait a bit17:54
seb128but we should try to sort early what we need17:54
seb128and if upstream is wanting to help getting there this cycle17:54
chrisccoulsonyeah. so, i think the big things are security updates and translations aren't they?17:55
seb128yes17:55
seb128+ sorting what users issues we will need to get sorted17:55
seb128ie dx indicator-menu integration17:56
seb128csd17:56
seb128somebody mentioned during the session also that printing was quite broken17:56
seb128could you try to coordinate with bratsche_ maybe to talk to upstream about the menu and csd17:56
chrisccoulsonyeah, no problem17:57
seb128+ try to get the security updates discussion going and see what we can do for translations?17:57
seb128thanks17:57
seb128otherwise your useraccount spec seems reasonable17:57
seb128chrisccoulson, anything else to add?17:57
chrisccoulsoni don't think i've got anything else to add17:58
seb128ok, seems you are in shape and going to be busy again this cycle17:58
seb128thanks chrisccoulson ;-)17:58
seb128dunno what we would do without you17:58
seb128don't forget to sleep and don't overwork yourself too much ;-)17:58
seb128next17:58
seb128didrocks, hey17:59
didrocksyes o/17:59
didrocksmy magical number is 5 WI a week17:59
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-une-app-selection17:59
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-quickly17:59
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-oneconf17:59
seb128didrocks, nice, somebody who reply before being asked, thanks ;-)17:59
didrocksy/w :-)17:59
seb128you have those on your list for now17:59
seb128is there any spec missing or not listed yet?18:00
didrocksno, I've gathered some part of other specs on thoses18:00
seb128you will be busy maintaining UNE too18:00
didrocksI guess… ^^18:00
Riddellis UNE going to be the old UNE or Unity?18:00
seb128unity18:00
seb128didrocks, your list seems quite detailed and in shape18:01
seb128you have a lot of alpha-2 items18:01
didrocksseb128: yeah, I think some WI are quite small, but it's more like a TODO reminder :)18:02
seb128right18:02
seb128it seems doable if you don't get too much sidetracked if maintaining other things18:02
seb128or doing merges and updates18:02
didrocksright, I've worked on the last two days to be able to close 3/4 WI :)18:02
seb128let me know if you feel you need to reschedule some items during the next weeks18:02
didrocksso, I think it's doable18:02
seb128seems you are up for a busy cycle too but should manage18:03
* seb128 hugs didrocks18:03
didrockssome WI can be postponed to alpha3 if it's short18:03
* didrocks hugs seb12818:03
seb128keep rocking ;-)18:03
didrocksthanks :-)18:03
seb128right, it seems you targetted almost all your items for alpha-218:03
seb128we can probably delay some quickly one to alpha-3 if required18:03
didrockssure18:04
seb128didrocks, thanks18:04
seb128Riddell, hey18:04
didrocksthanks to you for the review :)18:04
seb128Riddell, not sure if you want to do a kubuntu summary for us there18:04
Riddellhi seb12818:04
seb128or if you have something ready18:04
Riddellwe have lots of specs and todo items listed at https://wiki.kubuntu.org/Kubuntu/Todo18:04
seb128indeed18:05
* seb128 looks to the list18:05
seb128seems a good list18:05
seb128I trust you and the kubuntu team to be well organized and know what you have to do18:05
seb128I've no special comment I think, anything you would like to mention or discuss with the team today?18:06
Riddellas 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 not18:06
seb128I would say it's always good to write some goals18:06
seb128it might help you to focus18:06
seb128but there is no strong need for it18:06
seb128you can also reshuffle later if required18:07
seb128but it's up to you ;-)18:07
Riddellyes, I'll mark some as being for alpha 2, see if it works or no18:07
seb128seems good18:07
seb128anything else?18:07
seb128Riddell, thanks!18:08
seb128next18:08
Riddelljust usual reminder that if anyone is working on cross desktop bits to let me know when anything is liable to break18:08
seb128right, good point18:08
seb128seems people are taking that into account, I've seen ArneGoetje have specific items to test the kde backend for the language selector changes18:08
Riddellooh good18:08
seb128but we will make sure to let you know about the coming changes18:08
seb128thanks Riddell ;-)18:09
seb128next18:09
seb128rickspencer3, hello18:09
rickspencer3seb128, still otp18:09
rickspencer3sorry18:09
seb128ok18:09
seb128no problem18:09
seb128kenvandine is not there but I did review his items with it on the channel earlier18:09
seb128those who are interested can read the log from 5 hours ago18:10
* kenvandine is actually here now :)18:10
kenvandinebut glad to be done18:10
seb128;-)18:10
seb128seems there is only me left now18:10
seb128https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-gnome18:10
seb128https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-overriding-defaults-on-upgrade18:10
seb128I've those on my list18:10
seb128I 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 coming18:11
seb128well robert will be in charge mostly18:12
seb128but still there might be need for some extra hands to sort some of the changes18:12
seb128 18:13
seb128anybody has a comment about my specs?18:13
seb128I guess not, let's move on ;-)18:13
seb128I will catchup with rickspencer3 for his blueprints later on the channel18:13
seb128and we will have an eastern edition tonight too18:13
seb128some reminders before we end the meeting though18:14
seb128- there will be lucid .1 in july18:14
seb128(10.04.1)18:14
seb128so keep fixing bugs you think are worth fixing there by doing sru updates18:14
seb128don't spend too much time trying to fix every single bug though18:14
=== oubiwann_ is now known as oubiwann
seb128the maverick cycle will be short and we have lot to do18:15
seb128- maverick is open18:15
seb128lot of merges to do, help from everybody is welcome on those18:15
seb128- it's review time18:15
seb128by review I mean performance review18:15
chrisccoulsondoes that apply to me too?18:15
seb128so take some time to do that in the next week18:15
didrockschrisccoulson: 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 this18:16
seb128review."18:16
seb128chrisccoulson, when did you start?18:16
seb128later than that I guess?18:16
seb128anyway18:17
seb128that's all from me I think18:17
seb128rickspencer3, anything to add that I overlooked?18:17
seb128rickspencer3, I know you are busy, it's just in case18:18
ccheneyi wanted to note that i will be gone the most of next week for a server sprint18:18
seb128let's say it's a no, we can catch up later if required18:18
seb128ccheney, ok, good luck18:18
seb128thanks everybody18:18
ccheneyi will be available via email but probably won't be at keyboard on irc much18:18
kenvandinethx seb12818:19
didrocksthanks seb128 and everyone18:19
ArneGoetjethanks18:19
chrisccoulsonseb128 - i started in march18:19
kenvandinechrisccoulson, when do you think you'll get conman uploaded to maverick?18:19
seb128on which note it seems monday is a national holiday there18:19
chrisccoulsonkenvandine, i could do it now18:19
kenvandinechrisccoulson, it would be appreciated :)18:19
chrisccoulsonit's already uploaded to the lucid PPA18:19
kenvandinei saw18:19
kenvandinechrisccoulson, i am doing indicator-network now18:19
kenvandinewill get it into the lucid ppa first18:20
didrocksgoing out for some errands, see you guys18:25
* ccheney off to late lunch, bbia 1h18:25
seb128didrocks, have fun18:29
* seb128 going for dinner18:29
ArneGoetjeseb128: FYI, my WI/week for Lucid was 1.718:35
Amaranthnice, using a tmpfs for pbuilder is _fast_18:37
Amaranthand I'm almost out of RAM :P18:37
Amaranthoops, ran out18:37
chrisccoulsonhmmm, connman needs an upstart job18:41
chrisccoulsonand it needs porting to polkit-118:41
* ccheney back19:22
ccheneybrb, have to reboot machine running irc client19:22
ccheneyback19:25
* ccheney found out today his wife might not actually have our son until June 18th, heh21:07
pittigood night everyone21:39
=== onestone_ is now known as onestone
rickspencer3hey RAOF, robert_ancell, tremolux23:54
tremoluxhowdy!23:55
robert_ancellrickspencer3, hello23:55
rickspencer3I guess time to review blueprints in 5 minutes?23:55
rickspencer3TheMuso,  too23:55
* rickspencer3 feels like we are missing someone23:55
robert_ancellgood timing RAOF_!23:57
TheMusoMorning folks.23:57
robert_ancell[8:55] rickspencer3 feels like we are missing someone23:57
RAOF_Morning all.23:57
tremoluxheya everyone23:58
rickspencer3I guess we'll start here:23:59
rickspencer3https://blueprints.edge.launchpad.net/ubuntu/maverick?searchtext=desktop-maverick23:59
rickspencer3sort by assignee, and go through?23:59
rickspencer3no bryce :,(23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!