1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
5 <title>The Story of the GNOME project</title>
7 <body bgcolor=white text=black>
9 <h1>The Story of the GNOME project</h1>
11 <p>An incomplete recollection of some of the events in the story of the
12 GNOME project. Maybe one day I will finish it.</p>
13 <p>This is our local copy of the original pages from http://primates.ximian.com/~miguel/gnome-history.html</p>
15 <h2>The early days</h2>
17 GNOME was the result of various attempts from a group of friends that
18 wanted to improve free software. I list here some of the ideas
19 and projects that eventually lead to the creation of the GNOME
22 You might also find the <a href="helix-history.html">Story of Ximian</a>
26 <h3>The foundations for the GNOME project</h3>
28 In 1996 my friend <a href="http://people.redhat.com/sopwith">Elliot
29 Lee</a> was working at <a href="http://www.redhat.com">Red
30 Hat</a> for a summer as the webmaster. We shared a lot of common interests
31 related to the future of <a href="http://www.gnu.org/philosophy/free-sw.html">free software</a>. We both
32 contributed to various efforts to bring free software forward. After the
33 introduction of Windows 95, it was clear that the free software universe
34 was lacking a number of technologies and that we were lagging behind in
35 various areas. I did some work into a free implementation of the Java
36 Awt (back in those days Java was still seen as the solution for the lack
37 of software in Unix systems).<br>
39 At the time I was working with Ralf Baechle in the <a
40 href="http://lwww.linux.sgi.com">Linux/SGI</a> port
41 that was partially funded by SGI. From time to time I would devote a
42 few hours to other free software efforts that would help close the gap between
43 proprietary offerings and Linux. My friend Ariel Faigon at SGI had once
44 raised the issues of the future of free software and the lack of desktop
45 applications and the lack of an OLE-like model.<br>
47 Elliot and I tried to organize various efforts to address some of the consistency
50 issues in Linux. Our first attempt was the libapp effort, which was a set
53 of library functions that would be used to access common resources used
56 by applications (configuration management, keeping track of recently used
59 files, mime handling and so on). But we never quite did finish this project.
62 At this time the idea of producing a complete system like GNOME was out
65 of the question and we were aiming for the easy tasks first.<br>
67 At the Atlanta Linux Showcase a year before I had met Todd who was interested
70 in producing a full desktop based on Scheme. This project only produced
73 screenshots and we never got too far.<br>
75 In 1996 I recruited two students from the recently created Computer Science
76 degree in the <a href="http://www.fciencias.unam.mx">Facultad de
77 Ciencias</a> at UNAM. Those
78 two students were Arturo Espinosa and <a href="http://primates.helixcode.com/~federico">Federico Mena</a>.
79 They were working on assorted free software projects, and in projects
80 around my favorite language at the time Scheme. They worked with me in
81 free software and in fun projects at the <a href="http://www.nuclecu.unam.mx">Instituto
82 de Ciencias Nucleares</a> at the <a href="http://www.unam.mx">Universidad Nacional
83 Autonoma de Mexico</a>. There we also worked on the <a href="http://www.linux.org.mx">Mexican
84 Linux Users Group</a>.<br>
86 In the Summer of 1997 my friend Randy Chapman invited me to interview at
87 the Microsoft Internet Explorer for Solaris on the SPARC (because of my
88 background in the Linux/SPARC port). I went to interview to Microsoft
89 that summer and met both Randy Chapman and <a
90 href="http://www.nat.org">Nat Friedman</a> for
91 the first time in person. We had known for a long time from the LinuxNet
94 At Microsoft I learned the truth about ActiveX and COM and I got very interested
95 in it inmediately. Upon my return to Mexico Federico and I started to
96 design a GUI control infrastructure for Unix that we code named `GNOME'.
97 He was working as the maintainer of the <a
98 href="http://www.gimp.org">GIMP</a> back
99 then and our efforts were targeted towards its adoption on Tk at the time.
100 This project was the seed for what later became the <a
101 href="http://developer.ximian.com/tech/bonobo.html">Bonobo</a> component
102 architecture (sixteen months would pass before I started working on Bonobo).<br>
104 At this point the <a href="http://www.kde.org">Kool Desktop
105 Environment project</a> (KDE)
106 was showing a lot of promise: a team of programmers started an effort
107 to bring Unix to the desktop using the C++ based GUI toolkit. I mailed
108 my friend Erik Troan suggesting him to include that code into the Red
109 Hat distribution and I mailed Richard Stallman to let him know that this
110 interesting project existed. KDE was licensed under the terms of the
111 GNU GPL. I got a reply back from both Erik and Richard pointing out that
112 KDE dependency on Qt resulted in a piece of non-free software. Qt did
113 not end users the right to modify, redistribute nor distribute modifed
114 copies of the code and violated the terms of the GNU GPL. <br>
116 Being a free software entusiast, I contacted Troll Tech, the authors of Qt
119 to propose an alternate licensing scheme for Qt that would still allow them
122 to build a company while empowering users but got no reply. The Troll Tech
125 FAQ at the time also contained significant errors regarding the GPL and
128 ignored dual-licensing schemes. After a time out period, we decided to
131 do something about this problem. Also discouraging was the fact that the
134 KDE developers were not interested in resolving those issues as pointed
137 out in their FAQ document and their mailing list policies. <br>
139 We evaluated writing a free Qt replacement, but reimplementing an API would
140 most likely result in less efficient software and would have taken too
141 long to implement. GNUstep, Wine and LessTif were other projects that
142 had attempted to reimplement a proprietary API and just had a limited
143 success after a long development history. <br>
145 Various friends from the #linux channel in the LinuxNet network were also
146 in part responsible for the launch of the project. <br>
147 <h3>GNOME is born</h3>
148 <b>Update:</b>We did try for a few days to work on the GNUstep
150 Francisco Bustamente (bit), Federico and I would be working
152 whole thing to work, but it was too big, too slow, too
153 buggy, too incomplete
154 and there was little organization in the team.
155 After repeated attempts to
156 work on it, we eventually gave up.
160 So I started the GNOME project at that point in August 1997. The draft for
163 the announcement was sent to various friends of mine which included Richard
166 Stallman, Marc Ewing, Elliot Lee, Erik Troan, Spencer Kimball and Peter
169 Mathis. When the project was ready Federico and I sent the announcement
172 of the creation of the GNOME projects to a few mailing lists: The GIMP mailing
175 list, the Guile mailing list, the GNU project announcement mailing list
178 and comp.os.linux.announce.<br>
180 Federico and I started developing the GNOME libraries on our spare time.
183 He was still mostly working on the GIMP and I was still mostly working on
186 the X11 IRIX emulation code for Linux on the SGI/Indy. We setup the makefiles
189 to mimic the Gtk+ setup. <br>
191 Various early contributions from the people on the mailing list had a long
193 lasting effect: CORBA was going to be our foundation for the component architecture,
195 and DocBook would be used to write the documentation of GNOME. Initially,
197 we looked into Xerox's ILU, but the license of it was not free, so we had
199 to research other options: we tried MICO for some time, but it was too large
201 and too slow for most developers and users. Then we looked at Flick's optimizing
203 compiler and finally Dick and Elliot would start work on it. <br>
205 At this point a friend of ours registered gnome.org and offered to host the
207 CVS server for GNOME. <br>
209 By november that year GNOME had reached enough momentum that both Federico
212 and I dropped other projects and devoted ourselves completely to work on
215 GNOME. We did port the GtkXmHTML engine over the december vacations and
218 I started to read Slashdot.<br>
220 We had a meeting in the early days of December with Marc Ewing and DrMike
222 at the Red Hat offices. To make this meeting I had to skip the U2 concert
224 in Mexico City for their Pop tour. I remember that they were transmitting
226 the concert live on satelite TV, but Erik took me dancing.<br>
228 Marc was creating the <a href="http://www.labs.redhat.com">Red Hat
229 Advanced Development Labs</a> which
230 would be the first funded team of developers that would work towards improving
231 GNOME. RHAD Labs was created in Jannuary of 1998. Marc and DrMike worked
232 on the GNOME help browser; Raster worked on Gdk_Imlib, Enlightenment
233 and the Gtk+ themes engine. Later that year Owen, Jonathan, Dave and
234 Federico would join. <br>
236 <h2><a name="summit"></a>The GNOME summit</h2>
237 GNOME 0.13, 0.20 or 0.30 had been released and we were demoing it at the
238 Linux Expo that was being hosted at Duke University. This is also the first
239 time I did a presentation on the GNOME project (which turned out ok, despite
240 the problems I had with my laptop on stage). <br>
242 This was also the first time that I saw Nat Friedman after having met him
243 at Microsoft, and it was a lot of fun. He was working on a more extensible
244 dingus architecture for various terminal programs. The dingus-click feature
245 would eventually make it into GNOME terminal and prove to be a necessary
246 feature for everything that pretended to be a terminal emulator. <br>
248 Marc Ewing and Michael Fullbright organized the GNOME summit: the first meeting
250 where various GNOME developers would get together. This was organized the
252 day after the Third Linux Expo held at Duke University. Various GNOME hackers
254 were going to the conference, and various of us got together to discuss
256 the various directions that the project would take. <br>
258 Various hackers were present: Chris Lahey, Larry Ewing, Adrian Likins, Raster,
260 Tim Gerla, Jonathan Bladford, Rosanna Yuen, Matthew Wilson, Federico Mena,
262 Marc Ewing, Michael Fullbright, Mark Chricton, Jay Painter, Alan Cox. Notable
264 appearances include David Miller (which went there to get a GNOME shirt)
266 and Telsa Gwynne (which later would become involved in the documentation
268 effort). Elliot Lee would arrive later that day<br>
270 With the exception of Jay, all of them are still involved with GNOME hacking
273 <h3><a name="poundgimp"></a>#gimp</h3>
274 Various of the hackers involved in GIMP and Gtk+ used to hang around in the
275 #gimp channel on irc.mint.net. A lot of very clueful people used to come
276 by the channel and offer their input and their help in various matters.
277 Many of the people who came to #gimp would become GNOME contributors.
278 #gimp was also a good forum for discussing GNOME, as it did not drew the
279 attention too much to the project from the people who were not interested
280 in the success of the project.<br>
282 It remained in that way until most of the discussion in #gimp was related
283 to GNOME, at that point Zach created a new #gnome channel, and most of the
284 GNOME discussion took place in the new channel. <br>
285 <h3><a name="gnomelogo"></a>The GNOME Logo</h3>
286 Tuomas Kuosmanen (Tigert) was one of our friends that used to go by #gimp.
287 Tuomas being a GIMP user himself he did various logos, the GIMP mascot (Wilber)
288 and he also had done some small icons that were very nice looking. We started
289 to use Tuomas' icons in GNOME, and he would draw icons for us for the various
290 GNOME applications, and also for the various "Stock" icons (an idea I had
291 that Eckehard implemented to add some consistency to the look of applications).<br>
293 When we were looking for an icon for the GNOME panel, we went to Tuomas site,
294 and we picked one of the icons he had drawn that had no association to anything
295 yet, a gradient-filled foot in a square. This was the foot that was used
296 for the menu for a long time.<br>
298 The foot turned out to be problematic, as someone spotted a similar looking
299 logo, and both DrMike and Rasterman were worried about possible problems
300 caused because our GNOME foot looked to similar to the other logo. <br>
302 The Red Hat labs decided to sponsor a logo competition for GNOME a few months
303 later, and the prize was a digitizing tablet. There is one drawback to
304 the logo contest: it was run by the GIMP people, and hence one of the requirements
305 was to make the logo using the GIMP. This means that we did not get any
306 vector-based logos for the project. There were many good submissions, many
307 of them very good.<br>
309 We chose to use a new version of the foot done by Tuomas himself. The big
310 difference is that the new foot looked like a "G" instead (the other one
311 was a right foot, this would be a left foot, G-shaped). The logo was quite
312 nice, and we are still using it today.<br>
313 <h3><a name="gnomecal"></a>GnomeCal</h3>
314 Craig Small had been working on a calendar application for GNOME, but his
315 time constraints did not allow him to continue the work. And given the
316 state of complexity of gnome development, he had not done a lot of progress
317 on it. I went to Tijuana to provide Solaris consulting to a northern phone
318 company called Telnor. At Telnor I saw a recent version of CDE (At the
319 university machines, we did not have either a recent version of Solaris,
320 nor the disk space required to run CDE) and it had a nice calendar application.
323 When I came back, I proposed to Federico to write a calendar application
324 in 10 days (because Federico would never show up on weekends to the ICN
325 at UNAM to work on GNOME ;-). The first day we looked at OpenWindows calendar,
326 that day we read all the relevant standard documents that were required
327 to implement the calendar, and started hacking. Ten days later we did meet
328 our deadline and we had implemented GnomeCal (Arturo would help us on the
329 last two days to implement the year view of the calendar). This calendar
330 application had a pretty nice internal architecture and looked pretty nice
331 compared to anything out there. The user interface was also pretty good
332 for those days early in the GNOME history, and it was definetly comparable
333 to the features in proprietary small calendar applications. Little did
334 we know about Outloook back then.<br>
336 At that time, it seemed like a good idea to implement the calendar server
337 support, but we did not have the time to do it. Now, the funny thing is
338 that nobody ever implemented the ugly spec that was available back then.
339 Even today, the CAP protocol is not wildely implemented, and there is now
340 an effort to create a "thin" version of CAP called CRISP.<br>
342 A few years later we would come back to hack on the calendar, this time it
343 would be integrated into the <a
344 href="http://www.helixcode.com/apps/evolution.php3">Evolution</a> groupware
345 suite and it would be part of the core business of <a href="http://www.helixcode.com">Helix
347 <h3><a name="gnumericcanvas"></a>Gnumeric and the Canvas</h3>
348 I was beginning to become very frustrated when developing applications.
349 I would kept pointing at Tk's beautiful Canvas widget as an example of a
350 genuinely fine piece of code that improved the life of programmers. We
351 were spending countless hours writing repaing handlers, writing event handlers,
352 and redoing the same code over and over again, and getting it buggy over
353 and over again. I convinced Federico to look into the Tk canvas. I felt
354 completely powerless, as I was still not very familiarized with many of
355 the X concepts and was overwhelmed by it. <br>
357 Federico took a few days to study the Tk canvas, and he took a few days to
358 explain this to me. He did a first implementaiton of the Tk canvas that
359 he got running in a couple of months (in time for the Usenix conference,
360 as I remember showing the code to Marc over breakfast, as he was growing
361 impatient about the state of development).<br>
363 The Linux Kongress in Germany happened that year, and Marius Volmer, a then-active
364 gnome hacker raised a number of problems with the canvas implementation:
365 it was not going to be very easy to wrap the canvas for scripting languages,
366 indeed it was going to be very hard to do it. When I came back to Mexico
367 from the Kongress, we discussed the changes required to the Canvas.<br>
369 The new Canvas design was a lot cleaner, and it was fully based on GtkObjects
370 and used GtkArgs instead of the home-grown system that I had suggested before
371 (which was, ahem, very broken). <br>
373 At this time, I started designing and implementing the Gnumeric spreadsheet.
374 Gnumeric would be the first application to implement its own canvas items,
375 and it would be the first application to stress test the canvas. Various
376 changes and improvements to the Canvas were done because of the requirements
377 that Gnumeric had.<br>
379 <h3><a name="fedlabs"></a>Federico joins the Red Hat Labs.</h3>
380 Federico took one year out from college, and moved to North Carolina to work
381 at Red Hat Labs on GNOME. His first task at Red Hat Labs was to improve
382 the GNOME Calendar (GnomeCal). He was supposed to work on groupware features
383 of the calendar, but pressing needs, deadlines and other tasks at Red Hat
384 prevented Federico from finishing this work (which was, btw, extremely complex,
385 given the assorted collection of broken standards. Even today it is a hard
386 task for a single programmer to take on if you want to be standards compliant).<br>
387 <h3><a name="qpl"></a>The QPL</h3>
388 Around November 1998, Troll Tech announced their plans (FIXME: was it november?)
389 to release the upcoming version of Qt (Qt 2.0) under a new license that
390 was going to comply to the Open Source definition. This announcement did
391 actually have two effects: it killed project Harmony (which was a free clone
392 of the Qt API) and weakened the reasons why people would support GNOME instead
393 of waiting for the new Qt library. <br>
394 <h3><a name="099freeze"></a>The 0.99 code freeze.</h3>
395 In November 1998 we started to freeze the code for the GNOME 1.0 release.
396 We broke the freeze a couple of times to accomodate the integration of
397 Raph Levien's work on the GNOME anti-aliased canvas. There were various
398 interest mixed here: in one hand Red Hat was in need of a desktop environment,
399 and in the other hand, various hackers had been working very long hours
400 to make this happen. It would take a lot of discussion to get the Anti-Aliased
401 canvas into the main GNOME distribution. This would delay the release just
403 <h2><a name="gnome10"></a>GNOME 1.0</h2>
404 GNOME 1.0 was released in March 1999. It was announced to the world during
407 the Linux World Expo in San Jose, California. This version marked the freeze
410 of the GNOME 1.0 API. This release contained several bugs. The first version
413 of GNOME to ship in a Linux distribution was a derivative of GNOME 1.0 that
416 included various improvements over the plain 1.0.<br>
418 GNOME had been difficult to build and keep up to date, which led to the little
419 testing in 1.0 and gave GNOME 1.0 a bad reputation due to its instability.
420 This release already included a very basic CORBA support in the Panel,
421 and a pretty good object activation system (not the best one, but definetly
422 passable. This would be replaced for GNOME 1.4 with OAF).<br>
424 We fixed as many bugs as possible that people were reporting, and we released
425 new packages constantly (it has always been a tradition to release packages
426 with bug fixes as soon as possible). Red Hat shipped version 5.0 of their
427 operating system with GNOME 1.0.xx, which contains a load of bug fixes but
428 was still very unstable. They also included in this release KDE. <br>
429 <h2><a name="octobergnome"></a>October GNOME (1.0.55)</h2>
430 This release was cordinated by Elliot Lee at Red Hat. The purpose of this
431 release was to fix all the reported bugs that people had been running
432 into. By this time the new <a
433 href="http://bugs.gnome.org">GNOME bug tracking system</a> had
434 been in use for some time, and this helped developers track down problems
435 and fix them for the release. This release of GNOME was pretty solid
436 and got distributed by various Linux vendors. <br>
438 Elliot's work towards making a robust distribution of GNOME paid of, and
441 this version was deployed wildly. October GNOME was released in October
444 1999. The release number 1.0.55 corresponded to the major version of the
447 core gnome packages and libraries. The version name and the actual number
450 obey to the fact that we were trying to avoid a version number competition
453 with the KDE project as it could have been perceived as version number inflation.
456 So 1.0.55 was the tag chosen, and the "October GNOME" keyword was used to
459 refer to this release.<br>
460 <h2><a name="earlyindustry"></a>The GNOME early industry</h2>
461 In October 1999, two GNOME-based companies were incorporated in the United
462 States: <a href="http://www.eazel.com">Eazel</a> and <a href="http://www.helixcode.com">Helix Code</a>.
463 Both companies have been working ever since in various infrastructural
464 parts of GNOME as well as working on various components of the GNOME desktop.
465 Eazel was founded by Andy Hertzfeld, Bart Decrem and Mike Boich. Helix
466 Code was founded by Nat Friedmand and me. You can read <a href="helix-history.html">the
467 history of Helix Code</a>.<br>
469 Eazel's main focus is the file manager and file-manager oriented services;
472 Helix Code ships a pre-packaged version of GNOME called Helix GNOME and
475 is focused on people oriented services within Evolution.<br>
477 Bertrand founded <a href="http://www.henzai.com">Henzai</a> in the second quarter of
478 2000. His company is focused on GNOME for PDA devices. <br>
480 Gnumatic was incorporated in the year 2000 to work on financial software.
483 Led by Linas Veptas, Gnumatic produces GnuCash, the personal finance software
487 <h2><a name="guadec"></a>GUADEC</h2>
488 Mathieu Lacage organized the GNOME Users And Developers European Conference
489 (<a href="http://www.guadec.enst.fr">GUADEC</a>) in Paris France on March 2000. GUADEC
490 was initially a small conference to be delivered to the students of <a href="http://www.enst.fr">France
491 Telecom</a> in Paris by Havoc, Federico and me. I discussed with Mathieu
492 the possibility of getting funding for making GUADEC a larger GNOME conference
493 that planned. When he agreed, I started to raise funds from various free
494 software companies in the US and Germany. Mathieu did the same with companies
495 and sponsors in France. In the end we managed to get enough money to fly
496 around fourty of the core GNOME developers to France for fours days. <br>
498 The GUADEC conference was a success: it helped the various GNOME developers
501 to get to know each other; The high bandwidth communication that was made
504 possible between developers, contributors, translators and documentation
507 contributors at the conference really pushed GNOME forward: a global vision
510 of the project could be explained to more people and many things got in
513 sync at this point.<br>
515 The two GNOME-based companies <a href="http://www.eazel.com">Eazel</a>
516 and <a href="http://www.helixcode.com">Helix
517 Code</a> were represented in the conference. We did miss Elliot Lee though,
518 he could not make it. <br>
520 This conference would be the foundation for the success of the Bongo GNOME
522 release later in the year. <br>
523 <a href="docs/Guadec-thank-letter.txt"><br>
524 This letter</a> was sent to the to various sponsors of GUADEC.<br>
525 <h2><a name="bongognome"></a>Bongo GNOME (1.2)</h2>
526 The GNOME 1.2 was mostly a user interface polishing, update and improvement
530 In Jannuary 2000 <a href="http://primates.helixcode.com/~jacob">Jacob
531 Berkman</a> started to include
532 into gnome-core a number of user interface improvements that had been suggested
533 by the <a href="http://developer.gnome.org/ui-hitsquad">GNOME UI</a> team and from various ideas that
534 he, George and various other hackers contributed to the system. This release
535 would also include memprof (mem buddy) for the first time and will feature
536 applications built using the Glade GUI designer (and of course included
537 Glade and Libglade for this purpose). <br>
539 Bongo GNOME was released in May 2000 after a one month delay. This release
542 was originally supposed to be called "April GNOME". Delays in the release
545 pushed the name to "May GNOME", but people felt that in a few years we would
548 run out of months and it would be hard to tell which version came before
551 which version. Hence we decided to tag the release name Bongo GNOME and
554 all packages adopted the 1.2 convention for version numbers.<br>
556 This release of GNOME is still fully binary compatible with GNOME 1.0 as
559 shipped they year before: every application written against the GNOME 1.0
562 API would run unmodified in GNOME 1.2. The Foobar menu also appeared on
565 this release, and the input from the User Interface team could be seen all
568 around the desktop.<br>
570 Helix Code provided pre-build tested packages for GNOME 1.2 for seven Linux-based
573 distributions on Intel and PowerPC as well as a Solaris port. This was known
576 as the Helix GNOME distribution.<br>
577 <h2><a name="foundation"></a>The GNOME Foundation</h2>
578 The GNOME foundation was announced in August 2000 at the Linux World Expo
581 in San Jose California. FIXME, URL to the announcement.<br>
583 There was an extensive coverage on the news.<br>
585 Various companies joined together to continue the development of the GNOME
588 user environment and GNOME-based technologies. After the foundation was
591 announced, a number of initiatives from the founding members was announced:<br>
593 <li>Sun Microsystems adopts GNOME technologies for their user environment
595 in the Solaris OS.</li>
596 <li>Hewlett-Packard adopts GNOME for their user environment in the HP-UX
598 operating system.</li>
599 <li>Sun will port their recently OpenSourced StarOffice suite to the Gtk+
601 toolkit and will integrate with the GNOME <a href="software.html#bonobo">Bonobo component
603 architecture</a>.</li>
604 <li>IBM contributed the SashXB rapid development environment to GNOME.</li>
605 <li>GNOME would adopt and integrate Mozilla as part of its desktop strategy.</li>
606 <li>The GNOME project would adopt OpenOffice technologies.</li>
609 These announcements were just part of a bigger picture: Eazel's file manager
612 to appear in GNOME 1.4; Helix Code's Evolution groupware suite to appear
615 in GNOME 1.4. Together with the support of Gnumatic, VA-Linux and TurboLinux.<br>
617 Sun's commitment to GNOME is very widespread at this point: their teams are
620 working around various technologies in GNOME. Nautilus and Evolution were
623 demoed at Linux World Expo embedding StarOffice components. <br>
625 <h2><a name="accesslab"></a>Sun creates the GNOME Accesability Lab</h2>
627 In September 2000, Sun announced the creation of an accesability lab
628 that would help improve GNOME to be used by people with
631 <h2><a name="gnome14"></a>GNOME 1.4</h2>
633 The GNOME 1.4 release engineers are <a
634 href="http://primates.helixcode.com/~jacob">Jacob</a> and <a
635 href="http://www.advogato.org/person/mjs">Maciej</a>. This release
636 will include for the first time the Bonobo component system as
637 part of GNOME and will contain the new file manager <a
638 href="http://nautilus.eazel.com">Nautilus</a> and the <a
639 href="http://www.helixcode.com/apps/evolution.php3">Evolution</a>
projects / edu / osp-wiki.git / blob