/srv/irclogs.ubuntu.com/2009/06/10/#launchpad-meeting.txt

=== Edwin_ is now known as EdwinGrubbs
henningeHi jtv!14:59
jtvhi henninge!15:00
daniloshi jtv!15:00
daniloshi henninge!15:00
abentleyHi danilos, jtv, henninge!15:00
* mars wonders if he has the right meeting - looks like translations15:01
jtvhi abentley!15:01
daniloshi abentley!15:01
rockstarHey, code's here too!15:01
jtvmars: we arrive by team now, like the Olympics15:01
henningeHi rockstar!15:01
danilosok, ok, we can stop this :)15:01
abentleyHi rockstar!15:01
abentleyHi mars!15:01
marsjtv, heh, so who gets to light the MootBot flame?15:01
danilosheh15:01
marshi abentley!15:01
* jtv plots out n² for some ballpark values of n15:02
bachi barry?15:02
rockstarIt's really early for me.  This is my least favorite meeting of the week.15:02
sinzui1barry lost his connection 3 minutes15:02
sinzui1ago15:02
=== sinzui1 is now known as sinzui
marsrockstar, could be worse - look at thumper's TL calls :)15:02
rockstarmars, yes, those would be even worse.15:02
marsbarry!15:09
barryirc sucks for me today15:09
barrysorry15:09
sinzuibarry: your back for our meeting?15:09
barry#startmeeting15:09
MootBotMeeting started at 09:09. The chair is barry.15:09
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:09
barryhi everyone.  who's here today?15:10
EdwinGrubbsme15:10
jtvme15:10
BjornTme15:10
marsme15:10
bacme15:10
henningeme15:10
abentleyme15:10
adeuringme15:10
gary_poster_me did not send the email *and* is not around for to give reviews today, again.15:10
jtvand danilos, too15:10
gmbme15:10
danilosme15:10
* mars pokes flacoste15:11
flacosteme15:11
barrygary_poster_: ack15:11
salgadome15:11
barryallenap: ping15:12
barrycprov: ping15:12
allenapme15:12
cprovme15:12
sinzuime15:12
barrygmb: ping15:12
barryoops, gmb sorry15:12
gmbstill me...15:12
barrynoodles775: ping15:12
barryrockstar: ping15:13
noodles775me :)15:13
rockstarme15:13
barry[TOPIC] agenda15:13
MootBotNew Topic:  agenda15:13
barryvery light day today i thik15:13
barry    * Roll call15:13
barry    * Action items15:13
barry    * Mentoring update15:13
barry    * Peanut gallery (anything not on the agenda)15:13
barry[TOPIC] mentoring update15:13
MootBotNew Topic:  mentoring update15:14
barryanything to report ?15:14
henningeI hear I graduated?15:14
adeuringyes, that's at least my proposal15:14
henningeSorry for missing last week's meeting ...15:14
barryhenninge: you did. i will send out the announcement today.  congratulations!15:14
cprovbarry: noodles775 is almost there.15:14
barrycprov: fantastic15:14
henningebarry, adeuring. Thank you!15:15
jtvbarry missed the opportunity for a cruel joke there15:15
barryjtv: :)15:15
barryhenninge: you can switch from euro/friday if you want15:15
henningeanybody any suggestion?15:15
barryhenninge: we have good euro coverage, so it's up to you.  if anyone else wants to switch, that's fine too15:15
barryi just want at least one person for each euro day15:16
henningeI think I had look a Tuesdays15:16
barryand remember al-maisan is on loan to ubuntu15:16
barryhenninge: cool, just ping me when you decide15:16
henningeok15:17
barrywho is currently /not/ a reviewer (other than team leads)?  i know about deryck and leonardr15:17
jtvbarry: I'm a reviewer but without OCR slot15:18
jtv(was holding this for the peanut gallery)15:18
barryjtv: let's get you a slot!15:18
henningebarry: noodles775 and me were the only ones when we started.15:18
barryjtv: what would work for you?15:18
henningebarry: so since onyl deryck has joined lately, I guess that is all.15:19
jtvbarry: working day when I'm here starts 06:00 UTC.15:19
barryhenninge: right.  and deryck has started doing js reviews15:19
jtvany glaring holes in the schedule for the hours after that?15:19
barryjtv: so america probably doesn't work for ya :)15:20
jtvbarry: nyet, comrade15:20
barryjtv: we have two wholes in asia on tuesday and wednesday15:20
jtvbarry: oh, you're beginning to spell like an Asian15:20
barryjtv: but other than that we have pretty good coverage.  you're always welcome to double up on a euro slot15:20
danilosjtv, henninge: it would be nice not to have you guys taken up on the same day to OCR15:21
barryjtv: sorry, i meant too hoales15:21
henningedanilos: I was just thinking that15:21
jtvbarry: ohh, hoales15:21
intellectronicame (apologies for joining late)15:21
jtvso we're looking at a swap, not a hole15:21
jtvs/at/for/15:21
gmbjtv: How about Tuesday?15:22
* gmb just wants an easier life ...15:22
barrygmb: or henninge on tuesday and jtv on friday?15:22
jtvgmb: yes, that would work15:22
gmbEither way works for me.15:22
henningeme on tuesday, jtv on wednesday.15:22
jtvbarry: disadvantage of friday is: one needs-reply can bump your branch across my weekend.15:23
henningefriday gets pretty crowded, too.15:23
henningereviewer-wise15:23
jtvwhich is just great for week 3's15:23
henningeyeah15:23
barryjtv, henninge why don't you guys work it out.  i'm fine with whatever you decide, just let me know15:24
barryi do think friday is well covered either way15:24
jtvbarry: aye-aye15:24
barrythanks!15:24
henningebarry: me on tuesday, jtv on wednesday. My favorite.15:24
barryhenninge: works for me.  jtv?15:24
jtvhenninge: shall we do this out-of-channel?15:24
jtvoh15:24
jtvyeah, sure15:24
barry[AGREED] henninge to move to euro/tue, jtv to euro/wed15:25
MootBotAGREED received:  henninge to move to euro/tue, jtv to euro/wed15:25
* jtv conspicuously fails to race to the needs-review queue Right Now15:25
barry[TOPIC] peanut gallery15:25
MootBotNew Topic:  peanut gallery15:25
barryanybody have any topics not on the agenda?15:25
flacostemars:15:26
flacoste?15:26
noodles775Maybe the import error lint (F040...)15:26
barrynoodles775: can you elaborate?15:26
marsbarry, I have one15:26
noodles775There seems to be disagreement whether the lint warning about import errors should be disabled or left...15:26
barrymars: you're next15:26
noodles775Currently many files complain about this (i think after the code-reorgs...)15:27
flacostenoodles775: i think it's more buildout related actually15:27
flacostei don't kjnow15:27
abentleynoodles775 is describing lint failure messages when anything imports from canonical.launchpad15:27
flacostebut i also noticed that pylint is reporting crack error15:27
barryflacoste: maybe pylint doesn't have the correct sys.path?15:27
flacostebarry: it probably doesn't15:27
gary_poster_I'll look...15:28
barryflacoste: let's fix pylint if possible15:28
barrygary_poster_: thanks!15:28
sinzuiWe have other pylint issues15:28
barry[ACTION] gary_poster_ to look at bogus pylint import failures15:28
MootBotACTION received:  gary_poster_ to look at bogus pylint import failures15:28
daniloswe've seen them before buildout as well15:28
sinzuipylnt is different on jaunty and hardy15:28
sinzuiThey support different error messages15:28
flacosteyeah the utilities lint script should probably be moved to be generated by buildout15:28
flacosteso that it has the correct sys.path15:28
bacgary_poster_: if you fix the problem please look to remove directives in code which disable that warning15:28
barryflacoste: +115:28
flacostegary_poster is on leave for the next week15:29
flacosteso that will wait for 2 weeks at least15:29
gary_poster_bac, barry, flacoste, ok.  I'm out for a week and a day starting tomorrow, so I was intending to just diagnose15:29
barrygary_poster_: diagnose is fine.  please submit a bug report15:29
gary_poster_barry: ack, cool15:29
barrygary_poster_: thanks15:30
=== gary_poster_ is now known as gary_poster
barrysinzui: as for the other pylint problems.  new bug report, or tack onto the one gary_poster 's going to file?15:30
gary_posterthe interface stuff sinzui was mentioning in the review channel seemed unrelated, IIUC15:31
sinzuiIf we control the version of pylint, the we do not need to second guess what warning and suppressions are supported15:31
noodles775gary_poster: just fyi, an example here: https://code.edge.launchpad.net/~michael.nelson/launchpad/bug-376320-add-ppa-name-to-builder-status/+merge/723615:31
gary_posternoodles775: gotcha.  looks very suspiciously buildout related, yes15:31
sinzuigary_poster: the interface/adapter stuff is not new, but in jaunty the frequency of false positives has increased15:32
barrycool, thanks guys.  let's move on to mars's issue15:32
gary_postergotcha.  sounds like a legitimate problem, worthy of a bug report, maybe15:32
sinzuigary_poster: I don't think we can teach pylint about differed_import15:32
marsthanks barry15:33
marsok, something for the JavaScript writers in the room15:33
gary_posterdeferred, maybe not15:33
marsabout two weeks ago QA started an experiment to bring manual testing into the JavaScript review pipeline15:33
marshttps://wiki.canonical.com/Launchpad/Experiments/JavascriptTesting15:33
* sinzui has pondered replacing his navel-lint script with apure python script that only enforces his rules.15:33
marsthe idea is to have QA look at the work in different browsers during the code review step15:34
marssince it should be easier to catch and fix UI and browser issues while the branch is in development, rather than after-the-fact, on staging15:35
marsBy the way, this is unrelated to the [js] landing tag15:35
barrymars: since after this cycle, it's all ui from here on out, should we enforce this experiment for the next cycle at least, if not all of the rest of 3.0?15:36
marsbarry, I was going to ask for volunteers, rather than a team-wide experiment15:36
marsbut it could work both ways15:36
marsthe process is pretty simple15:36
barrywhat do others think?15:37
intellectronicai think it would be better to have everyone participate15:37
rockstarbarry, I think it should be enforced now.15:37
intellectronicawe don't really have time for partial experimentation. if we find that there are problems, we'll fix them15:37
barryi don't want to start this cycle, but i'd be willing to enforce it for 2.2.715:37
gmbOne thing to bear in mind here15:38
gmbIs sabdfl's edict at UDS:15:38
gmbUI reviews shouldn't be blockers to landing things.15:38
gmbDoes this come under that?15:38
intellectronicathat's a different thing15:38
intellectronicaand no, it doesn't come under that15:38
flacoste"UI reviews shouldn't be blockers to landing things."15:39
barrygmb: right, separate.  and remember we have [ui=rs] (with the understanding that you'll back fill that review later)15:39
flacoste!?!15:39
flacostethat's the first i heard of it15:39
flacosteand not what we are applying now15:39
marsgmb, that's a design review, rather than "I just denied IE users access to the site"15:39
rockstargmb, yes, this is the first I've heard of it too.15:39
intellectronicaimperfect UI can be fixed (and anyway it's often a matter of taste). broken code is really bad and the shortest time to fixing is too long15:39
flacostebeuno's review are blocking15:39
gmbflacoste, rockstar: He said it in a Launchpad gripe session for, IIRC, the community team (could be wrong about which track it was in; it was all a blur).15:39
intellectronicayeah, i also never heard about ui reviews not blocking, b.t.w15:39
jtvflacoste: that's exactly the part that he said we shouldn't be blocking on.15:39
gmbWhat jtv said15:40
flacostethat's new15:40
sinzuiThe principle problem with UI reviews blocking is that developers are not submitting designs to beuno *before* they write code15:40
flacosteand should be discussed15:40
flacostei don't agree15:40
rockstargmb, I think we need clarification on what he meant, because as it is now, beuno's reviews block.15:40
flacostewe are very bad at fixing thigns later15:40
intellectronicaare UI reviews a bottleneck at the moment? i didn't have that impression15:40
gmbSo why does ui=rs exist then?15:40
flacostefor trivial stuff15:40
gmbintellectronica: A bit. It depends how much of a fight beuno and kiko get into.15:40
flacosteit's not uised anyway15:40
sinzuigmb: I can get rs if I designed the UI with beuno *first*15:41
barryflacoste: no.  ui=rs exists explicitly not to block on beuno's review15:41
intellectronicagmb: for trivial landings or when you absolutely can't get a ui review and are very confident15:41
* barry remembers discussion that very fact with the man himself :)15:41
rockstarflacoste, the fact that we are bad at fixing things later is another issue.15:41
intellectronicagmb: surely if there's a disagreement it's even more important to resolve it before landing15:41
sinzuiI am doing UI review *before* code, and I don't start until Martin and seen my proposal15:41
rockstarsinzui, I am doing the same.15:41
gmbintellectronica: Right, but I've had branches wait up to three weeks because of UI disagreements + week 4.15:41
gmbI'm not saying that we should just land things without talking to Martin.15:42
jtvI believe full UI reviews were ultimately to be for "real" design decisions, not for "does it look okay like this."15:42
rockstarsinzui, because often, more code changes happen on UI review than code review.15:42
gmbThat's just crackpottery.15:42
sinzuirockstar: :)15:42
intellectronicagmb: sounds like you have to work a bit on your social engineering skills ;)15:42
marsjtv, good point15:42
jtvjust repeating...15:42
barryrockstar: yes!  it's the 80/20 rule15:42
flacostegmb: we should do a root-cause-analysis on your experience15:42
rockstarsinzui, also, I dread UI reviews, where I don't dread code reviews, so I do the band-aid thing.15:42
barryor its inverse. or something.15:43
flacosteanwyay, that's kind of besides the current discussion i think15:43
flacosteif we want to discuss UI reviews, we should bring that separately as another topic15:43
gmbflacoste: Well, I've got another big UI branch coming up in the next couple of days, so let's analyse that one rather than rehash my previous experience.15:43
barryflacoste: good point.15:43
barrylet's take up ui review issues on the ml please15:43
barryas for js, let's vote on requiring the experiment for all devs in 2.2.715:44
rockstarSo, with the current QA plan, at least they can defer it.  I think we should request a review from them (so they get an email) but not block on it.15:44
marsbarry, so!  full-team experiment for manual UI testing next cycle?15:44
barry[VOTE] require full-team experiment for manual ui testing in 2.2.715:44
MootBotPlease vote on:  require full-team experiment for manual ui testing in 2.2.7.15:44
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:44
MootBotE.g. /msg MootBot +1 #launchpad-meeting15:44
barry+115:44
MootBot+1 received from barry. 1 for, 0 against. 0 have abstained. Count is now 115:44
marsrockstar, we'll see if they get swamped - it's their call15:44
mars+115:44
MootBot+1 received from mars. 2 for, 0 against. 0 have abstained. Count is now 215:44
gmb+015:45
adeuring+015:45
MootBotAbstention received from gmb. 2 for, 0 against. 1 have abstained. Count is now 215:45
MootBotAbstention received from adeuring. 2 for, 0 against. 2 have abstained. Count is now 215:45
rockstar+015:45
MootBotAbstention received from rockstar. 2 for, 0 against. 3 have abstained. Count is now 215:45
bac+015:45
MootBotAbstention received from bac. 2 for, 0 against. 4 have abstained. Count is now 215:45
jtv+015:45
MootBotAbstention received from jtv. 2 for, 0 against. 5 have abstained. Count is now 215:45
gary_poster+015:45
MootBotAbstention received from gary_poster. 2 for, 0 against. 6 have abstained. Count is now 215:45
noodles775+015:45
MootBotAbstention received from noodles775. 2 for, 0 against. 7 have abstained. Count is now 215:45
henninge+115:46
MootBot+1 received from henninge. 3 for, 0 against. 7 have abstained. Count is now 315:46
jtvmaybe we haven't talked this through enough; I for one don't have a clear picture of how it would fit into the process.15:46
intellectronica+115:46
MootBot+1 received from intellectronica. 4 for, 0 against. 7 have abstained. Count is now 415:46
flacoste+015:46
MootBotAbstention received from flacoste. 4 for, 0 against. 8 have abstained. Count is now 415:46
flacosteactually, that should be a +115:46
sinzuiWhat really is manual UI testing? What how do I know it is successful15:46
flacoste+115:46
* sinzui cannot vote, and wants to15:46
marssinzui, I was about to get to that, then a car hit my topic :)15:47
barrysinzui: it's outlined on the wiki page15:47
* gmb apologises for DUI.15:47
intellectronicasinzui: ideally, we should prepare test plans with clear predicates, but sometimes it will be just monkeying about with the interface15:47
marsthe process is simple: you write up a manual test plan in the cover letter15:47
abentley-015:47
abentley+015:47
MootBotAbstention received from abentley. 4 for, 0 against. 9 have abstained. Count is now 415:47
marsQA follows it for the A and C browsers15:47
jtvmars: who is responsible for making sure the branch goes all the way through the process?  Still the reviewee as usual?15:48
marsjtv, yes15:48
flacosteactually, i'm -1 on a full team experiment at this point15:48
flacostenot that it matters :-)15:48
sinzuiI don't think this test can be performed by the team if they do not posses all the A-grade browsers15:48
intellectronicaflacoste: why? and it does matter15:48
marsjtv, QA handles wrangling the people with the browsers for testing15:49
flacostewell, i don't have a veto :-)15:49
marssinzui, we do15:49
jtvflacoste: I think that brings you to a total of 3 votes  :-)15:49
barrysinzui: devs don't but qa does15:49
flacostei think the experiment is too vague at this point to make the whole team follow it15:49
intellectronicasinzui: iiuc diogo and ursula have access to all platforms, and it's up to them to delegate the work if and when they feel they can't handle the load15:49
marssinzui, we do have the browsers.  QA has access to them, and to the pool of people who have registered as having the alternative environemnets15:49
flacosteand given that 2.2.7 is all-UI15:49
flacosteit could degenerate15:49
* noodles775 is unsure *how* i can go about fixing my branch if it fails for IE6 on XP? XP licenses as per the email?15:49
intellectronicaflacoste: it's clear in my mind. could it be that it's not adequately expressed?15:50
flacostenoodles775: you disable the feature for IE :-)15:50
flacosteintellectronica: probably15:50
marsnoodles775, disable the feature, yes15:50
flacosteand we haven't experimented it at all yet15:50
flacoste(i think)15:50
sinzuiour China OEMs are using IE6 on XP. They are not permitted to change browser or OS15:50
intellectronicaflacoste: that's why experimenting during the remainder of 2.2.6 can help doing the real thing for 2.2.715:50
sinzuiThey do not like Launchpad15:50
noodles775flacoste, mars: ok, FF3 on OSX?15:51
jtvsinzui: my shoes are broken, I don't like pavements :)15:51
marssinzui, that's what we are addressing with this15:51
barryintellectronica, mars so perhaps volunteers for 2.2.6 to flesh out the process so everyone understands it?15:51
flacosteintellectronica: so let's do a two-weeks experiment using volunteers15:51
marsnoodles775, not a concern, just the browser, not the environment15:51
barrybtw, if the experiment is a failure we don't need to keep running it for the whole cycle!15:51
noodles775ok15:51
sinzuijtv: I bought new All-stars and Doc Martins in London because I had holes in my shoes15:51
marsnoodles775, Opera on Linux is fine, no need for Opera on Win/OSX15:51
jtvflacoste: sounds good to me—reviewers could encourage reviewees to participate15:51
jtvflacoste: ...and if people don't want to, note a probable point for improvement15:52
flacostethat's the idea, volunteering reviewers15:52
flacosteare to make sure that the process is followed15:52
sinzuiWhen using safari (Webkit) can we substitute Konqueror or Epiphany-webkit?15:53
barrywe've gone over, and i apologize for that.  i will really try to fix my irc by next week15:53
flacosteif all the AJAX-team reviewers volunteer15:53
marsflacoste, I'll rely on barry's experiement experience here, but I do agree with your points, there is risk because it hasn't been tried yet15:53
intellectronicai rather do it for the remainder of 2.2.6 rather than two weeks, for simplicity, but either way is fine. i agree that a limited experiment is a good idea15:53
flacostewe kind of have a de-facto whole team experiment15:53
* Ursinha reads15:53
marssinzui, that I'm not sure about15:53
* sinzui want to add small devices to to list15:53
intellectronicai'll most definitely volunteer, as i'm sure everyone from the bugs team will ;)15:53
marssinzui, for Konqueror, no, you absolutely can not15:53
sinzuimars: they run the webkit version15:53
barrylet's defer the whole-team decision until we see how the volunteer experiment works for the rest of 2.2.615:54
sinzuiEpiphany is on tip15:54
marssinzui, heh, nice try, but no, the Webkit Konqueror is *not* Safari15:54
flacostevolunteers should sign up on the JavaScript experiment page15:54
marsI know, I tried it15:54
sinzuimars: 4.2 is I thought15:54
barryflacoste: +1 thanks15:54
sinzuiQT15:54
flacosteand15:54
jtvbarry: may haev to start a new vote before the bot gets confused15:54
flacostewe should put the link to the experiment in the launchpad-reviews channel15:54
flacostefor OCR15:54
marssinzui, the engine, sure.  But it still doesn't work the same as Safari.15:54
barry#endvote15:55
flacosteso that dev can look if they need to follow-it15:55
* barry knows a sure fire way to end the vote...15:55
barry#endmeeting15:55
MootBotVote is in progress. Finishing now.15:55
MootBotFinal result is 4 for, 0 against. 9 abstained. Total: 415:55
MootBotMeeting finished at 09:55.15:55
barrythanks everybody!15:55
intellectronicathanks barry15:55
jtvthanks barry!15:55
EdwinGrubbssinzui, mars: I had some good results using Arora to test webkit after I disabled its network caching.15:55
sinzuiflacoste: can we engineer a JS oops AJAX lib that run in staging/edge clients and send us reports when our users know we broke something15:55
marssinzui, yes, we can try.  It's on my Todo list15:56
marssinzui, well, my Todo wishlist :)15:56
flacostesinzui: we can anything, priorities, priorities, priorities15:57
sinzuiflacoste: I think that by putting enough eyes on the problem (per the Open Source mantra) there will not be a problem15:59
sinzuiWe use automated testing because we do not have enough eyes15:59
sinzuiJS + automated testing is painful15:59
sinzuiso using oopses might be the best way to verify scripts16:00
abentleysinzui: JS + manual testing is also painful16:00
sinzuiabentley: test for the sake of testing is painful. but users of staging and edge do not mind testing for us because we provide them newer services16:01
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== Edwin is now known as Guest51667
=== salgado is now known as salgado-afk
thumperhi barry23:30
barry#startmeeting23:30
MootBotMeeting started at 17:30. The chair is barry.23:30
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]23:30
barryhi thumper23:30
barryjml, mwhudson hi23:30
mwhudsonhello23:30
jmlhi23:31
barry[TOPIC] agenda23:31
MootBotNew Topic:  agenda23:31
barry# Roll call23:31
barry# Action items23:31
barry# Mentoring update23:31
barry# Peanut gallery (anything not on the agenda)23:31
barry[TOPIC] mentoring update23:31
MootBotNew Topic:  mentoring update23:31
barryjust wanted to let you know that henninge has graduated23:32
thumpercool23:32
barry[TOPIC] peanut gallery23:32
MootBotNew Topic:  peanut gallery23:32
thumperI've got a few things23:32
barrythumper: go ahead23:33
thumperthe launchpad code team have moved all interface enums to lp.code.enums module23:33
thumperyou may want to consider this too23:33
thumperalso looking into trying out lp.code.errors for our exceptions23:33
thumpermoving the enums reduces circular dependency issues23:33
thumperas they only rely on lazr.enum23:33
barrythumper: very nice23:33
* jml has one item.23:33
thumperit was mentioned in the team lead call this morning23:33
thumperand foundations and registry may do the same23:34
thumperalthough I don't think foundations has any...23:34
barrythumper: +123:34
barryregistry has a lot23:34
barrythumper: did you talk at all about making .enums a package?23:34
thumperI'm done23:34
thumperbarry: not exactly23:35
barryi'm a little concerned about having really huge modules23:35
thumperwhy make it a package than a module?23:35
thumperwould the enums/__init__.py pull them in?23:35
barrythumper: no, but maybe that would just re-introduce the circs23:36
barryin any event, it's not a big deal for now at least23:36
* barry was just curious23:36
* thumper nods23:36
thumperlets see how it goes23:36
barrythumper: +1.  thanks.  did you have another issue?23:36
thumperthere are advantages to just having one module23:36
thumperto get enums23:36
thumperfrom23:36
thumperlike not having to think :)23:36
barry:)23:36
jmlbarry: does beuno attend a reviewers meeting?23:36
* thumper passes floor to jml23:36
barryjml: he does not.  probably should though23:37
thumperperhaps I should pass the talking-stick to jml23:37
jmlbarry: even if it's just every second week, it'd probably be useful.23:37
barryjml: +1 i'll ask him to (i think he did at one point)23:37
barryjml: you're up23:38
* barry has one when you're done23:38
jmlbarry: that was my topic :)23:38
barryjml: cool!23:38
barryat the ameu meeting, mars brought this up: https://wiki.canonical.com/Launchpad/Experiments/JavascriptTesting23:38
* thumper looks23:39
barrythe idea is to put qa in the critical path for branch approval.  this is manual js testing by qa23:39
thumperhmm..23:39
* mwhudson mutters something about a "fix verified" bug status23:39
barrymars and company are asking for volunteers for 2.2.6 and we're considering making it mandatory team-wide (as an experiment) for 2.2.723:39
thumperseems like a branch blocker23:39
barrythat's not decided yet though23:40
thumper"fix confirmed" ?23:40
barrythumper: it could be yes23:40
thumperhow would the qa be done?23:40
jmlbarry: I'll try to have a look at the page later on today23:40
thumperif it wasn't landed on trunk?23:40
mwhudsonec2!23:41
barrythumper: i think qa would run the branch and try it with the A and C browsers23:41
jmlbarry: my first reaction is "I thought we were trying to improve UI velocity"23:41
barryjml: btw, this is separate from ui=* and the js tags on pqm commits23:41
barryit's also separate from ui reviews23:41
thumperis it going to be a requested review from the qa team that has to be approved?23:42
barrythumper: i believe that's the idea23:42
thumperhmm...23:42
jmlbarry: this seems to confirm my impression that this will slow down branches :)23:42
barry;)23:42
thumperI'm with jml on the velocity issue23:42
barryanyway, i just wanted to make you aware of the discussion at ameu :)23:43
thumperI was also going to raise the UI review not being blocking issue23:43
jmlbarry: thanks.23:43
barrythat's all i have23:43
jmlbarry: I'd like to read this page & send my thoughts on later.23:43
barryjml: please do!23:43
mwhudsonmaybe we could have something like, if it works, the qa person should submit the branch23:43
mwhudson1 less handoff23:43
barrythat's an interesting idea too23:44
mwhudsonor say, it's something the code reviewer should do23:44
barryanything else guys?23:45
mwhudsonif we can build tools to make it easy23:45
* thumper wants branch merge queues in LP23:45
jmlbarry: a low priority thing23:45
mwhudsonthumper: yes23:45
mwhudsonthumper: also, a pony23:45
jmlbarry: have you ever looked at the bzr developer docs?23:46
barryjml: it's been a while23:46
jmlbarry: http://doc.bazaar-vcs.org/latest/developers/index.html23:46
jmlbarry: maybe this is something we can work towards before, during & after open sourcing23:46
barryyes!  i'd also like to take a shot at sphinxing our docstrings23:47
jmldoctests, itym23:47
barryboth actually, as we markup more of our docstrings23:47
mwhudsonthere's still nightly pydoctor output23:47
jmlright. was about to mention :)23:48
mwhudsonat https://devpad.canonical.com/~mwh/canonicalapi/23:48
thumper:(23:49
thumperwe don't have much documentation for lp.code23:49
jmlbarry: anyway, what I mean is -- *I* get lost trying to find our reviewer, developer, testing docs & guidelines23:49
jmlbarry: it's an oral tradition for me23:49
mwhudson(i get emailed a list of which docstrings aren't valid reST every night...)23:49
jml(which is why these meetings are so valuable)23:49
barryjml: i hear ya23:49
barrymwhudson: any chance you can send those to launchpad@?  would make a nice email nag to reduce techdebt23:50
jmlbetter yet, any chance you can get 'make lint' to tell us about them.23:50
barryor that23:50
mwhudsoni would really really really like it if it was someone's job to make the developer experience better23:50
thumperfoundations?23:51
mwhudsonbarry/jml: yes, am wary of spamming launchpad@ more23:51
jmlme too.23:51
mwhudsonthumper: a nice idea, it's not what they actually do though23:51
barryi'm not.  i already have too much spam, so a little more won't hurt :)23:51
* jml tries.23:51
mwhudsonjml: file a bug about having make lint warn about this?23:51
barrymwhudson: me too.  *especially* after we open source. i'm hoping to find time to actually work on that23:51
jmlok.23:52
mwhudsonjml: it's not that we don't try, it's that it's noone's main responsibility23:52
barrymwhudson: exactly23:53
jmlmwhudson: agreed.23:53
jmlI think we're coming to a close here.23:53
thumperagreed23:53
barryand with that...23:54
barry#endmeeting23:54
MootBotMeeting finished at 17:54.23:54
mwhudsonthanks barry23:54
barrythanks guys23:54
thumperthanks barry23:54
jmlmwhudson: https://bugs.edge.launchpad.net/launchpad/+bug/38573623:54
ubottuLaunchpad bug 385736 in launchpad "'make lint' should warn about invalid docstrings" [Low,Triaged]23:55
mwhudsonjml: thanks23:55

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