[03:54] !dmwaters:*! Hi all, I need to do some quick emergency maintenence on a server, this won't take long. 1700 users affected. it'll take about 30 seconds.
[03:38] <SteveA> daf: Do I need to update some tests?
[03:39] <lulu> elmo: mmm what?
[03:45] <carlos> hi
[03:46] <carlos> daf: did you touched anything from the patch I sent you or could I continue with it?
[03:46] <daf> carlos: I didn't touch it
[03:47] <carlos> ok
[03:47] <daf> I was really tired last night, seemingly
[03:47] <carlos> daf: How is going?
[03:47] <daf> how was your exam?
[03:47] <carlos> daf: well, I cannot tell you I passed it, but neither I could tell I didn't...
[03:47] <carlos> so...
[03:48] <daf> sounds like how I feel coming out of exams :)
[03:48] <carlos> no idea 
[03:49] <carlos> daf: Which server will be used for betatesting?
[03:49] <carlos> rosetta.warthogs...?
[03:49] <daf> I suppose so
[03:49] <carlos> I think we should start feeding the database, it's not a fast process
[03:50] <carlos> daf: Do we have a list of projects that will be imported?
[03:50] <daf> nope
[03:52] <daf> it'll probably be best to start with ones which have already been imported into Arch, if possible
[03:52] <carlos> daf: Do we have them?
[03:52] <daf> what do you mean?
[03:53] <carlos> daf: I don't know anything about any imported project into arch already
[03:53] <daf> ah
[03:53] <daf> then we'd better ask somebody who knows
[03:53] <carlos> ok
[03:53] <daf> :)
[03:54] <daf> we have a couple of immediate obstables to overcome:
[03:54] <daf> Steve's authentication merge broke a few things
[03:55] <daf> well, mainly it was changing Rosetta to use some of the centralised database stuff
[03:55] <carlos> should I work on those task before resume my previous work?
[03:55] <daf> secondly, I've failed to work around this mysterious database error
[03:55] <daf> I'm discussing it with Steve, so don't worry about it for now
[03:55] <carlos> ok
[03:56] <carlos> which error?
[03:56] <daf> just so that you're aware of what's going on
[03:56] <daf> something to do with unindexable types, IIRC
[03:56] <daf> I can't fix that until we have the first problem fixed
[03:57] <carlos> then, you know the fix?
[04:00] <SteveA> let's talk about the beta test
[04:00] <SteveA> what exactly does it mean?
[04:02] <SteveA> daf: what do you have in mind?
[04:03] <carlos> I suppose will be some kind of usability test from "normal" users, and also a help to detect bugs we have when they try to "break" it
[04:03] <SteveA> Here are the things we have to choose from:
[04:04] <SteveA> * use a throw-away database, or the real database on emperor
[04:04] <SteveA> * allow only "trusted" people to access rosetta, or allow anyone to access it
[04:05] <SteveA> I think that's it.
[04:05] <daf> SteveA: I haven't really thought about it
[04:06] <daf> it was decided, at some point, that we would have a beta test
[04:06] <SteveA> let's think about it now.
[04:06] <daf> I don't belive what it would entail has ever been discussed
[04:06] <daf> ok
[04:06] <carlos> I don't think we should use the real database (yet), we are still doing some schema changes
[04:06] <daf> we have a list of participants
[04:07] <SteveA> so, we'll need a way of adding participants to the database as persons
[04:07] <daf> I suspet we'll want a mailing list for the participants and the Rosetta developers to use for discussion
[04:08] <SteveA> we can use the rosetta list for that, as all rosetta development discussion should be on the launchpad list now
[04:08] <daf> ok
[04:08] <daf> it's not a problem for rosetta list members to read the old archives, then?
[04:09] <SteveA> hmm, don't know
[04:09] <SteveA> otherwise, as jdub to set up a new list
[04:09] <SteveA> if we are to follow carlos' suggestion of not using the real database, then this should not really be called a "beta" 
[04:09] <lulu> like we have sounders for Warty - can we not have Launchpad testers for the apps
[04:10] <SteveA> the expectation with a beta, such as the "google groups beta" and the "orkut beta" is that data will persist
[04:10] <carlos> I mean, mailing list and application at something.canonical.com
[04:10] <SteveA> so, what we are planning right now is not a beta
[04:10] <SteveA> what's the collective noun for "launchpads" ?
[04:11] <carlos> SteveA: ok, then, we could still use our own database and migrate the data to the production one later, after all schema changes are done
[04:11] <SteveA> I would rather avoid migrating data if we can.
[04:12] <SteveA> it would be cleaner if we can say "after date XXX the data will be cleared, and we'll start running it for real"
[04:12] <carlos> ok
[04:12] <SteveA> we could of course export pot and po files
[04:12] <SteveA> people can do this, and reimport them, right?
[04:13] <daf> yes
[04:13] <SteveA> So, today, I want us to define what our "rosetta beta" means, and maybe change the name if it doesn't match the generally expected meaning of "beta",
[04:13] <SteveA> then we need to make a list of all the things we need to do to get to doing what we've decided "beta" means.
[04:14] <SteveA> then we need to agree who will do each of those things.
[04:16] <SteveA> So far, we have: The Rosetta "alpha" is where we make the rosetta application available to our "launchpad sounders".  The database will be thrown away once we get to the rosetta "beta" stage.  The "beta" will use the live database on emperor.
[04:16] <SteveA> Will this be a "total rosetta" or an "ubuntu rosetta" ?
[04:17] <daf> the alpha?
[04:17] <SteveA> yes, the alpha
[04:17] <SteveA> let's call it an "alpha".
[04:17] <SteveA> that's what we're aiming for right now.
[04:17] <daf> I don't see any reason to restrict it to ubuntu
[04:18] <SteveA> so, the beta will be on rosetta.canonical.com ?
[04:18] <lulu> SteveA: at the moment, we will only have the Ubuntu packages in Rosetta. it's rosetta.ubuntulinux.org. It is the distro view of Rosetta
[04:19] <SteveA> in that case, the alpha should present the same view on rosetta
[04:19] <daf> lulu: why is this the case?
[04:20] <lulu> indeed. when we go live with www.ubuntulinux.org...and hopefully Rosetta will go live at the same time, it will be Ubuntu's Rosetta.
[04:20] <daf> lulu: there is no rosetta.ubuntulinux.org yet
[04:20] <lulu> daf: the website will be www. ubuntulinux.org
[04:20] <daf> we are still talking about the alpha, and I don't think that will be on ubuntulinux.org
[04:20] <SteveA> daf: that doesn't matter.  the point is that rosetta.warthogs.hbd.com should present the Ubuntu part of rosetta
[04:20] <daf> correct me if I'm wrong
[04:20] <daf> ok
[04:20] <SteveA> the alpha should be doing similar things to the beta
[04:21] <SteveA> except that the beta will be solid enough that we are happy with it writing to the main database
[04:21] <lulu> daf: the applications that will go live at the same time are Rosetta and Malone for Ubuntu. We are in the Ubuntu distro...
[04:22] <lulu> sorry - talking about when we go live....not testing....
[04:22] <SteveA> we do have another choice then.
[04:22] <daf> lulu: ok, but I thought that Rosetta was (eventually, at least) supposed to be for all free software
[04:23] <SteveA> either the alpha is for ubuntu only, or the alpha is rosetta as a whole.
[04:23] <daf> lulu: is there a reason that we're restricting it to Ubuntu packages for now?
[04:23] <SteveA> daf: this is what we plan for the first deployment of rosetta
[04:23] <lulu> daf: absolutely yes it will be global, but Mark wants it for Ubuntu first as a pilot phase for our own distro...
[04:24] <daf> ok, that wasn't clear to me before
[04:25] <carlos> either for me
[04:26] <SteveA> let's not drop everything to change scope now
[04:26] <lulu> guys...that's not good. Rosetta and Malone first launch is for the ubuntu distro. Mark wants to get it working for Ubuntu first.
[04:27] <lulu> it should not change scope - just will only have Ubuntu packages in Rosetta to begin with.
[04:27] <carlos> lulu: it's not a problem for me
[04:27] <daf> that's not a problem, but it just wasn't clear
[04:27] <SteveA> will the app need to look any different or work any different if it is just for ubuntu?
[04:27] <daf> I think I might have propagated that misunderstanding as I was speaking to beta testers
[04:28] <daf> I don't think it affects functionality
[04:28] <lulu> For global Rosetta, we need it's own standalone site don't we.....with it's own branding - a generic Rosetta for all
[04:28] <daf> it's a thing of managing expectations
[04:28] <carlos> same problem here, but that could be fixed when we send the mail about the alpha start
[04:29] <SteveA> let's check I understand this right.  the potfiles in ubuntu rosetta will be those from ubuntu linux.
[04:29] <carlos> SteveA: yes
[04:29] <SteveA> we will be manually putting these into the database -- there is no form to add a new product or project or effort
[04:29] <carlos> SteveA: there is a way to create projects from the website
[04:30] <SteveA> does it make sense to allow people to create projects on rosetta.ubuntulinux.org ?
[04:30] <carlos> the product and efforts part are easy to add because it works like the products page
[04:30] <carlos> SteveA: I don't think so
[04:31] <SteveA> then, that is an answer to my question "does the app need to look any different or work any different if it is just for ubuntu?"
[04:31] <daf> that depends on what we want rosetta.ubuntulinux.org to be
[04:31] <lulu> SteveA: you tell us.........won't the whole of Warty be in Arch. That's what Mark said - Daf would be the owner of all the Rosetta projects first, as he needs to add them to Rosetta manually.
[04:31] <daf> if it is "*the* Rosetta", then yes
[04:31] <daf> if not, then rosetta.ubuntulinux.org will be for Ubuntu stuff only, and we will have to have the main Rosetta at some other to-be-decided location
[04:32] <daf> and we will probably have to brand the r.u.o one differently to some extent
[04:32] <SteveA> the idea of rosetta.ZZZ.org is that it is for ZZZ stuff only
[04:32] <SteveA> rosetta.gnome.org is just for gnome translations
[04:32] <carlos> are we going to share the database between rosetta's installations? (I think we should)
[04:33] <SteveA> it is always the same database
[04:33] <SteveA> we have just one golden database
[04:34] <carlos> Then I suppose we will need a way to "filter" the projets/products/efforts so we only show the correct ones but It could be done later, after Ubuntu's Rosetta launch and before we launch other Rosetta site
[04:34] <SteveA> yes
[04:35] <SteveA> this will be done through the virtual hosting support
[04:36] <SteveA> so, rosetta.fedora.org receives the request /+index
[04:36] <SteveA> and the apache or squid proxy that listens as rosetta.fedora.org rewrites that as
[04:38] <SteveA>   http://macquarie.canonical.com:8085/++vh++http:rosetta.fedora.org/++/rosetta/efforts/fedora/+index
[04:38] <SteveA> or something similar
[04:39] <SteveA> (I have the syntax a bit wrong)
[04:39] <SteveA> so, the rosetta server knows that it is serving as http://rosetta.fedora.org
[04:39] <carlos> ok
[04:40] <SteveA> and it has /rosetta/efforts/fedora/ prepended to each requested path
[04:41] <daf> let's not worry about these technical details now
[04:41] <SteveA> in the "LaunchpadContext" object, it will tell you that you're trapped within the fedora effort
[04:41] <daf> let's focus on the alpha release
[04:43] <SteveA> daf: where are we up to?  what is "The alpha release" ?
[04:44] <daf> apparently, the alpha release consists of making a running copy of Rosetta on top of a temporary database containing information about Ubuntu packages available to a selected group of people
[04:46] <SteveA> ok.  What will these people be allowed to do?
[04:47] <daf> log in, look at all the pages, change their language preferences, submit translations
[04:47] <daf> (off the top of my head)
[04:47] <SteveA> does the software allow them to do anything more than this?
[04:48] <carlos> SteveA: create new projects
[04:48] <carlos> but we could block it
[04:48] <daf> which we would need to restrict
[04:49] <SteveA> so... that means we either remove the "new projects" pages altogether
[04:49] <daf> it deosn't really matter, since the database will be temporary
[04:49] <SteveA> or we need a way of identifying "sounders" vs "staff" in the database
[04:50] <daf> we will need to be able to set "Rosetta admin" priveleves on People eventually
[04:51] <daf> (or something finer grained)
[04:51] <daf> we could probably do this using labels
[04:51] <carlos> we could do it with Labels easily
[04:51] <carlos> :-P
[04:52] <SteveA> I think a DBSchema would be more appropriate here
[04:53] <SteveA> anyway, you said it doesn't really matter
[04:56] <SteveA> in which case, the alpha allows the sounders to create new projects
[04:58] <daf> that's not a requirement, just a coincidence
[04:59] <SteveA> we need to write down what the alpha will be like
[04:59] <SteveA> it is important that we write down that we will not be disabling the "add new project" pages
[05:00] <SteveA> and that we'll need to decide whether it is okay for the beta, or need some way of classifying users before the beta.
[05:00] <carlos> For ubuntu's rosetta it should be moved away from the normal user's options
[05:02] <SteveA> daf - action item: write a clear description of what the "rosetta alpha" will do, where it will run, how we will run it.
[05:05] <daf> where *will* it run?
[05:06] <SteveA> in the alpha, I imagine we'll want to fix bugs more or less as they are reported
[05:06] <SteveA> so, it must be on rosetta.warthogs
[05:07] <daf> ok
[05:07] <daf> what do you mean by "how we will run it"?
[05:08] <SteveA> what are the activities involved in running the alpha?  who will do them?
[05:08] <SteveA> do we need to add new projects and products?
[05:08] <SteveA> who will do it?
[05:08] <SteveA> how?
[05:08] <SteveA> do we need to add new participants as Persons?
[05:08] <SteveA> who will do it?
[05:08] <SteveA> how?
[05:08] <SteveA> how do participants get their passwords?
[05:09] <SteveA> vividly imagine the alpha running, then imagine the steps needed to get there
[05:09] <SteveA> each one needs to be written down, and understood
[05:14] <SteveA> daf: does this make sense?
[05:21] <SteveA> daf: hello?
[05:22] <carlos> SteveA: seems like it's away (looking at jabber's status)
[05:22] <carlos>  /s/it/he/
[05:22] <carlos> SteveA: If it helps.. it makes sense for me 
[05:22] <SteveA> ok
[05:25] <daf> SteveA: yes, it makes sense
[05:25] <daf> sorry, I got called away
[05:26] <SteveA> good.
[05:27] <SteveA> can you take responsibility for producing this?
[05:27] <SteveA> then we can all review it when you're done.
[05:28] <daf> ok
[05:28] <SteveA> when can you do it?
[05:29] <daf> I could do it now
[05:29] <daf> I am anxious to fix other things, though
[05:30] <SteveA> I think it would be good to get this done today.
[05:30] <SteveA> even if it means pushing the other things back a bit.
[05:30] <SteveA> what do you think?
[05:31] <daf> concur
[05:31] <lulu> hi guys - just had a chat to Mark in SA
[05:32] <lulu> rosetta.ubuntulinux.org will be the Ubuntu translation effort.
[05:32] <lulu> mark is happy to have even the Ubuntu apps hardcoded on the front page with Welcome to Rosetta for Ubuntu....
[05:33] <lulu> we need to have the ability to translate the PO file for an application
[05:33] <lulu> this means we don't have to have all the plumbing available to set up and edit translation efforts.
[05:34] <lulu> but, someone can come into Ubuntus' rosetta and ask for a project to be translated - and that will be from that url
[05:35] <carlos> lulu: a project request form, right?
[05:35] <lulu> yup
[05:36] <lulu> the Global view of Rosetta.....could be at rosetta.shuttleworthfoundation.org/projects/$Project.name/$Product.name/POTemplate etc 
[05:36] <carlos> SteveA: Where could I see some info about the login code you added?, My code is not working anymore because I need a way to login first...
[05:37] <lulu> what Mark wants to do is get Ubuntu's Rosetta up and running, and then rosetta. gnome.org, rosetta.mozilla.org - 5 or 6 who use rosetta for their project...
[05:37] <lulu> then we amalgamate them in the Global view of Rosetta
[05:37] <SteveA> carlos: let's talk about that after this meeting
[05:38] <carlos> SteveA: ok
[05:38] <carlos> lulu: perfect
[05:40] <daf> lulu: so people can request any project from the Ubuntu Rosetta?
[05:41] <lulu> Mark doesn't want t o stop people asking to be able to translate, as word will spread.
[05:41] <lulu> 15th September we launch with Ubuntu's rosetta, but meantime we are working on Rosetta's global view...- generic Rosetta for all free software.
[05:42] <carlos> lulu: September?
[05:42] <lulu> but for that - we need to have all the plumbing of translation efforts set up.
[05:43] <lulu> 15th September the website launches. Rosetta for Ubuntu - Phase 1 - translate an Ubuntu application in Rosetta, is due.
[05:44] <carlos> Hmm, Why did I thought the release date was the first week of October?
[05:45] <lulu> Daf, Carlos, SteveA, Lalo, Limi - Mark said at the conference he was keen to have Rosetta for Ubuntu up. Daf - we discussed this. 
[05:46] <carlos> lulu: I know, If fact I also thought ubuntu official release was on october
[05:46] <lulu> ok - so can or can we not have the applications that are in Ubuntu translatable in Rosetta by the 15th September?
[05:47] <lulu> carlos: pre-release of Ubuntu is the 15th September. Official release is 15th October.
[05:47] <lulu> so we are aiming for those dates too.
[05:47] <carlos> lulu: ok
[05:47] <carlos> lulu: This schedule should not be a problem, we are almost there on feature implementation
[05:48] <lulu> daf: - when you did a status check last Thursday I asked you to write up on the wiki what we have done and what we still need to do.
[05:48] <SteveA> lulu: the bit of irc you missed: daf is going to work today on the list of all the things needed before we can release the alpha version of the rosetta service.
[05:49] <lulu> SteveA: ok - that was requested last week, but I appreciate people have been busy working on code. But, the purpose of it is to assist us in knowing what the goals are and how close/far we are away from it.
[05:50] <SteveA> with that list, we'll be in a position to answer the question "when can we have the alpha"
[05:50] <SteveA> note that we're intending to throw away the database after the alpha period.  but, pot and po data can be exported and re-imported
[05:52] <lulu> SteveA: good. Ok - so after Daf has donme the list, we can assess if the 15th September realistic to get Rosetta for Ubuntu up and running. But, without sufficient time for testing....it's tight.
[05:53] <lulu> Daf: once we know where we are, let's have a look and perhaps we need to manage expectations and shift the deadline...
[05:53] <lulu> daf?
[05:54] <carlos> lulu: well, the list daf is working on is more about the sounders "procedure" than the missing parts in Rosetta, the list of missing parts in Rosetta is already done since last week but it's not at the wiki (yet)
[05:54] <daf> I think I'm having trouble managing this as a time-based (rather than feature-based) release process
[05:54] <SteveA> the document daf is working on should cover the following:
[05:54] <SteveA> * what we mean by "rosetta alpha"
[05:55] <SteveA> * what software / database gets deployed where
[05:55] <SteveA> * who may use it
[05:55] <SteveA> * what they may do
[05:55] <SteveA> * what data we are / are not saving
[05:55] <SteveA> * who does the "by hand" administrative tasks, and how
[05:55] <SteveA> also
[05:55] <SteveA> * what we need to add to rosetta to be able to do the above
[05:59] <lulu> daf: yes - that is hard to get one's head around time based releases, but for a given date, we set the features we will release and make sure that there are no bugs in it. 
[06:00] <lulu> even if we have less features/basic requirements, but they work well.
[06:00] <lulu> ok - looking fwd to the list and then we can make decisions....
[06:00] <daf> sure, but we are perpetually slipping on our targets
[06:03] <lulu> daf: it seems that there's been misunderstandings on what targets we are supposed to meet in terms of time and functionality. so, if we can pin it down now, we can work to it.
[06:04] <lulu> don't despair :o) onwards and upwards!
[06:05] <SteveA> carlos: I'd like to take 10 mins break, but then can we talk about your question from earlier?
[06:05] <carlos> SteveA: sure
[06:06] <carlos> thanks
[06:16] <daf> will alpha testers be able to see the Malone/Soyuz stuff?
[06:18] <daf> https://www.warthogs.hbd.com/RosettaAlpha <-- initial revision up
[06:19] <SteveA> daf: do we want them to do so?
[06:19] <SteveA> that's another question for your document
[06:19] <daf> I don't know
[06:19] <SteveA> if we don't, we may need to do some work to stop them doing so
[06:19] <daf> would it potentially negative consequences if they could?
[06:20] <SteveA> also, should we be using a separate launchpad instance and database from our devel server?
[06:20] <carlos> I don't think they should see the other projects
[06:20] <daf> I think it only makes a difference if the Rosetta Alpha Launchpad instance doesn't have Malone and Soyuz
[06:20] <daf> because then we would be depriving the Malone/Soyuz guys of a development server
[06:21] <lulu> SteveA: when we have a staging server for all the apps - will we not have a launchpad login, and a rosetta login, malone login, soyuz login.
[06:21] <lulu> should we not have all the apps on the same dev server too?
[06:21] <daf> lulu: if you go to rosetta.warthogs.hbd.com now, you can see Rosetta, Soyuz and Malone
[06:21] <daf> lulu: the question is whether this is appropriate for our alpha testers
[06:22] <SteveA> daf: we can't just update the alpha server every half hour
[06:22] <lulu> so this perhaps should be renamed to launchpad.warthogs.hbd.com
[06:22] <SteveA> daf: the alpha server and our development server fulfil different goals
[06:23] <daf> then they should be separate
[06:23] <daf> the fact that "rosetta" is a machine name is confusing
[06:24] <lulu> can we rename it to launchpad?
[06:24] <SteveA> we can ask elmo about running the alpha on some domain name we'd like
[06:24] <SteveA> what will it be eventually?
[06:24] <SteveA> rosetta.ubuntulinux.org ?
[06:24] <daf> lulu: we could, but it would be better to name it to something not related to what the software is called
[06:25] <lulu> SteveA: rosetta.ubuntulinux.org  - correct for the distro view of Rosetta.
[06:25] <daf> "eventually" depenends on the outcome of the ubuntu.org negotiations
[06:25] <SteveA> then, it should be on port 80 of some machine called "rosetta.whatever"
[06:26] <SteveA> so, rosetta.warthogs.hbd.com is okay
[06:26] <daf> we could vhost launchpad.w.h.c on the same machine, perhaps
[06:26] <SteveA> we can get elmo to add devel.warthogs.hbd.com as an alias for rosetta.warthogs.hbd.com
[06:26] <SteveA> and get to our development server there
[06:27] <carlos> sounds good for me
[06:27] <lulu> SteveA: good idea Steve
[06:28] <SteveA> daf: be sure to write all this up.  getting elmo to do the domain stuff, and the apache config on rosetta.w.h.c is one of the tasks we need to do before being able to release an alpha
[06:28] <SteveA> also changing the development server configs
[06:28] <SteveA> and scripts
[06:30] <lulu> James said we may have new machines up by the beginning of next week...i.e. we may soon have a staging server too!
[06:30] <SteveA> carlos: I'll be back in a few minutes
[06:30] <carlos> ok
[06:31] <carlos> I have also some questions about the interface changes you did
[06:31] <carlos> Well, it's only one question :-)
[06:35] <justdave> heh, figures...  I added some table definitions to database/malone.py on Friday because I needed them for stuff I was working on.  star-merged today, and someone else (probably stub) added the same tables since then. :)
[06:36] <justdave> now to figure out how I tell which ones are his so I keep the right ones (I'll keep his instead of mine)
[06:38] <carlos> justdave: tla changes --diffs should show you stub's changes
[06:38] <justdave> yeah, it does.  doesn't show me mine though.  I'd basically like to back out my previous changeset to that file only.
[06:40] <carlos> justdave: I don't know the exact commands with tla, but you could use https://chinstrap.warthogs.hbd.com/archzoom to get a concrete version of one file
[06:41] <justdave> looking at my change logs, it looks like the changes to that file were committed as a single changeset with only that change.
[06:41] <justdave> so I could back out the entire changeset easily enough.
[06:42] <daf> justdave: I would do this:
[06:43] <daf>  - tla get the previous revision
[06:43] <daf>  - copy the file into your working tree
[06:43] <daf>  - commit
[06:43] <daf>  - delete the temporary checkout
[06:44] <daf> (by step 2, I mean copy the file in question from the temporary tree into the working tree)
[06:44] <SteveA> carlos: hi
[06:44] <carlos> SteveA: hi
[06:45] <carlos> You changed the Interface IRosettaProject to this: class IRosettaProject(IRosettaStats, doap.IProject):
[06:45] <SteveA> ok
[06:46] <carlos> SteveA: Is there any problem to do the same with the other classes that have the same methods defined in IRosettaStats?
[06:46] <justdave> heh, I love revision libs.  new checkout took all of 10 seconds because I already had it cached. :)
[06:46] <carlos>  /s/to do/if we do/
[06:47] <carlos> I suppose it should not be a problem, but you did not changed the other classes, that's why I'm asking
[06:47] <SteveA> I didn't change the other classes because I was working just on project.
[06:47] <SteveA> which other types are we talking about?
[06:48] <carlos> IProduct, IPOTemplate and IEffort
[06:49] <carlos> and ICategory
[06:49] <carlos> IEffort is not correct, it's ITranslationEffort
[06:50] <SteveA> as a first step, we can make IPOTemplate extend IRosettaStats
[06:50] <SteveA> and likewise for the others
[06:50] <carlos> well, and IPOTemplate does not have the messageCount method because it's served with the __len__ one but I suppose it's not a problem if we implement the other one that just returns len(self)
[06:51] <SteveA> as a second step, some of this functionality needs to be moved to canonical.database
[06:51] <carlos> ok
[06:52] <carlos> in time for the phase1 release?
[06:53] <SteveA> yes
[06:53] <SteveA> I'll be doing most of that, though
[06:54] <carlos> ok, then I will do the first step only, right?
[06:54] <SteveA> yes
[06:54] <SteveA> all that is involved is simplifying interfaces
[06:55] <carlos> ok
[06:55] <SteveA> you were also asking about logging in users
[06:55] <SteveA> I think
[06:55] <carlos> now, about the login/session part. Where could I see the interface we have to work with it?
[06:56] <carlos> I need to implement a template that let's the user log in the system
[06:56] <carlos> and other to update their preferences
[06:58] <SteveA> the template that lets a user log into the system for now will be a page at rosetta/+login
[06:58] <SteveA> the page requires a permission other than zope.Public to view
[06:58] <SteveA> so, it will cause the basic authentication dialog to appear
[06:59] <carlos> automatically?
[06:59] <SteveA> on a successful login, the user will be redirected to the path given in the query string, or if none is given, the rosetta front page.
[06:59] <carlos> I mean, I don't need to implement the authentication dialog?
[06:59] <SteveA> no
[06:59] <carlos> nice
[07:00] <SteveA> no need to implement the authentication dialog
[07:00] <carlos> then, what should appear inside the rosetta/+login template?
[07:01] <SteveA> I'll write that template.
[07:01] <SteveA> eventually, when we get cookie authentication, there will be a login form
[07:01] <SteveA> someone else can write that
[07:01] <SteveA> but we're using HTTP Basic auth for now
[07:01] <carlos> ok
[07:02] <SteveA> I will add the +login page today
[07:02] <carlos> so, until you write that template, how could I force the login dialog to appear?, change all pages that requiere authentication from zope.Public to zope.Private or something like that?
[09:39] <justdave> am I correct in assuming that I don't need to be on the soyuz mailing list anymore?  soyuz was originally the umbrella (what launchpad is now) which is why I subscribed to it, but soyuz seems to be just one of the components of launchpad now
[09:39] <SteveA> right
[09:39] <SteveA> launchpad is now the umbrella
[09:39] <SteveA> the platform
[09:39] <SteveA> to reverse the analogy