/srv/irclogs.ubuntu.com/2009/12/02/#ubuntu-meeting.txt

=== nxvl_ is now known as nxvl
=== asac_ is now known as asac
=== bjf is now known as bjf-afk
=== m4v is now known as mkv
=== richie is now known as Richie
=== YDdraigGoch is now known as Richie
=== yofel_ is now known as yofel
=== fader|away is now known as fader_
zulmorning13:52
kane_o/13:53
nijaba\o13:59
ttxo/14:00
sommerhey all14:00
mjeansonhi14:00
kane_hi there14:00
alexmo/14:00
nijabattx: not sure you noticed, but I just added an item about the server survey on the agenda.14:01
smoserhola14:01
ttxnijaba: I saw that14:01
nijabattx: cool, thanks14:01
zultestcase printHelloWorld()14:01
zul    print("Hello World!")14:01
ttxsoren, mathiaz, mdz: ?14:02
mathiazo/14:02
sorenOh, right.14:02
ttxkirkland: ?14:02
soreno/14:02
nijabaeuca-run-instance meeting14:02
kirklandttx: morning14:02
Daviey\o14:02
ttxxc2 meeting14:02
EtienneG_homefor once, I will be hanging around!14:02
kirklandnijaba: -t m1.xlarge14:02
sorencloudctl create ec2 m1.xlarge ami-lets-just-get-on-with-it14:03
ttxok, let's start14:03
zulEtienneG_home: yay!14:03
ttx#startmeeting14:03
MootBotMeeting started at 08:03. The chair is ttx.14:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:03
mdzttx, hi14:03
ttxFirst of all, let me introduce you to Jos Boumans, the new server team engineering manager.14:04
kane_o/14:04
nijabaWelcome Jos!14:04
* kirkland high fives kane_ 14:04
Davieyhey Jos!14:04
ttxkane_: you didn't force your IRC client to submission yet ?14:04
zulhey kane_14:04
kane_ttx: not yet. ran out of CFT my first day @canonical ;)14:04
sorenCFT?14:04
kane_Copious Free Time14:05
ttxkane might become jib in the future on Freenode14:05
kane_nice to see some familiar faces here from UDS though :)14:05
zulkane_, get use to the lack of thereoff from here on out14:05
* mdz hands jib some round tuits14:05
mdzs/jib/jane_/14:05
mdzkane_, rather14:05
nijabano wonders nobody knows what CFT is around here14:05
sorenHeheh :)14:05
mathiazkane_: o^2514:06
ttxI'll chait this meeting so that Jos sees how it goes, but will gladly hand over the cross to Jos next week :)14:06
ttxchair, even14:06
mdzhaha14:06
kane_i, in turn, am very happy for ttx to chair14:06
ttxnext...14:06
ttx[TOPIC] Review ACTION points from previous meeting14:06
MootBotNew Topic:  Review ACTION points from previous meeting14:06
ttxhttps://wiki.ubuntu.com/MeetingLogs/Server/2009112514:06
ttxACTION: ttx to review status of bugs 455625, 460085 and 461156 for any missing info14:07
ubottuLaunchpad bug 455625 in eucalyptus "Eucalyptus Loses Public IP Address" [Medium,Incomplete] https://launchpad.net/bugs/45562514:07
ubottuLaunchpad bug 460085 in eucalyptus "memory leak; rampart_context not freed (memory leaked per connection)" [High,Fix committed] https://launchpad.net/bugs/46008514:07
ubottuLaunchpad bug 461156 in eucalyptus "User data is not parsed correctly by Eucalyptus in some cases" [High,In progress] https://launchpad.net/bugs/46115614:07
ttxso I reviewed them... the first one is lacking some reproduction, the Eucalyptus team marked it invalid14:07
ttxthe second one is missing some feedback from the Eucalyptus team, basically the results of their long-standing rampart tests14:07
ttxThe third one is now fixed in Lucid, SRU pending14:08
ttxACTION: mathiaz to compile a list of easy merges for publication14:08
mathiazttx: done - http://ubuntuserver.wordpress.com/2009/12/01/a-selection-of-easy-merges-from-the-ubuntu-server-team/14:08
mdzmathiaz, did that go out to the mailing list(s) as well?14:08
ttxarh14:09
mathiazmdz: nope - I could send it there as well14:09
mdzmathiaz, I think it would be useful14:09
ttxmathiaz: I did a few days ago libcommons-attributes-java and libaopalliance-java14:09
mdzdholbach gave us some feedback that we should use the mailing lists more14:09
ttxmathiaz: and I wouldn't recommend the jruby1.2 one to the faint of heart14:09
mathiazttx: yeah - that's possible14:09
mathiazttx: I haven't looked at all the merge in details14:10
ttxNow on to this week's agenda14:10
mathiazit's just a list  of suggestion - to get people started14:10
ttx[LINK] https://wiki.ubuntu.com/ServerTeam/Meeting14:10
MootBotLINK received:  https://wiki.ubuntu.com/ServerTeam/Meeting14:10
ttx[TOPIC] Check blueprint status and progress for the week14:10
MootBotNew Topic:  Check blueprint status and progress for the week14:11
ttxkane_: ?14:11
kane_We covered most of them during the 1:1s we've had this week, and those that could be approved are.14:11
kane_There are some that aren't on the alpha2 milestone, and it's on me to have those reviewed by next meeting (before featured definition freeze)14:11
mdzttx, other-cloud-providers and vmbuilder-multiple-outputs are awaiting review14:11
ttxkane_: what about Feature definition freeze, and the remaining non-lucid-accepted-yet blueprints ?14:12
ttxmdz: Will look into it14:12
kane_mdz: the other cloud & vmbuilder aren't for alpha2 though, so we should have those done by next week14:13
kane_the minimum we do for non-alpha2 specs BEFORE feature definition freeze is to make sure we have the summary, rationale & user story in the spec, and any notes we took from UDS14:14
kane_that way we know what we're comitting to if/when we persue them in the next milestones14:14
ttxkane_: the minimum to make sure we don't lose the results of the UDS session14:14
kane_ttx: exactly14:14
ttxkane_: ok, what about "Discuss process for ongoing progress tracking" ?14:15
kane_feel free to summarize that one ttx14:16
ttxWe'll use http://www.piware.de/workitems/server/lucid-alpha2/report.html for global tracking14:16
ttxThen for each alpha2 spec do a quick summary of status here ?14:17
ttxWe'll skip for this week, unless someone wants to mention they are already raising flags on their assignments14:17
kane_yeah; there's a few easy ways to do this. I hope to cargo-cult on the other teams starting the next meeting.14:17
nijabaI don't see any of the community BP on this. Normal?14:18
nijabaI think ScottK and ivoks had some14:18
ttxnijaba: They appear on http://www.piware.de/workitems/server/lucid/report.html14:18
ttxthey are not specifically targeted to alpha2 (good for them)14:19
mathiaznijaba: they may not have been targeted for alpha2 though14:19
nijabaah, ok, sorry14:19
ScottKStill working on drafting.14:19
ScottKHope to finish shortly.14:19
ttxAnyone has questions on this topic ?14:19
mathiazttx: can we add WI to the whiteboard?14:19
mathiazttx: what happens if the content of a WI changes?14:19
zulfor the canonical-application-support spec what if the packages are not approiate what should i put next to the TODO14:20
ttxmathiaz: you mean if you add new ones, it will look like feature creep on the burndown chart ?14:20
mathiazttx: yes14:20
mathiazttx: and IIUC this looks bad14:20
smosergood questions mathiaz14:20
ttxmathiaz: the chart will be reset at an arbitrary point in time14:20
ttxi'd suggest FeatureDefinitionFreeze14:20
ttxafter that, added items will *really* be feature creep.14:21
ttxkane_, mdz: ^ ?14:21
mathiazttx: it seems that the list of WI should not be touched after Feature Definition14:21
mdzI believe pitti planned to reset the chart today-ish14:21
ttxmathiaz: well, it can, but then it really is considered feature creep.14:21
kane_the WI is a reflection of reality14:21
mdzbut of course we can ask him to do it whenever it is appropriate for us14:21
mdzI would say no later than tomorrow14:21
mathiazttx: also I'm still tracking next things to do (may be the granularity is too small)14:22
kane_the tool is there to give us insight, not something that restricts us from planning14:22
kane_but ttx is right; if there's new (unforeseen) work popping up, that may be feature creep14:22
mdzzul, when you review the package, you should change the "review" work item to "DONE"14:22
mdzzul, if, once you have done that, it turns out there is nothing more to do, you should *delete* the other work items associated with that package14:22
mdzthis will reduce the total number of work items in the chart14:23
zulmdz: gotcha14:23
ttxmathiaz: you mean work items are too small ?14:23
ttxmathiaz: not sure I get you14:23
mathiazttx: well - I guess I'm using Work Items and Next Action (in GTD) as the same thing14:24
mathiazttx: I think I understand myself - and we can move on14:24
ttxI've been translating my work items into GTD next actions14:24
ttx(manually, shame on me)14:24
ttxmoving on14:24
mathiazttx: same here - but we can discuss this offline14:24
ttx[TOPIC] Assigned and to-be-assigned bugs14:24
MootBotNew Topic:  Assigned and to-be-assigned bugs14:24
ttx[LINK] http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html14:24
MootBotLINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html14:24
ttxkane_: ?14:25
ttxnothing assigned to team14:25
ttxtoo many old bugs in that list to my taste, I think we should review what we should assign ourselves to14:26
ttxbut we'll let it be for the moment14:26
kirklandttx: +114:26
ttxshouldn't be the list of things you might work on someday14:26
ttxbut rather work in progress and what comes immediately after14:26
ttxbut I'm open to discussion14:27
ttxit's just that the list as it stands is not very useful to review14:27
kane_i have an action point on me to pick this up with marjo; there's an expectation that comes with bug list and i need to be brought up to speed with it14:27
zulit isnt14:27
ttxanyone has comments on the bugs they are assigned to on this list ? Anything blocking ?14:27
mathiazttx: the date the bug was assigned is probably useful14:27
mathiazttx: to make sure bugs are not aging14:28
ttxWe already discussed bug 460085, pending some eucalyptus upstream info14:28
ubottuLaunchpad bug 460085 in eucalyptus "memory leak; rampart_context not freed (memory leaked per connection)" [High,Fix committed] https://launchpad.net/bugs/46008514:28
ttxNothing else ? OK, let's move on then...14:28
ttx[TOPIC] Weekly SRU review14:29
MootBotNew Topic:  Weekly SRU review14:29
Daviey\o/14:29
* ttx leaves the driver seat to mathiaz14:29
ttx(while the car is still running)14:29
mathiazhttp://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html14:29
MootBotLINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html14:29
mathiaz^^ any bugs SRU worthy on this list?14:30
=== robbiew-afk is now known as robbiew
ttxonly high thing on the list id bug 454405, which is a karmic SRU already14:30
ubottuLaunchpad bug 454405 in eucalyptus "the CC is returning incorrect networkIndex values on describeInstances" [Critical,Fix committed] https://launchpad.net/bugs/45440514:30
zulmathiaz: bug 48576014:31
ubottuLaunchpad bug 485760 in php5 "Need to upgrade integrated zip module" [Undecided,Fix released] https://launchpad.net/bugs/48576014:31
kirklandttx: what's the plan for rolling/uploading a new SRU candidate of eucalyptus to karmic-proposed?14:31
mathiazno bugs nominated for dapper, hardy, intrepid, jaunty, karmic14:31
ttxkirkland: we need to get around the CLEAN=1 thing, then upload14:31
ttxkirkland: please see my comments on the related bugs and let me know what you think14:32
kirklandttx: i think we should upload, and then get around to the CLEAN=1 thing14:32
kirklandttx: yes, I'm on top of those14:32
mathiazhm - there should be bug 48941814:32
kirklandttx: i think it's better to have something in -proposed, and work on that incrementally14:32
ttxkirkland: I'm ok for release, I committed to the ubuntu-karmic branch already.14:32
ubottuLaunchpad bug 489418 in krb5 "Strange behavior of libkrb5 since karmic ..." [Undecided,Confirmed] https://launchpad.net/bugs/48941814:32
zulmathiaz:i just nominated 48576014:33
ttxkirkland: and wrote the SRU report14:33
mathiazwhich means that list of nominated bugs is not accurate :/14:33
kirklandttx: okay14:33
ttxkirkland: I wanted to get the feedback on rampart first though14:33
ttxkirkland: but I'm ok either way14:33
kirklandttx: okay14:33
smoserquery ttx14:34
ttxsmoser: that's me14:34
kirklandttx: so the SRU is blocking on the CLEAN=1 bits, and rampart feedback?14:34
smoseryeah, i'm a dolt14:34
czajkowski 14:34
mathiazlet's move on14:34
mathiazhttp://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html14:34
MootBotLINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/acceptedbugs.ubuntu-server.latest.html14:34
ttxkirkland: yes, but that doesn't prevent us from going to -proposed.14:35
kirklandttx: absolutely agree14:35
mathiazmost of the SRU are related to eucalyptus14:35
mathiazzul: how are other SRU's going?14:36
mathiazAnd the list of bzr branch to review is empty for the server team14:36
zulmathiaz: i havent had a chance to look at them due to spec writing14:36
mathiazhttps://code.launchpad.net/~ubuntu-server/+activereviews14:36
mathiazAnything else on the SRU front?14:37
ttxmoving on...14:37
ttx[TOPIC] 2009 Server Survey announce14:38
MootBotNew Topic:  2009 Server Survey announce14:38
ttxnijaba: ^14:38
nijabaI have just announced on Planet Ubuntu the release or the 2009 Server survey http://nicolas.barcet.com/drupal/en/2009-server-survey-announce14:38
nijabaCall for action:14:38
nijabaLast year this survey received a little bit less than 7000 full response and we hope to have at least that many this year.14:38
nijabaIn order to do so, it would be very nice that, in addition to the announce I made and the banner that Matt Nuzum is about to put on http://ubuntu.com/server, any of you that can republish the announce on a loco planet or some other means do relay the info in the next couple weeks.  So far, the plan is to keep the survey up at least until mid-january.14:38
nijabaI will shortly send an email to the server ML with the same information.14:38
nijabaquestions?14:39
nijabasuggestions?14:39
ttxnijaba: any major change in the questions asked ?14:39
nijabaquite a few changes, yes14:40
* ttx admits not having completed the survey yet14:40
nijabadetails on https://wiki.ubuntu.com/ServerTeam/Survey14:40
ttxok14:40
ttxnext is...14:40
mathiaznijaba: have you send an email to ubuntu-server@?14:40
ttx[TOPIC] Open Discussion14:41
MootBotNew Topic:  Open Discussion14:41
nijabamathiaz: as I just said, I will shortly send an email to the server ML with the same information.14:41
mdzI believe there is still an open issue regarding the meeting time?14:41
ttxmdz: yes, problematic for kirkland, impossible for nurmi14:41
mdzwho has the ball?14:41
nijabaivoks is complaining that he cannot attend during his work hours14:41
ttxmdz: kirkland hasd to ping maria, I think14:41
kirklandmdz: ttx: yes, I need to talk to maria14:42
mdzmaybe jos has some bandwidth to help, and he's in a nearby time zone to maria14:42
ttxmdz: ball is in kirkland side of the field, offense team is up.14:42
kirklandmdz: actually, I was sort of waiting on Jos to come on board, to make sure his availability was taken into account14:42
mdzkirkland also has blueprints to worry about ;-)14:42
kane_mdz: luckily i don't ;)14:43
kane_i'm happy to take this on -- i'll talk with kirkland seperately, figure out where it hurts and get a resolution14:43
kirklandkane_: one our later would suffice for both nurmi and i14:43
kirklands/ our / hour /14:43
kane_kirkland: understood. that may bite with other calls though, so let's sort it seperately if you don't mind14:44
kirklandkane_: sure thing14:44
ttxAnything else anyone wants to bring up ?14:44
DavieySpamassassin - 3.3.0 will hit beta "soon", i've emailed the DM to ask if he wants to work together to get the package updated.14:44
mathiazDaviey: how stable is spamassassin 3.3.0 for an LTS?14:45
ttxmathiaz: kane_ volunteered to write the meeting minutes (since he will write them all soon) so could you get him up to date with the minutes publication process ?14:45
mathiazttx: sure14:45
* kane_ thinks ttx may be taking this chairing thing very serious ;)14:46
Davieymathiaz: well it's still not even beta :).. But for *supporting* the released version - upstream would likely be more receptive for the LTS period.14:46
ttxkane_: let me enjoy that position for the last time :P14:46
ttx[TOPIC] Agree on next meeting date and time14:47
MootBotNew Topic:  Agree on next meeting date and time14:47
ttxUnless something else is announced, same time, same place, next week.14:47
mdz[action] jos?14:47
ttx[ACTION] jos to find out the best time for the meeting14:48
MootBotACTION received:  jos to find out the best time for the meeting14:48
Daviey(if it is changed, update the fridge)14:48
ttxthanks everyone !14:48
ttx#endmeeting14:48
MootBotMeeting finished at 08:48.14:48
* ttx opens the bar14:48
mdzjust one last thing...14:48
kane_thanks guys14:48
mdzttx, kane_ and I went over your blueprints with sabdfl yesterday14:49
nijabathanks for hosting ttx14:49
mdzand he was very pleased with your work14:49
mdzwell done14:49
ttx+114:49
Davieytop banana14:49
* smoser claps for ttx14:49
kane_(you guys)++14:49
smoserah. thats funny. i read mdz's statement to say that mdz and kane_ and sabdfl talked about ttx's work14:50
* kirkland high fives ttx14:50
ttxsmoser: not.. really.14:50
smoserthat "your" == ttx's . anyway. i'll be quiet now14:50
kirklandwell done, ttx!14:50
sorenOh, that's what I thought as well. :)14:50
alexmcongrats, ttx14:50
ttxwell done everyone14:51
ttxstop congratulating me14:51
ttx"<mdz> (ttx, kane_ and I) went over team's blueprints with sabdfl yesterday"14:51
smoser(i'd just like to say, that ttx's work was good, but zul's had one of the best videos *EVER*)14:51
zulwha?14:51
ttxsmoser: link14:52
kane_smoser++14:52
ttxI remember sabdfl congratulating smoser, though.14:52
mdzah, sorry I was unclear...I mean "the server team's work"14:53
* smoser was trying to make a joke about http://www.people.com/people/package/article/0,,20302940_20304165,00.html14:54
smoserbut should have said "of all time", not "EVER"14:54
artir 14:56
* nealmcb opens a bleary eye and sees he wasn't up quite early enough for the server team :)14:57
Davieyearly bird catches the worms.15:03
mhall119|workwho wants worms anyway?15:12
mhall119|workthe late bird gets the brunch specials15:12
nealmcblol15:16
cjwatsonfoundations folks?16:03
mvohi16:03
evhi16:05
* cjwatson works out the list to go round up16:05
cjwatsonsorry I got back a little late16:06
cjwatsonrobbiew has a schedule conflict, and Keybuk is ill16:06
cjwatsonjames_w,lool,slangasek: ping?16:07
james_whi16:08
james_wsorry16:08
cjwatsonthe only thing I have myself is the imminent feature approval deadline (TOMORROW)16:08
james_windeed16:09
cjwatsonthe cronmail whine I get indicates that there are still nine specs without work items16:09
cjwatsonfoundations-lucid-daily-builds foundations-lucid-fix-iscsi-root foundations-lucid-multiarch-support foundations-lucid-puppet-installer foundations-lucid-ratings-and-reviews-in-software-center foundations-lucid-robust-python-packaging foundations-lucid-upstart-policy foundations-lucid-upstart-server-review foundations-lucid-user-contributed-metadata-for-software-center16:09
cjwatsonI've asked mathiaz about foundations-lucid-puppet-installer, and I've asked Keybuk about foundations-lucid-upstart-policy and foundations-lucid-upstart-server-review16:10
cjwatsonfoundations-lucid-fix-iscsi-root is mine and I'll get it done today16:10
cjwatsonso for the remainder:16:10
cjwatsonjames_w: foundations-lucid-daily-builds16:10
cjwatsonslangasek: foundations-lucid-multiarch-support16:10
james_wyes16:10
cjwatsonmvo: foundations-lucid-ratings-and-reviews-in-software-center foundations-lucid-robust-python-packaging foundations-lucid-user-contributed-metadata-for-software-center16:10
james_wand I think distributed-development16:10
mvocjwatson: thanks, I work on that today, the first two are launchpad specs to a certain extend16:11
cjwatsonthere are some that don't show up in cronmail because they aren't targeted yet, or similar16:11
* mvo will add work-items to the best of his knowledge for them16:12
cjwatsonanyway, as Robbie already said, https://blueprints.edge.launchpad.net/ubuntu/lucid?searchtext=foundations is the list of work he has discussed with Mark already16:12
cjwatsonif you're planning anything NOT there, please shout ASAP16:12
cjwatsonbecause otherwise we won't be taking it into account for how heavily loaded you are, which is not in your best interest :)16:12
lool(sorry had a phone call at the beginning of the meeting)16:13
mvompt wants to have a software-center-ui-changes spec16:13
cjwatsonis there a laundry list of proposed changes already?16:14
mvohe has one, but its not written down anywhere yet AFAIK16:14
cjwatsonok, is there any hope of getting it written up by tomorrow?16:14
mvoI told him that the deadline is tomorrow16:15
mvofrankly with the load we have for s-c we will need help on this anyway16:15
mvofrom DX or someone else16:15
* slangasek waves16:15
mvo(especially since its not glade file changes)16:15
mvoaha, a volunteer ;) ?16:15
cjwatsonmvo: one of the work items probably ought to be going to find dbarth, then. :)16:16
tremoluxmpt mentioned to me that he expects to have all updates to the spec finished by tomorrow https://wiki.ubuntu.com/SoftwareCenter?action=show&redirect=SoftwareStore16:16
mvoheh :)16:16
cjwatsontremolux: OK, that's good, although we'll probably need a broken-out one for the specific changes from karmic->lucid as well16:17
cjwatsonunless there's already a section for that16:18
mvoagreed, I think we need to have them as work items16:18
tremoluxmvo, cjwatson: right16:18
tremoluxjust meant it as an fyi  :)16:19
cjwatsonjames_w: you already have WIs for distributed-development, although they don't look complete :)16:20
james_wif only :-)16:21
cjwatsonslangasek: foundations-lucid-multiarch-support needs work items written up, if you didn't see that in scrollback; will you have time to do that by the deadline tomorrow?16:23
james_wthe distributed development spec is fundamentally carried over from karmic, so https://wiki.ubuntu.com/DistributedDevelopment/ImproveDebianImportSpecification mostly applies from last time16:23
james_wshould I re-purpose that, or make a new spec?16:24
slangasekcjwatson: yep, will have it done today16:24
cjwatsonjames_w: re-purposing that is fine16:25
james_wthanks16:25
cjwatsonrelatedly, http://www.piware.de/workitems/foundations/lucid-alpha2/report.html is what we have to do for alpha2 (briefly, I think, things that are critical to product roadmaps) so if there's anything else you believe should be there then please either let robbiew or me know, or just milestone it16:26
cjwatsonwe'll be tracking pages such as that as we approach each milestone, along with the overall burndown list: http://piware.de/workitems/foundations/lucid/report.html16:27
cjwatsonthat "nobody" dude is a bit oversubscribed right now, so I think some work items need specific assignment :)16:27
james_wspecs are targeted, not work items?16:28
cjwatsonanyway, that's all I have16:28
cjwatsonjames_w: correct16:28
james_wok16:28
cjwatsonoh, also, welcome tremolux to the foundations team for this cycle!16:28
cjwatson(I can't remember whether we did that already, so making sure ;-) )16:28
james_wI'm not sure my specs will fit this scheme too well16:28
james_wwelcome tremolux!16:28
evwelcome tremolux!16:28
cjwatsonjames_w: it's OK to register individual specs pointing to the same wiki pages, FWIW ...16:28
cjwatsonalthough not entirely unconfusing16:28
james_wcjwatson: ah, interesting approach16:28
tremoluxthanks!  :D  very glad to be here16:28
cjwatsonyou could use anchors16:28
mvowelcome16:28
cjwatsonany other business?16:29
evmvo: Are you comfortable with me assigning the work item for a slideshow in the release upgrader to Dylan McCall?  He's expressed a willingness to help create that.16:29
* lool hugs tremolux 16:29
* tremolux hugs look16:29
tremoluxlool16:29
tremolux(jeez)16:29
mvoev: sure, that is fine16:30
evokay cool16:30
ScottKcjwatson: I have one issue.16:30
mvoev: I'm happy to help him with that too, so that he has a easier time to find his way in the code etc16:30
cjwatsonScottK: go16:30
ScottKCurrently qt4-x11 is FTBFS on armel due to an internal compiler error16:30
* cjwatson looks up the log16:31
ScottKDebugging armel compiler bugs is a bit beyond the community to do.16:31
cjwatsonI wonder if that's another of the -minternal-it=thumb bugs?16:31
loolI'd poke the mobile team, specifically NCommander was looking into kde-ish/qt-ish issues in the past16:31
cjwatsonasac: ^- do you know what's going on there?16:31
ScottKIt would be useful if we could get this fixed sooner rather than later as we can't really do anything towards getting KDE building on armel until it's fixed.16:31
ScottKlool: I already poked NCommander.  He saw it was an ICE and ran.16:32
evmvo: cool, I'll let him know16:32
cjwatsoncjwatson@jocote:~$ dchroot -c lucid16:33
cjwatsondchroot: pthread_mutex_lock.c:87: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.16:33
cjwatsonAborted16:33
cjwatson^- doesn't help16:33
loolcjwatson: Yes, implicit-it= might help indeed16:33
cjwatsonlamont: ^- is there any reasonable way to get at an armel lucid chroot right now?16:33
loolcjwatson: Where is this on?16:33
loolHmm v7 porter machine16:34
lool(I was wondering whether it might have been the older v5 one)16:34
ScottKI know doko_ was on vacation last week and is sick now, but I wanted to highlight it as a significant foundations issue that we need some help on.16:34
cjwatsonI am aware that a number of architectures have similar problems16:34
cjwatsonScottK: noted - I'll minute it and see what we can do about it. Thanks16:34
ScottKcjwatson: Thanks.16:34
asaccjwatson: try LANG=C dchroot ...16:35
asacthats the workaround16:35
=== mac_v_ is now known as mac_v
loolScottK: Not sure that's the issue, but the syntax of ARM assembly source changed, one compiler flag tells gas to parse the old style syntax -Wa,-implicit-it=thumb16:35
asacafaik qt/kde issues are not only thumb16:35
cjwatsonasac: ah, thank you16:36
asacbut its on our list to evaluate16:36
cjwatsonexcept not16:36
doko_yes, I'll add this for the next upload, but the glib issue is unrelated to that16:36
asacack16:37
cjwatsonLC_ALL=C LANGUAGE= dchroot ... # same thing16:37
asachmm16:37
asacLANG=C dchroot -clucid16:37
asacI: [lucid chroot] Running login shell: '/bin/bash'16:37
asac(lucid)asac@jocote:~$16:37
cjwatsonah, -clucid rather than -c lucid works16:37
cjwatsongrr16:37
asac;)16:38
cjwatson(it still aborts on logout, but hey)16:38
ogracjwatson, its pretty sure one of the -minternal-it=thumb bugs16:38
cjwatsonI'll test that out16:38
cjwatsonAOB?16:39
ScottKWe're close to uploading qt4-x11 4.6.0 final, so any arch specific compiler flags to try, please just let me know.16:39
loolHmm no specific assembly in the source, it might not be implicit-it-thumb after all :-/16:39
ogralool, the log seems to fail with assembler stuff16:40
cjwatsonwell, look, this is easily determined experimentally, we don't have to argue it from theory :)16:40
loolActually I think it's a compiler internal structure, anyway #ubuntu-arm16:41
lamontcjwatson: LANG=C16:41
lamontjust not sure what package to file the bug against...16:42
ogralamont, you forgot to say your macro "patches accepted" ;)16:42
lamontLANG=C dchroot is fine, fwiw16:42
cjwatsonanyway, end of meeting, I think we're done16:42
cjwatsonthanks all16:42
lamontogra: that was sepcial for you16:42
ograah :)16:42
slangasekthanks, folks16:42
* ogra feels special now :)16:42
loolScottK: https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/49039116:43
ubottuUbuntu bug 490391 in gcc-4.4 "GCC internal error (unrecognizable insn ...) building qt4-x11 for Thumb-2 on armel" [Undecided,New]16:43
lool(It's definitely thumb specific though)16:43
ScottKOK.  So should I add -Wa,-implicit-it=thumb for armel for our next upload?  This armel stuff is pretty well greek to me.16:45
ograScottK, https://wiki.ubuntu.com/ARM/Thumb2 might help a little16:45
cjwatsonScottK: I'm going to test that out nowish16:46
ScottKcjwatson: Thanks.16:46
=== dyfet` is now known as dyfet
* marjo waves16:58
* ara waves16:58
pedro_hola!16:59
* fagan waves16:59
bdmurrayhey16:59
* fader_ waves.16:59
sbeattiehey16:59
marjofagan: glad you can join us16:59
davmor2hello16:59
* fagan remembered this time :D16:59
marjo#startmeeting QA Team17:00
MootBotMeeting started at 11:00. The chair is marjo.17:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:00
marjoAgenda:17:00
marjo    * SRU testing -- sbeattie (Steve Beattie)17:00
marjo    * Bugday highlights -- pedro17:00
marjo    * QA mailing list -- fader17:00
marjoAnybody want to add to the agenda?17:00
marjo[TOPIC] SRU testing -- sbeattie (Steve Beattie)17:01
MootBotNew Topic:  SRU testing -- sbeattie (Steve Beattie)17:01
sbeattieSRU activity has slowed about, perhaps due to the US holiday last week.17:02
sbeattieSRU Activity report for the past week (since 2009-11-24):17:02
sbeattie* karmic: 11 new packages in -proposed (app-install-data-partner, conduit, devicekit-disks, evolution-indicator, iriverter, linux-firmware, muse, openafs, samba, telepathy-gabble, xorg-server) and 10 pushed to -updates (deja-dup, eucalyptus, gdm, kdeedu, kdeplasma-addons, treeline, tzdata, uim, ureadahead, xorg)17:02
sbeattie* jaunty: 2 new packages in -proposed (conduit, openafs) and 1 pushed to -updates (tzdata)17:02
sbeattie* intrepid: 1 new package in -proposed (pidgin) and 1 pushed to -updates (tzdata)17:02
sbeattie* hardy: 2 packages pushed to -updates (sun-java6, tzdata)17:02
sbeattie* dapper: 1 package pushed to -updates (langpack-locales)17:02
sbeattieThanks to Morten Frisch, bluenibor, VPablo, Alastair Carey, Mario Limonciello, Pjotr12345,  Steve Dodier,  Zaar Hai, Evan Broder, Fabrice Coutadeur, Philip Muskovac, and Jonathan Thomas for testing proposed updates.17:02
sbeattieThat's all I have on the topic for this week.17:04
marjosbeattie: thx17:04
marjo[TOPIC] Bugday highlights -- pedro17:04
MootBotNew Topic:  Bugday highlights -- pedro17:04
pedro_Tomorrow we're having our first Bug Day after coming back from UDS17:05
pedro_the target will be Ubuntu Translations https://wiki.ubuntu.com/UbuntuBugDay/2009120317:05
pedro_Thanks a lot to Victor Vargas (aka Kamusin) who organized mostly all of it17:05
marjoKamusin: thx!17:05
pedro_Next Week we're having a Compiz bug day and we are looking for more hands to organize it17:06
pedro_so if you have some time and want to learn how to organize a bug day just drop your name on https://wiki.ubuntu.com/UbuntuBugDay/Planning17:06
pedro_also if you have some ideas about the next target don't be shy and add it to that page as well17:07
* fagan will volunteer next week busy with college17:07
pedro_fagan, awesome! thanks17:07
pedro_marjo, that's all from here17:07
marjofagan: thx; glad to know you have the right priorities!17:07
fader_marjo: I thought the right priorities were QA > sleep > food > studying17:08
fader_:)17:08
pedro_sleep? food? what for?17:08
pedro_:-P17:08
fader_Hehe17:08
marjofader_: we need to talk privately :) for me to give you some needed advice17:08
faganfor me is food>college assignments>classes>everything else :D17:08
marjo[TOPIC] QA mailing list -- fader17:09
MootBotNew Topic:  QA mailing list -- fader17:09
fader_So with our recent discussions around transparency and involving the community more, I have realized we don't have a good venue to discuss general QA topics17:09
fader_There is a QA team mailing list on LP, but it seems to be older and has some entry requirements:17:10
fader_(And I lost the URL, hang on :) )17:10
fader_https://launchpad.net/~ubuntu-qa17:10
marjofader_ : lack of sleep...17:10
fader_stgraber is the owner of this, so I was hoping he might be able to tell us a bit about the rationale behind it being somewhat restricted17:10
fader_And to see if anyone else thinks it would be useful to have a general QA mailing list to discuss what needs tested and how to improve practices17:11
bdmurrayI was looking at this last week or so17:11
davmor2ubuntu-qa@lists.ubuntu.com this one you mean17:11
arafader_, the team is moderated, but the list is open https://lists.ubuntu.com/mailman/listinfo/Ubuntu-qa17:11
fader_ara: Ah, I interpreted the team being moderated to mean the list was as well, thanks17:11
bdmurrayhttps://lists.ubuntu.com/archives/ubuntu-qa/2008-July/000166.html17:12
marjofader_ : so no need for yet another mailing list, right?17:12
fader_Is this something we can/should point people to when they are interested in helping to test Ubuntu?  I'd be happy to help point people there and make announcements as we need tests17:12
marjofader_: yes, please17:12
davmor2marjo: no just utilise the one we already have :D17:12
fader_marjo: I'd say no, assuming everyone is happy using this existing list17:12
faganisnt it because we own the sru tools17:12
marjothat should be part of our community outreach for testing17:13
fader_Excellent, I'll send people there whenever they look like they can be tricked into helping us test. :D17:13
arafor the testing team we are going to have ubuntu-testing mailing list17:13
marjook, so from now on, we will use that list to get the word out to a broad audience17:14
fader_ara: What is the goal of that list?  How is it going to be different from the QA team list?17:14
marjoara: can't you also announce to the qa list we're talking about? more, the merrier, no?17:14
faganId like to have one main list rather than a QA list and a testing list17:14
fader_+1, unless ara has a legitimate reason to split the two17:15
araI wanted to have a sense of team, as the bugsquad. ubuntu-testing for team discussions17:15
faganFragmentation is bad when the teams are small17:15
marjofagan: i'm thinking of the QA list as covering a broader audience, while the testing list is for testing only17:15
marjofagan: but we want to expand the community from small to bigger17:16
fader_Is there anyone interested in the QA list that would not be interested in testing?17:16
* fagan doesnt think so17:16
marjoi ASSume QA list > testing list, no?17:16
fader_I'd hate to have to join two lists and post/see the same information twice :)17:16
marjofader_: oic17:16
faganI think we should revisit it when the testing team gets bigger17:16
fader_Again, maybe I'm missing a use-case, but I agree with fagan on this one17:17
arafader_, but, again, we can keep ubuntu-testing as internal discussion of the team17:17
faganMost of us are on IRC anyway17:17
faganI see ara's point though17:17
arafader_, not for announcements, but for things like, who is going to update the wiki for blah, blah, blah17:18
fader_Ahh, I see -- so have the QA list be very general for announcements and such, but the 'real work' gets done on the testing list?17:18
arafader_, the testing work yes17:18
faganSure then17:19
marjoi thot one of the problems we were trying to solve was to announce things like ISO testing and want to reach a broad audience?17:19
fader_ara: I see.  That sounds reasonable :)  I'd still personally vote for starting with one list and splitting off a second if it's needed, but I won't fight too hard. :)17:19
marjotherefore, use the QA list in addition to testing list17:19
sbeattiemarjo: sure, that's a typical thing to announce.17:19
fagan+1 then too17:20
fader_marjo: My worry is that anyone who will do ISO testing needs to be on the testing list anyway, to coordinate17:20
marjofader_ : yes, of course17:20
sbeattiepersonally, I'd like to see the QA team list get more discussion traffic as well.17:20
marjoso, your concern is the dup of info, right?17:20
fader_marjo: So basically, everyone has to be on both lists anyway, right?  That's what I'm trying to avoid, having two lists that are interdependent; why have them?17:21
araI don't mind using ubuntu-qa list, I just prefer the -testing term :)17:21
fader_Heh so maybe a name change is in order :)17:21
arafader_, no, no worries17:21
arafader_, if it is going to be a testing discussion on it, ubuntu-qa seems good to me17:22
marjoara: if that's the case, let's just use ubuntu-qa list17:22
davmor2Very quickly I think the ubuntu-qa mailing list was one of laserjocks implementations to improve qa involvement17:22
marjodavmor2: well then we've just rediscovered the original intent which remains the same today!17:22
marjobrilliant!17:22
aradavmor2, yes, but now it is just a list of mails from people asking for CDs :D17:22
sbeattiedavmor2: the list predated the team, the team was the "improve involvement" bit.17:22
davmor2ubuntu-testing ties into the main irc channel etc so it might be better to drop the qa in favour of the general testing17:23
marjodavmor2: no!17:23
fader_davmor2: Or use #ubuntu-quality more :)17:23
fagandavmor2: QA is the umbrella for testing17:23
marjoto me, QA includes bug management and testing17:24
marjofagan: agree!17:24
fader_At any rate, I think there is agreement that we should at least be using the list we have now, and that we might need a second one in the future.  I propose that we try to use the existing list and encourage people to sign up for it and discuss this further on-list as warranted.17:24
faganfader_: +117:25
* fader_ hustles off to sign up for the mailing list.17:25
marjofader_: just to be sure, what "list we have now" are you proposing?17:25
fader_marjo: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa17:25
faganubuntu-qa marjo17:25
marjook, so the decision is:17:26
marjoContinue to use: https://lists.ubuntu.com/mailman/listinfo/ubuntu-qa for QA related announcements and discussions17:26
marjoeveryone agree?17:26
cr3+117:26
fader_+117:26
faganbut we have to promote the list too17:26
davmor2+117:27
ara+117:27
fagan+117:27
fader_fagan: Definitely! :)17:27
on3_g+117:27
bdmurray+117:27
schwuk+117:27
sbeattie+117:27
pedro_+117:27
marjofagan: yes, i think that was a major part of the problem; no promotion of the list, so it was not well used17:27
marjoanything else on this topic?17:28
* fagan puts a planet post about the ubuntu-qa team on his todo list17:28
fader_marjo: Not from me; I'm happy.17:28
fader_fagan: Good idea; I'll blog about it as well.17:28
marjofader_: thx for bringing it up and taking the lead17:28
fader_np17:28
marjowow, such a lively discussion17:29
marjoi love it!17:29
marjook, any new topics for today?17:29
davmor2fader_, schwuk: should there be a quick link to the mailing list from the main ubuntu-qa page if there isn't one17:29
=== DKcross is now known as TDKcross
faganI think for the launchpad team we should keep it moderated and maybe make a new team for beginners17:29
fader_davmor2: There's not now AFAIK...17:29
faganLike what the docs team did a while back17:30
on3_gfagan: +117:30
schwukdavmor2: ok17:30
davmor2it'll help promote it with a minimum of work17:30
fader_fagan: That might be a good topic to discuss on-list, as maybe someone can fill me in on the purpose of the group(s) there :)17:31
on3_gi think info for beginners is poor17:31
marjofagan: can you please remind us of what the "docs team did"?17:31
fader_on3_g: +117:31
marjofolks: remember one of the outcomes at UDS was:17:31
* kamusin on3_g +117:32
marjomake it simple for the community to get involved, step 1, 2, 3...17:32
on3_gand info for another distro flavors like xubuntu and kubuntu (especially) too17:32
faganWell the documentations team has two parts the main team thats open and the commiters team for really active people it gives new contributes something to aim for17:32
marjofagan: oic17:32
on3_gmarjo: +117:33
marjoand they find it to be effective?17:33
faganYep17:33
faganPlus the moderated team can own SRU tools..etc17:34
arain any case, I would keep the testing team for people willing to test17:34
faganara: thats a given17:34
marjoara: agree17:34
ScottKGenerally I  think it would be good if the QA team considers itself working on Ubuntu the project, not just Ubuntu the distro.17:34
ScottKThat would encompass the other flavors as well (even if they get less resources from Canonical)17:35
faganScottK: we do test kubuntu and xubuntu as well17:35
ScottKfagan: I'm aware17:35
=== TDKcross is now known as DKcross
ScottKIt's just that when you say it's the Ubuntu QA team, think of Ubuntu the project, not Ubuntu the distro.17:36
davmor2ScottK: I don't but I only had time to rewrite the ubuntu desktop/installer/server testing docs so none really exist for kubuntu etc yet :(17:36
on3_gfagan: but all the info is related to ubuntu the distro17:36
faganon3_g: well im sure I saw on qa.ubuntu.com kubuntu isos to be tested17:37
davmor2on3_g: see above17:38
on3_gfagan: that's rigth but, is not just about iso testing17:38
marjoon3_g: the charter for the QA team is:17:39
marjoThe Ubuntu QA team is focused on developing tools, policies, and practices for ensuring Ubuntu's quality as a distribution as well as providing general advice, oversight, and leadership of QA activities within the Ubuntu project.17:39
faganI thought kde upstream has a very extensive qa process17:40
* fagan has got to go for dinner but will pick up the logs from the rest of the meeting17:41
fader_Maybe improving some of these test cases would be a good starting point for people looking to help but who don't know where to start.17:41
davmor21 query I have about upgrades dapper is pretty much coming to end of support isn't it should we be looking at doing upgrade from dapper-server to hardy-server aswell as hardy->lucid?17:42
on3_gmarjo: ok17:43
sbeattiedavmor2: yes, that's part of the LTS upgrade testing plan17:43
marjofader_ agree17:44
sbeattiedavmor2: at least, walking through dapper -> hardy -> lucid, and finding issues anywhere along the path.17:44
bdmurrayand we can start dapper to hardy testing now! ;-)17:44
sbeattieindeed! That's another excellent place for people to start.17:45
davmor2sbeattie: I just meant ensuring that dapper would upgrade to hardy still and separate hardy->lucid tests.  Being as if a user is still on dapper it's for a reason so they'll probably only want to upgrade to hardy rather than lucid17:46
marjodavmor2: you're probably right, so we should take that into account17:47
marjofor the upgrades test matrix17:47
marjoi think we have to be smart about upgrades testing because of the potentially humongous problem space17:49
marjoyet, aim for largest possible test coverage17:49
davmor2sbeattie: maybe me and you can get together tomorrow afternoon (for me) morning (for you) and trash out a plan?17:50
ScottKOne problem we had Dapper -> Hardy was that most of the testing was done on Main upgrades, but Universe packages failing can affect the overall upgrade success.17:50
marjoScottK: yes, that's part of the being smart concept17:51
ScottKRight, just mentioning it since a lot of the people here weren't around then.17:51
on3_gdavmor2: for begginers something like http://live.gnome.org/GnomeLove wil be great17:51
marjothe challenge is to plan ahead of time which paths to take17:51
sbeattiedavmor2: I unfortunately have conflicts tomorrow, but perhaps we can take it to email? I do want to explore this.17:51
davmor2sbeattie: no worries dude17:51
marjook, folks, we're down to 8 minutes17:52
marjowe should continue this sort of discussion as we solidify test plans for lucid17:52
marjofolks: anything else for today?17:53
marjoif not, i propose we adjourn the meeting17:54
fader_Just a reminder that A1 is next week... get ready for testing!17:54
davmor2not here17:54
davmor2working iso's would be good for that :)17:54
fader_davmor2: agreed :)17:55
marjogoing once17:55
marjotwice17:55
marjomeeting adjourned17:55
marjothx everyone for your participation!17:56
cr3cheerio folks!17:56
arathanks!17:56
marjosee you next week17:56
fader_Thanks all!17:56
sbeattiethanks, everyone!17:56
marjo#endmeeting17:56
MootBotMeeting finished at 11:56.17:56
davmor2thanks all17:56
=== fader_ is now known as fader|lunch
=== nik0 is now known as niko
=== fader|lunch is now known as fader_
popeyBONG!20:00
jcastrowoo20:00
popeyLoCo Council meeting time20:00
keffie_jayx:D20:00
JanC20:00
nizarusoh the big BONG :)20:00
huatspopey, I am :)20:00
popeyczajkowski / huats / itnet7 Welcome! - new members of the Ubuntu LoCo Council!20:01
huatspopey, thanks !20:01
itnet7Thanks!20:01
czajkowskithank you :)20:01
popeyhttps://wiki.ubuntu.com/LoCoCouncilAgenda is our agenda20:01
popeyReady to begin?20:02
huatspopey, I am around at the beginning while I am eating20:02
=== RoAk is now known as RoAkSoAx
huats..20:02
popeyhttps://wiki.ubuntu.com/LoCoTeamContact/ProposedAddition20:02
huatsbut I am ok20:02
popeyProposed addition to the loco team contact as clarification.. anyone got any comments about that?20:02
popeyThis came about after we discovered some LoCo teams actively _discouraged_ communication between the LoCo Contacts list and their own LoCo20:03
popeywe want to discourage that discouragement :)20:03
czajkowskiindeed!20:03
huats:)20:04
itnet7I think it's a great action!20:04
itnet7and really should have went without saying!20:04
itnet7:-)20:04
JanCloco contacts can decide if something is not useful for their team maybe, but all important info should be forwarded20:04
popeyyeah, thats trickey, deciding what's important20:05
popeyI propose that we add that to the wiki, then announce it on loco-contacts.20:05
nizarusJanC, I'm a loco contact and that's what I'm doing20:05
czajkowskiyou could also encourage your loco team members to join the list.20:05
popeyhuats / czajkowski / itnet7 / keffie_jayx / JanC - +1 or -1 on the change?20:06
czajkowski+120:06
itnet7+120:06
JanC+120:06
huats+120:06
keffie_jayx+120:06
popey\o/20:06
keffie_jayxexcellent20:06
czajkowskilovely jubbly20:06
popeyNext we have "Introducing new members"...20:07
popeyczajkowski / huats / itnet7 - Welcome again - want to give us one line about yourself for the minutes?20:07
huats(it might be better for me to get it last)20:08
czajkowskiAloha, I'm laura, based in Dublin Ireland and looking forward to getting involved in the loco council and helping where I can20:08
popey\o/ czajkowski20:08
* itnet7 is team contact for FloridaTeam and glad to be here!!!20:08
popey\o/ itnet720:08
itnet7:-)20:08
huatsOK so, I am Christophe, a french little guy and I am really really hapy to be amongst you all :)20:09
popeyyou are _so_ not little!20:09
huats(even jono ;))20:09
czajkowskihardly little20:09
popey\o/ huats20:09
itnet7lol ;-P20:09
czajkowski^5 itnet7 huats  :)20:09
popeyI'm working on getting you guys on the mailing list20:09
huatsthanks popey20:09
keffie_jayxhe is the one from the 5000-attendee parties organized by the frech teams20:09
popeysorry it's not happened already20:09
jonohey huats20:09
popeykeffie_jayx: you mean 20,000 attendees!20:09
popey(that number increases every time I see it)20:10
keffie_jayxpopey:  right right 5000 is only in his home bash20:10
huatspopey, ;)20:10
popeyOk, next keffie_jayx you have "Reproval process progress" on the agenda..20:10
keffie_jayxright...20:10
huatskeffie_jayx, actually my hometown party is this weekend but it won't be that big :)20:10
czajkowskihuats: only 500 :)20:11
hollmanHello all20:11
huatsczajkowski, that is the aim :)20:11
keffie_jayxso as we know, we have been working on getting a reapproval process in the life of LoCo Teams to learn more from you and offer assessment20:11
keffie_jayxwe declared some actions at the meet up at UDS20:11
czajkowskiyes I've the action of writing this up :)20:11
keffie_jayxit is sane to seewere we stand with regards the reaproval process.20:12
popeyok20:12
popeyI just grabbed the list out of gobby and pasted onto the wiki..20:12
popeyhttps://wiki.ubuntu.com/LoCoCouncil/ProposedTeamApprovalList20:12
popeyI haven't checked the sanity of that list (my action - will do asap)20:12
JanCshit, we're on top  ;)20:12
itnet7JanC: we're not far below you20:13
popeyJanC: no editing of the wiki and moving yourself!20:13
popey:)20:13
nizarustunisian team is missing20:13
popeynizarus: no, it's not20:13
huatsJanC, and we are not on the list :(20:13
popeynizarus: it's the _re_ approval list20:13
keffie_jayxnizarus: many teams are missing ;)20:13
keffie_jayxthis is only 3020:13
keffie_jayxout of 60 something20:13
JanCnizarus: you were approved or reapproved not that long ago IIRC?20:13
nizaruspopey, i know we should be reapproved on july20:14
popeynot necessarily nizarus20:14
nizarusJanC, we was approved on july 200820:14
popeyteams will be reapproved when we get to them20:14
popeyit might not be july20:14
popeybut we'll let you know in advance :)20:14
nizarusokay20:14
popeyok, so keffie_jayx outstanding things are a) czajkowski documenting and b) me sanitising that list?20:15
czajkowskiyup20:15
keffie_jayxno20:15
popeyoh?20:15
czajkowskioh?20:15
keffie_jayxalso, make sure awareness of this process happnes20:15
popeyok, but we can't do that till it's documented surely?20:15
czajkowskiwell that'll surely happence once A is done and the mailed out ?20:15
keffie_jayxexactly20:15
czajkowskipopey: great minds!20:15
popeyczajkowski: .. drink guinness20:16
czajkowskiI have sense ;)20:16
keffie_jayxalso decide on the schedules for each teams, would be nice20:16
keffie_jayxmakes sense?20:16
czajkowskiyup20:16
popeyok so 1) document, 2) publicise 3) schedule, 4) ??  5) profit!20:16
czajkowski5) choclate :D white choclate and JanC is 1st on the list :p20:17
huatsczajkowski, 6) share that chocolate20:17
czajkowskipopey: keffie_jayx is this document started somwhere, or based on a document ?20:17
huats:)20:17
czajkowskihuats: eh no :)20:17
popeyI don't know.. keffie_jayx ?20:18
keffie_jayxczajkowski: it is only word of moth and some documentation is already available in gobby20:18
keffie_jayxlike the emailing process20:18
JanCI'm happy to buy 1 kg of chocolate to share on FOSDEM  :P20:18
popeyOk, I can work with czajkowski on that20:18
czajkowskigrand job20:18
keffie_jayxalso20:18
keffie_jayxwe agreed on doing this in meetings20:19
popeydoing what?20:19
popeythe re-approvals?20:19
keffie_jayxoposed to emailing the reaproval proposals no?20:19
popeywe did?20:20
keffie_jayxpopey: I though we had decided that emailingwas not working, but then again I might have misheard20:20
popeyah ok20:20
huatskeffie_jayx, don't you think it will be really long in meeting20:20
huatsfrom my understanding (at the previous UDS)20:21
popeyno, we decided to mail the teams 3 times20:21
JanCI think in the past we agreeded that reapproval through mail if possible would make meetings shorter20:21
popeyto let them know they're up for approval20:21
popeygive them a month to reply/prepare and attend an online meeting20:21
keffie_jayxpopey: and they email the reapproval aplication and that is it?20:21
popeyif they don't turn up they get unapproved20:21
keffie_jayxok20:21
JanCand teams could appeal during a public meeting if they don't agree with a decision20:21
popeyyup20:21
keffie_jayxok20:21
popeyduring a meeting is what we agreed20:22
popeythe key thing is getting them to the meeting20:22
popeywe need to word the mails carefully20:22
popeybut firmly :)20:22
keffie_jayxdefinetelly, sorry for making you lose time20:22
JanCokay then20:22
huatspopey, I agree20:22
popeyno, it's fine, we all need to be on the same page20:22
popeyso as part of the documentation we can come up with a template mail20:22
popeyDear $LOCO20:23
czajkowskithat'd make sense20:23
popeyTurn up or else.20:23
popeyLove Loco council!20:23
huatsbut I think that if we just say the truth : a reapproval is not a blame but a normal process...20:23
popeyyup huats20:23
czajkowskiaye and point out, every loco at some point or another will go through this process20:23
popeyyup20:23
huatspopey, or your mail + asking for 1 kg of chocolate each :)20:23
popey:)20:23
popeyI am easily bribed20:23
popeyjust putting that out there20:24
popeyok, so czajkowski and I will make a start on the documents, and run that past the mailing list okay?20:24
popey(loco-council)20:24
popeyso everyone gets a chance to contribute20:24
popeyand we'll also pass it by jono/jorge to make sure we're not doing anything dumb20:24
czajkowskiheh smart move20:25
=== hibana_ is now known as hibana
popeyis that all we need to say about reapproval for now?20:25
itnet7does anyone think it would save time to look at the lists of re-approvals, and evaluate the teams by a loco council vote, on whether or not a team needs to do their re-approval in a meeting?20:25
czajkowskiwhen do we hope to start20:25
itnet7and for those teams that are spot-on, we can do it through mail20:26
popeyitnet7: what, pre-re-approve them if they're obviously great?20:26
popeyI think it would be fairer if everyone had the same process20:26
itnet7ah20:26
czajkowskiI think so to, make it the same across the board. For everyone loco to see20:26
itnet7agreed20:26
popeywould be more open that way20:27
popeyany other re-approval comments?20:27
JanCstill, looking at & discussing their reapproval page beforehand might help meetings go faster20:28
keffie_jayxit would be good to have a timeline for things to happen20:28
keffie_jayxjust to keep track.20:28
keffie_jayxthis things tend to take sooo longgg20:28
keffie_jayxand emailing is not a nice tracker of time20:28
popeywell we said 3 mails in a month, invite, if they dont turn up, unapprove20:28
czajkowskiaye we did agree on that at UDS20:29
keffie_jayxbut our roadmap to begin reaprovals should be nice20:29
JanCpopey: 3 in a month, how many approved locoteams are there ?20:29
keffie_jayxI am being optimistic when I say we begin january next year20:29
popeyno JanC20:29
popey3 attempts to contact _one_ team in a month20:29
popeyno keffie_jayx20:29
JanCah, okay  ☺20:29
popey:)20:29
popeybut we could re-approve two (or more) in one meeting20:30
popeyit depends how prepared they are - and how good (or bad) they are20:30
JanCwe'd need to, otherwise reapproval of all teams will take 10 years  ;)20:30
popeyyeah, job for life :)20:30
popeyok, shall we move on?20:30
JanCk20:30
keffie_jayxwait20:31
huatskeffie_jayx, we might each contact 1 team20:31
huatsby month20:31
huatsit will reduce the time...20:31
keffie_jayxso no estimated time for reaprovals yet20:31
keffie_jayxno estimated time for the actions popey and czajkowski have?20:31
keffie_jayxsorry If I am pushy about this20:32
czajkowskiit shouldnt take long to document it, and then get some input and tweek it20:32
czajkowskipopey: ?20:32
popeykeffie_jayx: we dont have the documentation yet20:33
popeyits not promoted, no teams even know about this process20:33
keffie_jayxthis is key because if we have 30 teams to do in 6 months then time is not on our side20:33
popey(except maybe belgium)20:33
keffie_jayxpopey:  right, is it safe to reduce the number of teams to reaprove for this cycle?20:33
popeykeffie_jayx: what expectations do you have?20:33
popeykeffie_jayx: no, I think it's good to have a target20:34
keffie_jayxpopey:  my expectations are keep it simple20:35
czajkowskikeffie_jayx: I think we shoul d aim for the 30 and I'm hopeful we shall reach the target and if we fall short, then it's a learning curve for us as it's not been done before.20:35
popeykeffie_jayx: no, i meant your expectations of timescales20:35
keffie_jayxpopey:  I said january, it is a nice way to start20:35
keffie_jayxit gives us a month to organize docs and promote the process20:35
czajkowskikeffie_jayx: do you think we can get documentation and awareness out in time?20:35
popeysounds reasonable20:35
keffie_jayxczajkowski:  yes. it is really up to us and the teams20:36
huatssounds to me too20:36
keffie_jayxand once you email a team contact three times, you know we mean business ;)20:36
czajkowskiokie dokie20:36
keffie_jayxit is really up to us being constant20:36
popeyagreed20:37
popeyshall we move on?20:37
huatsok for me20:37
czajkowskisounds goo d20:38
popeykeffie_jayx / itnet7 / JanC ?20:38
keffie_jayxsure20:38
JanC+1 ☺20:38
popey"State of the LoCo Governance Docs"20:38
popeykeffie_jayx - another one of yours :)20:38
keffie_jayxsure20:39
keffie_jayxLoCo Docs are probably the best pieces of docs on the Ubuntu wiki. but I think there are other general aspects that need to be documented20:39
keffie_jayxfor instance. the LoCo Concil and its functions are not clearly detailed in the LoCoCouncil wiki page20:40
keffie_jayxthis leaves the people a bit confused about what we do20:40
keffie_jayxand we do alot20:40
keffie_jayxSo I take the initiative to document our actions20:40
keffie_jayxso that the community can have a better sense of what we do20:40
keffie_jayxI speak of this particularly https://wiki.ubuntu.com/LoCoCouncil20:41
keffie_jayxalso20:41
itnet7popey: I agree sorry... work stuff20:41
itnet7+120:42
keffie_jayxalso our interaction with the LoCo Community should be documented20:42
popeyok, I agree completely20:42
popeywhat do you propose we do keffie_jayx ?20:42
keffie_jayxI took the initiative to blog about LoCo Team Contact changes20:42
keffie_jayxand we could make this a LoCo Council thing to do20:43
keffie_jayxand not only LoCo Contact Changes20:43
keffie_jayxonce a new team is formed20:43
keffie_jayxonce a new team is approved20:43
keffie_jayxonces a new team is reaproved20:43
huatskeffie_jayx, it makes high sense to me20:44
popeyok20:44
keffie_jayxso documenting a bit on this will make sure people that follow after us20:45
keffie_jayxkeep this little gestures of sympathy going long after we are gone20:45
keffie_jayxalso there is a leadership code of conduct that we should make reference of in our docs20:46
JanCright20:46
keffie_jayxthe LoCo Docs do not make reference to that and it would be healthy to add it20:46
keffie_jayxmakes sense?20:46
popeyyes20:46
JanCcertainly20:46
keffie_jayxI can drive this documentation and open it up for coments20:47
popeyThat would rock20:47
itnet7sounds good keffie_jayx !20:47
czajkowskilovely20:47
popeyit would also help the newbies :)20:47
czajkowskigrin20:47
czajkowskiany help is welcomed20:47
keffie_jayxok20:48
popeykeffie_jayx: you going to co-ordinate that on the mailing list?20:48
keffie_jayxI am done the, I will report via email my rpgress20:48
popeyexcellent stuff20:48
keffie_jayxyes, email and wiki on the Lucid Roadmap20:48
popeyok20:48
popeynext up is nizarus20:48
nizarusهنا /o\20:49
popey:)20:49
nizarushi20:49
czajkowskialoha20:49
nizarusso I'm from the tunisian LoCo Team20:49
popeynizarus: you were asking about setting up a legal entity to promote Ubuntu in Tunisia right?20:49
nizarusand we was approved on July 2008 https://wiki.ubuntu.com/LoCoCouncilAgenda/2008072220:49
nizarusyes popey20:50
popeyok, there was a reply from the cc, but I now see that you didn't see that..20:50
popeyone moment.20:50
nizaruspopey, haven't recieved it20:50
popeyThis is the reply from Mark Shuttleworth..20:50
popey"I agree with the sentiment that a legal entity is only appropriate in the most exceptional cases. Of course Canonical can't stop anyone from forming a legal entity: if you want to do that, and you have the required resources and competence, then go ahead. You would need a trademark agreement to call it an Ubuntu entity, but that can be granted using the template you have."20:50
popey"The most important thing to think about is how to wind down such an entity. Keeping a legal vehicle alive is a lot of work. It's a bit like a puppy - everyone wants one, not everyone is good at looking after the dog it grows into! Think carefully about it - there are real legal consequences for not responding to paperwork and administration in most countries if you are responsible for a legal entity, and Canonical cannot help."20:51
nizaruspopey, we know the consequences and we are ready to do it20:52
JanChttp://verein.ubuntu-de.org/files/agreement.pdf --> is an example of the agreement with Canonical you'll need to sign20:52
nizarusJanC, I got your document20:53
JanC(might be different but something like that)20:53
huatsthis is the document we (ubuntu-fr) have signed20:53
JanCmaybe huats knows if the French agreement is on-line too20:53
nizarussince 2 monthes i contacted canonical for trademak agreement20:53
nizarusbut no response20:53
huatsJanC, actually it is not online afaik20:53
nizarusthat's why i'm here20:53
huatsbut it was the same that was signed with ubuntu-fr20:54
huats(they both have been signed at the same time)20:54
popeynizarus: sadly the loco council cannot do anything about the responsiveness of the canonical trademark team20:55
sshdhi20:55
nizaruspopey, I see, but if there is any tips20:56
nizarus:/20:56
czajkowskinizarus: tips on ?20:56
nizarushow to contact canonical and got fast response :)20:57
popeybe patient and polite, thats my tip :)20:57
JanCmaybe if we put what sabdfl said on the wiki so that you can reference it, that might make sense20:57
nizaruspopey, patient for more 2 monthes ?20:57
popeynizarus: when did you last mail them?20:57
popeyI believe the trademark 'team' is quite small20:58
popeyand ubuntu is "quite big"20:58
nizaruspopey, I used the trademark contact form since 2 mothes20:58
czajkowskiand ~i'm sure it gets a lot queries20:58
JanCmaybe we can ask Canonical how long people should expect to wait?20:58
popeynizarus: I would contact them again20:58
popeynizarus: simply ask for an update20:59
nizarusand i got a confirmation with an information that i will have a response in 48 hours20:59
czajkowskinizarus: as popey pointed out, there is nothing we can do about the responose of canonical. Perhaps mail asking for an update to the situation20:59
JanCand ask what details peopel should include in their mail to avoid losing time?20:59
huatsnizarus, I have contacted the trademark team a few time20:59
huatsand I have waited about 2 months already20:59
ScottKnizarus: I'd suggest reviewing the bugs here: https://bugs.launchpad.net/ubuntu-community and filing one if you think it's needed.20:59
nizarushuats, you have a direct mail ?20:59
huatsnope21:00
nizarus:/21:00
huatsI have used the form too21:00
popeyi emailed them directly21:01
nizaruspopey, which adresse21:01
popeytrademarks @ ubuntu dot com21:01
nizarusthank's popey21:02
popeywhen I asked, I got a reply same day :S21:02
popeythat was over a year ago though21:02
popeythings have changed since then21:02
nizarusI will resent my mail and cc you21:02
popeyno need to cc me21:02
popeythere's nothing the loco council (or I) can do about canonical trademark issues21:02
popeyok, we're over time21:03
nizarusok21:03
popeyjcastro...?21:03
nizarusthx all21:03
huatsno pb nizarus21:03
jcastroyep21:04
popey"LoCo Week and LoCo Doc Day"21:04
jcastropopey, so basically21:04
popeyis it quick?21:04
jcastroI have no time to do this this cycle21:04
jcastroand was wondering if we still want to do this21:04
jcastroand if anyone is interested in driving?21:04
keffie_jayxjcastro:  I am21:04
czajkowskijcastro: I'm not familiar with it ?21:04
popeycan you mail the loco council about it?21:05
popeyas we're already over time21:05
jcastroyep21:05
huatsjcastro, same than czajkowski I don't know the idea21:05
jcastrono worries21:05
keffie_jayxjcastro:  there hasn't been a LoCo week ever, so this would be a first time21:05
jcastroright21:05
keffie_jayxjcastro:  LoCo Docs there was one in the Jaunty cycle21:05
jcastroit's one of those "been sitting on the backburner" ideas21:05
jcastroyeah21:05
keffie_jayxwhich was about a year ago21:05
jcastroI will send mails so I don't take up anymore time!21:05
popeyjcastro: as czajkowski / huats / itnet7  aren't on the loco-council mailing list *hint* *hint* can you To: them too please21:06
itnet7:-P21:06
keffie_jayxjcastro:  I am interested in docs day, since one of my previous items was based on that21:06
czajkowskijcastro: thanks21:07
popeyyeah, could be very helpful for that keffie_jayx21:07
jcastropopey, yeah21:07
keffie_jayxjcastro:  I think the LoCo Council needs to have clear what a LoCo Week is21:07
jcastroyeah21:07
popeycan we take it to the mailing list21:07
popeytick tock21:07
keffie_jayxor what the horsemen21:07
keffie_jayxthink21:07
keffie_jayxright right out of time21:07
czajkowskithanks folks21:07
keffie_jayxthanks21:07
jcastro\o/21:07
keffie_jayxgreat meeting21:07
popeywoah.. hang on21:07
czajkowskioh21:07
popeywe're over time and we have a team approval21:08
czajkowskipopey: is there another meeting on now ?21:08
huatspfff it is my first ubuntu meeting that is almost on time :)21:08
popeydrakulavich and sshd are here21:08
popeyno czajkowski21:08
czajkowskiI cna stay21:08
yltsrcyltsrc too21:08
czajkowskican others?21:08
huatsI can stay too21:08
czajkowskiitnet7: keffie_jayx huats JanC ?21:08
JanCno problem for me21:09
keffie_jayxI can stay21:09
czajkowskipopey: ?21:09
popeyok21:09
czajkowskinot to leave you out21:09
czajkowski;)21:09
popey30 mins past is the deadline21:09
popeyso we have 20 mins21:09
itnet7I can stay21:09
czajkowskigrand lets shoot21:09
keffie_jayxlet's do it21:09
popeyok .. before we start21:09
popeyit's probably best that one person leads this process, we don't want to have loads of questions bombarding the Belarus guys and gals..21:10
popeyvolunteer?21:10
* czajkowski sits back and watches this time21:10
popeyok, keffie_jayx ?21:10
huatspopey, may be an experience people might be better21:10
keffie_jayxme21:10
huats..21:10
popeygreat!21:10
keffie_jayxalright21:10
popeyhttps://wiki.ubuntu.com/BelarusTeam21:10
keffie_jayxAnyone here from the Belarus Team?21:11
yltsrcyes :)21:11
drakulavichme too21:11
sshdand me )21:11
keffie_jayxgreat :D21:11
keffie_jayxdo you have an approval aplication21:11
keffie_jayx?21:11
popeyhttps://wiki.ubuntu.com/LoCoGettingApproved is the process by the way21:12
yltsrcyes http://wiki.ubuntu.com/BelarusTeam/ApprovalApplication21:12
keffie_jayxok21:13
keffie_jayxyou have been doing release parties for how long?21:13
develop7me too21:13
yltsrcwe have release parties till 8.10 release21:14
yltsrc* since :)21:14
sshdwe have some release party21:14
keffie_jayxand it read that you have been participating with other lugs from the regions, can you describe further your itneraction with other teams in belarus21:14
sshd8.04, 8.10, 9.04, 9.1021:15
keffie_jayxany pictures :P21:15
sshdkeffie_jayx: in lvee, we connect with other lug from belarus21:16
sshdkeffie_jayx: lvee.org21:16
keffie_jayxsshd:  what is your colaboration particularly21:16
drakulavichhttp://picasaweb.google.com/antono.vasiljev/LVEE2008#21:17
JanCLVEE sounds cool21:18
keffie_jayxI ask about lug colaboration becasue your resource site make no reference about being a LoCo Team21:20
keffie_jayxunless it is not your site, just a refrenece site from belarus?21:20
keffie_jayxanyone?21:21
JanCkeffie_jayx means http://linux.by/21:22
czajkowskiyltsrc: drakulavich sshd ?21:22
keffie_jayx?21:22
yltsrcwe have not lug site, but we have separated forum on http://linux.by21:22
yltsrcand http://ubuntu.ru21:22
keffie_jayxthat's what I thought21:23
yltsrcbecause most of us russian-speaking and we provide support with russian team21:23
keffie_jayxhow many active members are there, and how many have secured Ubuntu membership?21:24
yltsrci am not sure, but all of us, who on http://launchpad.net/~belarus21:25
yltsrcand maybe more21:25
keffie_jayxyltsrc:  anyone seeking ubuntu membership that you know of?21:26
yltsrcwhat do you mean?21:27
drakulavichyou mean ubuntu developers?21:27
popeyOk. I am going to have to say -1 for now. I'd like to see a more comprehensive application, one which meets the criteria set out in https://wiki.ubuntu.com/LoCoGettingApproved21:27
keffie_jayxyltsrc:  ubuntu membership is for individuals that have contirbuted considerably to the Ubuntu Community. http://wiki.ubuntu.com/Membership21:28
popeyIt would be great if you could improve the application with more detail, reports and summaries of events before you come back to us for approval.21:28
keffie_jayxI agree with popey21:28
czajkowskiI'm also going to say -1, and would like to see more Ubuntu participation evidence, but would love to see you come back in a few months.21:28
itnet7-1, I do really like what you all have started though, and would like to encouarge you to tread on21:29
keffie_jayxI think your team has strated the process of consolidating a team but you still need to make sure your team can be functional with it's own resources,21:29
yltsrci think we haven't any ubuntu member21:29
keffie_jayxthe work you have done n events seems fantastic21:29
huatsSorry guys but my vote is also -1. I'd like to have more pics, and a clearer view of how you are exchanging on a daily basis21:29
itnet7definitely, good work so far!21:30
huatsI do think you have done a good start so far21:30
keffie_jayxyltsrc:  we hope to see you again in say 6 months time and we can evaluate your progress21:30
huatsyou need to continue !21:30
drakulavichthanx, guys. We'll be back :)21:30
huatsdrakulavich, we count on that !21:30
keffie_jayxkeep it up belarus21:30
keffie_jayx:D21:30
popeysorry it ended up being so late for you guys!21:30
czajkowskidrakulavich: good to hear21:31
popeyok, thats the end of our meeting21:31
itnet7no problem, can't wait to see good things in the future for belarus!21:31
keffie_jayxsorry for that too21:31
popeythanks keffie_jayx / czajkowski / JanC / itnet7 / huats21:31
keffie_jayxalrighty21:31
keffie_jayxminutes by me21:31
itnet7ty popey !21:31
keffie_jayx;)21:31
popeythanks keffie_jayx21:31
popeykeffie_jayx: you got the log?21:32
czajkowskilovely jubbly folks ;)21:32
keffie_jayxdrakulavich, sshd, yltsrc see you agian friends.. :D21:32
keffie_jayxpopey: yep21:32
yltsrcthanks, we'll be back :)21:32
huatsthanks guys !21:33
huatsthat was a great first meeting :)21:33
keffie_jayxawesome21:33
keffie_jayxnew council members rock21:33
keffie_jayxnow21:33
keffie_jayxnext meeting after the holidaysright21:33
keffie_jayxI suggest Europe friendly time21:33
* popey goes to beg for forgiveness from his wife21:33
czajkowskipopey: bring ice cream21:34
popeythis time suits me fine, any time from 20:00 UTC onwards21:34
keffie_jayxpopey:  good luck my friend, hope you don't end up in the couch tonight21:34
popeyczajkowski: i just had some :)21:34
popeyhaha21:34
popeyo/21:34
czajkowskipopey: for your wife!21:34
huatsit is good for me too21:34
czajkowskisuits me grand21:34
huatsthe ONLY thing that might bother me is that the baby is expected at the end of january...so who knows...21:35
huatsbut I will let you know of course :)21:35
czajkowskihuats: congrats !21:38
huats:)21:39
huatsthanks czajkowski21:39
czajkowskihuats: do you know if it's a girl or boy yet?21:39
huatsczajkowski,  a little boy...21:39
huatsso that I can train him to be a good rugby player21:40
huats;)21:40
huatsczajkowski, because I have seen your nice msg on facebook last week after the all blacks game ;)21:40
czajkowskiheheh21:42
czajkowski#;d21:42
czajkowskiyes21:42
czajkowskiyou did *ahem* get punished21:42
czajkowskihowever I had dan cater and chabal on the pitch, I was happy21:43
huats:)21:44
huatsI haven't seen the game yet21:44
huatsit was the night of the Ubuntu Party in Paris21:44
huatsso I have taped it21:44
huatsI think I'll have a look next week21:44
czajkowskido Ireland wasn't beaten once in 2009 :D21:46
huatsczajkowski,  :)21:48
=== Riddelll is now known as Riddell
=== nizarus_ is now known as nizarus
=== fader_ is now known as fader|away
=== mkv is now known as m4v

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