[11:23:38] yuvipanda: https://bugzilla.wikimedia.org/show_bug.cgi?id=39039 Is a python script executed by Makefile that take relevant i18n entries from javascript i18n file and push them into value-XX/string.xml a good way to solve this bug ? [11:29:27] Tpt: very [11:31:03] would be awesome to get done :) [11:33:49] yuvipanda: I'll try to do it today. [11:50:55] Tpt: much thanks :) [12:30:46] Oh, MaxSem isn't here. :-( [12:51:22] Jarry1250: around? [12:51:42] saw my comment on #24? [12:52:17] yuvipanda: Nope, have now. [12:53:00] Jarry1250: how do you think that'd work? (Parsing history instead of byline to get authors) [12:53:04] leaving aside unlinked authors [12:53:31] Well there's authors and there's authors... [12:53:38] The byline is a deliberate subset [12:53:52] well, both? [12:54:03] byline parses + a 'more' link that shows history data [12:54:14] I think you'll agree that farming out to history is a horrible cop out [12:54:32] Well, I'm not sure how many people actually care about the history [12:54:42] It's a legal requirement, but if it's not going to get clicks [12:55:19] Jarry1250: the legal requirement is that we credit authors, not that we link to history [12:55:26] well, 'contributors' rather [12:55:46] yuvipanda: Yup, but sometimes authors end up being credited in edit summaries [12:56:03] i'm guessing those would also be credited in the byline :) [12:56:12] *shrug* who knows [12:56:24] i'm thinking of byline being 'X, Y and contributors' [12:56:32] with a tap on the 'and contributors' opening up the rest [12:56:51] yuvipanda: I think we have a few unusual bylines though [12:57:19] you do indeed :) they're hard to parse. [12:57:33] Exactly, it sounds like work [12:57:46] So (full page history) [12:57:56] Would certainly be easier. [12:58:11] We must have a mobile friendly skin [12:58:26] Jarry1250:okay, link to history + license text same as Wikipedia mobilesite/app for v1, and let's see what we can do for v2 or v3 [12:58:58] Yuvipanda: Seems reasonable :) Do show the byline though [12:59:09] (if you are already, apologies!) [12:59:15] (don't have my phone in front of me) [12:59:19] Jarry1250: the full byline? [12:59:41] (I am not, am not even showing authors yet (next to do after about page (which I'm working on now))) [13:00:06] yuvipanda: Yes, although you could visually deemphasise it [13:00:15] Hold on, I'll put my phone back together [13:00:18] One sec [13:00:54] Jarry1250: hold on, I shall give you an updated version [13:01:04] Jarry1250: thinking of making RC1 tonight, and perhaps get a mention on signpost :) [13:01:44] Jarry1250: https://dl.dropbox.com/u/8768784/WPSignpost-debug.apk [13:07:33] yuvipanda: Yes, IB I think. And we should start thinking about a full special story. [13:07:41] *downloads* [13:10:05] Jarry1250: RC for the day, release + special in next signpost? [13:11:31] Yes, sounds good. Have you mentioned this to Ed? [13:12:04] Jarry1250: no, I haven't had any contact with Ed, sadly [13:12:11] would I find him on wikipedia-en? [13:12:13] or do I hit the talk page? [13:14:05] yuvipanda: Probably best to email him about something like this. He's not on IRC AFAIK [13:14:10] I'll PM you the email? [13:14:15] *his email [13:14:43] Jarry1250: sure! [13:30:45] Jarry1250: thanks :) [13:31:01] Jarry1250: No problem [13:31:34] talking to yourself? tch tch [13:32:06] Jarry1250: so, that build you have - about page fixes + attribution fixes = RC [13:32:13] so tell me if there's something going wrong there :) [13:32:47] yuvipanda: Look, I've got about 4 Git merge conflicts open, I'm allowed to talk to myself :P [13:32:53] Sure, will do. [13:33:25] haha [13:33:40]

[13:54:24] yuvipanda: Works nicely AFAICT. I would have the byline (not in forced caps) below the subtitle, then an

