Oracle Doesn't Get Open Source
Kohsuke Kawaguchi, the creator of the Hudson Open Source project woke up Monday morning and discovered he was no longer able to access the Source Code Repository to make commits. Oracle had decided to shut it down, as they are shutting down many projects in java.net to try to move it to their own infrastructure. Not only that, but the mailing lists were shut down as well. They said not to worry, they will have it up in a week.
No notice, no transition plan, no respect for the open source community or the project creator.
Fortunately KK knows open source better than Oracle. And KK knows how to run an open source infrastructure better.
He and others in the community moved the mailing list archive and list to Google Groups and Nabble - http://hudson-labs.org/content/mailing-lists so there is better functionality and search capability than before. He moved the source code to Git - https://github.com/hudson/hudson.
He did this all in a few hours. All completely open. Oracle is still a week away from completion… But the community is up and running!
No notice, no transition plan, no respect for the open source community or the project creator.
Fortunately KK knows open source better than Oracle. And KK knows how to run an open source infrastructure better.
He and others in the community moved the mailing list archive and list to Google Groups and Nabble - http://hudson-labs.org/content/mailing-lists so there is better functionality and search capability than before. He moved the source code to Git - https://github.com/hudson/hudson.
He did this all in a few hours. All completely open. Oracle is still a week away from completion… But the community is up and running!
Comments
The move to the new infrastructure is complete for a good number of projects, with the other ones done in a few hours if all goes well. And we're talking full migration with roles, issues, code and mailing lists preserved
- Justin Kestelyn, Oracle Technology Network
I think most of the rest of what I said is fairly accurate or my opinion. More coordination with KK and Winston to communicate with the community would have been good. Also a temporary solution like the community put in place would have been a good idea rather than a shut down of those services.
I'll also note the community seems to like the availability on Git - http://groups.google.com/group/hudson-dev/browse_thread/thread/8d3cf0ca1240280a?pli=1