Migrating to Java.net, because of JIRA.. agile?
since 2001, I am using SourceForge, and love to use it, except the approval process. and in several case we register to Google Code. and little work for Github, because of space limit, we cannot move to there. Java.net the current kenai version is different. I one of the java.net hater, because the infrastructure, but now.
I hope Java.net can become a dedicated FREE services for Java ecosystem, and we are moving mostly the project in SF to Java.net, thx to Sonya that give me a lot of quota for the projects. But sad, our old blueoxygen still in pending, but Sonya helping me, i believe in several day, our project move.
Thx for JIRA feature inside, so we can use it, we use dedicated JIRA now, and now we drop the JIRA server, use the JIRA in Java.net, because we believe the java.net server will be more stable, rather our server (got thunder, so usually restart every several weeks, that annoying).
Java.net also have GIT, coo.l, but we still keep the subversion, we still dunno how to collaborate using GIT in a easy and good way.
I am glad if we can have fisheye, hudson, greenhooper plugin for JIRA. and that will become mainstream development server in the world.
let's we see, where will Java.net move.. there will be Conf Call for Java.net topic for JUG leader, and hope we can get update for those.
we still keep the student work in UGForge, becuse, still dunno how to implement here.