[02:20] that would be a separate view altogether, as it is a page on its own [02:21] sabdfl: we can do that, if it is easier. [02:21] it'll be the same as any other Z3 widget really (except it'll take different init params, of course) [02:22] I'd like us to review what we have decided about people and package selectors, and then move on. [02:22] i'm talking about the forms that have these selectors on them [02:22] are we going to try to make them work well with the autogenerated forms? [02:23] sabdfl: yeah, that's what i'm saying. this'll be a widget like any other. (why wouldn't it be, afterall?) [02:23] it isn't hard -- they take the same input from a browser as any other widget that handles the same kind of data [02:23] this is just overriding the presentation of the data [02:23] as far as the code is concerned [02:23] yep [02:23] hello? [02:24] SteveA: let's pick up the pace of this meeting [02:24] the complex icky parts of a widget are those that handle form data sent by the browser [02:24] I'd like us to review what we have decided about people and package selectors, and then move on. (restated) [02:24] 1. brad will make a people-who-can-log-in selection [02:24] 2. stub will work on a pop-up people/packages selector [02:25] ok, some net weirdness, y'all disappeared [02:25] 3. steve will do a proof-of-concept-js thing [02:25] all done? [02:25] yup [02:25] yes [02:25] right [02:25] ok [02:26] dogfood: how is it going? [02:26] all new bugs shoudl be filed in dogfood malone now, right Brad? [02:26] can dogfood malone email people now? [02:26] SteveA: *have* to be :) i got jdub to disable the lp product in bugzilla [02:26] Kinnison: yes [02:26] yay [02:26] kiko: yes, I got already some mails [02:26] nice [02:26] Excellent. [02:26] are we migrating bugs from bz? [02:27] dilys integration should happen todayish [02:27] do we have the bug watch updater running on mawson? [02:27] kiko: i filed a bug for that. it's probably a topic for the next or next-next meeting [02:27] so we can set watches on bugzilla bugs? === BradB doesn't know anything about that. stub? [02:28] No - I pinged elmo about basic auth but didn't chase it through. [02:29] Watches are up and running, but our own bugzilla is problematic because of security (erm... not basic auth... SSL certificate I think?) [02:29] can we not allow things based on ip address in this case? [02:29] stub: huh? [02:29] mawson has an "intranet" ip address wrt the bugzilla [02:30] bugzilla watching is of very low priority to be honest. we're dogfooding, so even if it worked perfectly, you wouldn't know. [02:30] elmo: mawson needs to access the canonical bugzilla without a client certificate or basic auth. [02:30] of high priority is bug resolution workflow, because people are going to go in and fix bugs that i've already fixed. [02:31] SteveA: Oh - if "intranet" access means no cert or basic auth required, it should be working right now. [02:32] stub: it doesn't use client cert or basic auth (via apache), the auth is done on the bugzilla side? [02:33] stub: I'm making a suggestion that mandatory authentication in bugzilla could be turned off for requests originating at mawson. [02:33] are we sure we want to discuss bugzilla watching in this meeting? :) [02:33] yes. can we have bugzilla watching soon? [02:33] watching is a neat way to transition to malone [02:33] I'm not really too bothered about the details [02:34] elmo: bugzilla.warthogs.hbd.com is publicly available? [02:34] AFAIK it is [02:34] how about stub and elmo and brad can sort out bugzilla watching after the meeting? [02:34] elmo: the goal is for malone on mawson to be able to check the status of bugzilla bugs without needting to do client cert or basic auth [02:35] next? [02:35] daf: ping [02:35] stub: yes - but bugzilla won't let you see anything until you login [02:35] SteveA: pong [02:35] hiya daf [02:35] eek.... how embarassing... all those bugs are open to the world ;) [02:35] sabdfl: hi [02:35] SteveA: it was something i wasn't planning to think about until a week from now. my time is probably better spent making it possible to resolve bugs, right? :) [02:35] ok. Watches should be available right now on our internal bugzillas, and if it don't work it is a bug and should be reported! [02:36] daf and carlos: would you talk about getting rosetta to use the dogfood system? [02:36] bradb - can you not resolve a bug by editing the assignment to mark it "closed"? [02:36] Good news people! Gina just completed an update to today's hoary [02:36] SteveA: sure [02:36] Kinnison: rock [02:36] yep [02:37] sabdfl: kind of...there's no filtering though, so it doesn't buy you a heck of a lot (the amount of effort to actually find if something you're about to report has already been reported, and then from there already been resolved is enough to call it unusable.) [02:38] stub: eh, which bugzilla are you looking at? [02:38] sabdfl: and also, what if the bug is "closed", but there's still two package infestations saying "affected"? do we still show the package maintainer those in the bug listing? [02:38] BradB: I wasn't clear. By "sort out bugzilla watching", I meant "sort out how we're going to go about it, and write a message to that effect to the mailing list" [02:38] bradb good point [02:39] SteveA: ok [02:39] I'd like to defer discussion particular to malone to a malone meeting sometime after this meeting [02:39] as we are rather dragging on today [02:39] BradB: mdz wanted a "pending upload" state [02:39] for the assignment [02:40] maybe we should change "closed" to "pending upload" [02:40] SteveA: the sanity of bug workflow though depends on the people that are using it, so we need input not only "also", but rather "especially" from not-malone people. :) [02:40] then add a field to point at the "fixed" package [02:40] so "pending upload" is basically "closed" without a fixing package [02:41] SteveA: ok [02:41] sabdfl: we need closed though. [02:41] yes [02:41] BradB: sure, but we can continue that after the other stuff in this meeting [02:41] daf and carlos [02:41] SteveA: sure [02:41] but you're right, there is a problem with a bug marked "closed" without a package that closes it [02:42] what are you going to do to get rosetta on the dogfood system? [02:42] what help do you need from others? [02:42] how long will it take? [02:42] after the launchpad's mails we can assume then that our alpha testers will use the dogfood sytem, right? [02:42] when you're done movingn it, yes [02:43] although, the domain name they use will be the same as it is now [02:43] same db, same code, different domain [02:43] ok [02:43] need to (a) move user accounts, (b) move PO/POT files [02:43] I need a list of the things that are "particular" to the rosetta alpha system [02:43] the trickiest bit as far as I can see, is hiding Malone and Soyuz from the testers [02:44] perhaps we can do this using layers [02:44] such as having a custom front page, or whatever [02:44] we need to solve that problem anyhow [02:44] maybe we should solve it properly now [02:44] Can we just run multiple launchpad instances talking to the same database? [02:44] daf: I think that should be as simple as using the correct virtual hosting proxy rule [02:44] stub: we can, but I'd rather not do so if they are to have different code on them. [02:45] the code should be exactly the same [02:45] SteveA: really? [02:45] SteveA: how will it know to hide the tabs? [02:45] SteveA: Sure. A code drop would mean updating two codebases rather than one. [02:45] daf: get me the list of what is significantly "forked" in the code, and we'll work through it [02:45] I think it's mainly the main template [02:46] stub: we'd need to start thinking about ZEO if there was a round-robin/load balancing involved. For different domains, no problem with our current use of ZODB. [02:46] daf: ok, we can fix that with layers. [02:46] would it be easier if we just publish everything at launchpad.ubuntu.com? [02:46] then fix it properly when I've done the context stuff discussed yesterday [02:47] sabdfl: then all alpha testers will have access to all applications, is that what we want? [02:47] sabdfl: that doesn't make anything easier [02:47] use some sort of client-cert bsaed filtering to block access to directories other than /rosetta/ for the rosetta testers [02:47] SteveA: ok, will leave it in your hands [02:48] daf: so, as a matter of priority, make the appropriate change on the rosetta layer of the main launchpad code [02:48] i'm wondering whether we want to have people think of them each as distinct, or as a single system [02:48] daf: is there anything else in the code that needs changing ? [02:48] SteveA: other than that, it's changing the database and the ports used, I think [02:48] for example, for an upstream project foo.org, do we want them to just setup launchpad.foo.org and get bugs/bounties/translations/packages/support all in one [02:48] or do we want them to setup rosetta.foo.org and malone.foo.org etc. [02:49] daf: ok. Can you do the template change today, and start working on the moving of user accounts and product imports and po/pot export-import ? [02:50] daf: please stick up a wiki page with the list of tasks for getting rosetta using the dogfood system, estimate them, then start them [02:50] SteveA: do we have a cron jobs policy? [02:50] SteveA: we will need something like that to feed the database [02:50] with updated translations [02:50] carlos: but we don't need that yet, do we? [02:51] launchpad dogfood server has lots of products already [02:51] do you have that on rosetta alpha already? [02:51] and if we want to add their translations.. I hope we don't do it by hand [02:51] not yet [02:51] !lilo:*! Hi all. Reminder, if you're in the US and you want to attend the second day of the FTC's email authentication summit by phone, it begins in about 45 minutes, and the conference info is here: http://www.ftc.gov/bcp/workshops/e-authentication/ .... and please stop by ##ftc-summit (note two #'s).... thanks! [02:51] so it is a separate task, after getting rosetta alpha running on the dogfood system [02:51] !lilo:*! Actually, the conference has started now, please check the url for information on how to connect [02:51] but the script is almost ready (need to do some code refactoring) [02:51] sabdfl, launchpad.foo.org makes things a lot easier, IMO, and preserves the "launchpad brand" [02:51] it should not delay getting rosetta to use the dogfood system [02:51] sabdfl: If they have malone.foo.org and rosetta.foo.org, they will also need foaf.foo.org (or else foaf would have to be available under both malone.foo.org and rosetta.foo.org) [02:51] ok [02:51] I would love not having a soyuz virtualhost. [02:52] (because that means a virtualhost for each service) [02:52] carlos: well, updating translations by cron job is not the same as importing [02:52] daf: let me know when the wiki page is done, okay? [02:52] virtualhosts could be used to redirect into lp.../soyuz/ if the client wanted so [02:52] daf: the update can also do the import automatically [02:52] ok, and launchpad.foo.org we could get working a LOT sooner [02:52] also simplifies URL's, since everything is then in a fixed structure [02:53] YES! [02:53] and if we needed the separate virtual host thing, we can develop it later [02:53] well [02:54] SteveA: sure [02:54] so long as there is an easy API to get the public URL of something, it should be easy to change our minds later [02:54] as I said, it complicates URLs significantly; I'd rather soyuz.launchpad.org -> www.launchpad.org/soyuz automagically. and *that* be sold as the vhosting solution. [02:54] carlos: hmm, is an update really the same as the import? [02:54] sabdfl: what happens with our current alpha test domain? a forward to launchpad.shuttleworthfoundation.org/ ? [02:54] kiko: I agree [02:54] I suggest to keep the rosetta alpha as it is, from the outside [02:54] because you also need to consider [02:55] what if the person doesn't want a foaf.foo.org? [02:55] daf: as we are not creating new products/projects and we use soyuz information, yes [02:55] or rosetta.foo.org? [02:55] kiko: what complicates url's? [02:55] virtualhosting projects independently, sabdfl [02:55] (even if it is in the future) [02:55] carlos: we still need to create PO templates [02:55] projects being.... rosetta, malone, or projects being the upstream domains? [02:56] rosetta, malone and soyuz and foaf and doap and ... (you get the picture :) === SteveA wonders about calling them "launchplatforms" [02:56] but you are ok with an upstream project being able to create launchpad.upstream.org and have us handle that === SteveA thinks he's being silly [02:56] sabdfl, yes, definitely, that's perfect. [02:57] the answer seems to be different for soyuz [02:57] daf: true, is it a problem to create it if needed on update time?, a module could add a new domain so we will need to create a new template for an old product [02:57] i mean, soyuz WANTS to have a distro context [02:57] sabdfl: It means that if someone jumps from launchpad.upstream.org to launchpad.ubuntu.com, they will need to login a second time since the cookies cannot be shared cross domains. [02:58] sabdfl, but soyuz links to rosetta and malone internally. and then? [02:58] Bug 1949 resolved: first input field should be focused when translation page loads [02:58] https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1949 [02:58] stub: the single-sign-on stuff can fix that easily enough. it would be a couple of instant re-directs on going to the new site. [02:58] stub: we do have a solution to that, i think [02:58] nice work daf [02:58] sabdfl: It also complicates the issue of what URL to put in emails - launchpad.upsteam.org/malone/bug/65 or launchpad.ubuntu.com/malone/bug/65 [02:58] sabdfl: the code will work for any form that uses tabindexes correctly [02:59] ok [02:59] stub: good point [02:59] carlos: I'm not sure -- is there any extra information needed? [03:00] SteveA: Sucky because you have to use javascript redirects [03:00] stub: no, not javascript redirects [03:00] SteveA: Also doesn't scale if we end up with a few hundred virtual hosted launchpads. [03:00] daf: don't think so, we could use names like "main-1, main-2, main-3...." and rename it later by hand and get them based on their path inside the source code [03:01] stub: don't see why not. but, I think we're talking about different things. [03:01] daf: or we could even try to get the domain name for that po directory [03:01] do we have a decision on what to do about choosing virtual hosts for the present? [03:01] carlos: hmm, that's a bit smelly [03:02] carlos: let's add a form for creating new templates, and use that [03:02] daf: I know it's not perfect [03:02] SteveA: lets discuss it, you and i, after this meeting [03:02] k [03:02] I'd like to move on to karma [03:02] will you add by hand all templates we have in hoary/warty? [03:02] there was a discussion about karma yesterday [03:02] that's a huge work load... [03:02] and adding this kind of thing to the database [03:02] how's that all going? [03:03] carlos: we can't try to scale up rosetta till we can automate large amounts of it [03:03] the arch guys have made some good progress with getting code syncing [03:03] in december we can plan how to hook that automatically into rosetta [03:04] so once an upstream is syncing to arch, we can easily add it to rosetta [03:04] sabdfl: I have solved (more or less) the lack of arch archives [03:04] ok [03:04] how? [03:04] so that's not the problem [03:04] with python-apt (or whatever it's called) [03:04] que? [03:05] and now, using soyuz data [03:05] I get the information from where I can download the orig.tar.gz + diffs + .dsc [03:05] I download it and extract it [03:06] and I'm ready to find the .po/.pot directories [03:06] and import them into rosetta [03:06] I'm hoping for an email to the list outlining the plan for karma stuff, as this will touch various parts of launchpad in due course. [03:06] neat [03:07] carlos: are you extracting those from the librarian? [03:07] It needs to add the distribution archives by hand, but more or lees it's a help until we finish the arch part [03:07] Cookie auth should be working by tomorrow. I'm not wholy sure how this will affect page tests, so for now, page tests will continue to use basic auth. [03:07] Any other things to discuss at this launchpad meeting? [03:07] Kinnison: not yet, in fact I'm starting moving from apt-get to soyuz [03:07] If not, let's finish. [03:08] carlos: when you want to use the librarian; let me know [03:08] Kinnison: is there any documentation about it? :-P [03:08] SteveA: I just want to ask if elmo could open port 8000 up to the outside world for us? [03:08] carlos: Not yet :-) [03:08] spiv: whats the current position on having a status field on project / product? [03:08] carlos: If I can gather some use-cases from you and the others; I could write some [03:08] SteveA: so cookie auth will work in addition to basic auth rather than replacing it? [03:08] daf: yes, at least for now [03:09] SteveA: so soyuz can provide links directly to the librarian instead of having to act as a proxy to download from it [03:09] Kinnison: ok [03:09] carlos: for now, I think you'll just have to probe Kinnison's brain [03:09] mmmm cranial probage [03:09] Kinnison: can we do a proxy pass thing so that /downloads/... on the server is for the librarian? [03:09] SteveA: yes; but then soyuz will have to manipulate the URLs it gets from the FileDownloadClient instance [03:10] sabdfl: ouside the meeting scope, I have some questions about launchpad, I will give a speech tomorrow that will mention it and I'm not sure what should be said and what should not [03:10] I expect it will have to do so anyway, in reality [03:10] daf: :-) [03:10] SteveA: in that case; it'd be fine to do it proxy_pass [03:10] carlos: go ahead and make your own judgement [03:11] Kinnison: I think that's the kind of url we'd want to present to the outside world, rather than a port 8000 thing [03:11] carlos: you can speak freely [03:11] SteveA: ack. [03:11] sabdfl: ok, and about the "prize" of it? I mean, I don't know if it will be free of charge for all people or only to the community, etc... [03:11] SteveA: Should I add a getURIForAlias() method then? To only return the URI [03:11] SteveA: then soyuz can composite that with its url to form the full url for download [03:11] there will be many people working on local distributions in Spain [03:11] Kinnison: you mean the path? [03:11] rosetta, malone will be free of charge for any project to use [03:12] SteveA: yes [03:12] getPathForAlias or getURLPathForAlias ? [03:12] The former I think I prefer === Kinnison will code that [03:12] k [03:12] It'll be very short [03:12] sabdfl: ok [03:12] and we can have a convention that it will always be /downloads/... on any virtual host [03:12] or /files/ or whatever you think is best [03:13] that's up to the web-app guys :-) [03:13] wrapping up the meeting? Same time next week -- wednesday 12:30 UTC ? [03:14] ok [03:14] SteveA: ok [03:14] ack. [03:14] yep [03:14] thanks everyone. I'll send a mail about the next meeting. [03:15] thanks, Steve [03:16] daf: do we need to talk about anything urgent now? [03:17] carlos: we need to talk about the move, but it can wait for a few hours [03:17] ok [03:17] I need to have lunch and go out for a while [03:17] as soon as I'm back I will ping you, ok? [03:17] (I think that will be in about 2 hours or so) [03:18] ok [03:18] Well; this patch to the librarian compiles [03:18] (which is always a good start) [03:18] ok, later [03:20] >>> fdc = FileDownloadClient("launchpad.ubuntu.com", 8000) [03:20] >>> fdc.getPathForAlias(1) [03:20] '/1/1/3dchess_0.8.1-11.dsc' [03:20] SteveA: would that do? [03:20] SteveA: then the webapp can put 'https://....../download' on the front of that as appropriate and we can proxypass the result === debonzi is now known as debonzi|lunch === salgado is now known as salgado-lunch [03:23] uh [03:24] maybe I misunderstanding something, but you realise you're going to have to present a traditional archive layout too, right ? [03:24] elmo: that's an entirely separate thing [03:24] ok - what's this for then? [03:24] the webapp can just make the url an abs url as 3dchess_0.8.1-11.dsc [03:24] 'cos serving up an archive via https makes me want to run into a wall [03:24] elmo: this is to allow the soyuz webapp to generate urls to specific files in the librarian [03:25] elmo: It is not a generic archive-exposing thing [03:25] SteveA: yeah; that's do [03:25] elmo: remember the librarian will also have build-logs and stuff in it [03:25] and, if the url scheme is https, then apache can perm redir to http same url under /downloads/ [03:26] if we want to save https stuff. hmm, I guess that involves the same set-up cost, though === doko [doko@dsl-082-082-067-024.arcor-ip.net] has joined #launchpad [03:26] do clients generally do pipelining of requests for https ? [03:26] for stuff in an archive, shouldn't the webapp generate to the URL to the archive, not a librarian-specific URL ? [03:26] Why are we trying to munge the URL's the librarian is giving us? It should be returning the one true URL for that file. [03:26] stub: for dogfood we don't want to expose the librarian directly [03:27] elmo: When we have a useful place to put the archive; then yes it should [03:27] Kinnison: Then the librarian should be returning the correct URL rather than localhost:8080 or some port that is internal only [03:27] Kinnison: it should expose itself to the public? [03:27] we don't want to expose the librarian URLs period, IMO === Kinnison has no strong preference either way [03:28] oh, a prudish librarian [03:28] I was just supplying a solution as asked :-) [03:29] SteveA: dunno; but they can do session-restart to save the asymmetric crypto [03:33] Should I commit this patch or not then? [03:34] SteveA: https://wiki.canonical.com/RosettaToDogfood === kiko is now known as kiko-fud === kiko-fud needs to run off [03:41] daf: write the main template layer first [03:42] that way the code is ready [03:42] and you just need to get the data transfered [03:42] it shouldn't be "write a layer that overrides the main template", but "override the main template for the rosetta layer" [03:42] hmm [03:45] don't we want the layer only to be used by testers? [03:46] do it for the whole of rosetta now [03:46] when we have the context code done (fairly soon), we'll be able to be more selective [03:47] context? [03:47] what's "context" in this context? [03:47] object that allows you to see what applicaiton, package, product, whatever you're in [03:47] and allows you to get an appropriate URL to present for a given object [03:54] Merge to rocketfuel@canonical.com/launchpad--devel--0: Add getPathForAlias to librarian client (patch-758) [03:54] thanks babe. [04:04] dilys rocks [04:05] She's certainly very handy [04:05] sabdfl: What's your favourite backup media format? [04:05] why? [04:06] Trying to choose a backup method for ca. 200 gigs of data [04:06] (for home) [04:06] I can't choose between tape or disk for a start [04:07] I figured since I remembered some mumbling about your backups at home you might have a preference :-) === ddaa grumbles.. [04:10] The Warty python does not seem to have the guts to get a traceback out of gdb... === ddaa looks for python 2.4 in hoary === ddaa wonders where to look for hoary [04:11] !lilo:*! Reminder, if you're in the US and you want to attend the second day of the FTC's email authentication summit by phone, it's in progress and the conference info is here: http://www.ftc.gov/bcp/workshops/e-authentication/ .... and please stop by ##ftc-summit (note two #'s).... thanks! [04:14] Kinnison: a second hard drive :-) [04:14] sabdfl: feh; I already have RAID-1 going on :-) === Kinnison was just being taken-aback at the cost of tape hardware [04:15] sabdfl: Will the timings i put in that mail be okay for next wednesday? [04:15] yup [04:16] Mh... python 2.4 does not seem to be in hoary yet... [04:16] sabdfl: excellent [04:19] daf, carlos, is the alpha testing system supposed to be giving errors all over the show? === debonzi|lunch is now known as debonzi [04:30] rehi debonzi [04:30] Kinnison, yo [04:31] spiv: librarian works w/ sqlo--0.6, thanks [04:32] Kinnison: do you have any dump of dogfood db ? those stored in mawson look a bit strange, they have binary code inside or were corrupted .. am I missing something about dumps ? [04:32] cprov: erm; you want a dump of the dogfood db? just make one yourself. (you have sudo right?) [04:35] cprov: sudo -u launchpad pg_dump launchpad_dogfood | bzip2 -c > ~/lp-dump.bz2 [04:37] The nightly dumps are in pg_dump's custom format, which can be used by pg_restore to reload. Lets you do partial loads and reordering load order and stuff (because pg_dump is TOO STUPID to get the dump order correct). [04:38] yeah [04:38] I guess === stub goes to bed before he gets grumpier [04:39] nighty stub [04:40] Have to work on these late nights - I've started ranting on mailing lists. Never a good sign ;) [04:42] stub: thanks, I'll try this on with pg_restore [04:44] stub: i'd NEVER be one to suggest beauty sleep [04:44] however, you shouldn't have accepted that patch from me without comments [04:44] will commit a comments fragment now === BradB wonders if there's a pgsql option that prevents adding db objects without comments [04:45] meta constraints, as it were [04:45] we'd get piles of crap comments if we enforced that [04:45] Kinnison: which would mean piles of scolding email, i guess :P [04:45] hehe [04:46] seems easier to persuade stub to not accept poorly commented patches [05:00] SteveA: ping [05:18] Anyone know offhand if the test runner is smart enough to treat .txt files as documentation/test code (i.e. doctests :)? [05:19] I want to test code in dir foo/, and so I want demonstration in foo/README.txt to get run as doc tests. [05:19] s/demonstration/demonstration code/ [05:24] sabdfl: no, I saw it this morning but I don't understand why it does it if the code is not changing nor the database... daf is looking at it already [05:55] ok [06:13] Merge to rocketfuel@canonical.com/launchpad--devel--0: bring bounty tests on stream (patch-759) === BradB is now known as BradB|lunch [06:50] BradB|lunch: no, it isn't. you have to explicitly say in a test_something.py module that a particular text file is a test. There is a test_pages.py module that does that for all .txt files in canonical/launchpad/pagetests/ [06:50] I wouldn't like to have just any .txt file treated as a test [07:02] Merge to rocketfuel@canonical.com/launchpad--devel--0: Rosetta functional tests disabled, they were not working and we should improve them (patch-760) === kiko-fud is now known as kiko-afk [07:15] BradB|lunch, question for you in bug 2167. === lulu [~lu@host217-37-231-28.in-addr.btopenworld.com] has left #launchpad [] === BradB|lunch is now known as BradB [08:15] SteveA: I want to test that my changes to the PersonVocabulary work. I started writing this as doctest, then realized I sort of need the zope machinery running (e.g. to register an IZopeDatabaseAdapter) to test this. How would you recommend I write a simple test like that? (I could shoehorn it as a page test, but it's nothing near a functional test; all I'm testing is that PersonVocabulary returns the terms I expect.) [08:15] kiko-afk: ? [08:15] yes BradB? [08:16]

BradB|lunch, question for you in bug 2167. [08:16] BradB, right, there's a question -- two actually -- for you, in bug 2167. [08:16] :) [08:16] heh [08:16] ok, /me reads [08:17] BradB: why do you need to register an IZopeDatabaseAdapter? Can't you just register an IPeople or IPersons utility? [08:18] that's half the point of using utilities here -- to make this kind of test more straightforward [08:18] SteveA: It's a vocab that hits the DB. [08:19] SteveA: this test is only effective if it proves that noone broke the change i made to only return people who have passwords [08:20] if the vocab were to use IPersonSet... [08:20] then you'd just need to test that it uses the correct IPersonSet api [08:20] yeah [08:20] otherwise, you need to write a functional test [08:20] to live in .../ftests [08:20] darn [08:20] oh well [08:24] daf: can you add time estimates to here https://wiki.canonical.com/RosettaToDogfood or link to malone bugs, if there are any ? [08:29] sure [08:30]