<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.caminobrowser.org/index.php?action=history&amp;feed=atom&amp;title=Status_Meetings%3A2006-11-01%3ALog</id>
	<title>Status Meetings:2006-11-01:Log - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.caminobrowser.org/index.php?action=history&amp;feed=atom&amp;title=Status_Meetings%3A2006-11-01%3ALog"/>
	<link rel="alternate" type="text/html" href="http://wiki.caminobrowser.org/index.php?title=Status_Meetings:2006-11-01:Log&amp;action=history"/>
	<updated>2026-09-06T08:17:44Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.34.4</generator>
	<entry>
		<id>http://wiki.caminobrowser.org/index.php?title=Status_Meetings:2006-11-01:Log&amp;diff=6833&amp;oldid=prev</id>
		<title>Admin: Initial Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.caminobrowser.org/index.php?title=Status_Meetings:2006-11-01:Log&amp;diff=6833&amp;oldid=prev"/>
		<updated>2006-11-12T12:23:32Z</updated>

		<summary type="html">&lt;p&gt;Initial Page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;&amp;lt;pre&amp;gt;&lt;br /&gt;
12:05 &amp;lt;@ss&amp;gt; Sorry, I got caught up&lt;br /&gt;
12:05 &amp;lt;@ss&amp;gt; Let&amp;#039;s start.&lt;br /&gt;
12:06 &amp;lt;@ss&amp;gt; Everyone please put http://wiki.caminobrowser.org/Status_Meetings:2006-11-01:Agenda &lt;br /&gt;
            in your Camino.&lt;br /&gt;
12:06 &amp;lt;@ss&amp;gt; Camino 1.1a1:&lt;br /&gt;
12:06 &amp;lt;@ss&amp;gt; We&amp;#039;re still seeing that random hex crasher, which might be the random crasher we&amp;#039;re &lt;br /&gt;
            all seeing.&lt;br /&gt;
12:06 &amp;lt;@ss&amp;gt; (Or at least, I am)&lt;br /&gt;
12:07 &amp;lt;@ss&amp;gt; There&amp;#039;s also another crash&lt;br /&gt;
12:07 &amp;lt;@ss&amp;gt; It&amp;#039;s listed in the agenda.&lt;br /&gt;
12:08 &amp;lt;@ss&amp;gt; If anyone has time to look into those (for what little amount they can), it&amp;#039;d &lt;br /&gt;
            beneficial.&lt;br /&gt;
12:08 &amp;lt;@ss&amp;gt; I haven&amp;#039;t been able to reliably reproduce any crash unfortunately (or fortunately?).&lt;br /&gt;
12:09 &amp;lt;@ss&amp;gt; Camino 1.1:&lt;br /&gt;
12:09 &amp;lt;@ss&amp;gt; We&amp;#039;re down to 100 bugs, which is good.&lt;br /&gt;
12:09 &amp;lt;@ss&amp;gt; Very good. :)&lt;br /&gt;
12:09 &amp;lt;@froodian&amp;gt; w00t&lt;br /&gt;
12:09 &amp;lt;@ss&amp;gt; The Zoom bug is (Torben&amp;#039;s) is now in smfr&amp;#039;s SR queue&lt;br /&gt;
12:09 &amp;lt;@ss&amp;gt; Hopefully that&amp;#039;ll get in soon as it&amp;#039;s been requested a lot lately.&lt;br /&gt;
12:10 &amp;lt;@ss&amp;gt; Also, smorgan got the first part of session saving written, just needs reviews and &lt;br /&gt;
            such. :)&lt;br /&gt;
12:10 &amp;lt;@ss&amp;gt; Hopefully for alpha2 we can get those two things in.&lt;br /&gt;
12:10 &amp;lt;@ss&amp;gt; Tinderboxen:&lt;br /&gt;
12:10 &amp;lt;@ss&amp;gt; (boxset is burning, btw)&lt;br /&gt;
12:10 &amp;lt;@smorgan&amp;gt; I&amp;#039;d like to get Safari keychain compat in for 1.1 too, btw&lt;br /&gt;
12:10 &amp;lt;@froodian&amp;gt; speaking of which, i know it&amp;#039;s a little OT, but we&amp;#039;re gonna need software soon &lt;br /&gt;
                  if we&amp;#039;re gonna have it, wont&amp;#039; we?&lt;br /&gt;
12:11 &amp;lt;@ss&amp;gt; Have what?&lt;br /&gt;
12:11 &amp;lt;@froodian&amp;gt; software update&lt;br /&gt;
12:11  * ss isn&amp;#039;t sure he mentioned software update.&lt;br /&gt;
12:11 &amp;lt;@froodian&amp;gt; hence why i said OT ;)&lt;br /&gt;
12:11 &amp;lt;@froodian&amp;gt; but if it&amp;#039;s going to be in 1.1 it needs to be in some release prior to that, &lt;br /&gt;
                  so that it gets tested at least once&lt;br /&gt;
