Twitter github

Author Archive

EclipseCon 2011 Keynote Speaker Ideas

As I mentioned before, this year I want to be a bit more transparent about what the EclipseCon Program Committee is up to while we plan for EclipseCon 2011. One of the first actions we do as a committee is brainstorm ideas for keynote speakers.

In the upcoming weeks, we will finalize our list of keynote speakers. I know many of you that attend EclipseCon have attended many other conferences and have a wide variety of experiences with keynote speakers, if you have any suggestions the EclipseCon program committee will greatly appreciate it. We have already come with a preliminary list of our own but I would love to involve the Eclipse community in the process.

So, who would you like to see be a keynote speaker at EclipseCon? Or who would you NOT like to see? What do you like in a keynote speaker?

Silicon Labs Marathon Relay 2010

This morning I had the pleasure to run the Silicon Labs Marathon relay in Austin, TX.

I had the second leg which was a 10K and finished it in about 41 minutes which isn’t that bad for me. It was also delightful to run as a ringer on the Austin Runners Club women’s team. Overall, I felt good and think I’ll be good for the Chicago marathon in a couple weeks… my right ankle showed no sign of pain!

Eclipse.org Committers and Moving to Git

Are you an Eclipse.org project lead or committer? Do you mind being an early adopter and want to help Eclipse.org fully move to Git?

If you want to help, consider moving your Eclipse.org project to Git. It’s not that hard, here’s how you do it:

If you want to see what other projects are using Git already, check out http://git.eclipse.org

I also recommend you start using the EGit tooling which we recently released the 0.9 version of. While the tooling isn’t perfect yet, we are getting closer to a more comfortable feature parity against the git CLI…

The best way to ensure the tooling meets your needs is to give it a spin and file any issues you come across. We’ll be releasing a new version of EGit and JGit towards the end of this year so this is your chance to get involved and help Eclipse.org move to Git. Thank you to the people who have already done this and are doing their part.

Your EclipseCon 2011 Program Committee

It’s great to see the Eclipse Summit Europe 2010 program out the door. As some of you may know, I have the dubious honor of being program chair for EclipseCon 2011. Today, we held our first program committee meeting where we introduced each other and some of our thoughts on what would make the next EclipseCon great. So, first let me introduce you the folks that will be responsible for making the EclipseCon 2011 program awesome:

We are still in the early stages of planning the conference, but we are looking to bring you the best EclipseCon program yet. As program chair, I’m committed this year to attracting new talks and being more transparent about conference planning than in previous years. In the end, I want everyone to know that the program committee door is open if people have any questions or suggestions. At the moment, we are currently looking at potential keynote ideas, if you have any ideas for good keynotes, please let us know…

Feel free to email me or your favorite program committee member if you have any ideas.

EGit and JGit 0.9 Released

The EGit and JGit teams are proud to announce the availability of EGit and JGit 0.9 today. You can download via our p2 repository, Helios SR1 when it comes out or via the Eclipse Marketplace.

In terms of what’s new, on the EGit side, we added preliminary support for a synchronize view:

We also added some usability improvements to the history and repositories views. We also added a configuration editor to help manage your .gitconfig:

There were many other new things so I encourage to check out our new and noteworthy pages. On the JGit side we added a preliminary user guide, support for .gitignore, rename detection and a resolve merge strategy. On top of that, we refactored JGit to support non-filesystem based persistence which will enable JGit to run on the cloud (I’ll follow up in another post why this is important). If you’re interested in more information, please check out our release review slides as part of the Eclipse development process:

We’ll be releasing EGit and JGit 0.10 later this year to stay true to our relatively brief release schedule. The plan is to release 1.0 on time for the Indigo simultaneous release. Other than that, please enjoy the release and file any issues you come across. There are many ways to contribute, please check out our contributor guide for more information.

On a side note, if you want to show your support for the EGit and JGit teams, please consider on the Eclipse Marketplace.

Captn’ Karls: The Shoe 2010

Last weekend, I ran The Shoe (part of the Captn’ Karls trail series). The course was pretty challenging given the fact that my ankle isn’t 100 percent still and there were rocks everywhere…

And then it got dark which made it a bit worst when it comes to detecting rocks… so of course I managed to roll my bad ankle again…

I ended up finishing in roughly 3 hours and 20 minutes… which I’ll take given the course…

Zilker Relays 2010

Last weekend, I had the opportunity to run in the Zilker Relays with a friend.

We went for two legs each as we had some trouble forming a last minute team.

We ended up finishing in 1:07:03 which isn’t that bad… I ran about 15:30 on average… meh…

The Value of Documentation in Open Source

I’ve been starting a lot of documentation work lately for the EGit/JGit projects and happened to come across this timely article from Forbes. If you don’t want to read it, the gist of it is that solid documentation is more important than you think… especially when it comes to attracting a user and developer base. Here are some quotes…

“I can report that my company receives 70% plus of our site traffic from organic sources, and our documentation generates more than half of our overall site traffic. Furthermore, over half of our lead generation is driven by our documentation.”

While the article specifically mentions commercial software, I think the lesson of having solid and findable documentation apply to the open source realm. I mean, when’s the last time you’ve come across an open source project that you praised their documentation efforts? I can maybe count two total in my lifetime. As open source developers and project leads, we tend to put documentation last and our expectation is that users would pitch in to help. As users, we just want good documentation and don’t believe it’s our responsibility to help out necessarily…

So next time you’re working on that feature, weigh it versus taking some time to document things for your users. If you’re in Eclipse land, feel free to take a look at our documentation guidelines and some examples on how to crowdsource your documentation efforts a bit.

AustinJUG and Eclipse 4.0

Last night I had the pleasure to speak at my local AustinJUG.

It was nice to catch up with some local folks and introduce people to some new Eclipse technology. In the end, we kind of got sidetracked and there was some good discussion about source control in the corporate environment versus what is going on in open source communities. Unfortunately, it seems Subversion has a stronghold in a lot of companies still. I hope our work in JGit to make a liberally licensed Git library that runs everywhere will start swaying the tide…

Hood to Coast 2010

This year I had the opportunity to participate in the Hood to Coast 2010 relay, that starts in beautiful Mt. Hood and ends at the beach in Seaside, Oregon.

I’m always a fan of doing relay races so I was ready to conquer the 197 miles. I started out with Leg 5 which wasn’t that bad…

…besides the hill climb in the end… but I ended up running it in 43:00 which isn’t that bad. After that, Leg 17 was up  which was nice and flat 5.69 miles… it was a night run and I cruised in at 38:46 feeling pretty good.

A bit sore, but still good. My last leg was 29 and it was 6.11 miles full of terrible…

… the first 3.5 miles were essentially up hill with a nice steep grade climb to finish things off. After that, the downhill was probably the most enjoyable running I had the whole relay… I felt like I was floating. On average, I ran about a 7 minute mile pace the whole relay which isn’t bad given the status of my injured ankle. I think once my ankle recovers I’ll be back to my 6 minute mile pace. In the end, my team ended up finishing in 26 hours and 11 minutes (faster than last year!) which put is at 181th out of 1023 teams and in the 54th Open Men’s division.

‘Til next year where sub 26 hours should be in our future!