Twitter github

Category “work”

Planning for EclipseCon 2011

The cat is out of the bag! I have the unique honor of being Program Chair for EclipseCon 2011.

I think Oisin Hurley did a great job chairing EclipseCon 2010, I have some big shoes to fill. I have some awesome ideas brewing on how to make things even better next year and will be selecting a Program Committee (I prefer to call it a Circle of Caring) soon. If you have any ideas on how to make EclipseCon better, please feel free to let me know. Don’t be afraid to give your honest feedback, I feed off the criticism ๐Ÿ™‚

You can email me or track me down in person before EclipseCon 2010 finishes.

Help Name the Next Simultaneous Release of Eclipse

It’s that time of year, the Eclipse Planning Council is seeking feedback on what to name the next Eclipse release.

This year we ship Helios. Next year the name of the release should start with “I” since we prefer the alphabetical approach. The Planning Council seeded these list of names so far:

  • Isaac
  • Ion
  • Isis
  • Iris

Preference given to names that fit the moon, gods or scientists themes we’ve used in the past.

“I” is a hard one… I don’t have any great ideas so far so please give us some great suggestions!

Eclipse, NASA and Rocket Science and the Republic

I don’t know about you but I was blown away by Jeff Norris‘ keynote this morning at EclipseCon 2010. As a matter of fact, I can’t think of any other software industry related keynote that has impressed me as much. As Eclipse committers, it’s very humbling and rewarding to see your software being used by NASA to explore Mars, aid in planning astronaut’s schedules on the International Space Station and other things.

He also has no fear for Murphy’s Law given the amount of live demos he did, from remotely controlling the ATHLETE rover to do some moves for us to controlling a robotic Socrates head.

Space is hard. NASA develops complex systems to explore the universe. You can’t develop crap and run something like the Mars rover missions with brittle and poorly designed software. It’s my personal belief that community, open source and modularity act as enablers for building better software. Eclipse and OSGi exposes modularity and puts people on the path on building better software. Of course it’s not easy, but Eclipse helps.

At the end of the talk, he cleverly used the method of Socratic dialogue to drive some points home. I completely agree with his points about the importance of foundations, frameworks and architectures. I managed to record a poor video from the end of the talk, but here’s a snippet from the dialogue:

Jeff Norris: As software systems grow moreร‚ย  and more complicated, they are going to start taking on the properties we have seen in other industries like rocket science and building buildings. Where the level of complexity begins to demand this division of labor on a scale perhaps we haven’t seen before.

Robotic Socrates: To see the future of the software industry one could perhaps study the past of others. As space exploration demands the combined efforts of specialists with limited understanding of each others trades software developers must similarly diversify to meet the growing demands of their field.

Robotic Socrates: As software projects grow to the scale of skyscrapers, developers will specialize further in order to cope with the complexity of the systems they build.

Jeff Norris: Well, that sounds pretty risky… thousands of developers working on a system and not really understanding what each other are doing… doesn’t sound like a safe thing to do. How are we going to make it possible for those people to collaborate effectively without stepping on each other?

Robotic Socrates: Using the same principles employed in skyscrapers… foundations, frameworks and architectures. Do these terms sound familiar to you?

Jeff Norris: Indeed they do. This is what I think Eclipse is all about… So to conclude, I feel what Eclipse is enabling here is for people like me… to build systems that are appraoching unforseen levels of complexity without them falling apart. I’m really looking forward to what this community is building now and how we are going to use it to explore the universe in the future.

Thank you Jeff and NASA for a great keynote. I expect great things in the future from NASA.

OSGi DevCon 2010: OSGi Best and Worst Practices

Yesterday, Martin Lippert, Jeff McAffer and Paul Vanderlei gave a talk on OSGi Best and Worst Practices.

I really enjoyed the talk because between the four of us, we have a unique and pragmatic perspective on OSGi. I come mostly from a tooling OSGi background but have dabbled in runtime. Martin has been working with enterprise clients deploying OSGi technology for a long time. Paul focuses on embedding OSGi in crazy places. Jeff is just wise OSGi sage, helped Eclipse move to OSGi and has just been doing this forever.

We decided to go the presentation zen approach and it seemed to be received well by the audience. We were a little hesitant at first because deeply technical audiences don’t seem to take the zen style well from my experience, but looks like people enjoyed it. I guess anytime you characterize Peter Kriens as tinkerbell sprinkling OSGi dust everywhere people get a kick out of it.

On top of that, we had a good debate on Require-Bundle versus Import-Package.

