[12:16] morning [12:16] it sucks to be at work at 8 in the morning [12:19] its great when that means @home on the couch. [12:19] kiko: ping === asgeirf [n=asgeirf@203-173-59-20.dyn.iinet.net.au] has joined #launchpad [12:49] lifeless, yeah? [12:49] lifeless, my baz situation is terrible :-( [01:09] lifeless, I issue: [01:09] baz branch rocketfuel@canonical.com/launchpad--devel--0 christian.reis@canonical.com--lozenge/launchpad--trivialities--0 [01:09] lifeless, it eats up 900MB and then blows up [01:09] with COTM and 1.4.2 [01:16] kiko-zzz: ouch [01:16] kiko-zzz: do a baz library-add rocketfuel@canonical.com/launchpad--devel--0 [01:26] Merge to rocketfuel@canonical.com/arch-pqm--main--0: merge in community contributions r=bjornt (patch-27: robert.collins@canonical.com) [01:43] kiko-zzz: try again now, I've fiddled stuff on chinstrap to help === stub [n=stub@203-217-37-199.dyn.iinet.net.au] has joined #launchpad === camilotelles [n=Camilo@20132139198.user.veloxzone.com.br] has joined #launchpad [03:53] whats the ubuntu keyserver called ? === robitaille [n=daniel@d154-5-117-228.bchsia.telus.net] has joined #launchpad [04:02] keyserver.ubuntu.com === Lathiat_ [i=lathiat@gasp.bur.st] has joined #launchpad [04:07] elmo: yah, figured that out :0 [04:08] Is it known that the various links the launchpad-integration stuff pull up dont work? (cant see a bug but more wondering if its just not implemented yet), ex: https://launchpad.net/distros/ubuntu/breezy/+sources/gnome-panel/+translate [04:11] Looks like a dumb bug, actually :/ [04:11] and the firefox link ends up with "page not found" [04:11] AssertionError: No page title in canonical.launchpad.pagetitles for sourcepackage_translate [04:12] ex: https://launchpad.net/distros/ubuntu/breezy/+sources/firefox/+gethelp [04:20] Bah - I''ve just been working on improving script logging and realized it is a use case for the old Librarian API where the Librarian creates the LibraryFileAlias and LibraryFileContent records and commits rather than the client :-P [04:20] rotfl [04:29] spiv: Am I correct in that the Librarian will still generate the db records if you don't send the File-Content-Id or File-Alias-Id headers (as the docstring I'm reading suggest)? [04:32] spiv: And if so, any thoughts on how to expose this in ILibrarianClient ? addFile returns the LibraryFileAlias, so it isn't approprate and we would need another method to stuff a file into the Librarian and return the URL (which has different transaction semantics of course, since the file will exist in the database but the client can't see it yet) [04:32] which one bet bzr would be dogfooding? [04:33] jblack: translation ? [04:33] lifeless vs kiko bet. One of you two gets pie in the face, depending upon bzr dogfooding or not. [04:34] upon canonical dogfooding bzr for rocketfuel development [04:34] bzr already dogfoods itself ;0 [04:34] Yes. Who's bet which way? [04:34] I'm one the 'it will be done' side of the bet [04:34] Poor kiko [04:36] stub: So, yes, the librarian still supports both ways. === lifeless hopes so [04:37] (although up till now the plan was to slowly phase out the server-side ID generation...) [04:38] I'm thinking of adding 'stuffFile' as a method to ILibrarianUploadClient which stuffs a file into the Librarian so it won't get rolled back. I can't think of a better name ;-/ [04:38] stub: Yeah, a method that just returns the IDs and/or URL would make sense. [04:38] stub: And to retrieve the file, a 'getStuffed' method ;) [04:38] spiv: The use case I have is I want to stuff the tracebacks into the Librarian instead of spitting them out, which will greatly improve our cronjob spam. [04:38] hehe... [04:39] (so one extra line - the url - insteead of a dozen) [04:40] or a hundred [04:40] sweet [04:40] stub: Hey, cute trick :) [04:41] Any better names, or will I go with stuffFile (with an XXX saying it should be renamed to something that describes the difference in transaction handling between it and its couterpart addFile, and why they must return different things) [04:42] stub: Hmm. [04:42] so maybe 'serverAddFile' ? [04:43] or remoteAddFile [04:43] or justTakeTheFuckingFile [04:43] Or add a serverOnlyDB=True flag to addFile. [04:43] Although that feels a bit wrong. [04:43] storeTheFuckingFileNowDammitSheIsGoingToBlow [04:43] yes [04:43] I vote the blow [04:43] Even though it doesn't change the return types at all, just most of the implementation ;) [04:44] spiv: We need a new method since the return types will be different (can't return a LibraryFileAlias as it isn't yet visible to the client) [04:45] stub: Hm, it looks to me like it's returning ints, not objects. [04:46] Or I'm looking at the wrong layer :) [04:46] eh? Oh. If I returned an int, it would be a useless one. A URL is useful straight away, unlike the id. [04:47] Yeah, if you use getUtility(ILibrarianClient).addFile(...) you'll get an int. Hmm, annoyingly it ditches the content id, only returns the alias id, so you can't reconstruct the URL... looks like a new method is the way to go, then. [04:49] But a method on ILibrarianClient makes sense, rather than ILibraryFileAliasSet (because you don't want it to return an ILibraryFileAlias) [05:02] stub: Can you make a note somewhere on the LibrarianTransactions spec about this? The "Future directions" there is assuming this is a YAGNI. === robitaille [n=daniel@d154-5-117-228.bchsia.telus.net] has joined #launchpad === _Rappy_ [n=hunt-pre@dsl-253-122.monet.no] has joined #launchpad === zyga [n=zyga@2-mi2-1.acn.waw.pl] has joined #launchpad === robitaille [n=daniel@d154-5-117-228.bchsia.telus.net] has joined #launchpad [08:23] spiv: line 140 of lib/canonical/librarian/web.py seems to indicate that the librarian assumes a 1:1 relationship between libraryfilealias and libraryfilecontent [08:36] spiv: Actually, make that lib/canonical/librarian/db.py line 22 [08:36] That method cannot be implemented with the current signature === spiv lokos [08:37] looks, rather [08:42] stub: All that assumes is that (contentID, filename) is unique in LibraryFileAlias. That's not assuming 1:1 between alias and content. [08:43] That is an incorrect assumtion [08:43] Yeah, it is. [08:43] (it used to be ok) [08:44] It has never been ok [08:45] I'm just poking it a bit on my branch to see if that is the only case and if it is a simple fix [08:45] Well, it used to be intentional. The design thinking behind that decision might not have been ok, though ;) [08:46] At a glance, it shouldn't be too hard to fix. [08:47] And will almost certainly involve removing much more code than needs to be added. [08:48] The main addition looks to be that LibrarianStorage will need a 'getAlias(aliasID) -> LibraryFileAlias' or similar method for c.l.web.LibraryFileAliasResource to use instead of getFileAlias. [09:02] hi [09:04] morning [09:08] SteveA: morning [09:08] hi mark [09:08] SteveA: is it possible to have a required: for a particular dbschema value? [09:09] like context/status/enum:CLOSED [09:11] do you want to show something on a page only when a dbschema has a particular value? [09:11] i'm trying to understand what you are asking. it doesn't make sense to me yet. [09:12] yes [09:13]

