Twitter github

Posts Tagged with “eclipse”

Rock the Eclipse Board Vote 2010

Today, the Eclipse Foundation’s Board Member elections start (to be exact, February 22, 2010 at noon EDT). You should receive an email with voting instructions if you’re eligible.

I insist you vote. If you can’t vote, I highly recommend you become an Eclipse Member as it gives the power to vote and influence the future direction of Eclipse.

The people that both represent committers and solution members have a unique position to push the board on specific subjects. I recall that last year, the committer representatives pushed extremely hard to have JGit hosted at Eclipse.org (due to it’s unique licensing situation). The first time we brought the issue up we were denied the move. However, through some passionate persistence on the committer representatives end, we pushed forward and were successful with the JGit move. The committer representatives also had a large impact on moving the Eclipse Marketplace forward. Although it’s not the appstore some of us envisioned yet, it’s definitely a step in the right direction.

As for who you should vote for, I can simply say I vote for the people who are passionate and are committed (see Ed’s post) to the success of Eclipse. As always, I would be honored to be given the chance to represent the committers again on the board. I believe we have a great thing going on at Eclipse in respect to technology and open source project governance. I can only guarantee that I will continue to be passionate, do my best to attract/mentor new projects and improve the processes within the Eclipse community.

So what are you waiting for, rock the vote this afternoon.

Eclipse, Symbian and the Rise of the Weak Copyleft

In case you weren’t aware, the Symbian Foundation recently open-sourced their Symbian^3 platform under EPL. I’ve had a few people come to me and ask first, what is the Eclipse Public License and why would Symbian choose that license say over the GPL or APL.

So let me try to answer some of those questions (note: IANAL).

What is the Eclipse Public License?

The Eclipse Public License is an OSI approved license. It’s a weak copyleft license similar in spirit to the LGPL. Any changes and certain additions to EPL-licensed code need to be licensed on under the EPL.

This is unlike the GPL where it dictates that any work that is based on GPL-licensed code must itself be GPL-licensed. Some people like to call this licensing behavior viral.

If you want to learn more about the EPL, check out the EPL FAQ.

Why did Symbian favor the Eclipse Public License?

Well, according the Symbian FAQ, here is the reason…

“The Symbian Foundation has instead chosen the EPL because it wants to be absolutely clear about this: device manufacturers will be able to add new features and support new hardware without having to make all of that code open source, except where they are changing or making certain additions to EPL code supplied by the Symbian platform. We expect that device manufacturers will see the value of enriching the Symbian platform by contributing their innovations, but we don’t insist that everyone must contribute everything.”

On top of that, I postulate that Symbian recognized the importance of giving people a choice and protecting the investment in the Symbian platform code. This is where I argue a weak copyleft license like the EPL actually gives you more freedom than a strong copyleft license like the GPL. The GPL wants to devour your code and all of its friends. The EPL gives you a choice.

Why not LGPL? Well, there are some patent retaliation and reverse engineering clauses in the LGPL that make certain companies legal departments nervous. Other than that, I actually like the LGPL’s weak copyleft spirit.

The Rise of Weak Copyleft Licenses

One of my predictions is that in the near future, we will see a significant rise in the usage of weak copyleft licenses. If you’re looking to build an ecosystem full of commercial and individuals members, a weak copyleft license is the best choice in my humble opinion. Eclipse first blazed the weak copyleft builds ecosystems path with the CPL/EPL followed by Symbian. Microsoft is getting into the game with the MS-PL license (which is weak copyleft). Even Intuit’s Partner Platform is dancing with the EPL. I’m sure there are others in the wild.

Do other people have strong feelings on weak copy left licenses? Do you see a pattern too?

On a side note, if you have the time to burn on legal issues, I highly recommend taking a gander at Janet Campbell’s “Managing Open Source Legal Issues” video on EclipseLive.

EGit and JGit Builds Available

I have some good news everyone.

The EGit and JGit projects at Eclipse are producing consumable builds via Maven3 and Tycho.

It took awhile to get the build story working due to the diverse needs of all the consuming parties. There was a desire for JGit builds to produce p2 and maven artifacts and have those consumed by the EGit build. If anyone has worked with this mixed mode situation before, they should understand the pain of getting everything working. If you’re working in a mixed mode environment or already tied to maven, I highly recommend giving Tycho a chance (the team was also very responsive when we hit issues).

