Every Git working directory is a full-fledged repository with complete history and full revision tracking capabilities, not dependent on network access or a central server.

– Wikipedia

Did you know that agafgfafa @ yahoo dot com is also yours truly?  Neither does Eclipse.org.

When you set up your workstation, the identity you give yourself is only as valid as you make it. Since anyone can commit to a git repository, including you@localhost, Denis@home and agafgfafa @ yahoo dot com, the commit log of any given repository is only valid if you can recognize the identity of the committers.

The problem arises when you push your commits to a ‘central’ git repository, such as what I’m setting up at Eclipse.  Since git doesn’t natively keep track of a push, the git commit log comes in to Eclipse servers unchallenged.

I’m sure you, nor the Eclipse IP team, would appreciate a commit log that looks like this:

commit 89aac775141bda1387429928d3601290f9959bf5
Author:     Denis <denis@localhost>
AuthorDate: Mon Feb 1 13:58:30 2010 -0500
Commit:     Denis <denis@localhost>
CommitDate: Mon Feb 1 13:58:30 2010 -0500

commit 3de863bdd0e5f579ff47438ed725184a6869f58e
Author:     Billy Bob <razorh4x0r@dsl163-1111.ny.nc.rr.com>
AuthorDate: Wed Jan 27 15:51:10 2010 -0500
Commit:     Big Daddy Denis <denis@fondation.eclipse.org>
CommitDate: Wed Jan 27 15:51:10 2010 -0500

commit 3027d0d773461d8cf2c96c4f13d754203629f00d
Author:     Denis <theman@homebox>
AuthorDate: Wed Jan 27 15:31:51 2010 -0500
Commit:     Denis Roy <denis@eclpise.org>

I’ve hacked an update hook (based on Shawn’s clues) that will examine an incoming push and fail if it does not recognize all the committers, but it bears stating: committers will need to set this right before committing their code locally. Otherwise, the push will fail.

In the end, I’m sure it will all work out.  It will just take a bit of getting used to.

Participating in Babel, the crowd-sourced translations effort for Eclipse projects, just got easier: you will soon be able to point it to your update site or p2 repository, and Babel will figure out the rest for you.

Currently, Babel only supports parsing map files, then importing your English strings from your code repository. But since map files are not used by all projects, specifying your update/p2 site will make Babel easier to use.

For more info, see the mailing list post from our fearless leader, Kit Lo.

I have spent almost 3 and a half great years at the Foundation working for Denis and with the rest of the wonderful team there.  But the time has come to make a change in my career path and I have tendered my resignation, effective at the end of the month.  Eclipse has been a great place to work and a this is a great community to be a part of.  You have all made me welcome and I have met a lot of wonderful people through my role as one of the webmasters and as a participant in the community.  It has been wonderful working with all of you and a real pleasure to have been able to meet some of you in person at EclipseCon, the Portland DemoCamps, and other Eclipse related events.  I hope that we’ll be able to grow some of those relationships in the future.  I wish all the best to Denis and team at the Foundation.

Looks like Holger Voormann won my Bug 300K contest.  Holger, I will coordinate with Lynn and get some Eclipse swag to you ASAP.  Congrats!

I guess that means the next bug number of interest will be bug 314159.  That could just take a few months at this rate!

We’re closing in on Bug 300,000!

mysql> select max(bug_id) from bugs.bugs;
+-------------+
| max(bug_id) |
+-------------+
|      299646 |
+-------------+

Let’s have fun with this. If you open Bug 300K and it’s a legitimate, real bug, contact me at webmaster@eclipse.org and I’ll send you some Eclipse swag!

Bugzilla confirms it: 2009 was a great year for Eclipse, with 37,839 bugs opened and a whopping 53,466 bugs resolved.

Top bug reporters

480 Xiaodan Wang     @actuate.com
478 Markus Keller    @ibm.com
446 Tianli Zhang     @actuate.com
412 Dani Megert      @ibm.com
401 David Williams   @ibm.com
380 Paul Webster     @ibm.com
352 Andrew Overholt  @redhat.com
342 Steffen Pingel   @tasktop.com
335 Pascal Rapicault @ibm.com
324 John Arthorne    @ibm.com

Top bug resolvers

7851 Paul Slauenwhite @ibm.com
1140 Dani Megert      @ibm.com
1071 Steffen Pingel   @tasktop.com
1033 John Arthorne    @ibm.com
 710 Darin Wright     @ibm.com
 699 Eike Stepper     @esc-net.de
 627 Paul Webster     @ibm.com
 600 Curtis Windatt   @ibm.com
 534 Michael Rennie   @ibm.com
 531 Olivier Thomann  @ibm.com

Top bug commenters