12:12 &amp;lt;@ss&amp;gt; Ah...&lt;br /&gt;
12:12 &amp;lt;@froodian&amp;gt; anyway, we can continue&lt;br /&gt;
12:12 &amp;lt;@froodian&amp;gt; just wanted to mention that&lt;br /&gt;
12:12 &amp;lt;@ss&amp;gt; I&amp;#039;m not sure if we&amp;#039;re going to get it.&lt;br /&gt;
12:13 &amp;lt;@ss&amp;gt; But if we do, we&amp;#039;ll need to integrate a lot with the m.o system&lt;br /&gt;
12:13 &amp;lt;@ss&amp;gt; So we might need some server-side help.&lt;br /&gt;
12:13 &amp;lt;@ss&amp;gt; But that shouldn&amp;#039;t be a big problem.&lt;br /&gt;
12:13 &amp;lt;@ss&amp;gt; Build graphs are back for pawn (yay)&lt;br /&gt;
12:14 &amp;lt;@ss&amp;gt; perf data hasn&amp;#039;t been very useful though.&lt;br /&gt;
12:14 &amp;lt;@ss&amp;gt; It&amp;#039;d be nice if we had a tinderbox that produced reliable results. Alas. :)&lt;br /&gt;
12:14 &amp;lt;@ss&amp;gt; And... in lieu of waiting on m.o, mento&amp;#039;s bumping the SDK up on the tinderbox and in &lt;br /&gt;
            the project&lt;br /&gt;
12:15 &amp;lt;@ss&amp;gt; So we&amp;#039;re moving to 10.3.9 (and 10.3.0, where applicable) to build.&lt;br /&gt;
12:15 &amp;lt;@ss&amp;gt; That&amp;#039;s on trunk and branch, but not 1.8.0 branch&lt;br /&gt;
12:15 &amp;lt;@ss&amp;gt; Overall, our queues did alright this week and we landed 20 fixes (although some were &lt;br /&gt;
            combined)&lt;br /&gt;
12:16 &amp;lt;@ss&amp;gt; With smorgan as an sr though, we need some more reviewers. ;)&lt;br /&gt;
12:16 &amp;lt;@ss&amp;gt; If anyone sees murph, he might be good to ask.&lt;br /&gt;
12:16 &amp;lt;@ss&amp;gt; Any other business before we move to the specific bugs?&lt;br /&gt;
12:16 &amp;lt;@kreeger&amp;gt; yay 10.3.9&lt;br /&gt;
12:16 &amp;lt;@smorgan&amp;gt; Keychain relates to queues&lt;br /&gt;
12:16 &amp;lt;@smorgan&amp;gt; Like I said, I&amp;#039;d like to get it in&lt;br /&gt;
12:17 &amp;lt;@ss&amp;gt; Right, Keychain is all on pinkerton now, right?&lt;br /&gt;
12:17 &amp;lt;@smorgan&amp;gt; It would be a big help for getting Safari users to try out 1.1&lt;br /&gt;
12:17 &amp;lt;@ss&amp;gt; I&amp;#039;m not one for setting arbitrary dates, but I think it&amp;#039;d be good to get a2 by the&lt;br /&gt;
            end of the month (November).&lt;br /&gt;
12:17 &amp;lt;@ss&amp;gt; With some of these new features in.&lt;br /&gt;
12:17 &amp;lt;@ss&amp;gt; Keychain is a big one, and session saving.&lt;br /&gt;
12:17 &amp;lt;@pinkerton&amp;gt; yeah yeah&lt;br /&gt;
12:17 &amp;lt;@pinkerton&amp;gt; sorry&lt;br /&gt;
12:18 &amp;lt;@ss&amp;gt; :)&lt;br /&gt;
12:18 &amp;lt;@pinkerton&amp;gt; i&amp;#039;m totally swamped&lt;br /&gt;
12:18 &amp;lt;@pinkerton&amp;gt; i know that&amp;#039;s a priority, i&amp;#039;ll make some time for it&lt;br /&gt;
12:18 &amp;lt;@smorgan&amp;gt; I can write the next part of the keychain stuff now I guess, but eventually &lt;br /&gt;
                 it&amp;#039;s going to have to go in; I&amp;#039;m just wondering if that&amp;#039;s realistic or not &lt;br /&gt;
                 before I go forward with it&lt;br /&gt;