We will also be scheduling a release review soon to get an official incubation build out for everyone to try and give feedback. The only way the tooling will get better is if people try it and file bugs (or even contribute patches). You can be an early adopter and try installing the latest builds. We also have an extensive contributor guide online if you’re planning to contribute patches with Gerrit running to facilitate patch review.

If you hit problems or have suggestions, file bugs and try the EGit mailing list.

Eclipse Helios IP Review Deadline

It’s that time of year again at Eclipse!

In preparation for the Eclipse Helios release, projects are asked to get their IP logs in order by February 5, 2010.

SWT Tidbits

I saw some interesting SWT related things as of late so I figure I’d share with everyone.

STW – SWT Transition Widget

It’s a widget that enables transition effects in SWT… see for yourself…

I think the project is a good candidate for Nebula if anyone wants to reach out to them.

Nebula – AeroToolBar

It looks like the Nebula project will be getting a donated widget that resembles the Vista toolbar.

SWT UI Mockups

I generally find user interface wireframing tools very lackluster. However, taking an existing piece of live user interface…

And painlessly turning it into a mockup

Very cool!

Anyone see anything else good lately?

Mylyn Reviews

Just in time for Christmas, a new project proposal called Mylyn Reviews was posted. Mylyn Reviews aims to take the work done in the ReviewClipse project and mend its notion of code reviews to Mylyn tasks.

Mik Kersten and I will be mentoring the project as it moves and begins its new life at Eclipse. I’m personally very excited to see this project coming to Eclipse and evolving. I see a future where code reviews are integrated into Eclipse as easy as Mylyn tasks are.

Pan Handling in Open Source?

How should open source projects handle donations? And do it in a tasteful fashion?

panhandling-not-illegal

I ask because I’ve been doing some work lately do expose the Friends of Eclipse program at Eclipse in a variety of ways. For example, I want to add a link on Eclipsepedia as we have on a variety of the Eclipse download pages.

Friends of Eclipse

I’m a fan of the Friends of Eclipse program because I believe in the power of community. All donations benefit the Eclipse community in some fashion from providing more bandwidth for users and committers to sponsoring Eclipse community events. The program is there as a way to contribute to Eclipse for people who may not have the time to become a committer but have the financial resources and desire to contribute. For awhile, I don’t think the program was very visible and that’s changed as the link has appeared on the download page. There are now over 1000 donations to the program! I see a future where we could get a considerable amount of support from the Friends of Eclipse program and help the Eclipse Foundation sponsor more events.

But is there a line that we can cross where it seems like we’re pan handling :)?

I tried to look at how other projects handle donations.

If you look at Wikipedia, their approach is to have everything front and center.

Wikipedia

It seems to work for Wikipedia as they tend to have a fund raising drive model. Their users don’t seem to mind either. The Linux Foundation has a way to donate on its web page and they also have a program similar to the Friends of Eclipse where you can sign up for individual membership with some benefits.

Linux Foundation Individual Membership

How do other people view donation in the open source context? Is there a line to cross?

How do other open source projects do this?

Riding out the twilight storm…

My inbox and twitter account has been under attack lately by Stephanie Meyer and her Twilight minions.

twilight

My current Google Alerts query for Eclipse-related news is this:

eclipse -lunar -aviation -mitsubishi -solar -twilight -heroes

It used to be much longer before and I’m trying to strike a balance now.

Anyone have a better one :)?

The Bookshelf: Building Open Communities

One of my big interests is building and analyzing communities, especially in the open source space. I’ve learned a lot from my experience in the Gentoo Linux and Eclipse communities and take joy in the experience. There are so many interesting topics within community building from effective communication mechanisms to development processes to governance. I see a future where a lot of software is developed in the open and building a community around that will be vital to the success of that piece of software. As I was writing this post, Microsoft just announced that they are open sourcing the .NET micro framework and attempting to build a open community around the technology…

Microsoft is also in the process of forming a community of interested and involved members to help shape the future direction of the product. There will be a core technology team that is composed of Microsoft and external partners, and people will be encouraged to propose projects, which will be vetted before they are accepted…. The site will also support people building extensions that exist alongside the platform rather than being integrated into it…