11417 Paul Slauenwhite  @ibm.com
 5070 Denis Roy         @eclipse.org
 4836 Dani Megert       @ibm.com
 4367 Steffen Pingel    @tasktop.com
 3774 John Arthorne     @ibm.com
 3452 Susan F. McCourt  @ibm.com
 3081 Boris Bokowski    @ibm.com
 2861 Paul Webster      @ibm.com
 2702 Darin Wright      @ibm.com
 2630 Olivier Thomann   @ibm.com

I admit to being chatty, but I’m honestly surprised to make this list.

Most attachments submitted

682 Steffen Pingel      @tasktop.com
613 Xiaodan Wang        @actuate.com
548 David Green         @gmail.com
458 CDE Administration  @ibm.com
404 Matthew Hall        @woodcraftmill.com
400 Tomasz Zarna        @ibm.com
376 Kim Moir            @ibm.com
340 John Arthorne       @ibm.com
339 Maggie Shen         @actuate.com
319 Olivier Thomann     @ibm.com

Most contributed patches approved for IP Log

68 Ian Tewksbury       @ibm.com
51 Matthew Piggott     @piggot.ca
46 Ankur Sharma        @ibm.com
46 Chris Jaun          @ibm.com
44 Ian Bull            @eclipsesource.com
40 Tim Buschtoens      @eclipsesource.com
37 Pawel Pogorzelski   @ibm.com
36 Benjamin Cabé       @sierrawireless.com
31 Danny Ju            @oracle.com
29 Raksha Vasisht      @ibm.com

Do you have ideas for more queries or “top-X” lists that would be interesting?  Post them in the comments.

Uptime of our core services (Website, Bugzilla and CVS) has been on the rise, with an average availability of 99.973% for 2009.  If there were 525,600 minutes in 2009, core Eclipse services were missing in action for about 142 minutes.  Sadly, about half of that was because an ISP tech unplugged the wrong cable in May  :(   Oh well, accidents happen.

I’m hoping for 99.99% for 2010.

I just donated some of my hard-earned money to two of my favourite projects:

- Wikipedia.  I use Wikipedia several times a week when I want to read up on just about anything, so I usually make a donation every year. If Wikipedia ceased to exist, I would be very unhappy, so this is the least I can do.

- Amarok.  With a good set of headphones on, amarok serves up the right mix of tunes needed to block out external distractions and allow me to be more productive.  This is a sound investment (pun intended).

Of course, the Eclipse Foundation also accepts donations.  If you feel you’re getting great value from the best (and free) IDE/toolset available, a small donation to show support will go a long way.

The Eclipse Portal now has limited mailing list management capabilities to make it easier to see in one place which lists you are subscribed to, and to show you project lists you might not be subscribed to.  There were undoubtedly be nice features that are missing that we can add, but hopefully this is a start in the right direction.  You can find the mailing list management in your Profile widget like this (only, hopefully you won’t see my ugly mug staring back at you ;] ):

If you have more than one address in the Portal, the mailing lists will be manageable from the first one found.  Once you click on the [mailinglists] link, you get a window that looks like this one:

Lists shown as ‘required’ are lists that the Portal believes you are required to be a member of due to some relationship with the Foundation.  They are still listed so that you can see them, even if you can’t manage them.  There are a couple of places where it might get this wrong.  It can’t currently tell the difference between Project lists you are required to be on (the normal *-dev list) and ones that you are not that also have -dev on the end, so if I subscribe to phoenix-epic-dev here, it won’t let me unsubscribe.  You can still do so by the normal means.  Other lists like *-releng, etc will be manageable properly.  We support a key in the meta-data to determine which is the primary list for each project, but it appears that it’s not up to date enough to rely on.  Hopefully we can change that in time.  Other features could certainly be added, but hopefully this will help get things started.  One thing that is likely to be added soon is the ability to update all the mailing lists to use a new email address when you change it via the Portal.  The address used is the one you have on file with us in the Portal.

It’s a bit slow to respond because Mailman lists are stored in large Python marshalled dictionaries, not in a database that’s easily queryable.  But it’s quick to use (two clicks to do most actions).

Great!  Now that I have everyone’s attention… 

You’ll be thrilled to know that I just learned how to configure an NFS server.  Yeppp.  Folks have been doing this since 1973 and I just figured this out last week while a lot of you were eating turkey.  Go try CVS.  Or downloads. Or running a build.  I bet you a beer at EclipseCon 2010 that it will be faster.

Bah, just try it.  You know you’ll get your beer anyway.

Hudson and Builds need hardware.  But it’s fall, and the money tree is bare.  Every day, the UPS guy does not bring a large shipment of boxes in my name.  But that’s not stopping Dave Carver, Kim and I from trying stuff out.  Stay tuned.

I’m adding e4 to git.  Right now.  You see, in this community, sometimes your bug is ASSIGNED, and soon RESOLVED FIXED before you even open it.

That is all.  You may return to your regularly scheduled programming.