Opening Java

Freshness Warning
This blog post is over 16 years old. It's possible that the information you read below isn't current and the links no longer work.

13 Nov 2006

So Java is now open source, licensed under the GPL. At startup camp, I discussed this a bit with Tim Bray. The challenges around open sourcing something as complex as Java (or Solaris) are immense. Establishing clear intellectual property is alone something that can take months. You’d think that it would be a simple question—it’s Sun’s code, so of course they have the right to release it under any license they wish. In reality such things are complex.

Sun needs to make sure that every contractor that has ever touched the Sun codebase had released their work to Sun. Most likely every contractor Sun uses is performing "work for hire" and Sun owns everything they do, but the lawyers need to check that anyway.

Some parts of Java were created by third parties and licensed to Sun. In the event that the license doesn’t allow opening the source, Sun would have to renegotiate, rewrite the licensed features from scratch, or do something to make sure Java is operational with these features excluded.

It’s possible that Java contains technologies that Sun acquired when they purchased or merged with other companies. So they need to go back and make sure there’s a clear IP chain with all of those, too.

So when Jonathan Schwartz thanks the lawyers when announcing Java’s move to the GPL, he’s acknowledging a whole lot of hard work.

Recently Written

The Trap of The Sales-Led Product (Dec 10): It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7): One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16): When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27): An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24): Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21): Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19): Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17): Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.