You know when Microsoft is releasing stuff under the Apache 2.0 license and attempting to build communities there’s a shift in the industry happening. Good for them!

Ok, on to the point of this post now. My reading list went empty recently and I needed to fill it with some interesting books. In particular, I was looking for books related to open source and community building. The good news is that I found a couple of interesting books, the bad news is that I wish there were more books on these topics. I’ve been devouring the Art of Community book by Jono Bacon (Ubuntu’s Community Manager).

It’s a fascinating book which outlines some of the aspects of community building and share’s many of Jono’s experiences in developing the Ubuntu community. A lot of the things he discusses can be mapped to what is going on within the Eclipse community. Jono’s coverage of the importance of meritocracy and governance pleases me.

Anyone else have a chance to read the book yet?

Another book that I’m looking to devour is the Groundswell by a couple of Forrester Research’s analysts.

I’m always a fan of case studies around social technology and how it can impact your business. My favorite recent example is the United Breaks Guitars debacle… how much heartache did that cost United? I’ll let people know what I think of Groundswell when I finish it.

Anyone else reading anything good around open source of community building lately? Any recommendations?

Lowering Contribution Barriers in Open Source

Inside the Eclipse community, we’re looking at ways to make it easier for people to contribute. Part of that work involves working on improving the web presence of Eclipse when potential contributors come visit (the other major part is at the code level, but we will leave that for another post). To help me with some ideas on how to improve the contributor experience on the Eclipse.org site, I wanted to look at how other open source communities are handling it at the moment. My thought was that visiting other community sites would also help me play the role as contributor since I’m so entrenched with things at Eclipse and have a difficult time putting myself into the role of a contributor.

Mozilla

When visiting the Mozilla site, I was greeted with a gigantic Get Involved button.

mozilla

Mozilla realizes that there are many types of contributors out there and accommodates appropriately for that.

mozilla2

As a bonus, Mozilla even had contribution options based on how much time you have available!

mozilla3

Awesome!

Symbian

The Symbian site had no clear way for me to realize how I can contribute to the effort. The site was pretty but I’m not sure the excessive use of flash is going to win bonus points with developers (does Flash even run on Symbian-based phones?).

symbian

After some digging, I found the Symbian developer site.

symbian2

It was pretty easy to find links to code, bug tracking and forums. I didn’t see any obvious links for people who may want to contribute translations or their artistic skills to the project. Then again, the Symbian foundation is pretty new so maybe they aren’t at the point where they need translation contributions.

Fedora

Inside the Fedora site, I immediately was drawn to the Join Fedora link.

Join Fedora

After clicking that link, I was presented with a wonderful variety of ways I can contribute to the Fedora project.

fedora2

I’m a huge fan of any open source community that realizes that contributors come in all shapes and sizes; there aren’t only coders out there.

Ubuntu

The Ubuntu site had nothing obvious on how to get involved immediately (you have to scroll down quite a bit to see a link to get involved).

ubuntu

I dug around a bit and found a link to Get Involved with the Ubuntu community. I was delighted to be presented with the way I would like to get involved.

ubuntu

Ubuntu seemed to classify its contributors into developers, non-technical users, technical users and people willing to donate money.

Seems reasonable.

Conclusion

What did I learn at the end of this exercise? It’s important to realize that there are many different forms of contributor roles in open source. Here’s my simplified version of the major roles contributors may play:

  • Writers
    • These people can help with things like documentation and articles
  • Developers
    • These people can code; provide patches; potentially become committers
  • Translators / Internationalization

    • These people can help with internationalization efforts
  • Graphical Artists / Designers
    • These people can help with artwork; don’t let coders design things
  • Evangelists
    • These people can help organize events and spread the word; marketing is key

There are contributors that may fit many of these roles, but most will specialize in one type of role. The key thing to understand is that you need to cater to each of these roles including how much time people have (like Mozilla did). For example, developers will want to know how to access code and contribute patches to the project. Translators will need to know where to go to translate strings for the project or file bugs for long German words that wreak havoc on your user interface. And so on…

What do people think? What can open source communities do better at making it easier for people to contribute? As a next step, I’ll take a look at playing the role of contributor in one of these communities and write a “Hello, World” type application.

If you have any ideas on how to improve the contributor experience at Eclipse, please comment on this bug.