Status Meetings:2008-04-16:Log

From Camino Wiki
Revision as of 09:51, 16 April 2008 by Sardisson (talk | contribs) (log)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
[11:44am] You were promoted to operator by chanserv.
[11:44am] You changed the topic to "http://wiki.caminobrowser.org/Status_Meetings:2008-04-16:Agenda".
[11:44am] murph was promoted to operator by you.
[12:00pm] smorgan joined the chat room.
[12:00pm] smorgan was promoted to operator by you.
[12:00pm] peeja joined the chat room.
[12:00pm] pinkerton joined the chat room.
[12:00pm] pinkerton was promoted to operator by chanserv.
[12:01pm] peeja was promoted to operator by you.
[12:01pm] ardissone: let's give mento a couple
[12:05pm] jeff joined the chat room.
[12:05pm] jeff was promoted to operator by you.
[12:06pm] ardissone: ok
[12:06pm] ardissone: hopefully mento shows
[12:07pm] ardissone: everyone please open your Camino 1.6RC1 or newer to http://wiki.caminobrowser.org/Status_Meetings:2008-04-16:Agenda
[12:07pm] ardissone: we put out the rc last Thursday and have heard nary an evil thing about it
[12:08pm] ardissone: which bodes well
[12:08pm] ardissone: our schedule is for releasing tomorrow
[12:09pm] ardissone: there is an l10n build; i've downloaded it but haven't had a chance to play with it
[12:09pm] pinkerton: this includes the crash fix from 200.14?
[12:09pm] ardissone: yes
[12:10pm] pinkerton: ship it
[12:10pm] ardissone: 1.6rc1=1.8.1.14
[12:10pm] pinkerton: ah ok
[12:10pm] pinkerton: double ship it
[12:10pm] ardissone: i'd like to see if we could get it staged and get the update definition written so that marcello can test the update process in italian
[12:11pm] ardissone: but the former definitely requires mento
[12:12pm] ardissone: we should have 10 ML langs
[12:12pm] ardissone: which is down from 1.5
[12:12pm] ardissone: but still good
[12:12pm] smorgan: What did we lose?
[12:12pm] ardissone: spanish should come in 1.6.1
[12:13pm] ardissone: en-GB, cs, sk, and es
[12:13pm] ardissone: or, if ernesto is ready soon-ish, we could do a ML v2 again
[12:14pm] ardissone: we're probably 2/3 of the way through the website overall
[12:15pm] ardissone: sam'll stay up all night to finish 
[12:15pm] ardissone: so, basically, the release is blocked on mento and ss 
[12:16pm] ardissone: but we should be good
[12:16pm] ardissone: anyone have anything else on 1.6?
[12:18pm] ardissone: 2.0
[12:18pm] ardissone: so far smorgan's been working on it 
[12:18pm] ardissone: he keeps generating patches
[12:18pm] ardissone: which is good
[12:19pm] ardissone: some of them are getting stuck in some of our queues
[12:19pm] ardissone: which is not so brilliant
[12:19pm] pinkerton: sorry, it's on  my todo list
[12:19pm] jeff: I reviewed one of his this morning
[12:19pm] ardissone: cool 
[12:19pm] jeff: more coming later today
[12:20pm] ardissone: even better 
[12:20pm] ardissone: as a reminder, our very rough scoping doc is http://wiki.caminobrowser.org/Development:Planning:Camino_2.0
[12:21pm] pinkerton: we also need to talk at some point about another camino shin-dig at or after wwdc
[12:21pm] ardissone: sam's started a page on it, too
[12:21pm] ardissone: http://wiki.caminobrowser.org/Camino_Meet-up:2008
[12:22pm] ardissone: i don't know if he's done more on the legwork or not
[12:22pm] ardissone: maybe after releases give him his life back we can ask 
[12:23pm] ardissone: murph: anti-phishing update?
[12:23pm] pinkerton: heh
[12:23pm] murph: I have the "about:blocked" page integrated now, just working on the look of it
[12:24pm] murph: i expect the feature to be ready to go in plenty of time for 2.0
[12:24pm] ardissone: awesome!
[12:24pm] ardissone: and we'll see some v1 patches soon?
[12:25pm] murph: yes, shouldn't be long now, and we can get a jump start on reviewing 
[12:25pm] ardissone:
[12:25pm] murph: Google's still working out some server side issues with the v2 API
[12:25pm] ardissone: i forget where we stand on the whole api key thing, though
[12:25pm] ardissone: heh
[12:26pm] murph: we can supply our own "client" identifier for the url-classifier to use...
[12:28pm] ardissone: jeff: tabs(pose) update?
[12:28pm] pinkerton: brb need food badly
[12:28pm] murph: so when they actually permit other users, we'll probably want to formalize an agreement with them
[12:29pm] jeff: patches coming soon, the ones that deal with disabling features when it is active
[12:29pm] jeff: and *trying* to make it cool
[12:30pm] ardissone: heh
[12:31pm] ardissone: oh, there's one "2.0 needs action" thing I forgot
[12:31pm] ardissone: i think maybe smorgan or pinkerton need to weigh in on bug 428747
[12:32pm] ardissone: and provide some "guidance" to Core
[12:32pm] ardissone: if "allow all" is OK, that's apparently really easy
[12:32pm] smorgan: Isn't the policy up to them?
[12:32pm] ardissone: they seem to want to know what we want 
[12:34pm] pinkerton: i don't follow what's going on there
[12:34pm] smorgan: So is the only "attack" figuring out that extensions are there?
[12:34pm] ardissone: that's what i gather
[12:35pm] ardissone: it's an information leak, not a security threat
[12:35pm] ardissone: pinkerton: they changed things so web pages can't load chrome:// resoruces
[12:35pm] ardissone: which breaks ftp listings, the error pages, and flashblock, among others
[12:36pm] pinkerton: ah
[12:36pm] ardissone: they fixed toolkit to make it have an "allow" exception to not break the first two there
[12:36pm] ardissone: but our chrome reg only knows "deny"
[12:37pm] pinkerton: ah
[12:37pm] pinkerton: it feels wrong to change it to "allow"
[12:37pm] pinkerton: but i don't have anything to back that up
[12:37pm] ardissone: and only because i caught the build bustage and bsmedberg checked in a "deny" hack
[12:38pm] pinkerton: heh
[12:38pm] ardissone: allow is/was the current state
[12:38pm] ardissone: before the patch
[12:38pm] pinkerton: oh
[12:38pm] pinkerton: but that takes a lot of work?
[12:38pm] pinkerton: oh i see, that "reopens" the security hole
[12:38pm] ardissone: only to make it an allow exception
[12:39pm] ardissone: but yes, it reopens the info leak
[12:39pm] pinkerton: can't we just move to webkit? 
[12:39pm] ardissone: blanket-allow is supposedly easy; allow-this-but-not-that is harder
[12:39pm] ardissone: heeh
[12:40pm] pinkerton: well i guess in the short term we can go back to blanket allow to fix things while we figure out what we ultimately want to do
[12:40pm] pinkerton: so tot builds are more usable
[12:40pm] pinkerton: we never guarantee the security of nightlies
[12:40pm] smorgan: I don't really see that it's worth the effort for us
[12:40pm] smorgan: People can do a version check on Camino to know if FB is installed
[12:40pm] ardissone: (if they backport this to the branch, they'd have to fix our chrome reg)
[12:41pm] smorgan: I don't think any real information is leaking here
[12:41pm] ardissone: yeah, me either
[12:41pm] pinkerton: ok
[12:41pm] smorgan: So if they are okay with allow, I'm all for it
[12:42pm] ardissone: i just didn't want to speak for Camino there 
[12:42pm] ardissone: anyone have anything else on 2.0?
[12:44pm] ardissone: do we know when we hear things about SoC?
[12:44pm] smorgan: Monday
[12:45pm] ardissone: crosses fingers
[12:45pm] ardissone: anyone have anything else today?
[12:47pm] ardissone: ok
[12:48pm] ardissone: well, hopefully we see mento today 
[12:49pm] ardissone: otherwise, everyone have a good week, and get ready for a major release 
[12:50pm] smorgan left the chat room.