[05:35] <stub> sabdfl: Should the bugattachment table reference Message or BugMessage?
[11:36] <lifeless> BradB: I don't know .. should I ?
[12:47] <sabdfl> stub: good question
[12:47] <sabdfl> i think Message, if the attachment came from a Message
[01:51] <lifeless> hey ki	
[01:53] <sabdfl> hey kiko
[02:04] <kiko> hello sabdfl 
[02:04] <kiko> hey lifeless 
[02:04] <kiko> lifeless, did you get a minute to sort out salgado's key?
[02:11] <lifeless> kiko: I haven't seen the email.
[02:11] <lifeless> let me check again.
[02:12] <lifeless> ah I think I have it.
[02:12] <lifeless> guilherme ?
[02:12] <elmo> yeah
[02:12] <lifeless> yeah, I have it. will be done in ~ 10.
[02:13] <kiko> thanks
[02:15] <kiko> I may be out of touch, but why is Soyuz leading me to notready.ubuntu.com?
[02:16] <lifeless> dogfood.canonical.com is where you want to be
[02:16] <lifeless> launchpad is now the production install.
[02:16] <kiko> and the old addresses are dead, then.
[02:16] <kiko> I see
[02:16] <kiko> lifeless, they run the same database, I assume?
[02:16] <lifeless> nope
[02:17] <kiko> sabdfl, we have some "views" we'd like implemented in malone -- a way to limit a list of bugs per distribution, and per distribution release
[02:17] <kiko> I am wondering today if there is enough information to tie all this together, however
[02:18] <lifeless> kiko: salgados key is registered, he can register his archive and merge now.
[02:18] <kiko> thanks.
[02:18] <sabdfl> kiko: i'd rather not address that till we've solved some other problems
[02:18] <kiko> sabdfl, okay, because that's one of the pending soyuz items we have
[02:18] <lifeless> sorry it took so long
[02:18] <kiko> no problem
[02:18] <sabdfl> we've got solid answers to how bugs relate to package, and package release, but not yet the higher level distrorelease and distro
[02:19] <sabdfl> this is stuff we can hammer out in spain
[02:19] <kiko> okay, let me note that
[02:19] <sabdfl> right now the goal is to clean up what we have so we can show it to people in spain
[02:19] <kiko> sabdfl, does this mean hiding what is unimplemented?
[02:19] <kiko> I was meaning to get a few features landed this week
[02:19] <sabdfl> also, i am find a a LOT of low-hanging fruit
[02:19] <sabdfl> in terms of links between pieces of the system that ARE working
[02:19] <lifeless> sabdfl just wanted to hear the ping
[02:20] <sabdfl> so i'm starting to add portlets to project and product to show related bits elsewhere in the system
[02:20] <kiko> well, I have the current tasklist open for this week:
[02:20] <kiko> - getting pending finally displayed in the interface (required DB schema work, kinnison/cprov in charge)
[02:20] <kiko> - Karma infrastructure (salgado)
[02:21] <kiko> - SQL DistroAnnotations (sabdfl to approve, debonzi)
[02:21] <kiko> - PackagesSubcription (sabdfl to define)
[02:21] <kiko> - activate Librarian links (debonzi)
[02:21] <kiko> - Links to distro and distro release bugs (debonzi)
[02:22] <kiko> - Report a bug on displayed source package (sabdfl to advise, debonzi)
[02:22] <sabdfl> distro annotations? in general, don't work on annotations stuff, it's fluff for the moment
[02:22] <kiko> - Fix edit distro information
[02:22] <kiko> - Fix permissions on edit distro (cprov)
[02:23] <kiko> So there's a lot that is blocked by SEP
[02:23] <kiko> (someone else's problem)
[02:23] <sabdfl> kiko: i'm sure there is a lot that could be done in terms of cleanups
[02:23] <sabdfl> but my most important goals are:
[02:23] <kiko> sabdfl, code cleanups?
[02:24] <sabdfl> kinnison / cprov: get the package workflow from uploaded, through pending, to installed, and published in the archive working
[02:24] <sabdfl> salgado: make sure that we have the general karma framework up, with specific karma for one (even tiny) part of the system
[02:25] <sabdfl> debonzi: make sure soyuz is using the same layout and standards as malone
[02:25] <sabdfl> zcml and naming and file structure
[02:25] <kiko> by cleanups and layout and standards you mean code, not UI. 
[02:25] <kiko> I see.
[02:25] <kiko> we like to deliver more than is expected!
[02:25] <sabdfl> i'm nervous about things like canonical.soyuz.browser
[02:26] <sabdfl> (from memory)
[02:26] <kiko> most of that is going away in some debonzi-patches
[02:26] <sabdfl> right now, i'm starting to beat up on rosetta for that stuff
[02:26] <sabdfl> RosettaProjectSet, RosettaProduct etc MUST GO (TM)
[02:27] <kiko> we've gotten rid of those for us at least
[02:27] <sabdfl> great
[02:27] <sabdfl> i will take a wander through soyuz this afternoon, ok>
[02:27] <kiko> I need to sit down with daf and carlos to sort out some rosetta infrastructure for us, but I'll do that in mataro
[02:28] <kiko> it's difficult to answer questions like "What is the translation status for my distribution", "What is the translation status for release Hoary", "How was the translation status for release Warty (in the past)"
[02:28] <kiko> I don't think rosetta has a concept of history, which limits how useful it is to soyuz right now, AIUI
[02:29] <kiko> (I could be analyzing this all wrong, but I'd like to see someone else do better <wink>)
[02:29] <carlos> kiko: I think it's better if you send us your needs at the moment so we can look at them before Matar and prepare the "interview"
[02:29] <kiko> carlos, look three lines up, the questions we want to answer are there.
[02:29] <kiko> that is a good summary.
[02:30] <carlos> ok
[02:30] <kiko> we would also appreciate having the "translation status" made into a good framework of statistics to display
[02:30] <kiko> I know you are involved in the mechanics of things, but we want at least some reporting
[02:30] <carlos> we have them for projects/products
[02:31] <sabdfl> i must say thngs are starting to come into focus
[02:31] <carlos> I suppose it's a matter to do an agregation function for distributions
[02:31] <kiko> carlos, we need *history*, which is an issue.
[02:31] <sabdfl> it's *starting* to be possible to move through the Launchpad efficiently
[02:31] <kiko> products/projects are timeless
[02:31] <carlos> kiko: we don't have history yet
[02:31] <kiko> right.
[02:31] <carlos> kiko: mark asked us to do it later
[02:32] <kiko> yes, I understand, but i just want to point out that that is a limiting factor in soyuz-rosetta integration.
[02:32] <carlos> kiko: why?
[02:32] <kiko> I'm not meaning to sound anxious, just state the [perhaps obvious]  fact, to be addressed whenever
[02:32] <carlos> you can get the current status
[02:32] <carlos> that's all
[02:32] <kiko> carlos, because those questions can't be answered without history
[02:32] <kiko> exactly
[02:33] <kiko> but soyuz has a moving concept of current
[02:33] <sabdfl> focus on the present
[02:33] <kiko> the distro release hoary is today current, tomorrow old
[02:33] <carlos> kiko: dude, that feature is not something critical for soyuz
[02:33] <carlos> it's critical for Rosetta :-)
[02:33] <sabdfl> the linkages from soyuz take you to where you CAN TRANSLATE
[02:33] <carlos> kiko: but that will be still valid
[02:33] <kiko> I agree, I agree
[02:33] <sabdfl> providing a transaltion for a prior release may still be helpful and useful
[02:33] <kiko> don't shoot me down for just pointing out the obvious :)
[02:33] <carlos> :-P
[02:33] <sabdfl> sure
[02:34] <kiko> but when we do a roundup of the pages and missing bits, that's one of the things that show up, which is why I bring it up.
[02:34] <kiko> I understand of course prioritization
[02:35] <kiko> I just want acknowledgement that it's "to be dealt with" to avoid people frowning because it was supposed to have been solved already!
[02:37] <sabdfl> good point
[02:37] <sabdfl> maybe i should prepare a shopping list for next week, for each of the teams
[02:37] <sabdfl> hey daf
[02:37] <sabdfl> lunchtime
[02:37] <kiko> enjoy it
[02:38] <sabdfl> taking lifeless out to lunch to talk bazaar
[02:38] <sabdfl> baz is going to ROCK
[02:38] <lifeless> that is, a bazaar lunch
[02:38] <sabdfl> already, it's much better
[02:39] <kiko> it's killer indeed
[02:39] <kiko> works perfect on our diskless boxes
[02:40] <carlos> :-)
[02:41] <sabdfl> daf, carlos, that pqm merge is on its way
[02:41] <carlos> sabdfl: ok, will review it after lunch. Thanks
[02:43] <kiko> BradB?
[02:55] <dilys> New Malone bug #93: "Filing a new bug takes a *long* time", submitted by Christian Robotton Reis
[02:55] <dilys> https://dogfood.ubuntu.com/malone/bugs/93
[02:58] <dilys> New Malone bug #94: "No confirmation of bug ID or success when a bug is filed", submitted by Christian Robotton Reis
[02:58] <dilys> https://dogfood.ubuntu.com/malone/bugs/94
[03:00] <dilys> New Malone bug #95: "Could we have an automatic-ish duplicate-matching system?", submitted by Christian Robotton Reis
[03:00] <dilys> https://dogfood.ubuntu.com/malone/bugs/95
[03:03] <dilys> New Malone bug #96: "Activate librarian links for packages", submitted by Christian Robotton Reis
[03:03] <dilys> https://dogfood.ubuntu.com/malone/bugs/96
[03:07] <dilys> New Malone bug #97: "Bug count is bogus?", submitted by Christian Robotton Reis
[03:07] <dilys> https://dogfood.ubuntu.com/malone/bugs/97
[03:08] <dilys> New Malone bug #98: "Fix edit distro permissions", submitted by Christian Robotton Reis
[03:08] <dilys> https://dogfood.ubuntu.com/malone/bugs/98
[03:13] <dilys> New Malone bug #99: "double-spacing in bug comments?", submitted by Christian Robotton Reis
[03:13] <dilys> https://dogfood.ubuntu.com/malone/bugs/99
[03:14] <dilys> New Malone bug #100: "Assignee should be settable from new bug", submitted by Christian Robotton Reis
[03:14] <dilys> https://dogfood.ubuntu.com/malone/bugs/100
[03:37] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: rosetta and sourcesource cleanups, and project portlets (patch-886)
[03:37] <dilys> Merge to 	rocketfuel@canonical.com/launchpad--production--1.5: snarf devel (patch-3)
[03:37] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: fix syntax error in broker.py (patch-885)
[03:37] <dilys> Merge to 	rocketfuel@canonical.com/launchpad--production--1.5: merge from devel (patch-2)
[03:37] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: improve sourcesource review process (patch-884)
[03:37] <dilys> Merge to rocketfuel@canonical.com/buildbot--devel--0: ensure generated data is not unicode (patch-79)
[03:44] <dilys> Bug 2014 resolved: Create a findByPeople() method on SourcePackages and BinaryPackages
[03:44] <dilys> https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=2014
[03:44] <dilys> Bug 1998 resolved: Missing package maintainer information.
[03:44] <dilys> https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=1998
[03:52] <carlos> dilys is going to ask a higher salary, she's working too much..
[03:57] <sabdfl> dilys ROCKS
[04:15] <sabdfl> carlos: is RosettaProjectSet definitely needed, or could it be merged to ProjectSet?
[04:16] <carlos> where is it?
[04:17] <carlos> ooh, domain.py...
[04:17] <carlos> sabdfl: ask Steve
[04:17] <carlos> it was a sample code for the domain thing 
[04:17] <carlos> that's what it's still there
[04:18] <sabdfl> so do you guys use it at all?
[04:18] <carlos> sabdfl: I think so
[04:18] <carlos> but it's not really needed
[04:18] <carlos> I mean, it could be merged
[04:18] <sabdfl> i'm going to try to get rid of it now
[04:19] <carlos> I think the functionality is already merged, it's just a matter of doing some .zcml changes
[04:27] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: rosetta zcml cleanups (patch-887)
[04:45] <carlos> daf: ping?
[05:23] <carlos> sabdfl: should we move from canonical/rosetta/browser.py to canonical/launchpad/browser/ ?
[05:23] <sabdfl> carlos: yes, but let me finish my walkthrough first
[05:23] <sabdfl> you can work on that next week
[05:24] <carlos> ok, I'm adding new pages and saw the new layout
[05:24] <carlos> that's why I'm asking
[05:24] <sabdfl> carlos: yes, for new pages, please put them in the new zcml files, definitely
[05:24] <sabdfl> thanks
[05:24] <sabdfl> !
[05:25] <carlos> new zcml files and new browser location?
[05:25] <carlos> or only zcml files
[05:25] <carlos> ?
[05:29] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: banish RosettaProjectSet (patch-888)
[05:48] <carlos> sabdfl: we need a place to add/edit Licenses
[05:48] <carlos> sabdfl: where do you think it's the best place to do it?
[05:49] <carlos> we should stop using facked values...
[05:49] <sabdfl> carlos: add a LicenseSet and Licence class, traverse to them from rosetta for the moment
[05:49] <sabdfl> we will probably add that to DOAP
[05:50] <sabdfl> but i don't think that's critical to get done before mataro
[05:50] <carlos> ok, so I implement it into Rosetta and it will be moved later.
[05:50] <carlos> so just use License.id = 1 and that's it
[05:50] <carlos> ok
[06:09] <sabdfl> yes
[06:25] <carlos> sabdfl: how could I restrict the access to a concrete page inside a browser:pages directive?
[06:25] <carlos> I have this:
[06:25] <carlos> <browser:pages for="canonical.launchpad.interfaces.IProduct"
[06:25] <carlos>         permission="zope.Public"
[06:25] <carlos>         class="canonical.rosetta.browser.ViewProduct"
[06:25] <carlos>         lp:url="Rosetta/projects/$Project.name/$Product.name">
[06:25] <carlos>         <browser:page name="+rosetta-index"
[06:25] <carlos>             template="../templates/rosetta-product-index.pt"
[06:25] <carlos>             lp:url="Rosetta/projects/$Project.name/$Product.name/index" />
[06:25] <carlos>         <browser:page name="+newpotemplate"
[06:25] <carlos>             template="../templates/potemplate-new.pt"
[06:25] <carlos>             lp:url="Rosetta/projects/$Project.name/+newpotemplate" />
[06:25] <carlos>     </browser:pages>
[06:25] <carlos> and I want that <browser:page name="+newpotemplate"
[06:25] <carlos> is only available to authenticated users
[06:31] <carlos> sorry: /s/is/be/
[06:31] <sabdfl> ROAR!
[06:47] <sabdfl> carlos: restrict access, you mean have a specific permission on that page?
[06:48] <sabdfl> so you want to have a pages directive, then inside that 10 different pages, each with a custom permission?
[06:48] <sabdfl> i also had that problem
[06:49] <sabdfl> it makes sense to me you could say "pages" and specify the view class, then have a bunch of "page" elements whcih specify permission and template
[06:49] <sabdfl> but i don't think zcml allows that just yet
[06:50] <carlos> yea, that
[06:50] <carlos> ok
[06:50] <sabdfl> stevea can probably knock it up in a few minutes though :-)
[06:50] <carlos> will ask for alternatives to Steve
[06:50] <carlos> is there?
[06:50] <carlos> ok
[06:50] <sabdfl> right now you need a different pages directive, which sets the permission
[06:51] <sabdfl> and each page inside that must use the permission, and class of the pages directive
[06:52] <carlos> will try it, thanks
[06:55] <carlos> hmmm I need then also two different classes
[07:02] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: add advanced project searching (patch-889)
[07:11] <sabdfl> bradb!
[07:12] <sabdfl> have had lots of fun today
[07:12] <sabdfl> in the good sense
[07:12] <dilys> Merge to 	rocketfuel@canonical.com/launchpad--production--1.5: merge from devel (patch-4)
[07:15] <BradB> sabdfl: heh
[07:16] <BradB> What did you think of the search UI changes? Way off the mark, or an improvement?
[07:17] <sabdfl> neat
[07:17] <BradB> They're kind of in a halfway house, to be honest. 1. I was hinting at the fact that we should aim to make our widgets less ugly in our various forms (i.e. "normal" HTML submit buttons and input widgets are so unappealing) and 2. I'm halfway to hiding the rest of the "filter criteria", by default.
[07:18] <sabdfl> how do you make the button so slick?
[07:19] <elmo> wd40
[07:20] <BradB> sabdfl: CSS. The HTML is messy at the moment (it was a quick prototype to see if you think it looks good, next up is create a page test for that accepted functionality and then be able to clean it up a bit)
[07:20] <sabdfl> ok
[07:20] <sabdfl> but dude, are you addicted to this page?
[07:20] <sabdfl> i'm free-ranging on the launchpad finding tons of low hanging fruit that pulls it all together nicely
[07:21] <sabdfl> there are lots of separate pieces of functionality that can be interlinked now
[07:21] <BradB> sabdfl: I have to be, because it's 80% of what Malone is.
[07:21] <sabdfl> no it isn't
[07:21] <sabdfl> you're still thinking of malone in a traditional bug collector sense
[07:21] <BradB> sabdfl: E.g. the next thing that /really/ needs help is making it simple to go from that list to editing assignments.
[07:21] <sabdfl> and yes, we have to get that stuff right
[07:21] <sabdfl> but we have some time to do it
[07:22] <BradB> sabdfl: The quick search mods I made were just an attempt at making life easier for the user. The bug id/text search was a need-to-have though. I go nuts trying to report bugs on dogfood without being able to usefully search to see if they've already been reported.
[07:23] <sabdfl> yes, that was definitely needed
[07:23] <BradB> The one-click mods collectively save a load of time for Malone users too.
[07:23] <sabdfl> we need a google-style approach, and you are on your way there
[07:24] <sabdfl> check the new project search stuff i did today for the style i prefer though
[07:24] <sabdfl> at least, when i can merge it
[07:26] <elmo> BradB: don't let it stop you, but lamont always brings enough spares for the team +their family
[07:26] <BradB> elmo: That work on PPC?
[07:26] <elmo> yes, same card as I have
[07:27] <elmo> that's why I bought it - I knew from borrowing LaMont's that it works :)
[07:27] <BradB> wow.
[07:27] <BradB> What was the exact model again?
[07:28] <elmo> Cisco Aironet 350 Series
[07:29] <BradB> noted, thanks
[07:29] <carlos> Do we have an easy way to check if a form has the required fields filed?
[07:29] <BradB> sabdfl: got a moment to brainstorm on making assignment editing not suck?
[07:29] <carlos> or should we do all checks before using them always?
[07:30] <elmo> hey, sweet, hotplug got fixed
[07:30] <BradB> cool!
[07:30] <BradB> elmo: does that mean i can plug in a NIC and have it Just Work?
[07:31] <elmo> oh, you could always do that - unplug use to be broken tho, at least for this card/my machine, so you couldn't plug, [...] , unplug it and then plug it back in plug
[07:31] <BradB> ah
[07:31] <elmo> but I just pulled it out to get the model off the back of the card for you, and plugged it back in afterwards
[07:31] <elmo> [and it worked] 
[07:32] <BradB> I've noticed that playing music sounds like arse on my machine, more or less.
[07:33] <elmo> arse how?  too fast?
[07:33] <elmo> if so, try using direct output rather than alsa
[07:33] <BradB> Sometimes it seems a bit fast (maybe I'm imagining it), but it definitely seems to bleep and skip.
[07:34] <elmo> yeah, try !alsa
[07:34] <elmo> works fine for me with xmms
[07:36] <dilys> Bug 2165 resolved: How do I download a binary package?
[07:36] <dilys> https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=2165
[07:37] <kiko> BradB, yo?
[07:38] <dilys> Bug 2046 resolved: Implement paging for package pages
[07:38] <dilys> https://bugzilla.warthogs.hbd.com/bugzilla/show_bug.cgi?id=2046
[07:40] <BradB> yo
[07:40] <kiko> dude!
[07:41] <BradB> sweet!
[07:41] <kiko> is it possible/easy to file a bug for a certain package via a URL?
[07:41] <kiko> if you could hook that up for us we'd get automagic bug-filing links from soyuz
[07:41] <BradB> kiko: Yeah, sabdfl's already done something like that for Malone.
[07:41] <BradB> kiko: Just look at the request that gets sent on the add form.
[07:42] <kiko> BradB, can you detail hmmmm 
[07:42] <kiko> but that would require creating a custom view/template?
[07:42] <BradB> kiko: heck no, that's too much work.
[07:42] <kiko> then you mean a form post? :)
[07:42] <BradB> er, well, depending on what you mean. hang on, i'm search for sabdfl's stuff.
[07:42] <sabdfl> grep for filebug in zcml/
[07:43] <sabdfl> hey kiko
[07:43] <kiko> hey sabdfl 
[07:43] <kiko> w00t
[07:43] <kiko> malone/projects/$Project.name/$Product.name/+filebug
[07:43] <sabdfl> there is a custom View class
[07:43] <kiko> sabdfl, could I have one for a source package?
[07:44] <sabdfl> tricky
[07:44] <kiko> is it indeed?
[07:44] <sabdfl> hmm... if your stuff traverses to a SPECIFIC source package then actually, not tricky
[07:44] <BradB> kiko: just use the add form dude.
[07:44] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: break cross merge deadlock (patch-890)
[07:44] <kiko> yes, a specific source package --- I'm in soyuz!
[07:44] <BradB> http://localhost:8086/malone/bugs/+new
[07:44] <dilys> Malone bug #61 fixed for product The Rosetta Translation Portal: Create a new table to store temporary po/pot files to be imported
[07:44] <dilys> https://dogfood.ubuntu.com/malone/bugs/61
[07:44] <BradB> kiko: and...? :)
[07:44] <kiko> well, I'd rather use a link than a button, but..
[07:45] <sabdfl> kiko: let me do it now it will give me a chance to poke around in soyuz a bit more
[07:45] <carlos> BradB: the bug edit form changes after you submit it :-?
[07:45] <BradB> kiko: You're looking for a URL to use to add a bug to a source package or a product. That URL is http://localhost:8086/malone/bugs/+new with the appropriate params.
[07:45] <kiko> sabdfl, cool.
[07:45] <sabdfl> BradB: no, it so is NOT :-)
[07:45] <kiko> BradB, that means using a <submit> button :)
[07:46] <BradB> sabdfl: why not?
[07:46] <sabdfl> BradB: you are still thinking in terms of malone as a monlithic bug system
[07:46] <BradB> sabdfl: No, I'm thinking in terms of not duplicating effort.
[07:46] <sabdfl> try to imagine that the launchpad will actually be highly fragmented
[07:46] <sabdfl> lots of small communities, all using it, all just seeing their bugs, their packages
[07:47] <sabdfl> the fact that its all in one system gives us great opportunities for collaboration
[07:47] <sabdfl> but where possible we still want people just to see information that is really relevant to them
[07:47] <BradB> sabdfl: I've already imagined that. :) Why is it good to solve the same problem more than once here?
[07:47] <sabdfl> launchpad.dia.org should in general only see bugs related to dia
[07:47] <sabdfl> because kiko wants to add a bug ON A SPECIFIC PACKAGE
[07:48] <BradB> sabdfl: that can be done with the link i provided.
[07:48] <sabdfl> so, he's imagining a scenario where the guy is already looking at the package, and all he wants is to add a bug to that
[07:48] <BradB> sabdfl: he'd have to provide the appropriate params to that link, but that's a given.
[07:48] <sabdfl> your method would take him to the MASTER BUG ADD PAGE with a zillion knobs and buttoms
[07:48] <sabdfl> most of which are unrelated to HIM
[07:48] <BradB> sabdfl: no.
[07:48] <sabdfl> yes
[07:48] <kiko> well
[07:48] <kiko> the issue is passing parameters via HTTP GET 
[07:48] <BradB> sabdfl: he could do what i've already done and submit the URL with .js.
[07:49] <kiko> or via a JS POST
[07:49] <sabdfl> http://localhost:8086/malone/bugs/+new doesn't know anything about sourcepackage
[07:49] <sabdfl> unless you add paramteres
[07:49] <kiko> both of which I think are limited..
[07:49] <sabdfl> much better to use the context, luke
[07:49] <BradB> sabdfl: that's /precisely/ what i'm saying :)
[07:49] <BradB> sabdfl: the "context" is something the caller is smart enough to pass in to us.
[07:50] <BradB> sabdfl: Remember, you already went off and solved this problem again, which ended up breaking things, because you rewrote code for which I've already written code that solves the problem, and in your rewrite left out important things that BugFactory already does (e.g. auto-subscribing the submitter)
[07:50] <BradB> sabdfl: duplicating work is error prone and costs more money.
[07:51] <BradB> If one /really/ /really/ insists on creating their own form for this, then it's not that big of a deal, they just have to be certain to use BugFactory as their content factory.
[07:52] <sabdfl> parameters are suckier than context
[07:52] <sabdfl> but the end result is that they guy's browser suddenly shoots off to some master page, which has a ton of knobs on it
[07:52] <sabdfl> and yes, maybe your parameters pre-set the knobs in a ncie way for him, but there are still a daunting number of knobs
[07:52] <sabdfl> i'm going to keep teasing you about this till you get it ;-)
 parameters are suckier than context
