1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
5 <meta name="Author" content="KaiRo - Robert Kaiser">
6 <title>And the beast shall come forth... - Mozilla Infrastructure</title>
7 <link rel="stylesheet" type="text/css" href="slides.css">
8 <link rel="contents" href="index.html" title="Contents">
9 <link rel="index" href="toc.html" title="Overview">
10 <link rel="start" href="index.html" title="Start">
11 <link rel="first" href="slide_introduction.html" title="First page">
12 <link rel="previous" href="slide_comm_infra.html" title="Previous page">
13 <link rel="next" href="slide_l10n.html" title="Next page">
14 <link rel="last" href="slide_end.html" title="Last page">
17 <div id="header"><div id="header-text">And the beast shall come forth...</div>
18 <img src="template/header-logo.png" height="38" width="260" alt="">
20 <div id="slidenav"><div id="subheader-text">Community Project Organization and SeaMonkey 2</div>
21 <a href="toc.html" accesskey="t">toc</a> ||
22 <a href="index.html" accesskey="s">start</a> ||
23 <a href="slide_comm_infra.html" accesskey="p">< prev</a> |
24 <a href="slide_l10n.html" accesskey="n">next ></a>
27 <h1>Mozilla Infrastructure</h1>
29 <div class="simplebox">
31 <li><a href="http://bugzilla.mozilla.org">bugzilla.mozilla.org</a> product/component structure problems -
32 <span class="hilite"><a href="http://www.gerv.net/temp/bmo-reorg.html">bmo reorg</a></span> needed ASAP!</li>
33 <li>Not certain yet how non-FF projects can/should deal with post-CVS <span class="hilite">mozilla2 world</span></li>
35 <li><span class="hilite">One hg-repo-per-project</span> gets hard when you want
36 core+​editor+​mailnews+​suite-specifics+​calendar+​chatzilla+​...</li>
37 <li>Developers may need to <span class="hilite">relearn a whole toolchain</span>, including VCS, webtools, etc.</li>
38 <li>Mozilla2 still sounds as too much of a <span class="hilite">moving target</span> to even try adding stuff on top</li>
39 <li>How much <span class="hilite">rewriting</span> do our apps need? manually? automated?</li>
40 <li>SeaMonkey/Thunderbird/Sunbird <span class="hilite">not even at alpha</span> on 1.9 yet,
41 no free dev resources to look at even more experimental stuff atm</li>
44 <li>We might need/want a <span class="hilite">1.9.1</span>, being 1.9 + selected toolkit fixes that couldn't make FF3