/srv/irclogs.ubuntu.com/2010/11/03/#ubuntu-meeting.txt

=== ian_brasil___ is now known as ian_brasil
=== evilnhandler is now known as nhandler
=== MosquitoOo is now known as MaWaLe
=== ivanka is now known as ivanka-train
=== MosquitoOo is now known as MaWaLe
=== bilalakhtar_ is now known as bilalakhtar
=== ian_brasil__ is now known as ian_brasil
=== JanC_ is now known as JanC
mvohi14:59
mvosorry robbiew for missing the mumble call, this week we changed from daytime-saving back so I thought it was 1h later14:59
robbiewmvo: no worries...you're fired15:00
robbiew:P15:00
mvo*arrr*15:00
cjwatsonmvo: like anyone else was in it anyway. :)15:02
mvoall fired!15:02
barrymumble fail15:03
robbiew#startmeeting15:03
MootBotMeeting started at 10:03. The chair is robbiew.15:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:03
robbiew#endmeeting15:04
MootBotMeeting finished at 10:04.15:04
robbiew:)15:04
evlol15:04
barrybest meeting EVAR15:04
robbiew\o/15:04
mvolol15:04
robbiewmvo: on mumble, if you want to join15:04
* cjwatson quotefiles15:06
=== jacob_ is now known as jacob
=== dholbach_ is now known as dholbach
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
highvoltageEdubuntu meeting going to start around 5 minutes late  (sorry)19:00
* stgraber waves19:03
stgraberhey sbalneav19:03
highvoltagehey it's sbalneav!19:03
sbalneavpresent.19:04
highvoltageI added most of the items from UDS to our roadmap page: https://wiki.ubuntu.com/Edubuntu/Devel/RoadMap19:04
highvoltageit includes some important dates, milestones and the work items for those milestones19:05
highvoltageit will probably expand a bit over the next few weeks and the milestone items will probably even out at least a bit19:05
highvoltageedubuntu-council members are expiring end of 2010, so we'll need to contact the CC for the EC elections/re-elections/re-confirmation/(whatever-it-will-be)19:07
highvoltagehttps://launchpad.net/~edubuntu-council/+members#active19:07
* stgraber is getting something to drink. Speaking for 2 hours in a very warm conference room really kills you.19:08
highvoltageI just did that too :)19:09
highvoltageI sent an e-mail out to the current EC, just so that we'll know who still wants to be on it for when we email the CC19:10
mgariepyhello19:11
highvoltageideally we'd want as many people to stay on it as possible19:11
highvoltagehowdy marc19:11
highvoltagenixternal: are you around?19:12
stgraberhey lak19:13
stgraberalkisg19:13
alkisgHi all19:13
stgraber(autocomplete mistake ;))19:13
highvoltageI didn't get any answer from that email yet, if I don't by tomorrow I'll just start poking everyone with a very, very sharp stick19:14
sbalneavOwing to my personal life, my involvement for the last 6 months was sucktastic.  I'd be more than happy to stay on, as I *DO* want to get back into the swing of things (my lack of participation wasn't due to lack of interest on my part).  That having been said, if someone else wanted my spot, I'd be more than happy to surrender my spot to free up space for someone else.  I'm planning on being in for the long haul, and I don't 19:14
highvoltagesbalneav: IRC cut you off after "and I don't..."19:15
highvoltagesbalneav: but I think the gist of it is there, and I can't speak for everyone but I for one am glad to have you onboard there and I think everyone else is too!19:15
sbalneavneed official titles to keep me interested :)19:16
highvoltage:)19:16
highvoltagewe can even make up a few if you want?19:17
sbalneavCheif cook and bottle washer seems to be the one that suits me most in my life :)19:17
highvoltageI was thinking more in terms of something that includes beer and pizza in the title, but we need that position filled as well, so why not :)19:18
stgraberhehe19:18
highvoltagewe didn't have much planned for this meeting, it's our first one after UDS though19:19
stgraberanyway, based on the list of members in edubuntu-members on LP and the current EC members, I don't think it's going to change much. We just want to know who still wants to be on board, so we can merge that to the list of people who'd like to join and send that to the CC for final decision19:19
highvoltagestgraber: we don't need to write up any specifications, right? is there anything pending approval?19:19
stgraberthat should be a quick and easy process, so we have the EC renewed for a year and can continue our work19:20
stgraberhighvoltage: we might need to update and assign some of our specs, but that's about what's needed at this stage19:20
highvoltageok, great.19:20
stgraberhighvoltage: I don't know if you worked on the work items yet, that'd be something good to have in the blueprint whiteboard19:21
highvoltageI guess it's also worth mentioning (if anyone else missed it perhaps) that next UDS will be in Budapest, Hungary19:21
stgraberbut it's really details as we already know who's going to work on it and don't have dependencies on other teams except cjwatson and ev for the installer issue19:21
* mhall119 is looking forward to a european trip19:21
highvoltagemhall119: yeah!19:22
mhall119highvoltage: do they allow South Africans in Hungary?19:22
highvoltagemhall119: it's in the schengen area so getting a visa will be easy :)19:22
mhall119schengen?19:23
stgraberhey mhall119, did you get the answers you needed from Dylan on Friday ? I didn't really see you much after that.19:23
mhall119stgraber: I did, but I'm working mostly by memory now, he put me on the right track at least19:23
mhall119wish I had something to take notes on that night19:23
highvoltagemhall119: not sure what exactly it means but it covers a bunch of european countries, I used it before to travel to france/spain19:23
stgrabermhall119: cool19:23
mhall119highvoltage: oh good19:23
highvoltagemhall119: and the US visa stuff will be easier next time, so next time in Orlando should be easy too!19:24
stgraberhighvoltage: that's all countries that signed the schengen-dublin agreement for exchange of goods and people traveling through the schengen area19:24
mhall119hopefully there will be a next time in Orlando too19:24
highvoltagemhall119: aparently there will be19:24
mhall119that's the rumor19:24
mhall119I haven't heard it confirmed yet19:25
stgraberwe'll probably know more at next uds19:25
highvoltageyup19:25
highvoltageanything we need to cover for this meeting? at this stage I feel all talked-out and just want to do stuff :)19:27
mhall119so there will remain the "2d" gnome session in 11.04, so the big question for the qimo session will be gconf->dconf issues19:27
mhall119I assume those will hit sabayon and other parts of Edubuntu as well19:27
highvoltageindeed.19:28
highvoltagemhall119: have you looked at dconf at all?19:28
mhall119I'm not sure how to start testing that, can I just install gnome3 packages inside a maverick vm?19:28
mhall119highvoltage: not yet19:28
mhall119I just got to where I kind of understood gconf :(19:28
highvoltage"Having all of the keys in a single compact binary format also avoids the intense fragmentation problems currently experienced by the tree-of-directories-of-xml-files approach."19:29
highvoltageugh19:29
highvoltagehaving everything in one binary caused lots of problems in the Windows registry in the first versions of Windows that used it, hopefully gnome will handle it more elegantly :)19:30
highvoltage(that's on http://live.gnome.org/dconf btw)19:30
mhall119yeah, it'll at least support stacking different dconf sources19:31
mhall119also http://library.gnome.org/devel/gio/2.25/ch26.html19:34
mhall119"Migrating from GConf to GSettings"19:34
highvoltageheh, stgraber just talked about that19:34
highvoltage(well, IRL)19:34
highvoltagemhall119: I have no idea how you currently plan to do the qimo stuff (time-wise)19:36
highvoltagemhall119: but I guess a lot of things will become somewhat clearer towards alpha 119:36
mhall119highvoltage: neither do I19:36
mhall119I'd like to get a quick and dirty qimo-session-gnome working as soon as I can, then clean it up over the rest of the cycle19:36
mhall119it'll kind of depend on when gnome3 lands in 11.04 though19:37
highvoltagemhall119: I think we should target to have at least a working qimo gnome session in there by alpha 2, since feature freeze happens a few weeks after that19:37
mhall119will alpha1 have gnome2 or gnome3?19:37
highvoltageI don't know, I hope that it contains at least most of the important parts19:38
mhall119guess we'll find out19:39
mhall119I already made a working custom session in gnome219:39
mhall119it's just not been configured to be Qimo-like19:39
highvoltageok, most of that work should still work in gnome3 at least.19:40
mhall119we may have to support both gconf and dconf in the next release, there's a bunch of apps that don't look to have been ported19:40
highvoltagemhall119: from what I understand from what stgraber explained to me, if you use gsettings then it shouldn't matter19:40
mhall119right, but for me I have to separate the configs of multiple apps between Qimo sessions and Gnome sessions19:41
mhall119if some apps are still using gconf, instead of gsettings, I've got to provide separate stores for both19:41
highvoltageok, I didn't realise you modify application settings as well19:43
mhall119I modify some of their default, specifically the gnome panels and nautilus desktop manager parts19:43
highvoltagemhall119: can I get it from a ppa or a branch or something?19:43
highvoltagewell gnome-panel and nautilus should be fine19:43
mhall119highvoltage: no, I've just been hacking stuff in a vm so far19:43
highvoltageok19:43
mhall119it's very crude, more just to prove that a qimo-gnome-session is possible19:44
highvoltagemhall119: well, one thing you could perhaps do so long is clone that vm and dist-upgrade it to natty and roll with the updates and see what breaks already19:44
mhall119true, I'll give that a go19:44
highvoltagelet's move over to #edubuntu, I guess we have nothing left that we need to do in meeting space :)19:46
=== nhandler_ is now known as nhandler
barryjames_w, slangasek, thumper, ajmitch ready for our meeting?21:01
james_whola21:01
* slangasek waves21:01
barrypoolie seems to be offline21:02
barry#startmeeting21:02
MootBotMeeting started at 16:02. The chair is barry.21:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]21:02
* james_w apologies as he will have to leave before the hour mark21:02
thumperah...21:02
thumperis this the time we had it last time?21:02
ajmitchit is21:02
barry[LINK] https://wiki.ubuntu.com/DistributedDevelopment/2010110321:02
MootBotLINK received:  https://wiki.ubuntu.com/DistributedDevelopment/2010110321:02
james_wI'm pretty sure21:02
flacosteme21:02
barryutc-wise, yes :)21:02
flacostebarry: poolie is21:02
barryflacoste: hi!21:02
* ajmitch is here, though I'd forgotten about it21:03
barry[TOPIC] action items21:04
MootBotNew Topic:  action items21:04
barry   * barry to start some sphinx docs to be well-integrated w/ wiki.u.c21:04
barry 21:04
barrynot done21:04
barry   * barry to talk to dholbach about making sure udd is well advertised in pkg guide21:04
barry 21:04
barryi did talk a little to dholbach about this at one of the many uds sessions.  james_w was probably there too (as was poolie).  he wants to promote/document udd we just have to figure out how to do this21:05
barryso i think this item is "done" though there's probably a future action item about actually helping dholbach with the integration21:05
barryjames_w: your thoughts?21:06
james_windeed21:06
james_wbarry, I agree with barry21:06
barrycool21:06
barry   * poolie to start list thread to find problems which can be carried on at UDS21:06
barry 21:06
barryi think this is not done21:06
persiaJust as a note on historical practices, it might be better to take an action to write the docs in consultation with dholbach, rather than helping him with them.21:06
barrypersia: i figure it will us writing the bulk of the docs and daniel helping to integrate them21:07
barrywell, poolie's action item is probably moot now, but i'll leave it on the agenda until he says otherwise21:07
barry[TOPIC]  * UDS post-mortem21:08
barry 21:08
MootBotNew Topic:   * UDS post-mortem21:08
barryjust a quick apology for letting two of our sessions get lost in the shuffle.  after talking with robbiew about rescheduling due to poolie's travel adventures, i lost track of the sessions and realized too late that the education and user feedback sessions didn't get rescheduled :(  i take the blame for that21:09
barrywe did have a good planning session though i thought21:09
barrywe need to get poolie's notes into the blueprint though because gobby was down at the time21:09
barryi'll take an action item to check with him on that21:10
barry[ACTION] barry to ask poolie to put his session notes in the blueprint21:10
MootBotACTION received:  barry to ask poolie to put his session notes in the blueprint21:10
barrydoes anybody else have any feedback on uds?21:10
james_wI found it very useful21:11
james_wthere was better feedback than previous UDS, so I think that it's something people are thinking about much more21:11
james_wunfortunately though there are still plenty of hurdles21:11
barrytrue.  on the positive side, i've heard we may have a really stellar candidate for the job opening21:12
james_wexcellent21:13
barryi also think the planning session was really excellent.  great feedback from folks like slangasek21:13
slangaseksorry I couldn't attend the whole session, but glad my feedback was helpful21:14
barryany other thoughts on uds?21:14
barryflacoste: we missed you and illuminati :)21:14
barry[TOPIC] top bugs21:15
MootBotNew Topic:  top bugs21:15
james_wthe session identified some focii for the various teams, but didn't really get them all assigned, do we need to work on that?21:15
james_wwhoops, sorry21:15
jelmer'evening21:16
barryjelmer: hi!21:16
james_whi jelmer21:16
flacostebarry: i should be at the next one :-)21:16
barryjames_w: we do, but i think poolie's got the list so i think we have to wait for him21:16
barryflacoste: \o/21:16
barryhere's the pre-uds list.  i guess next time we can consolidate them with the list from the session:21:17
barry* bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from my local mirror (slangasek)21:17
barry   * [[https://launchpad.net/bugs/295274|(watch file support)]] - james_w and barry to sprint on that at uds-n21:17
barry   * [[https://launchpad.net/bugs/653307|Import fails with missing referenced chk root keys]]21:17
barry   * [[https://bugs.edge.launchpad.net/bzr/+bug/603395|bzr commit in a heavyweight checkout does not propagate new tags]]21:17
ubottuLaunchpad bug 295274 in bzr-builddeb "merge-upstream shouldn't require --version when debian/watch is present" [High,Triaged]21:17
barry   * changelog merge problem (probably caused by dpkg-mergechangelogs).  need more investigation by barry21:17
ubottuLaunchpad bug 653307 in Ubuntu Distributed Development "Import fails with missing referenced chk root keys" [Critical,In progress]21:17
ubottuLaunchpad bug 603395 in Bazaar "bzr commit in a heavyweight checkout does not propagate new tags" [High,In progress]21:17
barryjames_w: and i looked at the watch file bug and i made notes.  hopefully i can understand them now that uds is over and make some progress on the bug21:18
slangasekjames_w: any status change on bug #653832? 696 failed imports :/21:18
ubottuLaunchpad bug 653832 in Ubuntu Distributed Development "Import fails with "trying to import version ... again"" [High,Triaged] https://launchpad.net/bugs/65383221:18
persiaFor the watchfile thing: probably best to check for debian/rules get-orig-source: before trusting it21:18
james_wslangasek, yes, at least in the gourmet case, did it ever get retried?21:19
slangasekjames_w: it was retried before you commented that the bug was "harder than you thought"21:19
barrypersia: right21:19
slangaseknot retried after that, is that the next step?21:19
james_wslangasek, ok, I'll retry now21:19
slangasekok, thanks21:19
james_wslangasek, it may well stamp on your revisions in that branch though :-(21:19
slangasekfwiw, gourmet is far from the only interesting package in that list21:20
james_windeed21:20
slangasekah, well, I guess I'll cope :)21:20
barryany other feedback on top bugs?21:21
james_wspiv seemed to have a good handle on the corruption in bug 653307, but not exactly how it came about21:22
ubottuLaunchpad bug 653307 in Ubuntu Distributed Development "Import fails with missing referenced chk root keys" [Critical,In progress] https://launchpad.net/bugs/65330721:22
barryexcellent21:22
james_whe said that the easiest fix might be to re-import all of those branches21:23
ScottKbarry: I'd like to see someone tackle Bug #499684 sooner rather than later as the more users there are, the harder it will be to change to something better.21:24
ubottuLaunchpad bug 499684 in bzr-builddeb "Interface to dpkg-buildpackage inconsistent and not well documented" [High,Triaged] https://launchpad.net/bugs/49968421:24
barryScottK: yeah, we talked about that at uds.  the -- is really ugly :/21:25
ScottKYep21:25
barryScottK: i'll put that on the top bugs list21:26
jelmerjames_w: do you know whether it's easily possible to support not explicitly declared options in a bzr subcommand?21:26
james_wjelmer, I do not. It's probably not that much work to add21:26
james_wI got bored of trying to add them explicitly, mainly because trying to explain the meaning of things like -su vs. -sa is really hard21:27
barryjames_w: where is -su documented?  i don't see it in dpkg-genchanges21:29
barry(manpage)21:29
james_wsorry, I mean -si21:29
* barry nods21:29
barrymoving on...21:30
barry[TOPIC]  * USA leaves DST21:30
MootBotNew Topic:   * USA leaves DST21:30
james_wplus I think they are interface warts, so I'm not pleased about inheriting them21:30
barryit would be best if users didn't need to worry about them at all, but i don't know if that's possible21:31
james_windeed21:31
barryi mention the dst thing because the meeting will be an hour earlier local time for me.  it's still fine, but i wanted to give folks a chance to chime in if the current 2100 utc meeting time has become inconvenient for them21:31
james_wit still works for me21:31
slangasekfine for me21:32
james_wand this time is better for our antipodean friends21:32
barrycool.  no change necessary then21:32
barry[TOPIC]  * Pushing changes to Debian (python-cheetah use case)21:33
MootBotNew Topic:   * Pushing changes to Debian (python-cheetah use case)21:33
barryi bring this up because it's something i'm thinking about now and it's a use case we should address21:33
barrybut we don't need to solve it here21:33
barrybasically: i fixed python-cheetah in the ubuntu source branch but we really should get the changes into debian.  i don't know that udd has a good story for that yet21:34
james_wsomething like submittodebian?21:34
barryjames_w: something like that, yeah.  there is bug reporting via email involved21:34
barryreportbug on ubuntu does not make debian developers happy21:35
james_wshouldn't be too hard to generate the diff21:35
james_wemailing is perhaps a trickier fish, though perhaps we just modify and rely on submittodebian21:35
slangasekyou mean we can't just push to lp:debian/$package and have Debian build from branch? <g,d,r>21:35
barryslangasek: :-D21:36
barryjames_w: oh.  submittodebian(1)  \o/21:36
james_wheh21:36
barryjames_w: looks very interesting, and i'll give that a try with python-cheetah21:37
jelmera "bzr submittodebian" that takes into account common ancestors etc might be nice21:37
persiaMight be nice to have three stories: 1) pushing a change to the BTS, 2) committing a change to Vcs-*, 3) push to lp:debian/foo and upload package21:37
barrywould pushing to lp:debian/foo get clobbered when the change lands in debian and gets imported back into launchpad?21:38
persiaWouldn't that have the same handling as when folk push to lp:ubuntu/foo and then upload now?21:38
slangasekjelmer: I did hack submittodebian a while back to notice when it was on a bzr branch and attempt to DTRT21:38
slangasekcould stand to be improved some, yes21:39
jelmerslangasek: ah, that's probably even nicer than adding yet another (sub)command.21:39
barryotoh having it as a subcommand makes it more discoverable perhaps21:40
jelmerpersia: supporting push to lp:debian/foo would require us to have a Debian build environment on Launchpad21:40
jelmerpersia: support push to lp:debian/foo and build, that is21:41
james_wwell, in some sense push as well right now21:41
james_wACL are tied to upload rights21:42
james_wunfortunately I have to leave now, sorry21:43
james_wthanks everyone21:43
jelmerThanks James21:43
* slangasek waves21:43
barrythat was very helpful, thanks.  i'll add my experience to the wiki and file a bug for a new feature21:43
barrythanks james_w21:43
barrywe're basically done anyway21:44
barry[TOPIC] AOB21:44
MootBotNew Topic:  AOB21:44
barrydo you have anything else not on the agenda?21:44
persiajelmer, I meant the build to be done on the local machine where the developer has the necessary key to upload to Debian: I doubt any DDs would trust those to LP.21:45
jelmerpersia: Ah, ok21:45
jelmerpersia: Yeah, I wouldn't trust them to /any/ remote machine.21:45
persiaFor some definition of remote.  I know several who don't trust them to laptops, and use debsign -r against trusted machines that may not be local (but are housed in a trusted environment)21:46
persia(or debrsign, depending)21:47
barryanything else for today?21:47
barry#endmeeting21:48
MootBotMeeting finished at 16:48.21:48
barrythanks everyone.  see you in two weeks21:48
slangasekthanks!21:49
ajmitchthanks21:50

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