[07:52] <kiko> that is soooo true
[07:53] <sabdfl> it doesn't require duplicating work
[07:53] <kiko> it should be in a style guide somewhere
[07:53] <BradB> I get it. I've already provided you an example of why my suggestion works better than yours too, with the example of what happened when you went and reinvented this. :)
[07:53] <kiko> sabdfl, indeed, if done correctly <wink>
[07:53] <sabdfl> i have refactored my +filebug to use your BugFactory ;-)
[07:53] <sabdfl> BradB: what do you mean, went and reinvented this?
[07:53] <BradB> sabdfl: i.e. when you didn't use BugFactory :)
[07:54] <sabdfl> the solution was simply to use bugfactory from my specialised addform
[07:54] <sabdfl> that's no problem
[07:54] <BradB> sabdfl: as i said above though, if people /really/ insist on creating a separate addform for this, fine, not that big of a deal, as long as they use BugFactory as their content factory.
[07:54] <sabdfl> but the user experience should not be to be redirected to one central master page
[07:54] <BradB> IOW, I think we agree.
[07:54] <BradB> sabdfl: I'm not as insistent on the URL as on the content factory.
[07:54] <sabdfl> dude, i'm not going to be happy till you drop the /really/ attitude
[07:54] <sabdfl> this is important
[07:55] <sabdfl> we need to think of lots of *little* projects using malone, rosetta, the bounty system, support tracker
[07:55] <sabdfl> they should each see it as their system
[07:55] <sabdfl> they don't want to collide with a zillion other knobs, and data from a zillion other projects
[07:56] <sabdfl> https://dogfood.ubuntu.com/malone/projects/canonical/rosetta
[07:56] <BradB> Okay, not /really/ then. It makes perfect sense for people to create their own fancy context-aware bug add forms as long as they use BugFactory (which is why I filed a bug when somebody went off and didn't use BugFactory.) Creating a form is otherwise reasonable, though ideally our schemas would be setup to properly inherit from one another, so we don't have duplicate schema defs, etc.
[07:57] <sabdfl> this url would be better as launchpad.canonical.com/rosetta/bugs
[07:57] <sabdfl> the schema recreation thing is what i was bitching about to stub the other day
[07:57] <sabdfl> creating a BugAddSchema is crazy
[07:58] <BradB> kiko's original question asked me for a url though, hence why i told him about the existing all-purpose add form that one could trivial call behind-the-scenes. but i can happily live with new forms that reuse existing code.
[07:58] <sabdfl> i then have to copy the title and description and required fields from the main schema into the AddFormSchema, and remember to update them
[07:58] <BradB> eeg!
[08:00] <sabdfl> exactly
[08:00] <sabdfl> that's why i want to be able to create a form, and specify fields that come from different schemas
[08:01] <BradB> sabdfl: Reuse is a general problem we're seeing in Malone. e.g. think about it, if we decide to use icons or do some other fancy things to the bug listing to make it real-estate sensitive, we're going to have to then go in and modify the places where this was reinvented in the pages malone has for source packages and products.
[08:01] <sabdfl> btw, lifeless is digging through sqlobject and could use your insight
[08:02] <BradB> sabdfl: so when i say that the bug listing is 80% of malone, that's what i mean. i don't necessarily mean the link at "See the complete bug list" is 80% of Malone, but rather that a cool, easy-to-grok-and-get-to-where-i-want bug listing is an /integral/ part of Malone.
[08:03] <sabdfl> agreed
[08:03] <sabdfl> we really DO need the big form with all the master knobs
[08:03] <sabdfl> i totally get that
[08:03] <sabdfl> but it's not a huge priority *right now*
[08:03] <sabdfl> i want to be able to show off malone for a small upstream project in mataro
[08:04] <sabdfl> and right now, there are lots of places it could do with polish
[08:04] <sabdfl> that have nothing to do with the big master form
[08:04] <BradB> sabdfl: my current focus is on making editing assignments not suck. i want to reject bugs, and i can't even explain why i'm rejecting them.
[08:04] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: advanced project searching and selection (patch-891)
[08:04] <sabdfl> ok
[08:04] <sabdfl> rock
[08:04] <sabdfl> there's some really nice code behind the ProjectSet.search function now
[08:05] <BradB> and also, i want to get to the assignment in one-click from the bug listing, not two.
[08:05] <sabdfl> ok
[08:05] <carlos> sabdfl: or there is a bug with arch -> mail gateway  or you forgot to add any change with your last commit
[08:05] <robertc> BradB: do you know the sqlobject & sqlos innards ?
[08:06] <carlos> the mail report does not have any new/modified file
[08:06] <BradB> robertc: Depends on what you want to know :)
[08:06] <BradB> robertc: I don't know anything specific about SQLOS though.
[08:06] <BradB> er, sqlos
[08:07] <robertc> we have a problem where new transactions are not getting the ConnectionAdapter registered with them, using initZopeless
[08:07] <robertc> this leads to everything after the first commit() in a single thread failing.
[08:08] <BradB> This sounds like neither an sqlobject, nor an sqlos problem.
[08:09] <BradB> robertc: do you have a unit test demonstrating the failing behaviour? that would be a starting point as to figuring out what's going wrong (and, of course, making sure it doesn't come back.)
[08:09] <robertc> heh. I can write if I can guarantee a database etc etc.
[08:10] <kiko> skippin off for a bit
[08:10] <robertc> its really quite easy though :  initZopeless(), + select something + change + commit. then select + change + commit.
[08:10] <BradB> robertc: Practicality beats purity. You can guarantee a database.
[08:10] <kiko> sabdfl, let me know what comes out of it
[08:12] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Added forms to create and edit a potemplate and reenabled the poexport test (patch-892)
[08:16] <robertc> SQLBase.begin() is wrong. it makes a new txn without joining it to the connection.
[08:16] <robertc> i.e. it should be :
[08:17] <robertc>     def begin(self):
[08:17] <robertc>         txn = self.manager.begin()
[08:17] <robertc>         txn.join(self._dm())
[08:17] <robertc> (untested )
[08:20] <robertc> yep, thats it. FIXED.
[08:21] <sabdfl> carlos: that your merge? cool
[08:21] <sabdfl> robertc: you ROCK
[08:21] <BradB> robertc: Just please make sure a test comes along proving that your fix works. :)
[08:21] <robertc> hah.
[08:22] <carlos> sabdfl: yep, we are really close to be able to import files from the web without any manual process from daf or I
[08:23] <robertc> BradB: normally, I'd be the test-nazi on this, but frankly, after 4 hours on it, + 2 days of rob wier & a day of stevea, I'm over it.
[08:32] <sabdfl> carlos: excellent, thank you!
[08:32] <sabdfl> i'm still refactoring the rosetta zcml
[08:34] <carlos> ok
[08:54] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: Fix 'initzopeless second commit and thereafter' (patch-893)
[09:19] <dilys> Merge to rocketfuel@canonical.com/launchpad--devel--0: fixed Submit a Bug button to go to the bug add page (patch-894)