Reopen this Ticket

[09:13] is what i'd like [09:13] i see [09:13] though enum: is ugly [09:14] enum-value-is:CLOSED ? [09:14] the way you'd do that now is either write a method on the view class to say isClosedTicket(), and use view/isClosedTicket in your tal:condition [09:14] or use a python: expression in the page template [09:15] it would be quite easy and quick to add enum:CLOSED or enum-value-is:CLOSED [09:15] that returns a boolean, etc. [09:16] say, 50 loc max with another 50 lines of doctest documentation [09:19] sabdfl: decide on a name, and i'll do it this morning while i'm still waking up properly ;-) [09:20] enum-value === Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad [09:26] so, tal:condition="context/status/enum-value:CLOSED" [09:39] moin moin, Keybuk [09:39] SteveA: yes please [09:40] heyhey [09:41] sabdfl: underway [09:41] guys, i need good names for the support ticket tracker, and the spec tracker [09:42] are we tracking bugs on rosetta, malone, rest-of-launchpad, or are they all launchpad? [09:43] i tend to say to people "hey, have you considered using launchpad as your bugtracker for FooProject" [09:43] but, i say "have you considered using Rosetta to translate BarProject" [09:43] so, i think launchpad spec tracker, lauchpad ticket tracker, are good names [09:44] (or other names in that slightly dull ilk) [09:45] Keybuk: any idea why this might be? [09:45] steve@zeus8 /scratch/dists/launchpad $ baz archive-mirror [09:45] corrupt archive found (mname and mirror_of mismatch). sftp://chinstrap/home/warthogs/archives/steve.alexander@canonical.com name steve.alexander@canonical.com mirror_of sure [09:45] Unable to connect to any mirror for archive steve.alexander@canonical.com === SteveA looks into it more. [09:45] these seem to involve some of the things i had to change with jblack yesterday, to get my archives resigned [09:46] SteveA: the archive is registered in ~/.arch-params/archives/ but if you go contact the archive, it's =meta-info/name is something else [09:46] stevea@chinstrap:/home/warthogs/archives/steve.alexander@canonical.com/=meta-info$ cat name [09:46] steve.alexander@canonical.com [09:46] uh [09:46] =meta-info/mirror [09:46] sorry [09:47] $ cp name mirror -- should fix it [09:47] ok [09:47] Keybuk: nice. it works. thank you. [09:56] sabdfl: enum values are sometimes None, iirc. So, you'll want to be able to say enum-value:None I think. [09:57] SteveA: as a special case, yes [09:59] stub: please could you look at mark.shuttleworth@canonical.com/launchpad--helpme--0 ? [09:59] patch 25-97-0? [10:00] adds a few tables, and some minor tweaks (index, and some extra fields on product) [10:00] has comments.sql too [10:01] darn, None is a bit awkward in that it is lossy. With any other kind of dbschema item, i can inspect it, and ask it for what are valid values for it. For None, I don't even know that it came from a dbschema value, so it has to just two possibilities: enum-value/None or enum-value/(anything else). [10:02] on reflection, i'd prefer not to have None in dbschema, but allow the value of a dbschema item to be None, so it is NULL in the database, yet have it refered to in code as a standard dbschema item. [10:02] (a future refactoring perhaps) [10:03] still, easy to work around now. but, we lose some error checking in the case of None. [10:15] we don't really need NULL dbschema items [10:15] stub: pls ack on the db patch? === sabdfl [n=mark@pdpc/supporter/silver/sabdfl] has left #launchpad [] === dand [n=dand@gw.datagroup.ro] has joined #launchpad === carlos [n=carlos@243.Red-83-47-24.pooles.rima-tde.net] has joined #launchpad [10:23] morning [10:27] hi carlos === Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad === cprov [n=cprov@haddenham.pepperfish.net] has joined #launchpad === sabdfl [n=mark@217.205.109.249] has joined #launchpad [11:29] sabdfl: tracked down the bug in page templates that doesn't allow '-' in page templates. proposed a fix on the zope3 / page templates list, and with fred drake (maintainer). enum-values branch up for review. some minor improvements since you merged. [11:29] back to menus ;-) === WaterSevenUb [n=WaterSev@azevedo.astro.up.pt] has joined #launchpad [11:35] damn I'm good. pqm using config-manager now passes tests. [11:35] kiko-zzz: prepare for a PIE. [11:39] now for getting configs from bzr branches. [11:41] jamesh: ping [11:45] cprov: pong [11:49] jamesh: do have any ETA for review my branches in you queue ? [11:54] aw crap [11:54] people have added in YET MORE WARNINGS [11:54] i'm going to fix the existing ones, or get other people to fix them, and make warnings into errors when running tests [11:57] warnings from your db nazi ? [11:58] no [11:58] just warnings [11:58] warnings about ambiguous sql query results [11:59] i fixed all of them before brazil [11:59] well, salgado fixed some [11:59] now they're back [11:59] BjornT, bradb-away : these all seem to be in malone code === BjornT takes a look [12:01] The method BugTaskReleaseTargetingView.createTargetedTasks [12:01] request url: http://localhost:9000/distros/debian/+bugs/1/+target [12:01] The method PersonView.setUpAssignedBugTasksToShow [12:01] request url: http://localhost:9000/people/sabdfl/+assignedbugs [12:01] The method PersonView.__call__ [12:01] request url: http://localhost:9000/people/sabdfl/+assignedbugs [12:01] :1: UserWarning: Getting a slice of an unordered set is unpredictable. [12:01] [12:01] the last one is almost certainly from a system doc test or a page test [12:01] the others are in code and need sorting out [12:02] SteveA: Soyuz has some critical queries as well. [12:03] critical? [12:03] SteveA: ok. i didn't add those, but i can take a quick look to see if it's easy to fix === lifeless feels dirty [12:03] okay. do you know if brad added those? [12:03] sabdfl: ack. [12:03] once these are all fixed, we can make the warnings errors so that they won't occur again. [12:03] sabdfl: Please stick review requests on the wiki so I can't lose them ;) [12:04] SteveA: i'm not sure, but he did the release targeting, so i'd assume he added them. [12:07] SteveA: they generate lot of random warnings and are slow, they need polishing [12:07] cprov: i don't see the warnings when i run tests [12:07] cprov: are they not in RF yet? [12:08] SteveA: they are, soyuz is not entirely tested atm. [12:08] well, that's shite. [12:09] if there's no tests, then the code is kinda broken by default. [12:09] SteveA: indeed, we can't trust [12:09] we need to know the extent of the problem [12:10] like, what modules / classes / functions are not tested [12:10] list these, so we know how big the problem is [12:10] right now, i have no idea how much of a problem this is, or how much work it is to rectify [12:12] SteveA: I totally agree and feel the same about soyuz code, it's generally bronken and we don't know it, it's always a surprise. [12:13] okay. we must organise an audit. [12:13] if we don't know exactly what the problem is, we can't fix it [12:13] Indeed. Rolling this into the meeting item I suggested in /msg seems like a good plan === cprov is happy with this decision [12:15] separate item [12:15] it [12:15] is on the agenda [12:15] okay [12:15] stub: is there a place to stick dba-only reviews? [12:16] end of PendingReviews page [12:16] there is a DBA section [12:16] ah. cool. thanks [12:16] SteveA: in PersonView.setUpAssignedBugTasksToShow there's an XXX about the warning, no author, though... [12:16] argh [12:16] how does this stuff get past review?! [12:17] well, it's not impossible that it was one of kiko's trivials [12:18] stub: added to wiki [12:19] jamesh: ping === stub wonders wtf has happened to his sound again??? [12:23] sabdfl: yeah? === stub [n=stub@203-217-37-199.dyn.iinet.net.au] has joined #launchpad [12:25] jamesh: howdy. please could you take a look at the Specification infrastructure that i landed last week, and ping me so we can have a quick chat about a bof-o-matic scheduler? [12:25] database/specification* [12:26] shows up on product and distribution as a "Specs" tab, and also an "Add Feature Specification" action item [12:26] okay [12:27] sabdfl: Do you want constraints on the ticketing table, eg. only assigned to a distribution/sourcepackagename or a product? Or can a ticket be opened on 1 product and 1 sourcepackage/distro simultaneously [12:32] SteveA: i can fix the first warning. the other i'm not sure exactly how to fix, they were added by salgado, though. [12:32] okay. please do fix the first one [12:33] we can talk together about the others, and with salgado, later today or tomorrow when you're at pov [12:33] stub: see the comments :-) [12:34] but yes, i was planning to relax that constraint [12:34] a sort of "push upstream" feature [12:34] stub: saw my request to remove some English po files from plone? [12:34] probably from distro -> upstream more than from upstream -> distro(s) [12:34] stub: please ignore it [12:37] jordi: ok. [12:37] jordi: I wasn't sure if it was possible anyway without much work ;) [12:38] sabdfl: The commends said the constraint, so I just added them in. Shall we leave them there and drop them if we add that feature? [12:40] stub: hmm. that's not cool. At some point i'll need it for real :) [12:42] jamesh: is your review-branch script source around somewhere ? [12:42] jamesh: I want to bzrify it [12:44] jordi: Probably best if we add a feature to hide or deactivate them (which means we get too keep all the information linked to them). [12:44] lifeless: james.henstridge@canonical.com--2004/pending-reviews--devel--0 [12:45] stub: +1 on hiding pofiles rather than removing them [12:45] they will Just Come Back (tm) [12:53] yup. As long as people can't click on them to translate the Evil Useless PO.. :) [01:03] Merge to rocketfuel@canonical.com/launchpad--devel--0: [trivial] Final bits for launchpad-buildd package 2 (patch-2336: daniel.silverstone@canonical.com) [01:04] Meeting-00:55 [01:06] stevea: Here? [01:06] #canonical-meeting [01:07] morning, carlos [01:07] vinsci, morning [01:10] ddaa: before we meet next week, please could you clear out IBranch so that it looks more like ITicket, and we can start using it immediately? [01:10] i think you'll need to move it to IPyBazBranch or something, to free up the namespace [01:11] err... no ddaa === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [01:14] morning salgado [01:15] yo sabdfl! [01:15] stub, around? === niemeyer [n=usuario@brutus.conectiva.com.br] has joined #launchpad [01:22] morning niemeyer [01:23] niemeyer: can we take some time to catch up today? in the next two hours or so, before i head to south africa? [01:23] salgado: yes [01:23] launchpad meeting in 25 mins [01:23] Good morning! [01:24] sabdfl: Sure! [01:24] sabdfl: I'll be a little bit off today because I'm installing Ubuntu on the notebook, but we can certainly do that [01:25] SteveA: Where's the meeting? Here? [01:25] stub, can you hold the production tag until (your) tomorrow morning, and review the shipit DB patch for me? (I really need to get this in the next rollout) [01:25] niemeyer: yes, here [01:25] niemeyer: lasts exactly 45 minutes [01:25] Ok.. my /home/niemeyer backup should be finished by then.. :-) [01:26] salgado: ok [01:26] stub: what is your tomorrow morning? === Kinnison has a patch he wants to get into RF which explicitly shouldn't go into production this cycle [01:27] stub, here's the last version of the patch. it's not going to be changed before I merge everything. https://chinstrap.ubuntu.com/~dsilvers/paste/fileyzrigW.html === Nafallo [n=nafallo@unaffiliated/nafallo] has joined #launchpad [01:31] Kinnison: Probably about 16 hours time [01:32] sabdfl: Please, ping me when you're ready [01:32] salgado: any idea when you'll be okay to merge? [01:33] Kinnison, it has to be in less than 10 hours, so that's what will be [01:35] salgado: You got comments for me to look at too? [01:37] stub, did you see my email about the whitespace migration script? [01:37] stub, oh, shit. I forgot that. will write now [01:37] carlos: yes, but havn't got there yet sorry. [01:38] salgado: can you talk with bjorn please about the warnings that some person/bug pages and code is generating? [01:38] SteveA, sure. I do remember we talked about this problem though. and we didn't find what caused them [01:39] i thought we did, and you had a plan for fixing them [01:39] stub, ok, if you can do that before leaving today that would be really good so I could get some data tomorrow [01:39] okay, i'll look into it later [01:39] maybe with bjorn tomorrow [01:40] SteveA, yes, the problem is n PersonView.setUpBugTasksToShow(). there's an XXX there. but as the comment says, everything there has an oderBy [01:41] salgado: It all seems fairly clear except for ShockAndAwe, so they can be done later if you have a deadline [01:42] stub, okay. I'll do for the shock and awe and try to do for some others. anyway I'll leave an XXX in the DB patch to remind me to do that. do you think it's a problem? [01:43] A bug report is better, and you can just describe shockandawe to me now if you would rather. [01:46] stub, okay. the shock and awe is the name of a program. we'll be sending some computer shops (and maybe other shops?) a letter with some information about shipit and a token. then they'll be able to login with that token (their account is already created by one of the ShipIt admins) and place a request [01:46] launchpad meeting soon. /msg me items for the meeting [01:47] salgado: But what goes in the table? [01:49] stub, ah, each row contains only the information about a specific shock and awe program, and that can be linked to the ShippingRequest table === SteveA goes to workrave before the launchpad meeting === Kinnison too [01:53] bradb: what is your current spec pipeline? === camilotelles [n=Camilo@20132139198.user.veloxzone.com.br] has joined #launchpad [01:55] BugInContext (not yet approved, just wrote it yesterday, blocks BugAndTaskPageURLs) and then implement MaloneSearchResults on the other bug listings (the first merge only implements it on the sp bug listing page.) After that, it depends entirely on what else is part of MaloneOneDotZero (I did extensive gardening lately to make it easy for others to tell me what I understand 1.0 to be, what spec statuses are, etc. but haven't heard [01:57] GMV [01:57] er, that is, i did extensive gardening to record what I understand MaloneOneDotZero to be, to give others a prelim. list and be able to say "yeah, that looks good" or "add this, remove this, etc." [02:00] MEETING TIME [02:00] so it is [02:00] and I'm here [02:00] all present, please yawn^w say Aye! [02:00] Aye! [02:00] Aye [02:00] Aye! [02:00] aye [02:00] Aue! [02:00] aye [02:00] erm, s/u/i/ [02:00] aye [02:01] here [02:01] aye [02:01] aye [02:01] morgs sends apologies [02:01] daf is off sick [02:01] niemeyer: around? [02:01] mpt is off sick [02:01] ddaa is on vacation, isn't he? === mpool [n=mbp@cor6-ppp610.for.dsl.connect.net.au] has joined #launchpad [02:02] stub: ? [02:02] yer [02:02] debonzi is at university [02:02] anyone not accounted for? [02:02] as usual, /msg me extra agenda items as we go along [02:02] SteveA, I'm giving niemeyer a ring [02:03] okay. he had a phone call with mark [02:03] so, maybe that is still going on [02:03] he was around a little earlier [02:03] here [02:03] hi james [02:03] jordi? === mpt [n=mpt@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [02:04] hi mpt. how are you feeling? [02:04] let's move onwards [02:04] == Agenda == [02:04] - roll call [02:04] - agenda [02:04] - next meeting [02:04] - production / staging [02:04] - who can work on soyuz ui? [02:04] - soyuz not tested [02:04] niemeyer apparently wasn't notified of the meeting, so I apologize for him -- he's currently out getting a hard drive to swap into ubuntu [02:04] - defining malone 1.0 [02:04] - three sentences [02:04] [02:04] SteveA: a bit light-headed, but better [02:04] thanks [02:04] we called the roll, displayed the agenda [02:04] next meeting: same time next week? [02:05] yes [02:05] Aie. [02:05] SteveA, yes [02:05] IOW, not 22h ago [02:05] yo === ..[topic/#launchpad:SteveA] : Discussion with Launchpad users and developers. || https://launchpad.net/ || Includes Rosetta and Malone. || Developers' meeting, Thursday 8 Sep, 12:00 UTC [02:05] yes [02:05] - production / staging [02:05] stub: ? === SteveA notes he forgot to mention activity reports in the agenda. that can come after the current item [02:06] The usual. Staging running fine daily updates, production will be tagged when salgados shipit feature branch lands === lifeless notes its a shame we dont roll out code that has been on staging for a while [02:06] - activity reports [02:06] stub, the database on staging hasn't been refreshed in a while, right? [02:06] so tomorrow or saturday I expect === SteveA waits [02:07] lifeless, in this particular instance, we should have -- I miscommunicated with stub [02:07] staging db should be refreshed daily [02:07] stub, it would help if you /didn't/ cut exceptions, even for you-know-who -- policy is policy === kiko puts stub in dire straits [02:08] stub, interesting -- carlos said it wasn't being refreshed because of the rosetta update [02:08] carlos? [02:08] kiko, I asked stub to refresh it today before next script run [02:08] I switched it back on around tuesday [02:08] ah, okay [02:08] Here! Here :-) [02:08] perfect [02:09] hi niemeyer [02:09] ready to move on? [02:09] (to stub) [02:09] yup [02:09] - activity reports [02:09] stub, please disable it again this weekend (at least until Friday night in Europe) so I can get new language packs to test latest changes [02:09] carlos: i will [02:09] stub, thank you === stub is up to date [02:09] ugly ducklings vs sailing on swan lake [02:09] uptodate (last 2 went in 5 minutes ago) === BjornT is up to date === carlos is up to date [02:10] the usual [02:10] ugly as ugly can be, but will this time start over [02:10] stub: any news about gina run in production ? [02:10] up to date === salgado is up to date too === cprov is up [02:10] I'm a few behind. === Kinnison stretches his elegant white neck out, realises it's covered in swan feathers and has five simultaneous asthma attacks === SteveA has activity reports, but not sent yet. will send them today. [02:10] sending in one for yesterday (restarting) === moonunit [n=moonunit@bi-02pt1.bluebird.ibm.com] has joined #launchpad [02:11] zappa! [02:11] anyone else? [02:11] yourself? [02:11] ah [02:11] i represented [02:11] sorry, the /mes get me sometimes [02:11] okay, moving on === jblack thumps his chest twice with his fist. RepreSENT === niemeyer is up to date ;-) [02:12] as there's no bot to help out, if i missed anyone, speak up [02:12] - who can work on soyuz ui? [02:12] so, daf was scheduled to take some time out of rosetta development to improve the soyuz pages [02:12] nobody's really free at the moment [02:12] but, daf is on sick leave [02:12] I'm interviewing for replacements [02:12] mark has plans to do some model refactoring in soyuz that makes the pages easier to write [02:12] we have quite a few good prople [02:12] debonzi is at uni [02:13] interviews went well? [02:13] prople? where did that come from? [02:13] yes, lots of good people, too. [02:13] up to date [02:13] we'll have winners declared next week, I'll have them have a phone call with you before approving [02:13] okay, cool. [02:13] so, the answer is, no soyuz ui work for a little while [02:13] but some end in sight [02:14] cprov, Kinnison: any other points on this issue? [02:14] cprov, I started the build farm work on Tuesday, continuing that this morning [02:15] For now it's not too bad [02:16] Mark's model refactoring will probably have to happen before someone works on the UI [02:16] okay, that's at least a week off happening [02:16]