Manoj Iyer writes, The Linux Test Project test suite LTP-20020507.tgz has been released.
Visit
our website ( http://ltp.sourceforge.net )to download the latest version of the
test suite, and, for information on test results on pre release, release
candidate and stable releases of the kernel. There is also a list of test cases
that are expected to fail, please find the list at
http://ltp.sourceforge.net/expected-errors.php

The highlights of this release are:
– The IBM LTC Test team, part of the Linux Test Project, has published a
paper (PDF format) titled “Linux Technology Center Testing” summarizing
the results from enterprise testing recently completed.
http://ltp.sourceforge.net/LTCtestv1.0.pdf
– New LTP tests added, bug fixes for S390 and cleanups to remove compile
time warnings.
– LTP Automation script updates.
– LTP test suite ltp-20020507.tgz is also available at the OSDL’s Linux Kernel
Scalable Test Platform.(STP). Visit http://www.osdlab.org/stp for more
information.

We encourage the community to post results, patches or new tests on our mailing
list and use the CVS bug tracking facility to report problems that you might
encounter with the test suite. More details available at our web-site.

ICC-Rocks writes, “In light of the imminent release of the first ‘stable’ version of GCC, version 3.1, OSNews features an interview with Mark Mitchel, GCC’s Release Engineer. They are talking about GCC 3.x, the future and the competition.”

Anonymous Reader writes, “Codingstyle.com has posted a Playstation 2 Linux Kit Roundup, containing links to programming documentation, tutorials, and development tools. This is timely information, with the public release of the PS2 kit late last month in Japan, as well as the planned release on May 22 in North America as well.”

GeekPAC writes:
Tuesday, May 7th, 2002, from the home of Wayne’s World, Aurora IL., tonight LIVE on
www.thelinuxshow.com, at 6pm pt, 7pm mt, 8pm ct, and 9pm et…. Kevin Hill, Jeff Gerhardt, Doc
Searls (Linux Journal), Arne Flones and Russ Pavlicek; have another strange and wonderful show lined up tonight on The Linux Show!!

In Segment One – Hot News: We will be covering the hot Linux news of
the last few weeks. In particular we will discuss the hot story from over the weekend of Microsoft getting THRASHED by Peruvian congressman Dr Edgar David Villanueva Nuñez, as well as some very HOT news from the American Open Technology Consortium. As a follow-up to last week we will discuss some major back tracking on MS license claims from a story from a week ago.

In Segment Two – Winning Minds One At A Time
We are joined tonight by writer Christina Dyrness. Christina is the first of a series of writers and pundits from the main stream technology press that we are inviting on TLS. We are doing this for the dual purposes of trying to get a better picture of main stream perceptions of the Open Source community, as well as trying to win over those opinions.

We are pleased to have Christine as our first guest in this effort. The motivation for inviting her was an article at the nando times. This article was posted on their web site April 10th, 2002; and is unfortunately no longer available. We have asked to have permission to reprint the article on our site for showtime.

In the article she asserted that “Here’s the riddle: If Linux is gaining more market share among big-spending corporate customers, why have sales at Red Hat — the undisputed Linux leader — been creeping steadily downward?

This kind of perception is common in the main stream technology press, so we felt that we should have her on as a guest to give her a better picture of what is really going on in the Linux and Open Source universe. The facts are, almost everything in her article was factually correct. What we need to address is perceptions of the facts.

Christina Dyrness has been writing about software and high-tech companies – including Red Hat, SAS Institute and IBM – at The News & Observer in Raleigh, NC since December 1998. Prior to that she covered venture capital and start-ups for the Washington Post-owned TechCapital Magazine and wrote about high-tech businesses for news outlets in Southern Florida. She grew up in Alaska, went to college at the University of California in Santa Cruz, and journalism school at UC Berkeley.

Please join us on the show, and check our IRC
Chat(irc.thelinuxshow.com
#linuxshow).
Remember tune in at 6pm pt, 7pm mt, 8pm ct, and 9pm et. NOTE: we are now on
Daylight Saving Time in the US.
Catch the Linux show at
www.thelinuxshow.com

We have just released the Call for Papers for the Linux.conf.au 2003
Conference (http://conf.linux.org.au/). I was wondering if you could add this to the Slashdot submission queue so that it gets good exposure? I have attached a copy of the CFP, but if you think it is too long for
a slashdot article, you can link to the copy on our web site: http://conf.linux.org.au/cfp.html.

Thanks,

James Henstridge.
(on behalf of the LCA 2003 Call for Papers committee)

Matt Barnes writes: “Hello All
I am pleased to announce the formation of a Brand New Linux Users Group (LUG) in High Springs Florida (yes its in the boonies) and would like to welcome any and all of you who are interested in sharing your linux experience to contact me for more information and a schedule of upcoming events. If you are a newcomer to Linux and would like to check things out before you take the plunge, we welcome you as well. Anyone is welcome regardless of experience, so dont be afraid to throw your two cents in and get involved we are looking forward to a long and successful linux experience. Any other LUG’s wanting to collaborate, share resources, or offer advice? Your input is gladly accepted and highly valued. Our current goal is to finish the Outdoor Linux Project before it gets too hot and also to Start work on the Underwater Linux Project coming up this summer. If you would like further details please feel free to contact me at: MattsBTCnet@netscape.net for a detailed introduction and ways you can participate.

We invite you to check our webpage for updates

http://floridalinux.kicks-ass.net.”

Sander Vesik writes: “The first build of OpenOffice.org for MacOSX is now available for download as both source and binaries. For the full text of announcement, see below.”
DEVELOPER RELEASE OF THE OPENOFFICE.ORG OFFICE SUITE FOR MAC OS X NOW AVAILABLE

Community Development Reaches Milestone of the Mac OS X Port of
OpenOffice.org Office Suite

May 7, 2002 – The Openoffice.org community (http://www.openoffice.org)
today announced the availability of the first milestone build of the Mac
OS X port of the OpenOffice productivity suite. This build uses the X11
Windowing System from XFree86.org to run on either Mac OS X or Darwin,
and is available today for developers interested in helping finish the
port.

“I have been astonished at the speed and quality of the work the
community has done. We have been working together in a tight, efficient
ensemble, and have now something we can use,” said Ed Peterlin,
Community developer, OpenOffice.org. “This is exciting for me as a Mac
user — it’s been incredibly fun to get this far — and know that we
will be able to finish this with just a little more help.”

“Apple encourages Open Source development, and supports the open source
community through the Darwin Project,” said Ron Okamoto, Apple’s vice
president of Worldwide Developer Relations. “Apple is delighted that a
Mac OS X port of the major open source office suite, OpenOffice.org
1.0, has progressed so far so quickly.”

Earlier this month, the OpenOffice.org community announced
OpenOffice.org 1.0, the open source office suite, developed over a
period of 18 months through the global, collaborative effort of many
thousands of volunteers. The OpenOffice.org 1.0 office suite features
key desktop applications, ­ including word processor, spreadsheet,
presentation, and drawing programs ­ in more than 25 languages.

The code for the Mac OS X port of OpenOffice.org has been in development by the community since April 2001, when the code base was released by Sun Microsystems, Inc. The current release, a pre-alpha release is targeted to developers familiar with developing for the Mac OS X platform.

“The developer release of OpenOffice for Mac OS X is a great
demonstration of the power of Open Source software and its ability to
support multiple platforms.” said Zaheda Bhorat, Community Manager,
OpenOffice.org, Sun Microsystems Inc. “Combining the enthusiasm and
expertise of the OpenOffice.org community and the UNIX-based, open
standards nature of Mac OS X – such as its support for popular Open
Source software like X11 and gcc – enabled us to add exciting new
platforms like Mac OS X to our large and growing list of platforms.”

The OpenOffice.org 1.0 software runs stably and natively on multiple
platforms, including Linux, PPC Linux, Solaris, Windows and other
flavors of Unix. The Mac OS X developer release uses a ZeroG installer. The OpenOffice.org community wishes to thank ZeroG in this key contribution to delivering this port.

The Max OS X build is currently available as an alpha release in English
only, although the OpenOffice.org 1.0 is currently available in more
than 25 languages. It is only a matter of time, once this port is
completed, that the OpenOffice.org community will implement the
localizations.
Developers interested in contributing to making this exciting port a
part of the standard OpenOffice.org suite offering can find the tools
and resources on the OpenOffice.org site. The next step, now that the
port has advanced to this stage, is to create a beta release using the
Aqua interface for end users to help finalize. And the OpenOffice.org
community is willing to make it happen.

About OpenOffice.org

OpenOffice.org is the home of the open source project and its community of developers, users and marketers responsible for the on-going development of the OpenOffice.org 1.0 product. The mission of OpenOffice.org is to create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format. Additional ports, such as FreeBSD, IRIX and Mac OS X are in various stages of completion by developers and end-users in the OpenOffice.org community. OpenOffice.org 1.0 is written in C++ and has documented API’s licensed under the GNU Lesser General Public License (LGPL) and Sun Industry Standards Source License (SISSL) open source licenses.

OpenOffice.org is the largest open source project with over 7.5 million lines of code. To date, more than 4.5 million downloads of earlier versions of OpenOffice.org 1.0 have taken place. With the release of the 1.0 version, the OpenOffice.org community expects that number to grow significantly as businesses and individuals around the world explore the free alternative to proprietary office suites.
Copyright The OpenOffice.org community (www.openoffice.org)

– By Jeff Field –

The Dragon brand of motherboards from Soyo has become synonymous with a large feature set. The company’s newer Pentium 4 Dragon boards, on the surface, seem to live up to that name, but looks can be deceiving. How do these boards hold up, and which one should you buy?
Soyo released two Dragon Pentium 4 boards recently. Customers might be confused about which board to buy, because they are similar. I hope to alleviate that confusion and help you decide which board to purchase, if either.

The boards and expansion
The two boards in question are the P4I Fire Dragon and the P4S Dragon Ultra. The Dragon in the name of both boards is (almost) an acronym that explains their features — DDR SDRAM, RAID, Audio, AGP Pro Slot, Overclocking and Networking. The “Fire” in the Fire Dragon’s name comes from the on-board IEEE1394 (“Firewire”) controller/ports, while the “Ultra” in the Dragon Ultra represents the USB 2.0 available with the board.

Each board uses a different chipset. The P4I (Fire Dragon) uses an Intel i845 chipset, while the P4S (Dragon Ultra) uses the SiS 645. Both support similar features, so the most interesting differences are in other features — particularly in expansion methods.

The Fire Dragon comes with two DDR SDRAM DIMM slots, six 32-bit PCI slots, one 4X AGP Pro slot, four USB ports (two rear, and two on the included Sigma-box, which occupies a 5.25″ drive bay), two IEEE1394 Firewire ports (one rear, one on the Sigma box), two nine-pin serial ports and one 25-pin parallel port.

Also located on the ATX I/O panel are the analog audio connectors and the RJ45 connector for the on-board 10/100 Ethernet. Four IDE connectors are present, two of which connect to the HPT IDE/RAID controller on-board, and the two PCI bus-mastering IDE ports, which function through the i845 chipset. All of the on-board ports support up to ATA-133 transfer rates. Also included is a daughterboard for digital audio.

The Dragon Ultra comes with three DDR SDRAM DIMM slots, six 32-bit PCI slots, one 4X AGP Pro slot, six USB 1.1 ports (two rear, four front), two nine-pin serial ports, one 25-pin parallel port, analog audio outputs, and an RJ45 network connector. There are, once again, four IDE hard drive connectors, two of which are bus-mastering and controlled by the chipset and two of which are attached to an HPT IDE/RAID controller. The USB 2.0 controller touted on the box is not actually present, but you receive a postcard inside the box to mail out to receive the card, which is very strange.

Board layout and design
At first glance the layouts to these two boards seem very similar, but there are some subtle and important differences between the two. First, the positioning of the hard drive connectors on the Fire Dragon differs from that of the Dragon Ultra in that the hard drive connectors are perpendicular to the PCI and AGP slots, with more space between them and the DIMM slots than on the Ultra. This makes it easier to fit a longer-length AGP card in the AGP slot, an important feature as newer cards get longer. On the Dragon Ultra, the positioning of the IDE ports and DIMM sockets may prove to be a problem when dealing with larger video boards.

The next concern is the power connectors. The Fire Dragon uses all three of the connections present in Pentium 4-compliant power supplies. The main ATX power connector is on the bottom of the board, as opposed to the top with the Dragon Ultra. I prefer the design of the Fire Dragon, because having it on the bottom of the board means I do not have to stretch the larger ATX cable over top of the CPU fan, potentially blocking airflow.

As for the aesthetics of the design, the Fire Dragon sports a patriotic design with a red PCB, blue PCI slots and white IDE connectors, while the Dragon Ultra uses the trademark color scheme of the Dragon line — purple PCI slots, yellow and blue IDE connectors and a black PCB.

On-board features and Linux compatibility
Included on-board with both of these motherboards are networking, IDE/RAID, and six-channel PCI/digital audio. The question is, how well do these work, and do they work with Linux?

In both instances, the networking was configured and installed under Debian Linux by compiling and loading the correct drivers. Once this happened, the networking was fully functional. The audio is supported by both the kernel audio drivers (CMIPCI driver) and ALSA (cmpci driver). Included with the boards is a daughterboard that allows for digital audio output. All features of the audio on both boards worked perfectly.

The IDE/RAID can function as either a pair of normal IDE controllers, or a RAID controller with Raid 0,1 and 5. The HPT controllers on both boards are the same and were supported by the kernel. I found no problems.

Also surprisingly simple for me was configuring the Firewire on the P4I Fire Dragon. Though no FireWire devices were tested, the controller itself was picked up by the kernel FireWire modules automatically, and seemed to be functional.

Installation and ease of use
In both cases, the boards come with my favorite feature of the Dragon line — large, detailed print manuals with well-written instructions on installing and operating the board. I love this feature because it is very helpful, when telling someone which motherboard they should buy, to know you are recommending a board with quality documentation. The manuals for both boards cover the topics you would hope, guiding the user through most of the steps of the board installation perfectly.

The boards themselves are well labeled, and a person with moderate PC assembly experience would probably have no problem installing these boards.

Performance

System Configuration
CPU	Pentium IV 2.4Ghz
RAM	256MB Crucial PC2100
Hard Drive	WD102BA 7200 RPM
Video	Leadtek GeForce 3
Network	3Com 3C905c 10/100 NIC
CD-ROM	Memorex 48X CD-ROM

The following performance results are in seconds. “Kernel” is kernel compile times of a “default” Linux 2.4.17 configuration done via “make clean; time make -j3 bzImage“.

LAME and OggEnc are MP3 encoding benchmarks that measure the speed at which a CPU encodes PCM audio into an MP3. For LAME, version 3.92 was used with the command line “lame –alt-preset standard test.wav test.mp3” and OggEnc version 9 was used with the default setting (VBR quality 3) and the same test file via the command “oggenc test.wav.” The test file was Smashing Pumpkins’ “Tales of a Scorched Earth.” This test gives an idea of the overall CPU performance of a system.

The last test, POVBench, is a 3D rendering test using the popular POV-ray program. The command line is “povray -i skyvase.pov +v1 -d +ft -x +a0.300 +r3 -q9 -w640 -h480 -mv2.0 +b1000.” POVBench focuses on the floating-point power of a system’s processor. More information on POVBench, as well as a database of results, is available at this site.

System Performance Time in Seconds, Lower Scores are Better.
OEM	Board	CPU	Kernel	LAME	OggEnc	POVBench
Soyo	P4S	P4 2.4	159	55	28.4	20
Soyo	P4I	P4 2.4	165	54	27.9	20

Here we see performance is very close in these tests. The P4I (Fire Dragon) was consistently slightly slower — about 6 seconds — than the P4S at the kernel compile test, otherwise the results are similar.

Quake 3
Quake 3 benchmarking measures the 3D performance of a system, however, 3D performance is determined mostly by the video board in newer systems, because they are the bottleneck and not the processors. Quake3 timedemos are done with Quake 1.30 and the four.dm_66 demo. Quake3 was launched from the console via the “xinit -e quake3” command in order to be sure Quake3 was the only program using the X server. The NVidia 1.0-2880 drivers were used.

Quake 3 Timedemo Performance Frames Per Second, Higher Numbes are Better
OEM	Board	CPU	640D	800D	1024D	1280D	1600D	640H	800H	1024H	1280H	1600H
Soyo	P4S	P4 2.4	260	238	171.4	105.5	108.9	246	209	141.9	88.4	87.2
Soyo	P4I	P4 2.4	259	232	172.9	106.1	109.2	248	208	142	88.7	86.6

Here we see exactly what I expected — similar results, because the CPU did not change and the benchmark is mostly CPU limited.

Conclusion
While either of these boards will serve the needs of 90% or more of the readers we have, the P4I Fire Dragon comes out on top for several reasons. Performance is similar in both, but where the P4I wins is with features and the chipset. While stability was not an issue during all of my testing, my personal experience says when possible, use an Intel chipset. Chipsets from VIA and other manufacturers tend to have glitches and problems, and if Intel is an option, they really do make excellent, well-supported chipsets.

Also, the P4I Fire Dragon supports FireWire out of the box, and the FireWire on the board is Linux supported. The only place where the P4S trails the P4I is in price, where the slightly older P4S Dragon Ultra is about $50 to $60 cheaper than the P4I Fire Dragon. Both boards may be found on Pricewatch.

This is the GNOME Summary for 2002-04-23 – 2002-04-28.

==============================================================
Table of Contents
--------------------------------------------------------------

1. What to maintain a core part of GNOME2?
2. Worlds coolest archiver hits 1.0
3. New release of Overflow
4. Bynari Announces InsightConnector for Evolution
5. Info Anarchy article on Evolution
6. Multi-head support merged into GTK+ main tree
7. Been missing the Nautilus mailing list lately?
8. Hunter awaken
9. GNOME 2 release schedule updated
10. Translated GNOME summaries
11. Hacker Activity
12. Gnome Bug Hunting Activity
13. New and Updated Software

==============================================================
1. What to maintain a core part of GNOME2?
--------------------------------------------------------------

There are some modules that are part of GNOME but which currently is not
getting as much attention as they should. So if you have ambitions of
being one of the cool people, who can claim to be a maintainer of a core
part of GNOME, this is your chance to step up and join the ranks. I will
here tell you which modules are available and how you go about adopting
one of these modules First of all raising your hand and saying 'I
volunteer' will not get you a maintainership, remember that these are
modules that are part of the core and GNOME and as such are important to
the overall success of the project. So to become the maintainer you will
have to prove yourself first by submitting some patches to it for
reviewal by some of the existing core GNOME hackers. I will 
outline who on a per module basis. 

The first module that needs a new maintainer is libgtop. Libgtop is the
library that allows applications such as the GNOME System Monitor to get
the needed information from the system. Important tasks for someone
wishing to take on this module is getting pending patches merged and to
make it support a wider range of operating systems. People interested in
taking on this module should contact Kevin Vandersloot at
kfv101(at)psu.edu. Kevin can provide you with some starts to get you
started. 

The second module that needs a new maintainer is the gconf-editor
module. The Gconf-editor is a GUI tool which will be the main tool for
most users wishing to tweak their system settings in GNOME2 beyond what
the GNOME setup tools let them. Gconf-edit is currently being maintained
by Anders Carlsson, but Anders is also hacking away at Nautilus and
other important parts of GNOME and could need someone to take over the
burden. Take a look at the gconf-editor bugzilla or mail Anders to get
some tasks to get you started. Anders mail address is 
andersca(at)gnu.org 

The third module that needs a new maintainer is gnome-vfs. GNOME-vfs is
the module among those listed here that sees the most development at the
moment, but it is more like people from other parts of the GNOME project
adding things to it as they need it, not like a maintainer devoting him
or herself fully to making this module all that it can be. People
interesting in taking on this module should check out gnome bugzilla for
some tasks and mail patches for them to the gnome-vfs mailing list which
you find at 

        http://lists.ximian.com/mailman/listinfo/gnome-vfs

The last major module I will mention is gtkhtml2, which is one of the
html rendering libraries we are using in GNOME 2. As you might know we
have 3 html widgets in GNOME 2, gtkhtml1 which is the module used in
Evolution and which has html editing capabilities. 
Then we have the gtkmozembed widget which is the widget that lets you
embed mozilla in your apps like Galeon does. Lastly we have gtkhtml2
which is currently used by yelp and nautilus. The point of gtkhtml2 is
to fill the gap between the simple and fast gtkhtml1 widget and the full
featured but also bigger gtkmozembed widget. Gtkhtml2 was developed
originally by some of the coders at Code Factory like Anders Carlsson,
but they don't have time at the moment to continue its development. What
we need is for a someone to step up and complete its current featureset
and optimize it. Since it will be used by the help browser it needs to
be lightning fast so that when people press the help button help appears
'instantly'. For information on getting started on gtkhtml2, check out
gtkhtml2 bugzilla and/or mail Anders Carlsson at andersca(at)gnu.org 


==============================================================
2. Worlds coolest archiver hits 1.0
--------------------------------------------------------------

File Roller, everyones favourite archiving tool, has reached 1.0. Paolo 
Bacchilega announced the release this week, so if you haven't downloaded
it already remember to do so now. The 1.0 release is for GNOME 1.x but
there is also a very nice GNOME 2 version available from the File Roller
website. 
        
http://mail.gnome.org/archives/gnome-announce-list/2002-May/msg00021.html
http://fileroller.sourceforge.net

==============================================================
3. New release of Overflow
--------------------------------------------------------------

Jean-Marc Valin released version 0.6.1 of Overflow upon the world this
week. Overflow is a really nice and interesting data flow oriented
develop environment which lets you build applications visually by
connecting simple building blocks. This tool is used for a lot of cool
things like for instance voice recognition software. 

        http://freespeech.sourceforge.net/overflow.html
http://freespeech.sourceforge.net/images/overflow3.jpg

==============================================================
4. Bynari Announces InsightConnector for Evolution
--------------------------------------------------------------

Bynari announced this week their InsightConnector for Evolution which
lets Evolution communicate with their Messaging and Collaboration
server. So if you want to replace Outlook with Evolution and Exchange
with InsightServer 3.5 all running on GNU/Linux now is your chance.
Press release linked below. 

        http://linuxpr.com/releases/4742.html

==============================================================
5. Info Anarchy article on Evolution
--------------------------------------------------------------

There is a nice article on Evolution on Info Anarchy. The author is a
little misguided in his desktop choice in general  [:)] , but he has
understood what the best mail client around is. Check out the link and
maybe you learn something new about your favourite mail client. 

        http://www.infoanarchy.org/story/2002/5/1/64850/34022

==============================================================
6. Multi-head support merged into GTK+ main tree
--------------------------------------------------------------

The GTK+ hackers is not resting on their laurels now that GTK+ 2.0 is
out. Owen Taylor of Red Hat, merged the multi-head tree that Erwann
Chenede of Sun have been working on for some time. This means that we
will have first class multi-head support built into GTK+ with the
upcomming GTK+ 2.1 release. 


==============================================================
7. Been missing the Nautilus mailing list lately?
--------------------------------------------------------------

If you are still reading the archives on nautilus.eazel.com you will
probably have noticed that there has been no new messages on the
mailing-list for a while. That is because the mailing list has now moved
to gnome.org. So for your archive reading and keep track of the great
progress being done by people such as Dave Bordoley, David Emory Watson
and of course Darin and Alex, check out the link below. 

        http://mail.gnome.org/mailman/listinfo/nautilus-list

==============================================================
8. Hunter awaken
--------------------------------------------------------------

The GNOME bug-squashing team have good results and have managed to get
GNOME bugzilla under control. Since the effort began we have for
instance managed to get the number of Nautilus bugs down from just above
1200 to just above 1000 now. There is still many more bugs that can be
resolved and we still need more volunteers to help us with this.
Everyone using GNOME can help with this and helping out triaging bugs is
actually a very important part of making sure GNOME 2 runs well. So
please come onto IRC and drop into #bugs on irc.gnome.org 
or join our mailing-list to join the effort to make GNOME 2 bug free.
Also remember that we still do bug days in #bugs each thursday. 

        http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

==============================================================
9. GNOME 2 release schedule updated
--------------------------------------------------------------

Gregory Leblanc one of the members of our prominent release team sent
out a mail this week giving us a updated GNOME 2 release schedule.
According to this updated schedule the beauty that is GNOME 2 will now
premiere late June. So that means that this truly will be the summer of
love  [:)] http://mail.gnome.org/archives/gnome-hackers/2002-May/msg00012.html

==============================================================
10. Translated GNOME summaries
--------------------------------------------------------------

In the quest to make the world happy we now have French, Spanish,
Hungarian and Korean - all the links below. 

        http://www.gynov.org/news/index.php4
http://es.gnome.org/actualidad/
http://cactus.rulez.org/projects/gnome/summary/
http://developer.gnome.or.kr/news/

==============================================================
11. Hacker Activity
--------------------------------------------------------------

Thanks for Paul Warren for these lists.

Most active modules:
 59 evolution
 50 gnumeric
 49 gtk+
 42 gnome-utils
 35 gimp
 33 galeon
 31 pan
 29 gtkmm-root
 27 libgda
 26 gnome-pim
 26 gnome-panel
 25 gnome-control-center
 25 monkey-sound
 24 profterm
 24 printman
 23 garnome
 23 libegg
 22 gnome-games
 22 anjuta
 22 gok
[129 active modules omitted]

Most active hackers:
 63 kmaraas
 48 pablo
 43 gman
 36 minmax
 35 hp
 35 dnloreto
 31 jberkman
 29 rodrigo
 29 andersca
 28 srittau
 26 hadess
 26 murrayc
 25 jamesh
 24 jody
 24 jdub
 23 orph
 23 baddog
 23 dtb
 22 jbaayen
 21 fejj
[135 active hackers omitted]


==============================================================
12. Gnome Bug Hunting Activity
--------------------------------------------------------------

This information is from http://bugzilla.gnome.org, which hosts bug and
feature reports for most of the Gnome modules. If you would like to join
the bug hunt, subscribe to the gnome-bugsquad mailing list.

Currently open: 6917 (In the last week: New: 770, Resolved: 817,
Difference: 
-47)

Modules with the most open bugs (excluding enhancement requests): 

  nautilus: 1013 (In the last week: New: 39, Resolved: 49, Difference:
-10)
  gtk+: 498 (In the last week: New: 42, Resolved: 37, Difference: +5)
  gnome-core: 273 (In the last week: New: 67, Resolved: 61, Difference:
+6)
  gnome-vfs: 258 (In the last week: New: 6, Resolved: 5, Difference: +1)
  galeon: 229 (In the last week: New: 112, Resolved: 81, Difference:
+31)
  control-center: 221 (In the last week: New: 38, Resolved: 25,
Difference: +13)
  GIMP: 188 (In the last week: New: 9, Resolved: 13, Difference: -4)
  gnome-applets: 184 (In the last week: New: 23, Resolved: 103,
Difference: -80)
  sawfish: 160 (In the last week: New: 10, Resolved: 4, Difference: +6)
  gnome-panel: 142 (In the last week: New: 88, Resolved: 61, Difference:
+27)
  medusa: 126 (In the last week: New: 0, Resolved: 0, Difference: 0)
  balsa: 122 (In the last week: New: 22, Resolved: 11, Difference: +11)
  gnome-pilot: 108 (In the last week: New: 6, Resolved: 1, Difference:
+5)
  gnome-utils: 96 (In the last week: New: 12, Resolved: 25, Difference:
-13)
  glib: 81 (In the last week: New: 9, Resolved: 3, Difference: +6)
  
Gnome Bugzilla users who resolved or closed the most bugs: 
  
  kmaraas@gnome.org: 128 bugs closed.
  heath@pointedstick.net: 95 bugs closed.
  yaneti@declera.com: 80 bugs closed.
  Uraeus@linuxrising.org: 64 bugs closed.
  lrclause@uiuc.edu: 37 bugs closed.
  shane.oconnor@ireland.sun.com: 35 bugs closed.
  louie@ximian.com: 27 bugs closed.
  hp@redhat.com: 26 bugs closed.
  glynn.foster@sun.com: 25 bugs closed.
  kfv101@psu.edu: 18 bugs closed.
  otaylor@redhat.com: 15 bugs closed.
  bordoley@msu.edu: 15 bugs closed.
  jody@gnome.org: 14 bugs closed.
  jfleck@inkstain.net: 14 bugs closed.
  charles@rebelbase.com: 14 bugs closed.
  
==============================================================
13. New and Updated Software
--------------------------------------------------------------

power-applet  - APM/ACPI battery applet
Enlightened Sound Daemon  - sound server
Yelp  - Help browser for GNOME 2.0
bond  - rapid application development tool.
oggdoctor  - ogg tag editor
Gneuro  - An euro converter applet
GtkDigital  - A GTK calculator display
gtktalog  - Disk catalog tool
Glade-Perl  - Glade Perl source code generator
File Roller  - Archive manager.
Web Administrators  - Web Hackers
GCronTime2  - planner
gtkmm2  - GTK+ C++ binding
gnomemm  - C++ bindings for GNOME
Metacity  - Integrated window manager
GNOME Terminal  - terminal console app
Overflow  - Graphical design tool.
gael  - Electronic Design Automation
Armada Backlight Controller  - Compaq Armada backlight controller
XdeFactor  - Manage your company
gIcon, the Nikon F90x Camera Manager  - Management Software for the
Nikon F90X
libelysium  - Set of utility functions
GMime  - Editing, and parsing MIME
gedit  - Lightweight text editor
Greenwich  - Whois client for GNOME
devhelp  - API docs browser
GChemPaint  - 2D chemical structures editor

For more information on these packages visit the GNOME Software map: 
http://www.gnome.org/softwaremap/latest.php

Another week of frantic GNOME 2 hacking, lots of polish getting adding
and bugs getting fixed. Seems like our accessibility support puts extra
pressure on the developers to make sure the interfaces are perfect. If
for instance the keyboard focus don't get moved around correctly in an
application we risk that blind users will not be able to use GNOME 2 for
instance. Of course having properly working focusing in all parts of the
GNOME desktop is an advantage for all users, since it maked keyboard
navigation work flawlessly for instance. See you again in a week for
more news and rave reviews from the world of GNOME.
 
Christian Fredrik Kalager Schaller 
gnome-summary@gnome.org 

The Honeypot Project encourages all sysadmins to stop throwing away malicious code. Don’t just scramble to get it out of there so quickly that you don’t take time to rip it apart and find out what makes it tick. To that end, the project is issuing a challenge. Read more at Wired.com.