improve dashboard links
[slides.git] / fosdem2006 / slide_01.html
... / ...
CommitLineData
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
2<html>
3<head>
4 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
5 <meta name="Author" content="KaiRo - Robert Kaiser">
6 <title>SeaMonkey: "Ancient" History</title>
7 <link rel="stylesheet" type="text/css" href="slides2006.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_01.html" title="First page">
12 <!-- <link rel="previous" href="slide_01.html" title="Previous page"> -->
13 <link rel="next" href="slide_02.html" title="Next page">
14 <link rel="last" href="slide_end.html" title="Last page">
15</head>
16<body>
17
18<h1>"Ancient" History</h1>
19
20<div class="explanation">
21<ul class="timeline">
22 <li><b>1998</b>:
23 <ul>
24 <li>January 23:
25 <ul>
26 <li>Netscape <span class="hilite">opening up development of Netscape
27 Communicator</span> internet suite</li>
28 <li><a href="http://www.mozilla.org/">Mozilla</a> project
29 <a href="http://wp.netscape.com/newsref/pr/newsrelease577.html">
30 founded</a> to bring new power to that product.</li>
31 </ul>
32 </li>
33 <li>March 31:
34 <ul>
35 <li><a href="http://wp.netscape.com/newsref/pr/newsrelease591.html?cp=nws04flh1">first
36 developer release of the source code</a> to Communicator</li>
37 </ul>
38 <li>Netscape internally looking for a <span class="hilite">codename</span>
39 for next big release (planned as version 5.0 at that time)
40 <ul>
41 <li>Developer voting</li>
42 <li>Surprising result: <span class="hilite">"ButtMonkey"</span> winning!
43 ("jenga" as run-in)</li>
44 <li>Netscape management deciding to use the similar sounding but comparably
45 harmless <span class="hilite">"SeaMonkey"</span>.</li>
46 <li>Codename getting heavily tied to suite development,
47 binaries getting released on project page with that codename.</li>
48 <li class="small">(Thanks to dveditz, Google cache and pseudorandom.org
49 IRC logs for helping us to find out about that.)</li>
50 </ul>
51 </li>
52 </ul>
53 </li>
54 <li><b>2002</b>:
55 <ul>
56 <li>June 5:
57 <ul>
58 <li><span class="hilite"><a href="http://www.mozilla.org/releases/mozilla1.0.html">Mozilla 1.0</a></span>
59 <a href="http://www.mozillazine.org/articles/article2278.html">released</a></li>
60 <li>People <a href="http://www.schnitzer.at/mozparty/">partying</a> all
61 over the world</li>
62 </ul>
63 </li>
64 <li>April-August:
65 <ul>
66 <li>A few developers start project for <span class="hilite">standalone
67 browser</span></li>
68 <li>called "m/b", later "Phoenix", then "Firebird", now
69 "Firefox"</li>
70 </ul>
71 </li>
72 </ul>
73 </li>
74 <li><b>2003</b>:
75 <ul>
76 <li>April 2:
77 <ul>
78 <li>mozilla.org publishes
79 <a href="http://www.mozilla.org/roadmap/roadmap-02-Apr-2003.html">new
80 roadmap</a></li>
81 <li>calls for <span class="hilite">fading out suite</span>
82 after Mozilla 1.4 in favor of standalone browser and mail</li>
83 <li>Suite would not be retired for the "foreseeable future" though</li>
84 </ul>
85 </li>
86 </ul>
87 </li>
88</ul>
89</div>
90
91<p class="forward"><a href="slide_02.html" accesskey="n">next</a></p>
92
93</body>
94</html>