, same size as the prose, maybe in grey? [14:03:16] Jarry1250: yeah, my thinking too [14:10:10] wgMFFeedbackLinks sets the email address to which feedback is sent right? Why am I not finding it in InitializeSettings.php ? [14:11:37] cause it's in mobile/php [14:11:44] mobile.php [14:23:26] New patchset: Siebrand; "Remove duplicate array keys." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/20707 [14:29:03] MaxSem: ? [14:29:20] and http://noc.wikimedia.org/conf/highlight.php?file=Mobile.php has a password :o ? [14:30:09] don't worry, your password is also exposed: http://noc.wikimedia.org/conf/highlight.php?file=SrikanthLogic.php :P [14:30:38] ah! [14:31:04] so my interest is how do I change feedback email ID for my project. Shell request? [14:31:37] you're a committer, you can submit a patchset [14:32:25] MaxSem: which file? I don't see mobile.php on MF code [14:32:35] or its in ops [14:32:42] it's in operations/mediawiki-config [14:34:35] got it, thanks! [14:55:12] Change merged: Siebrand; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/20707 [15:20:03] yuvipanda: https://github.com/Tpt/Wikipedia/commit/91b6562654aea9fa1c108794921369bd93263a54 [15:23:50] New patchset: Siebrand; "Remove unreachable code." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/20722 [15:31:05] Change merged: Siebrand; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/20722 [16:30:37] Jarry1250: https://dl.dropbox.com/u/8768784/Screenshot_2012-08-20-21-58-58%20%281%29.png [16:30:42] screenshot of author name [16:30:46] (had some issues that I just fixed) [16:31:40] yuvipanda: Definitely enough room on that arrangement for your standard byline in full I reckon [16:32:22] Jarry1250: the standard byline is just the name and date [16:32:26] I don't see how date is useful there [16:33:12] yuvipanda: Oh, I didn't mean the date [16:33:21] I just meant to need to parse the author list [16:33:25] *no need [16:33:31] in that case I'll need to parse *out* the date [16:42:30] yuvipanda: Sorry, missed your reply [16:43:08] I meant only for the newer format [16:43:44] No point putting lots of effort into perfecting the bylines on 2008 issues really [16:44:08] Jarry1250: hmm, right. [16:44:13] but good enough for an RC :) [17:06:24] Heya. [17:06:28] MaxSem: Are you around? [17:06:57] I have some questions about the article extract API. [17:07:02] sure [17:07:58] How does the content get broken up into sections and such? [17:08:27] I don't entirely follow the regexen. [17:11:37] basically, the API can output several formats. I chose 'raw' here which uses plain text with section titles prefixed with double \ufffd [17:12:10] Basically, we need to be able to split on top-level sections. [17:13:30] we already have get_top_level_sections() [17:13:44] Sorry, I'm juggling a couple of different conversations simultaneously. [17:14:44] np, we could continue later [17:15:06] No, I'm extracting myself from the others. This one's better. :-) [17:15:36] (One of the others has Kul in it. I need to get away from that guy.) :-P [17:16:57] so we just have to reuse it [17:17:15] Right, back in my own hotel room. [17:17:57] where are you?:P [17:17:59] ajerith: ha ha [17:18:45] greetings all [17:18:50] awjr: yo [17:18:51] Delhi, with Dan and Kul. [17:18:53] tfinc: greetings... [17:18:56] Hey tfinc. [17:18:58] hello [17:19:17] awjr: having run through http://www.mediawiki.org/wiki/Wikimedia_Apps/HowToReleaseAnApp#Android ... what else should i expand on ? [17:19:32] greetings tfinc [17:19:38] tfinc: got my hands full right now can we chat about it alteR? [17:19:39] greetings ajerith & preilly, how goes vuim hacking? [17:19:39] er [17:19:40] later [17:19:43] awjr: sure [17:19:51] vumi* [17:20:16] yuvipanda: i see you've been active on the signpost app dev. do you have a first release candidate ? [17:20:48] tfinc: there are a few more updates to install in production [17:20:54] tfinc: ajerith is making really good progress [17:21:26] tfinc: I will in a few minutes. Final testing [17:21:36] tfinc: no push notifications for 1.0. I want to release it and see how it goes [17:21:39] preilly, tfinc: Reality and my code are slowly converging. :-) [17:21:47] ajerith: we'lll be running a hackathon in india in november. will we see you there? it would be good to thank you in person [17:21:48] and see how my puny tiny little VPS handles the load :) [17:22:00] yuvipanda: why don't you host it on labs ? [17:22:08] s/host/test [17:22:14] tfinc: very good question, actually. [17:22:27] I've a nice little VPS with all the stuff setup (uwsgi, nginx, etc) so it was easy putting it there [17:22:32] . [17:22:41] yuvipanda: you wouldn't want to host a production app against labs but if your just testing then go for it [17:22:45] tfinc: I'd like to come. I even have a visa that'll last that long now. :-) [17:22:50] woot! [17:23:05] tfinc: well, this goes into Google Play in a week at most, so I'd consider it production :D [17:23:08] But I left my phones in Kul's room and have to go back and get them now. :-/ [17:23:17] so I think for now keeping it on my VPS would od [17:23:18] *do [17:23:44] ajerith: good luck with that [17:25:15] ajerith: the recent SMS ban affected you guys much? [17:25:41] * yuvipanda notes that everyone in India is now limited to 5 SMS / day at least until end of month, by a Govt. order [17:25:41] Okay, phones rescued. [17:26:07] yuvipanda: This is the first I've heard of it. [17:26:16] yuvipanda, WTF is going on with your govt? [17:26:19] ajerith: MUMBAI: A government directive to telecom operators, asking them not to allow cell phone users to send more than five SMSs or MMSs at one go over the next 15 days not only failed to check spread of threats to people from the northeast but also ended up creating a communication hurdle for many consumers in Mumbai on Saturday. [17:26:40] It's an operator-operated service, though. [17:26:49] well, it is *supposed* to be 5 SMS in 'one go', but it's implemented as '5 SMS per sim per day' [17:27:10] Oh, right. Stupidly misguided "anti-terrorism" measures. [17:27:28] The US doesn't have a /complete/ monopoly on those. ;-) [17:27:30] MaxSem: the usual. It's either these guys or the religious right to come to power. [17:27:52] not much choice, really :) [17:29:08] So, back to vumi-wikipedia stuff. [17:29:39] Jarry1250: I'm ready to cut an RC :) [17:31:03] damn [17:33:40] tfinc: RC1 cut. https://github.com/yuvipanda/WPSignpost/WPSignpost-1.0RC1.apk/qr_code [17:33:45] making screenshots now, will mail out in a bit [17:33:52] MaxSem: It looks like get_top_level_sections() concatenates all the lower-level section content back together. Is that the case? [17:35:04] it returns a list of top-level sections [17:37:28] Oh, right. I see it now. [17:37:40] so looks like there should be a function returning text of section and all its sub-sections [17:37:52] * ajerith is in a bit of a post-dosa slump. [17:38:45] yuvipanda: woot! [17:39:26] MaxSem: At the moment, the menu lists all sections and subsections in a flat menu. [17:40:43] ajerith, now I remember: I was going to implement it once I've received your review of my previous commits. I didn't realise that it would just quietly stick:P [17:41:05] MaxSem: Ah. Code does that from time to time. [17:41:31] so since they were ok, I guess I could continue with it [17:41:40] Do you have time to work on it today, or should I pick it up in the morning when I'm fresh? [17:41:46] once I'm free from that WLM burden [17:42:18] I'll be able to tell it in an hour - after our sprint kickoff [17:42:22] I need it by tomorrow India time, but I'm happy to do the work myself now that I have a better idea of what's going on. [17:43:22] ajerith, would be great as I'll need some time to recall how that hting works and WTF is that Python thingie:( [17:44:23] but if it's needed urgently I'll try to find time [17:44:58] MaxSem: it's sort of urgent [17:45:13] MaxSem: Okay, don't worry about it then. Probably easier for me to do it in the morning. [17:45:42] preilly, we'll discuss the priorities in 15 mins;) [17:45:46] That was pretty much my plan anyway, I just wanted to pick your brain about it. [17:46:14] I probably have a better idea than you do about what we need, but you know the API better. [17:51:15] MaxSem: So the top-level sections are "2"? [17:52:37] awjr: hangout link please [17:53:52] https://plus.google.com/hangouts/_/e4bcffa32d6b34595b61457deb5c184d4034fb0d?authuser=1&hl=en-US [17:54:07] ajerith, ??? [17:54:26] MaxSem: The section level numbering. [17:54:35] hmmm, so far (1) rejection from filing an issue because bug submitter didn't want to sign up for a github account [17:54:43] There's no level 1 as far as I can see. [17:55:03] ajerith, they can be 1 - it's a convention to generally use second level [17:55:20] awjr: i'm in [17:55:34] MaxSem: Ah. So we can't just hardcode it. [17:56:00] yeah [17:56:46] What's a good way to format section headings in SMS? [17:57:37] hmmm [17:57:48] a separate line? [17:58:10] a separate line *like this*? [17:59:02] How do we differentiate second and third level headings? [17:59:24] Or do we not worry about that? [17:59:48] (Not worrying about it is a valid approach, but I'm not sure if it's the right one.) [17:59:58] awjr: can you send the hangout link? [17:59:59] I don't think we have real ways to highlight them [18:00:03] https://plus.google.com/hangouts/_/e4bcffa32d6b34595b61457deb5c184d4034fb0d?authuser=1&hl=en-US [18:00:06] brion ^ [18:00:09] hmm [18:00:17] "Join Google+ by creating your public profile" [18:00:21] cause == like this == would be too geeky:p [18:00:23] that… doesn't seem right :D [18:00:26] MaxSem: No, we only have plain text. [18:00:51] Also, that might be too character-wastey. [18:00:52] what, no equal signs?:P [18:01:41] it seems to be trying to force me to bvibber@wikimedia.org [18:01:48] but i'm already logged in as brion.vibber@gmail.com, wtf? [18:02:26] brion, yeah, google+ picks a random account of yours [18:02:36] i've had weird issues with multi sign-in and google+ [18:02:43] I have to use it in a different browser due to that [18:02:45] ok lemme see if i can fix this [18:03:07] Most of these things like to use the first account you signed in with. [18:03:14] brion if you both accounts associated with eachother, you should be able to click your picture in the upper right hand corner of the interface and select your other account [18:03:24] ok i'm in [18:03:26] The one with /0/ in the URL. [18:16:37] make that 'number of people who didn't want to report issues on github - 0' [18:16:49] github's signup page seems to hide their free tier a litttle bit (not too much) and he just got confused [18:17:00] Jarry1250: sent out email to mobile-l [18:17:03] shall email ed now [18:25:11] tfinc: email sent. Test it out when you can. You're getting push notifications only in the next release :) [18:26:19] yuvipanda: i'm in our sprint kick off meeting. will look at later. [18:26:24] yuvipanda: no push notifications. slacker. [18:26:26] ;) [18:26:51] yuvipanda: if i open up multiple issues will it happen faster ;) [18:32:43] tfinc: :P [18:32:47] tfinc: you can try! [18:57:13] awjr: there? [18:57:26] jdlrobson: one sec [18:57:28] https://mingle.corp.wikimedia.org/projects/wlm_android_app/cards/133 < does seem to meet acceptance criteria so i'm a little confused [18:59:20] jdlrobson: i wasn't presented with the confirm upload/license option after selecting a photo from my gallery to save for later nor when i took a photo using my camera [18:59:30] jdlrobson: iirc it worked fine the first time i did it, but not the second [18:59:57] jdlrobson: also i did not get the save for later confirmation after selecting a photo [19:00:40] lets try replicate awjr as works for me on latest master [19:00:45] I click use my current location [19:00:47] grab a monument [19:00:56] and click photo in top right [19:01:10] i choose "choose from gallery" [19:01:20] i get the confirm upload page [19:01:47] which has license info on it [19:01:51] i click save for later and get confirmation message [19:02:04] does that not happen for you awjr ? [19:02:42] jdlrobson: it did, although i had initially tested from campaign browsing [19:02:50] mm [19:02:52] let me try that then [19:03:15] ooh [19:03:18] yeh looks like a bug [19:03:32] Error in success callback: Camera6 = TypeError: Cannot read property 'config' of undefined [19:03:58] also, what is supposed to happen after a user selects 'save for later'? right now the user is just presented with the select photo for upload dialog, which seems weird. [19:04:16] oh, it looks like that wasn't defined in the acceptance criteria [19:04:18] they get a confirmation message [19:04:34] it says this has been tucked away in your incomplete uploads available from the welcome screen [19:04:34] jdlrobson: right but after they click ok in the confirmation message [19:04:50] yeh that wasn't defined. I assumed it would go back to the screen before as that's what happens elsewhere in the app [19:04:59] i think it's the right behaviour [19:06:12] maybe it should have a link 'back to monument' [19:06:18] but yeh that needs to be defined [19:06:38] philinje can address it if it needs to be changed, but let's not worry about it for now [19:07:05] jdlrobson: sorry i broke the tests :( [19:07:25] jdlrobson: i'll be sure to check the tests on my changes in the future [19:10:23] awjr: it's ok - you know how to run them right? [19:10:27] awjr: can you pass me the link for the previous iteration storywall ? [19:10:28] it happens [19:10:37] i'm a terrible offender :) [19:11:14] jdlrobson: i believe so, i just hit test.html in a web browser right? [19:11:51] tfinc: under the 'team favorites' section on the right side of the interface, there's a link that says 'previous iteration story wall' [19:12:23] yup that's it awjr [19:13:17] awjr: yup. i see it. thanks [19:13:31] np [20:10:47] Go to sleep -> Think 'Check mail once before going to sleep' -> See a few easy issues reported -> Go 'fuck it, let me go fix these!' -> Lose sleep. [20:10:52] sigh [20:11:08] xD [20:11:55] where are you located? India? [20:12:01] Yes. [20:12:25] And it's nearly 2am here, so I really need to get some sleep as well. [20:13:00] Platonides: indeed [20:13:06] and I've to be up at 6:45 tomorrow [20:13:09] yuvipanda: You still need to come visit me in Delhi before I go. [20:13:23] ajerith: get me a flight ticket and I will :) [20:13:29] * yuvipanda notes he's an unemployed student [20:13:47] But Kul's been dropping subtle hints about a hackathon in November, so maybe I'll come to that. [20:14:23] ajerith: I think that's pretty confirmed, really? tfinc was inviting you to that too [20:14:56] yuvipanda: Some of it depends on how much work I have to do at the time. [20:14:56] yuvipanda: i've got a couple exception backtraces for you on the signpost app. crashes on my kindle fire & galaxy tab 10.1 [20:15:08] filed as issues on github [20:15:10] brion: saw that, I don't think ActionBarSherlock supports the Kindle fire [20:15:20] d'oh [20:15:21] brion: those and tyler's issues are what woke me up [20:15:43] fire shouldn't be hard to fix if it's treated like other android 2.3.x [20:15:50] lemme peek at the source for that [20:16:00] i was wrong, it does support it [20:16:57] we're not planning https://mingle.corp.wikimedia.org/projects/wlm_android_app/cards/172 for this iteration? [20:17:03] My boss seems to have appointed me the India person in our dev team, so I'll probably be back in November. [20:17:19] ajerith: sweeet! [20:18:08] We recently hired a full-time person in India on the business side of things, so with luck I'll be here more often in the future. [20:18:31] ajerith: looking forward to meeting you in Bangalore then! [20:18:39] wonderful city except for everything shutting down at 10:30 pm [20:18:40] :) [20:18:55] :-) [20:19:15] [20:21:01] brion: jdlrobson also, fun look at inline styles + table usage example here: https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-06-18/Investigative_report [20:21:22] the one with the key yuvipanda ? [20:21:28] yup [20:21:41] we should have classes for this.. key1, key2, key3…key10 [20:21:49] these should be consistent across wikipedia [20:22:11] that's a nice big table whee [20:22:22] * jdlrobson hates signpost's mobile site [20:22:53] it's also slightly crazy and has mismatching number of I think [20:23:14] jdlrobson: this is the first instance inline styles are causing me trouble in the signpost app. I'll scrub them and see how things go tomorrow. [20:23:24] but I can't actually *fully* scrub them [20:23:28] since they'll lose all style and meaning [20:23:45] now that I think about it, I realize I've no idea what I'm supposed to be doing... [20:24:00] I can't really edit the page - what would I replace those with? key1, key2, etc don't exist [20:24:48] yuvipanda: I will solve tables soon [20:24:50] I hope [20:25:30] we all do, jon :) [20:26:52] awjr_lunch / MaxSem : Nice to see names instead of iso code [20:26:56] *codes [20:27:34] jdlrobson: those colors are actually templates, so shouldn't be too horrible to change [20:32:04] okay, now I *really* should sleep [20:32:06] gnite! [20:42:04] multichill: yeah, i was gald to get those done finally! [20:43:26] Did I see directly that only one language is available? [20:43:52] multichill: what do you mean? [20:44:22] http://wlm.wikimedia.org/api/api.php?action=adminlevels&format=json&uselang=nl returns it in Dutch, but lower levels are just one language? [20:45:36] multichill: if mappings are available in dutch, then you will see them in dutch, otherwise it falls back to the default language configured for that country [20:46:12] Ok, now the field says "translated" [20:46:25] multichill, speaking of default languages - do our defaults make sense? [20:46:27] Probably cleaner to also mention what language [20:46:56] Think so, not sure what it is now since the last time I looked at it was some time ago [20:47:27] http://wlm.wikimedia.org/api/api.php?action=adminlevels&format=json&uselang=lb <- no fallback? [20:48:18] nothing to fall back to: it's country's default language [20:50:31] tfinc/philinje: how many people are currently using the latest beta? should the API maintain backwards compatibility for them? [20:50:46] * tfinc is getting ticked off at the chromebox [20:52:01] MaxSem: Huh? It should output *something* [20:52:05] awjr: are you around for a quick hangout test ? [20:52:34] tfinc: sure [20:52:35] multichill, in an unrelated language? [20:52:45] Always better than nothing at all [20:53:03] awjr: just invited you [20:53:18] i'm not convinced that the boxes speakers work [20:53:46] http://wlm.wikimedia.org/api/api.php?action=adminlevels&format=json&admtree=us&uselang=nl <- This doesn't look very Dutch [20:53:49] awjr: FAIL [20:53:59] tfinc: i feel like i remember seeing a pair of small speakers in r31 [20:54:02] awjr: this box is proving to be more fail then win [20:54:05] dunno if they're always in there or not though [20:54:15] tfinc that is too bad :( just in terms of peripheral hook ups? [20:54:20] awjr: i'd need them to be usb speakers [20:54:26] ... [20:54:35] the thing is. this device has an internal speaker [20:54:43] but it stops working after i plug in the yeti mic [20:54:54] le sigh [20:55:20] i'll have to tinker with it more later today [20:55:49] but i do have all the cabeles now [20:55:55] so its purely software now [20:56:15] MaxSem: a small number of people are using the beta. They will re-install with the next beta, and we can mention the API compatibility in the release notes [20:56:46] philinje, I mean can I break the compat right now?] [20:56:52] guess not [20:57:12] tfinc: That was one of the feedback things I got. Please show a warning or something when people are using an old version [20:58:07] MaxSem: better to do it at end of week [20:58:23] ok [20:58:41] MaxSem: could we use something else for testing changes? [20:58:43] awjr: hey, i will change my schedule this week and next to Mon, Wed, Fri [20:59:17] awjr, not test but deploy new features [20:59:21] philinje: ok - are you still able to meet tomorrow to discuss the upcoming iteration? [20:59:24] MaxSem: roger [20:59:37] awjr: yes [20:59:39] I just don't want to keep two FT indexes, TS has enough [20:59:45] philinje: cool [20:59:51] and I think there needs to be another meeting before the estimation meeting on Wed, for discussion of cards with certain engineers [21:00:19] philinje: can it not be done ad-hoc? [21:00:23] it's hard to squeeze that in with weekly iterations [21:00:38] ad hoc is not working for various reasons [21:01:10] philinje: ok what do you propose? [21:02:05] maybe a half hour with Jon, Brion, you and Max before the estimation meeting [21:02:20] like, immediately before, or sometime on tuesday? [21:02:55] well, Wed would be better for my schedule, so immediately before [21:03:08] philinje: purpose? [21:03:46] awjr, what is the number of the current beta? [21:04:01] to clarify the cards and make sure they are suitable, as well as explaining things that are not so well understood [21:04:07] MaxSem: 2 [21:04:15] thanks [21:04:46] philinje: if we do it 30 minutes before estimation, then there's no time to make any improvements for estimation [21:06:10] awjr: i can do the changes on the spot? [21:07:22] philinje: we've basically been using the weds meeting for that purpose anyway and finishing up estimation on monday. i think the problem is that a) new things get introduced between weds and monday and b) the cards aren't getting cleaned up enough before monday [21:09:22] awjr: there is a small amount of clean-up and a small amount of new cards, so the discussion is about whether something could be done, should be done, or how it will be done [21:10:22] philinje: then perhaps we should make that the focus of the weds meeting, and only do any prioritization on weds if it makes sense [21:10:33] there is very little opportunity for ad hoc discussion, even though some of us are int the same location [21:10:36] awjr: ok [21:10:44] philinje does that work for you? [21:10:48] yes [21:10:53] great [21:11:09]