I think the devil in the picture above looks more productive, right :)?

In the end, I hope you benefited from our experiences and learned something along the way.

Eclipse Mentors and Google Summer of Code

FYI, the Google Summer of Code (GSOC) program is getting under way and Eclipse.org is participating.

So what’s next?

If you’re an Eclipse committer and interested in mentoring, here’s what you need to do.

  1. Make sure you have an idea listed on the ideas wiki page
  2. Be sure to sign up on the soc-dev mailing list so you can ask any questions
  3. Sign up as a mentor at Google so you get entered in the system

After we have all the mentors sign up, students will begin their submissions and we will go through the review process.

I’m looking forward to another successful year working with students via the GSOC program.

Singlesourcing and Crowdsourcing Documentation

One of the most common complaints I hear about open source projects is around documentation, from the complete lack of documentation to just outdated documentation. There’s many reasons why this is the case, from time to skills but I’m not going to go into that. Yesterday at EclipseCon, David Green and I gave a talk about Crowdsourcing and Singlesourcing Documentation at Eclipse and our thoughts on how to solve the documentation problem for Eclipse.org related projects.

While the talk is focused on Eclipse.org related projects, there is nothing in there that prevents you from taking what we did and apply it to your own projects, whether or not they are open source. The key lessons here is that most developers don’t like contributing to documentation to begin with. They also never have the time. On top of that, if the barriers to contributing documentation is high, no one will contribute and you’ll end up with low quality documentation.

Lower those barriers by enabling a variety of people to contribute documentation, not only people with commit access to the project. If you involve and enable the community to contribute, you may be surprised at what contributions you get.

What other experiences have people faced when it comes to open source related documentation? What can make things better?

The Start of an Adventure – EGit/JGit 0.7.1

The EGit/JGit teams are happy to announce the EGit and JGit 0.7.1 release.

You can install it by pointing to this software repository in Eclipse:

This marks the first official release of EGit and JGit at Eclipse.org and a big step towards Git at Eclipse. This release was mostly focused on the move to Eclipse.org and infrastructure related items. It’s important to note that this release is still an incubation release. I don’t want to be cliche, but Rome wasn’t built in a day.

It’s especially hard that people have been spoiled by the quality of the CVS tooling at Eclipse. On the whole, we are rapidly working on improving JGit and the tooling but require community feedback to make it happen. The workflows aren’t perfect yet but the tooling works well in many cases.

So now that you understand a bit, how can you help?

The goal is to have 0.8.0 go out just before the Eclipse Helios release (June 2010). We plan on adding a Git Repositories view, further expanding http support and cleaning up the user interface. With the help from the community, I expect great things by the Helios release. On top of that, we expect to have one or two Google Summer of Code (GSOC) students working on improvements.

For now, put your beta testing hats on and explore what EGit and JGit has to offer.

We thrive on community feedback and involvement.

OSGi DevCon 2010 – Working with OSGi

Tomorrow as part of OSGi DevCon 2010… Simon Archer, Jeff McAffer, Paul Vanderlei and I will be giving an awesome OSGi tutorial. The tutorial will take you through developing a fully functional OSGi-based application based on the famous Toast example from the OSGi and Equinox book.

We’ll cover the key elements of OSGi and creating OSGi-based systems with principles and practices that are applicable in a wide range of application domains and execution scenarios. A lot of time and effort went into the book and Toast example. In my opinion, the Toast example is the best OSGi example out there and you’ll benefit from learning it.

Why should you come to our OSGi tutorial? Well, you’ll have the eyes and ears of four guys who have been doing OSGi for many years. On top of that, you’ll get to hear us make some controversial statements like when programming OSGi, don’t use OSGi. Oh, and you’ll hear Jeff talk about how modularity is the lubrication of collaboration.

Activate Chuck on build.eclipse.org

Choice is important when it comes to open source and we try to provide it at Eclipse. To promote choice, your lovely build.eclipse.org maintainers have kindly installed the Chuck Norris plug-in.

So now you have a choice between the Hudson butler and an ass-kicking Chuck Norris on your build page.

Chuck can be activated on a per-hudson project basis. It’s off by default.

Enjoy. Activating Chuck is so much better than working on EclipseCon presentations ๐Ÿ™‚

EclipseCon 2010 Tweetup

There will be a Eclipse community tweetup at EclipseCon.

The Eclipse community has a fine tradition of taking over the Hyatt bar on the night before EclipseCon. Let’s continue that tradition.

Please sign up if you can come!