12:18 &amp;lt;@smorgan&amp;gt; If it&amp;#039;s not, it&amp;#039;s not, and I&amp;#039;ll write it later&lt;br /&gt;
12:18 &amp;lt;@ss&amp;gt; You mean Keychain for 1.1?&lt;br /&gt;
12:18 &amp;lt;@ss&amp;gt; I think that&amp;#039;s realistic.&lt;br /&gt;
12:18 &amp;lt;@smorgan&amp;gt; Yes&lt;br /&gt;
12:18 -!- mento has joined #camino-mtg&lt;br /&gt;
12:18 &amp;lt;@ss&amp;gt; It was planned for the in the first place&lt;br /&gt;
12:18 &amp;lt;@ss&amp;gt; We only moved it out because no one was working on it.&lt;br /&gt;
12:18  * mento unmutes&lt;br /&gt;
12:19 &amp;lt;@smorgan&amp;gt; ss: unless you are planning on sr&amp;#039;ing, it&amp;#039;s not really your call on whether &lt;br /&gt;
                 it&amp;#039;s realistic&lt;br /&gt;
12:21 &amp;lt;@smorgan&amp;gt; I guess I&amp;#039;ll go ahead and write it, and we&amp;#039;ll see what happens.  It&amp;#039;s not &lt;br /&gt;
                 likely to rot much if at all even if it doesn&amp;#039;t end up in 1.1&lt;br /&gt;
12:21 &amp;lt;@ss&amp;gt; Sounds good.&lt;br /&gt;
12:21 &amp;lt;@pinkerton&amp;gt; ok&lt;br /&gt;
12:21 &amp;lt;@ss&amp;gt; Anything else before specific bugs?&lt;br /&gt;
12:21 !sand.mozilla.org ss invited thebot into the channel.&lt;br /&gt;
12:21 -!- thebot has joined #camino-mtg&lt;br /&gt;
12:21 &amp;lt;@ss&amp;gt; Bug 314628&lt;br /&gt;
12:21 &amp;lt; thebot&amp;gt; ss: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=314628 enh, --, Camino1.2, &lt;br /&gt;
                stuart.morgan@alumni.case.edu, NEW, how do i find out &amp;quot;what is being used as my &lt;br /&gt;
                dock menu?&amp;quot;&lt;br /&gt;
12:22 &amp;lt;@ss&amp;gt; We need ideas on what to do there to show a folder as in use as the dock menu.&lt;br /&gt;
12:22 &amp;lt;@pinkerton&amp;gt; can&amp;#039;t we change the icon?&lt;br /&gt;
12:22 &amp;lt;@pinkerton&amp;gt; taht shouldn&amp;#039;t be hard to code&lt;br /&gt;
12:23 &amp;lt;@froodian&amp;gt; what if it&amp;#039;s a collection though?&lt;br /&gt;
12:23 &amp;lt;@smorgan&amp;gt; It would have to be a badge&lt;br /&gt;
12:23 &amp;lt;@froodian&amp;gt; does that mean the top10 would never have its own icon by default?&lt;br /&gt;
12:23 &amp;lt;@froodian&amp;gt; yeah&lt;br /&gt;
12:23 &amp;lt;@pinkerton&amp;gt; ah&lt;br /&gt;
12:23 &amp;lt;@pinkerton&amp;gt; well, what about doing it only for folders displayed in the tree?&lt;br /&gt;
12:23 &amp;lt;@pinkerton&amp;gt; that&amp;#039;s half the battle, no?&lt;br /&gt;
12:23 &amp;lt;@pinkerton&amp;gt; people trying to delete fodlers and not being able to? or did we fix that&lt;br /&gt;
12:24 &amp;lt;@froodian&amp;gt; we fixed that&lt;br /&gt;
12:24 &amp;lt;@smorgan&amp;gt; We fixed that&lt;br /&gt;
12:24 &amp;lt;@pinkerton&amp;gt; i c&lt;br /&gt;
12:24 &amp;lt;@smorgan&amp;gt; This is cosmetic&lt;br /&gt;
12:24 &amp;lt;@pinkerton&amp;gt; gotcha&lt;br /&gt;
12:24 &amp;lt;@smorgan&amp;gt; I&amp;#039;m not sure why we care right now...&lt;br /&gt;
12:24 &amp;lt;@pinkerton&amp;gt; seems low priority, given other things&lt;br /&gt;
12:24 &amp;lt;@smorgan&amp;gt; AFAIK it&amp;#039;s only on anyone&amp;#039;s radar because I touched it for the trivial menu fix&lt;br /&gt;
12:25 &amp;lt;@ss&amp;gt; I think it was kind of a &amp;quot;while you&amp;#039;re there&amp;quot; sort of thing.&lt;br /&gt;
12:25 &amp;lt;@froodian&amp;gt; it&amp;#039;s worth talking about bugs.  i mean, that&amp;#039;s the whole point. ;)&lt;br /&gt;
12:25 &amp;lt;@froodian&amp;gt; but yeah, i think what we have now (or will have) will be fine&lt;br /&gt;
12:25 &amp;lt;@froodian&amp;gt; for now&lt;br /&gt;
12:26 &amp;lt;@froodian&amp;gt; next?&lt;br /&gt;
12:27 &amp;lt;@froodian&amp;gt; (though we should mention the icon badge idea in the bug)&lt;br /&gt;
12:27 &amp;lt;@ss&amp;gt; Bug 355490&lt;br /&gt;
12:27 &amp;lt; thebot&amp;gt; ss: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=355490 nor, --, Camino1.2, &lt;br /&gt;
                d.elliott@sms.ed.ac.uk, ASSI, Need a way to access all tabs quickly from the tab &lt;br /&gt;
                bar&lt;br /&gt;
