Linked by Andy Roberts on Thu 9th Jun 2005 20:58 UTC
Java The recent announcement from Apache regarding their plans to embark on their own J2SE implementation called Harmony has re-ignited the long-running Java/OSS debate. James "Father of Java" Gosling reacted in an unexpected way by giving a misleading view of what open source is really all about. Now that the dust has settled a little bit, it's time for an article that is not championing the cause for the relicensing of Sun's implementation under more permissive, open source terms, but simply a look at what could (and could not) happen under the open source model.
Permalink for comment
To read all comments associated with this story, please click here.
Then why does Ubuntu call it a fork?
by Anonymous on Fri 10th Jun 2005 00:52 UTC

"This procedure involves a temporary fork of the package, but:

* if the maintainer accept the patch than the fork can be deleted immediately and the package reimported from Debian.
* if the maintainer does NOT accept the patch we still need the fork to fix the issue for us.

Either way is a win-to-win situation because it is work that needs to be done.

For bugs that are NOT RC we can relax and wait for Debian to incorporate the fix.[[BR]]? If this will not happen in a decent amount of time (let say 15 to 20 days or 2 uploads of the package in Debian?) we might want to fork and upload. "