/srv/irclogs.ubuntu.com/2008/01/31/#launchpad-meeting.txt

=== bigjools-afk is now known as bigjools
=== mrevell is now known as mrevell-lunch
=== SteveA_ is now known as SteveA
=== mrevell-lunch is now known as mrevell
* gmb runs to get a drink13:55
kiko#startmeeting13:59
MootBotMeeting started at 13:59. The chair is kiko.13:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:59
kikohello engineers of the third millenium14:00
kikowelcome to another fantastic weekly meeting14:00
daniloskiko: thank you14:00
kikohosted by your perpetually unstable chairman14:00
kikokiko o cruel14:00
intellectronicame14:01
kiko(that means kiko the humble in portuguese)14:01
kikowhere's my agenda14:01
* kiko shows raw text14:01
kikothis is a RAW agenda14:01
* Hobbsee fears14:01
* Hobbsee covers eyes14:02
kikoso who is here this bright morning14:02
mptme14:02
gmbme14:02
kikome14:02
carlosme14:02
matsubarame14:02
adeuringme14:02
intellectronicame14:02
danilosme14:02
sinzu1me14:02
mrevellme14:02
mthaddonme14:02
bacme14:02
EdwinGrubbsme14:02
cprovme14:02
salgado_me14:02
Hobbseenot me14:02
bigjoolsme14:02
jtvme14:02
=== salgado_ is now known as salgado
allenapme14:02
Iulianme14:02
BjornTme14:02
schwukme14:02
SteveAme14:02
barryme14:02
kikokeep em coming14:02
flacosteme14:02
vednisme14:02
kikowhere's this new chap, maris14:03
kikoah there you ae14:03
* flacoste welcomes vednis14:03
statikme14:03
kikoare too14:03
kikoSteveA, we have no stew.14:03
kikobut now we do!14:03
stubme14:03
FujitsuThat was nice timing.14:03
stubSlow clock sorry14:03
kikovery good14:03
leonardrme14:04
kikohello sprinters14:04
kikothanks for making it14:04
kikothis meeting is not the same without sprinters14:04
kikoso14:04
kiko[TOPIC] agenda!14:04
MootBotNew Topic:  agenda!14:04
kiko * Roll call14:04
kiko * Agenda14:04
kiko * Next meeting14:04
kiko * Actions from last meeting14:04
kiko * Oops report (Matsubara)14:04
kiko * Critical Bugs (Rinchen)14:04
kiko * Bug tags14:04
kiko * Operations report (mthaddon)14:04
kiko * DBA report (stub)14:04
kiko * Sysadmin requests (Rinchen)14:04
kiko * New packages required (salgado)14:04
kiko * A top user-affecting issue (mrevell)14:04
* kiko doesn't fuck up the paste! 10 points14:04
statikhurrah!14:04
kikothat knocks off two topics in one go14:04
mrevellheh :)14:04
bigjoolskiko, your language is terrible today :)14:05
kiko[TOPIC] behold a pale horse!! next meeting time14:05
MootBotNew Topic:  behold a pale horse!! next meeting time14:05
kikovery good14:05
kikoso Rinchen the Ill has been attempting to conspire to change the meeting time14:05
kikothe proposed meeting time is 18:00 UTC14:05
kikothis is in order to allow Tim Penhey the Kiwi to participate14:06
kikoprimarily14:06
kikoI think it's really important that all team leads be here14:06
SteveAand His Team of Antipodians14:06
SteveAhi abentley14:06
SteveAdoes aaron know about this meeting?14:06
kikoI believe Rinchen has contacted most people more seriously affected by this change14:06
stubNot me14:07
kikoSteveA, that's probably a question for his manager and super-manager <wink>14:07
SteveAstub: you commented in the last meeting14:07
* kiko hands edwinGrub some internet14:07
mptAll our managers are super-managers14:07
kikois anyone surprised or taken aback by 18:00 UTC as the new meeting time, apart from stub?14:07
* SteveA basks in the flattery14:07
kikospeak now or hold your peace until next thursday14:08
SteveAjamesh is not here14:08
bigjoolsI did not know about it14:08
danilosI'd prefer to have it earlier once we hit summer time again14:08
danilosuntil then, I am completely fine with it14:08
kikosure, we can consider changing it again in the future14:08
kikovery well14:08
intellectronicai'd prefer to have it earlier, since i have a class on thursday evenings14:08
intellectronicathat's not as serious as the kiwis' needs, though14:09
kikoyeah, to me it's a big deal that tim can't come14:09
Hobbsee3am meetings are fun!14:09
kikointellectronica, chat with me about it after the meeting, maybe we can arrange something14:09
kiko[AGREED] 18:00 UTC next thursday, next meeting14:09
MootBotAGREED received:  18:00 UTC next thursday, next meeting14:09
kikothanks MootBot the Redundant14:09
daniloskiko: I assume this is set for the future meetings as well?14:09
gmbkiko: Someone should update the team calendar. Want me to take care of that?14:09
danilos(until discussed and changed again)14:09
stubIf we are changing the time, we could consider changing the day too (although Thursday is now a good day for me)14:09
kikogmb, thanks!14:10
kiko[ACTION] gmb to update the team calendar and the meeting agenda14:10
MootBotACTION received:  gmb to update the team calendar and the meeting agenda14:10
kiko<wink>14:10
kikodanilos, yes, that's correct.14:10
gmbBoys and their toys...14:10
kikobut we can change it again14:10
kikothat's the beauty of decisions14:10
kiko[TOPIC] Actions from last meeting14:10
MootBotNew Topic:  Actions from last meeting14:10
kikoso the actions were:14:10
kiko * kiko to add the lp-dependencies question to the MeetingAgenda template14:11
kikoI did that, but somebody killed it?14:11
* kiko curses14:11
kikooh, sorry, I did14:11
kiko * New packages required (salgado)14:11
kiko10 points for doing it, then -10 points for not noticing14:11
kikoRinchen and kiko have inflicted the 18:00 time on us, so done too14:11
kikoSteveA and stub: staging sorted, I believe?14:12
kikoand mrevell and mpt?14:12
kiko* Rinchen and kiko to figure out how to manage lp-bzr's absence from the meeting; consider rotation or time-shift14:12
kiko * SteveA and stub to discuss options for staging DB and report back14:12
kiko * mrevell and mpt to discuss https://launchpad.net/bugs/18548614:12
ubotuLaunchpad bug 185486 in launchpad "Merge account option should be on profile page" [Undecided,New]14:12
* kiko discovers how to paste in X14:12
mptWe discussed it briefly14:12
mptI don't remember the conclusion14:12
mrevellmpt: We concluded, I believe, that you'd look at a better way of handling it.14:13
SteveAwe're putting staging on carbon14:13
mptah yes14:13
kikoGOOD14:13
mthaddonyup14:13
mptI will need to solve it while rejigging the person page14:13
stubkiko: staging only sorted in the short term, although that might depend on the langpack db14:13
mrevellmpt: as part of the Actions menu changes, I think.14:13
kikothe short term is what I'm after14:13
kikothanks stub14:13
* mpt assigns it to self14:13
kikothanks SteveA14:13
kikoSteveA, mthaddon says there's an ETA of ~ 1.5 weeks on that14:13
kikoconfirmed?14:13
mthaddonkiko, confirmed14:14
kiko[AGREED] staging to carbon (and in 1.5 weeks or so)14:14
MootBotAGREED received:  staging to carbon (and in 1.5 weeks or so)14:14
mthaddonor sooner, I hope :)14:14
kikompt, anything more to add to the subject?14:14
danilosstub: what's going on with langpack db on carbon (if anything)?14:14
* kiko clicks tongue14:15
stubdanilos: I don't know14:15
kiko[TOPIC]  * Oops report (Matsubara)14:15
MootBotNew Topic:   * Oops report (Matsubara)14:15
kikodo it mats14:15
matsubaraToday's oops report is about bugs 187389, 157606, 185706, 4483414:15
ubotuBug 187389 on http://launchpad.net/bugs/187389 is private14:15
matsubaraYesterday I asked flacoste to take a look at bug 187389. It might interest14:15
matsubarapeople in the SC team as well.14:15
ubotuBug 187389 on http://launchpad.net/bugs/187389 is private14:15
matsubaraI found out about it while trying to reproduce bug 157606. Someone from the Bugs team would like to take that one?14:15
ubotuLaunchpad bug 157606 in malone "IntegrityError with unknown milestone when changing bug's project" [Medium,Confirmed] https://launchpad.net/bugs/15760614:15
mptkiko, I just assigned the bug to myself.14:15
mptfor 1.2.4.14:16
kikompt, thanks.14:16
matsubarasinzu1: you ok with targetting bug 185706 to 1.2.2?14:16
kikomatsubara, ah, because of the tickcount thing14:16
* sinzu1 thinks14:16
kikodoes that bug really need to be private?14:16
matsubarastub, I've added 3 more OOPSes to 44834. Please follow up in the report if that sheds any light there.14:16
ubotuLaunchpad bug 185706 in launchpad "OOPS in +editemails form if email address field is empty" [Undecided,New] https://launchpad.net/bugs/18570614:16
sinzu1matsubara: I'll commit to 1.2.214:17
flacostehmm, we keep getting problems with the +editemails form14:17
matsubarathanks sinzu114:17
kikosinzu1, flacoste: what's up with that?14:17
flacostekiko: we'll look it up14:17
kikoflaky validator is what this one looks like14:17
kikovery well14:18
sinzu1kiko: bad validation14:18
kiko[AGREED} sinzui agrees to https://launchpad.net/bugs/185706 for 1.2.214:18
MootBotAGREED received: [AGREED} sinzui agrees to https://launchpad.net/bugs/185706 for 1.2.214:18
ubotuLaunchpad bug 185706 in launchpad "OOPS in +editemails form if email address field is empty" [Undecided,Confirmed]14:18
matsubarasomeone from Bugs?14:18
kikooh you don't need the angles, hmm14:18
BjornTmatsubara: you can assign bug 157606 to me14:18
ubotuLaunchpad bug 157606 in malone "IntegrityError with unknown milestone when changing bug's project" [Medium,Confirmed] https://launchpad.net/bugs/15760614:18
matsubaraThanks BjornT14:18
kikoflacoste, what's the decision on 187389?14:18
kikoAGREED <BjornT> matsubara: you can assign bug 157606 to me14:19
kikohmm14:19
kiko[AGREED <BjornT> matsubara: you can assign bug 157606 to me14:19
flacosteflacoste: we'll also look that one up14:19
kiko[AGREED] <BjornT> matsubara: you can assign bug 157606 to me14:19
MootBotAGREED received:  <BjornT> matsubara: you can assign bug 157606 to me14:19
flacostekiko: ^^^14:19
kikoweird.14:19
kikothanks flacoste14:19
matsubaragot it alredy14:19
matsubaraalready, even14:19
kiko[AGREED] <kiko> flacoste, to take 187389 for 1.2.2 too14:19
MootBotAGREED received:  <kiko> flacoste, to take 187389 for 1.2.2 too14:19
kikomatsubara, what else? I thought I saw some weird OOPSes in yesterday's report.14:20
stubBug 4483414:20
ubotuBug 44834 on http://launchpad.net/bugs/44834 is private14:20
matsubarakiko: which one?14:20
kikomatsubara, can't look them up now though14:20
matsubaraI asked stub to take a look in the weird ones from yesterday's14:20
matsubaraI don't know if it's the same, but it's a SQLObjectNotFound error14:21
kikoright14:21
kikovery good14:21
kiko[TOPIC]  * Critical Bugs (Rinchen)14:21
MootBotNew Topic:   * Critical Bugs (Rinchen)14:21
matsubarajtv also took a look since the same bug hit on TrannslationMessage14:21
kikoyeah, I saw that14:22
kikosomething about doesn't exist in the database, right?14:22
matsubarano critical bugs from Rinchen14:22
kikogreat14:22
matsubarayes kiko14:22
kiko[TOPIC] * Bug tags14:22
MootBotNew Topic:  * Bug tags14:22
stubmatsubara: Not sure if I'm best for that - looking like an SQLObject issue, possibly caching.14:22
kikono tags proposed14:23
kikoso it's getting to that time14:23
kikowhere tom tells all14:23
matsubarastub: who'd be the best person to look at it? jamesh perhaps?14:23
kiko * Operations report (mthaddon)14:23
mthaddonIn the process of migrating the staging DB to carbon, demo to jubany and the langpack DB to asuka14:23
mthaddonIS is working on the timing of testing for new production DB - I'll update everyone as soon as I know the details14:23
mthaddonDid anyone have a chance to look at the backtrace I posted to the list?14:23
mthaddonThat's it from me unless there are any questions14:23
SteveAstub: which bug is that?14:24
salgadomthaddon, from which appserver is that BT?14:24
kikomthaddon, remind us about the backtrace.14:24
stubJubany should not be running demo14:24
kikoah, the crash14:24
kikocore14:24
kikowhatever14:24
mthaddonsalgado, it's from gandwana - not sure if it was lpnet3 or 414:24
stubJubany is the production db and shouldn't be running anything else14:24
matsubaraSteveA: bug 4483414:24
ubotuBug 44834 on http://launchpad.net/bugs/44834 is private14:24
kikoagreed with stub14:24
SteveAI think jubany can run demo14:24
mthaddonkiko, https://pastebin.canonical.com/2139/14:24
SteveAI'm interested in a rationale for why it shouldn't14:25
kikomatsubara, for bug 44834 to be properly debugged we'd need access to the DB logs.14:25
stubit can, but it shouldn't. Sysadmin 101 stuff.14:25
ubotuBug 44834 on http://launchpad.net/bugs/44834 is private14:25
SteveAI'm still not hearing a rationale14:25
danilosmthaddon: what are the reasons to move langpack to asuka? jtv, have you been involved in these discussions?14:25
carlosdanilos: see the mailing list14:26
daniloscarlos: ok, thanks14:26
mthaddonstub, my understanding is it's not a perfect solution, but better than having staging updates on carbon affect demo14:26
carlosdanilos: they need some disk space in carbon14:26
mthaddondanilos, because we want to migrate staging DB to carbon, but we don't have enough disk space for that and langpack as well14:26
daniloscarlos: ok, but do we need langpack db if we can't use it for performance testing?14:26
kikocarlos, danilos, jtv: asuka isn't a speed demon14:26
daniloskiko: exactly my point14:27
kikooh that was unfortunate14:27
kiko[TOPIC] * DBA report (stub)14:27
carloskiko: ;-)14:27
MootBotNew Topic:  * DBA report (stub)14:27
matsubaramaybe he was writing it14:27
Hobbseekiko: op abuse, no?  :)14:27
kikoyeah but I can't kick myself as host now14:27
kikogrumble14:27
* Hobbsee can, if you like...14:27
stubBecause that is the most critical system we have. You just don't stick other stuff on there. If anyone things 'launchpad is slow today', we have to shut demo down to remove that variable.14:28
carlosdanilos: good point... although right now we worry more about being able to debug problems than performance. Anyway, jtv is going to discuss alternatives with Steve and kiko outside this meeting14:28
daniloscarlos: ok, just making sure we're on top of it14:28
jtvcarlos: right.  The big problem is that staging is too slow.14:28
stubI can put more rationale together after the meeting.14:28
kikovery well14:28
kiko* DBA report (stub)14:28
kikoanything of note and concern stub?14:29
stubBut I am strongly opposed to putting any unnecessary services on jubany and I'm fairly sure the IS group would back me on that.14:29
SteveAI'd prefer we measure the effect of demo, and base a decision on measurement rather than just "nothing should run there"14:29
stubSteveA: It is a production system. If we want to experiment on it, then you have been feeding people the wrong message the last year.14:29
stubI've got most of a spec splitting Person into Person and Account, which is the first part of creating a high availability authentication service for things that need it, such as Landscape.14:30
stubI'm unsure of the status of the new database hardware evaluation.14:30
stubNothing else to report at the moment.14:30
kikothanks stub14:30
kikogreat news on person versus account14:30
kikoI will be your #1 fan when that's done14:30
kikobtw, thanks also for helping me prepare the query14:30
kikofor the SUBOPTIMAL distro upstream bugs report14:30
kikoanyone else have anything to thank stub specially for?14:31
kikovery well14:31
SteveAthe thing I don't get is that demo is meant to run exactly the same code as lpnet, just with a different database, for a small set of users evaluating it14:31
SteveAdemo is not for doing anything experimental on.14:31
SteveAif we're doing experiments on 'demo', they need to stop14:31
stubSteveA: It is taking resources on our bottleneck.14:32
kikoSteveA, I think it's more the fact that there is load interaction from running two instances14:32
SteveAstub: the APIs guys should read through your spec on splitting account and person14:32
stubEven if the load is fine for the first day or week or month even, it an screw up at any time.14:32
SteveAstub: please send leonardr a copy14:32
leonardryes please14:32
stubI'll put the wiki link on the mailing list when I've filled in some remaining sections.14:33
kikohow many of edwinGru do we need today?14:33
kiko[TOPIC]  * Sysadmin requests (Rinchen)14:33
MootBotNew Topic:   * Sysadmin requests (Rinchen)14:33
kikojoey's sick14:33
kikoso am I but I don't get any better so I'll handle this topic14:33
kikowho has RT requests14:34
* EdwinGru develops the secret to cloning14:34
kikoand wants them addressed14:34
mrevellkiko: I have request 29852, which is about mail to launchpad-feedback bouncing14:34
kikobigjools, did we get the package you wanted backported?14:34
kikomrevell, so I don't get that. I have seen mail getting through there regularly14:34
kikowasn't that a one-off fluke?14:34
bigjoolskiko: lamont installed his first version in mawson and it worked very well when I tested it14:34
mrevellAs of yesterday, I was still seeing some mail bounces and it'd be nice if the IS guys could take a look.14:34
mrevellkiko: some mail is getting through14:35
kikobigjools, that's great news! lamont is the man14:35
mrevellkiko: but it appears other mail is bouncing.14:35
bigjoolshe sure is14:35
kikomrevell, how does it bounce? can I see a bounce message?14:35
kikobigjools, communicate to him my thanks ** 214:35
bigjoolswill do14:35
mrevellkiko: Sure, just a sec. It's complainging of a timeout14:35
kikohe also helped me figure out my postfix mess14:35
kikookay14:36
kikoany other RTs?14:36
kiko[TOPIC]  * New packages required (salgado)14:36
MootBotNew Topic:   * New packages required (salgado)14:36
mrevellkiko: https://pastebin.canonical.com/2168/14:36
salgadoif any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP.14:36
kikoanybody have library requests?14:36
kiko514:36
kiko414:36
kiko314:36
kiko014:37
kikovery good!14:37
kikothat didn't even hurt14:37
kiko[TOPIC] * A top user-affecting issue (mrevell)14:37
MootBotNew Topic:  * A top user-affecting issue (mrevell)14:37
mrevellhi14:37
kikohi14:37
mrevell I've got a couple this week.14:37
kikoeww14:37
mrevell:)14:37
mrevellThe main issue I've seen reported this week has been translation timeouts, although I've seen that jtv has responded to reports on launchpad-users.14:37
mrevelljtv: is there a particular answer that you'd recommend for members of the Launchpad team to say if they're asked in #launchpad or other venues about translations timeouts?14:38
jtvThere was a spike last weekend.14:38
kikojtv, spike in use too? what do the server logs say?14:38
danilosjtv: language pack generation?14:38
jtvI have some recommendations that I repeat as necessary.14:38
kikoyeah, not very comforting ones though14:38
jtvdanilos: possible14:38
kikoso14:38
kikoquestion for you14:38
kikocarlos once upon a time wrote an AJAX suggestion fetcher14:38
kikowhat do we think of going back to that?14:39
jtvkiko: Yes, we do think of that.14:39
jtvkiko: sinzui has promised to look at that in later cycles.14:39
kikowhy sinzu1?14:39
carloskiko, jtv: I think we could try to profile current code again (it changed a lot with the new DB refactoring) before going for AJAX14:39
daniloskiko: I think we can instead hardcode only the handful of messages (like "File", "Open") which cause the problem14:39
daniloskiko: because we have thousands of rows for those14:39
kikodanilos, hmmm, that's an interesting thought14:40
kikohardcode where?14:40
kikoa special table?14:40
daniloskiko: yeah, possibly14:40
SteveAhardcode or cache14:40
kikointeresting14:40
sinzu1kiko: I was asked. I have some experience with that kind of problem. I have not hacked on it (I have some high priorities at this time)14:40
kikoINTERESTING IDEA!!!14:40
daniloskiko: these are only *external* suggestions, so it's not important to be 100% correct14:40
kikodanilos, +10 for a great new interesting idea14:41
danilosSteveA: hard code which ones we decide to cache14:41
kikoI had not considered it before14:41
kikoso two more topics before the bell strikes14:41
kiko[TOPIC]  * Future of the "ui" bug tag (mpt)14:41
MootBotNew Topic:   * Future of the "ui" bug tag (mpt)14:41
mpt<https://help.launchpad.net/TaggingLaunchpadBugs> says that the "ui" tag is for "A bug that suggests the user interface is confusing or otherwise difficult to use"14:42
SteveAflacoste: can we talk over https://devpad.canonical.com/~matsubara/oops.cgi/2008-01-30/B1498 in a bit?14:42
kikoso it does mpt14:42
mptbut <https://launchpad.net/launchpad-project/+bugs?field.tag=ui> shows that it's been used for many bugs that happen to involve the UI at all14:42
flacosteSteveA: sure, after our call maybe14:42
mptregardless of whether it's confusing or difficult14:42
kikompt, okay14:42
kikompt, why don't we have a confusing tag or something?14:43
mptSo, we either need to reinforce the current meaning, change the meaning, or retire the tag14:43
SteveAchange the meaning14:43
SteveAwhat kiko suggests14:43
SteveAui is for ui14:43
SteveAconfusing is for confusing14:43
kikoI'd change the meaning to mean "ui-affecting" which is a useful thing14:43
mptI don't think a "ui-affecting" tag would be that useful, because it would apply to ~1/3 of all Launchpad bugs14:43
kikothat's okay though14:44
mptand because I can't think of a use case for it14:44
mptWhy would anyone search for bugs that did or didn't include that tag?14:44
kikothere are interesting intersections14:44
kikosoyuz and ui14:44
kikompt, at any rate, you need a confusing tag, that's established14:45
kikowe can retire ui separately14:45
mptok14:45
kikoor even later if you feel it's useless14:45
kikoanyone have a comment on "confusing" as a bug tag?14:45
kikoor do we want to hold this until the next meeting?14:45
kikoSteveA, mpt?14:45
mptPerhaps I could think about it some more and make a proposal in the Bug Tags section next week14:45
kikompt, very well14:46
* mpt ponders a justplainwrong tag14:46
kikolast topic of the day14:46
kiko * What should we do about pillar +portlet-details (kiko)14:46
salgadois it the bug report that is confusing?14:46
salgadoor the UI?14:46
kiko[TOPIC at that * What should we do about pillar +portlet-details14:46
kiko-1014:46
kiko[TOPIC] * What should we do about pillar +portlet-details14:46
MootBotNew Topic:  * What should we do about pillar +portlet-details14:46
Hobbseempt: *grin*14:46
Hobbseempt: that would require being able to file tags on people.14:46
mptsalgado, good point14:46
kikoso intellectronica mpt and I have been engaged in a war around the +portlet-details portlet on pillars14:47
jtvsalgado: needs-info?14:47
mptI have?14:47
intellectronicawar?14:47
kikoI have the feeling that +portlet-details has been a standard name for now14:47
kikoand we expect most if not all content objects to have one14:47
kikodo others share this view?14:47
intellectronicai have a slight objection14:48
intellectronicasimilar to mpt's, i guess14:48
kikoso nobody cares about the fact that there is  a portlet-details for a bug, for instance, but not for product?14:48
kikoyes intellectronica?14:48
=== EdwinGru is now known as EdwinGrubbs
mptkiko, that's a means assuming an end14:48
intellectronicawhen the details portlet is not placed on the left hand column, i think it should have a different name14:48
mptWhat's your use case for everything having a portlet-details?14:48
intellectronicai wasted a few good hours exactly because this is confusing14:48
kikoI don't disagree intellectronica14:49
kikobut that points to me to a separate problem14:49
kikoa) does the actual code of the portlet need to be different?14:49
kikob) if it does, then shouldn't we have two separate files instead?14:49
kikompt, adding portlet filler, mostly. but it's a de facto standard and if you want to change it you talk about it first14:49
mptkiko, we did, in 2006.14:50
kikoare you being cheeky?14:50
mptNot at all.14:50
mptIt was part of the Launchpad 1.0 design discussions.14:50
kikowhat did we agree to then? I am an old man and my memory is withered14:50
mptThat for standard-ish metadata for projects, project groups, and distributions, we'd show it as a table on the Overview page, instead of as a portlet.14:51
kikompt, that's not what I'm discussing14:51
kikowhat I'm discussing is the renaming of the portlet.14:51
kikoyou could have a) copied it or b) made it reusable as a table without renaming it14:52
mptI could have just embedded it into the Overview page and deleted the portlet entirely14:52
mptand then we wouldn't even be having this discussion14:52
kikookay I won't discuss this further, but where I see smoke..14:52
mptbut I was in a hurry at the time, so I did it the quick way14:52
mptfor which I am now truly sorry :-)14:52
kikolast topic14:53
kiko[TOPIC]  * Blockers14:53
MootBotNew Topic:   * Blockers14:53
flacosteFoundations: not blocked14:53
jtvTranslations: need more kiko-time!14:53
BjornTBugs: not blocked14:53
matsubaraReleases Team: not blocked14:53
statiklpcomm: not blocked14:53
adeuringhwdb: not blocked14:54
bigjoolsSoyuz: not blocked14:54
kikovery well14:54
kikoI think that's all, once more14:54
kikoluckily for us14:54
kikoand for the lunch downstairs too14:54
kiko#endmeeting14:54
MootBotMeeting finished at 14:54.14:54
kikothanks for coming14:54
mrevellThanks all, thanks kiko14:54
statikkiko: thanks for hosting, and for not kicking me14:54
kikoas you can see, when I chair, we overrun!14:54
=== sinzu1 is now known as sinzui
kikosomebody should put up a vote to reinstate SteveA the Punctual14:54
flacostei thought SteveA was boycoittinf because of the channel change?14:55
=== salgado is now known as salgado-brb
kikoflacoste, he's your manager, you talk to him!!14:56
=== kiko is now known as kiko-fud
=== matsubara is now known as matsubara-lunch
=== salgado-brb is now known as salgado
=== kiko-fud is now known as kiko
=== matsubara-lunch is now known as matsubara
=== salgado_ is now known as salgado

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