I think this is good news, in that it gives some time to develop a good strategy before self-hosting anything.
In between contemplating my own wiki pain for my own projects, and tweeting with @RichardConroy about why more people aren't using more JVM languages, I really feel there is a void here that needs to be filled. I also feel like it needs a bit of a "big think" and don't expect it to be filled brilliantly in days or weeks. Kenai itself is/was a really good effort, and regardless of whether it gets open sourced or emulated in a new solution, I think there's room for something new. I have yearnings! - R On Mon, Feb 8, 2010 at 10:07 AM, Charles Oliver Nutter <head...@headius.com>wrote: > Ok, so there's been a change... > > I emailed Ted Farrell at Oracle to plead for Kenai source to be > released. He explained that would be too difficult right now due to > the license/code-vetting process require, which I understand. However, > he also said that Kenai was not actually going to be shut down. > > Apparently, they want to actively make Kenai be the new java.net > infrastructure! They have posted a clarification on http://kenai.com. > So it seems like there was a miscommunication (or a change of heart), > and projects won't actually need to migrate off Kenai if they don't > want to (details of how they'll transparently migrate to java.net are > unclear). > > We've already started moving some services off Kenai, unfortunately, > and it may be best if we continue down that path. It would be nice to > be completely self-managed, so no project site ever bumps us around > again. But what do you all think? > > On Tue, Feb 2, 2010 at 12:16 PM, Charles Oliver Nutter > <head...@headius.com> wrote: > > Kenai.com is being shut down. Apparently the project itself will live > > on for Oracle internal use, and may rise again as some kind of public > > offering, but the kenai.com domain and all projects hosted there are > > being discontinued. We need to migrate to something else. > > > > For source control, making a complete move to Github seems like it's > > probably the simplest answer. We already maintain a mirror there, so > > we just need to move any unmirrored branches and make the repository > > switch. > > > > JIRA and mailing lists are still graciously hosted by Codehaus, so > > there's no immediate danger to them. Good thing we never got around to > > migrating them, I guess. > > > > The wiki will have to move again. Currently all the pages are still in > > MediaWiki format, which Kenai supported. Our options are to migrate to > > a regular MediaWiki, try to find a wiki package that supports > > MediaWiki, or try to convert all content to another format. > > > > On the bright side, we can now aggregate everything directly under the > > jruby.org domain, rather than having people pop out to kenai.com for > > some services. > > > > - Charlie > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