12:27 &amp;lt;@ss&amp;gt; delliott wanted us to talk about that again, though we did last week.&lt;br /&gt;
12:27 &amp;lt;@smorgan&amp;gt; All we need here is icon ideas, AFAIK&lt;br /&gt;
12:27 &amp;lt;@froodian&amp;gt; he doesn&amp;#039;t know we did&lt;br /&gt;
12:27 &amp;lt;@ss&amp;gt; Ah...&lt;br /&gt;
12:27 &amp;lt;@froodian&amp;gt; i don&amp;#039;t think there&amp;#039;s anything to say that we didn&amp;#039;t say last week&lt;br /&gt;
12:27 &amp;lt;@ss&amp;gt; Well then, smorgan already said in the bug what the meeting decision was.&lt;br /&gt;
12:28 &amp;lt;@froodian&amp;gt; right&lt;br /&gt;
12:28 &amp;lt;@ss&amp;gt; So that should be good enough.&lt;br /&gt;
12:28 &amp;lt;@smorgan&amp;gt; I&amp;#039;ve commented about the behavior in the bug, so he should know about that &lt;br /&gt;
                 decision now&lt;br /&gt;
12:28 &amp;lt;@ss&amp;gt; Bug 355033&lt;br /&gt;
12:28 &amp;lt; thebot&amp;gt; ss: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=355033 nor, --, ---, &lt;br /&gt;
                stuart.morgan@alumni.case.edu, NEW, Keychain password prefs need clarification&lt;br /&gt;
12:28 &amp;lt;@smorgan&amp;gt; I just thought this would be good 1.1, since we&amp;#039;ve done a bunch of pref work&lt;br /&gt;
12:28 &amp;lt;@smorgan&amp;gt; I can do this easily if it&amp;#039;s green-lighted&lt;br /&gt;
12:28 &amp;lt;@ss&amp;gt; It&amp;#039;s probably a pinkerton decision.&lt;br /&gt;
12:28 &amp;lt;@ss&amp;gt; I think most the rest of us agree. :)&lt;br /&gt;
12:30 &amp;lt;@smorgan&amp;gt; The main question is, does anyone see any value to the two-pref system we have &lt;br /&gt;
                 now&lt;br /&gt;
12:30  * froodian doesn&amp;#039;t, other than fun checkbox validation&lt;br /&gt;
12:30 &amp;lt;@froodian&amp;gt; ;)&lt;br /&gt;
12:30 &amp;lt;@pinkerton&amp;gt; heh, let me read&lt;br /&gt;
12:31 &amp;lt;@pinkerton&amp;gt; make it so&lt;br /&gt;
12:31 &amp;lt;@smorgan&amp;gt; Both parts?&lt;br /&gt;
12:31 &amp;lt;@smorgan&amp;gt; Boing being single pref and web-form only&lt;br /&gt;
12:31 &amp;lt;@pinkerton&amp;gt; yes&lt;br /&gt;
12:31 &amp;lt;@smorgan&amp;gt; cool&lt;br /&gt;
12:31 &amp;lt;@kreeger&amp;gt; lunch&lt;br /&gt;
12:31 -!- kreeger is now known as kreeger-lunch&lt;br /&gt;
12:31 &amp;lt;@froodian&amp;gt; 21 bugs since last week :)&lt;br /&gt;
12:31 &amp;lt;@froodian&amp;gt; (fixed)&lt;br /&gt;
12:32 &amp;lt;@ss&amp;gt; Anything else?&lt;br /&gt;
12:32 &amp;lt;@ss&amp;gt; Alright then. See you all back here next week and happy bug fixing (or triaging, or &lt;br /&gt;
            reviewing, or whatever)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
		
	</entry>
</feed>