https://twitter.com/cra/status/325604872512737280

I took it pretty easy on the hilly trails and enjoyed the views from the top:

https://twitter.com/cra/status/325620951435866113

I ended up finishing in 1:27 running a 9:20 min/mile pace.

The next morning I ran the Rogue Trail Series: The Loop race. I finished the 10km trail race in 49:58 and ended up 12th, so not that bad. I had a lot of fun chasing folks:

https://twitter.com/cra/status/325956602983227392

I look forward to the last race in the series which a few years ago I had the special honor of slipping and falling on a cactus, it was good times.

Why? I like to do it and it helps me to perform better. Since starting a new job at the tweet house a couple years ago, I’ve neglected my writing about running and the desire to run a sub 3 hour marathon. That’s going to change today though! Last week, I participated in the first race of the Rogue Trail Series titled The MAZE. It was a beautiful morning to run:

I started in the back because I arrived a bit late and had to pass a lot of people which was fun. While the course had some single track terrain, there were ample opportunities to pass people. I even tried to vine me passing someone to see how that would turn out while running at a decent clip:

Chasing and passing vine.co/v/bDDYW71vWur

— Chris Aniszczyk (@cra) March 24, 2013

I ended up finishing decently at ~51 minutes and could have easily picked up the pace towards the eng. More importantly, I felt great at the end:

I look forward to the race in the series!

What’s new? I recommend checking out the JGit New and Noteworthy along with the EGit New and Noteworthy documents. The team is excited to get a new version ready for the Juno SR2 release. The release tag is: 2.3.1.201302201838-r

You can download the latest release using this repository (or the Eclipse Marketplace): http://download.eclipse.org/egit/updates-2.3

Enjoy and the next release will be in time for Kepler in June 2013. I personally look forward to recursive merge support soon (see bug 380314).

• Laila
• Ladon
• Laplace
• Lok
• Lorentz
• Luna

Note that this community poll will be used to pick top choice. We may have a series of run-off polls with voting until majority consensus achieved. The poll will be opened for a week and then I expect the final decision on the name will be made by Feb 15th at the latest (after Eclipse Legal approval is finalized).

Go vote and be heard!

To add your name to the list of possible names, see bug 398191. Here’s an initial list of names to get your creative juices flowing:

Have fun, the bugzilla entry will remain open until January 22nd to gather suggestions for potential names. After that, a community poll will be used to pick top choice. We may have a series of run-off polls until a majority vote is achieved. The poll should be opened on January 22nd with a week of voting allowed. The final decision on the name will be made by Feb 15th at the latest, maybe earlier depending how quickly final Legal approval is.

Essentially, it allows you to query the GitHub timeline (note: timeline data is available starting February 12, 2011). As an added convenience, the data is also available on Google BigQuery via a public dataset to make it easy to try out a few queries before downloading all the archive data locally. A couple downsides to Google BigQuery are that  the user interface is a bit clunky and there are query quotas in place (unless you sign up for the service), other than that it’s pretty straightforward to use.

Of course I got distracted from my initial task and started to search for profanity usage across the GitHub timeline in 2012. I mean, who isn’t interested in seeing how many instances of the seven dirty words they can find across the GitHub timeline? It all starts with a simple query (see the gist).

How many instances did I come across?

37,674 as of today (also posted a CSV online).

Here are some of my favorites:

• fuck fnv hash sucks. SO MANY COLLISION. I don’t think hashing in the way to go
• open source n shit
• Added shit, fixed some shit, broke some more. Have fun.
• deleted the motherFucking buzz killing mood fucking .classpath files
• THE FLYING FUCK JUST HAPPENED
• Fuck unicode
• Refuckulate date thing to make it compile Windows

After this distraction, I was happy add the new word “refuckulate” to my lexicon.

Enjoy grokking the GitHub Archive, I highly recommend it!

The countdown is finally over…

Shutting down CVS in T-1 minutes. Makes perfect sense. Despite what Husker Du might think youtube.com/watch?v=J1sYN0…

— Wayne Beaton (@waynebeaton) December 21, 2012

Over 80% of the projects at the Eclipse Foundation are finally on Git and CVS access is switched to be read only. I believe the projects left on SVN will migrate soon enough, there are just too many advantages with using Git.

One interesting bit of history regarding this migration to Git is it all started back in 2009 when some community and Eclipse Foundation board members wanted to have Git, JGit and EGit all at Eclipse. You may not believe it, but at that time, moving to Git was a bit controversial. I dug up a old Google doc that we had discussing the pros and cons of moving to Git (prepping a presentation for the Board), this is what we had for benefits:

• Committers want Git support on eclipse.org
• Provides all contributors equal tool support: non-committers equal citizens, reduces contributor startup time; have all committer tools at start, reduces contributor -> committer conversion bump
• More accurate recording of activity: author recorded separately from committer; better IP tracking, code movement detection; better IP tracking after-the-fact; easy to maintain history, audit trails
• Open source implementations; meets mandate to avoid vendor lock-in.
• Widely popular: github.com has become very high traffic site.
• Staying power; many large projects use Git, its not going away. Big current users: Qt, KDE, Linux, Android, X.org, Wine, OLPC, OpenAFS, Ruby, Perl5. More considering: GNOME, ASF
• Easier to move projects to eclipse.org

An entertaining part of this analysis was the mention of GitHub becoming a high traffic site in 2009… GitHub recently posted some stats so we have an idea of what life was like in 2009 compared to now…

How times change.

What’s new? I recommend checking out the JGit New and Noteworthy along with the EGit New and Noteworthy documents. While there were a lot of new features, my favorite feature is the performance improvement in EGit for re-indexing repositories (it’s now done incrementally, see bug 393642).

The release tag is: 2.2.0.201212191850-r

You can download the latest release using this repository: http://download.eclipse.org/egit/updates

Enjoy and happy holidays! The next release will be in mid February.

Since Gerrit 2.4 (see release notes), a Rebase button was added that will take the most recent patch set and have it be rebased onto the tip of the destination branch or the latest patchset of the change depended upon. A new patch set containing the rebased commit will be produced and added to the change. It’s a great feature which helps alleviate a common workflow when working with Gerrit.

Note: Another option would be to set the Submit Action (via Admin > Projects > [Project Name] > General > Project Options) for your project to use ‘Cherry Pick’ as this would keep a clean history with no merge commits when submitting changes.

Anyways, enjoy and happy rebasing!

As some of you may know, a portion of my current job at Twitter is defining our open source strategy and compliance efforts. While at Twitter we’re fortunate that compliance is less burdensome than at some other traditional companies who have many distribution points (e.g., devices), nevertheless it’s still important to respect licenses and the software authors intention. We mostly run on open source software and are cognizant of the benefit we receive from a variety of open source communities and what it means to give back. We also don’t mind sharing what we develop, on top of preferring liberal licenses as that helps with adoption (and also makes compliance less complicated) in my opinion.

At the end of the day, it was a great event bringing together participants from different companies to discuss open source compliance issues and best practices. Thanks again to the Linux Foundation for hosting the event.