10 posts

We're almost done!  The vast majority of projects that have requested to move have gone live on the new site.  We've been working to lock down the rest of them and expect that to be done in the next day or two. 

The content management system (editorial, wiki, forums, blogs)  will go dark some time on Friday, and will stay down through the weekend while we move the bits to our new servers and integrate with the Kenai half of the site. 

The remaining 30 or so projects that haven't been migrated yet will be pulled out of the final data dump we receive from Collab and go live in early March. 

Hope to see you all on the other side! 


Migration Update Blog

Posted by communitymanager Jan 17, 2011

At long last, an update. 

I haven't said anything in a while, because there hasn't been much to say.  Work is happening.  About 400 projects have now been moved over to the new site, and my email client is currently choking on sending the next batch of notifications to project owners.  I expect to get them all out by the end of today.

Expect the Collab forge to start looking like a ghost town over the next couple of weeks. 

Some projects are being locked for migration this week.  In a few days you'll be able to find their repositories, mailing lists, and issue trackers on the new site at <>.  Docs and files, and the mailing list archives will remain on the old site for another few weeks.  When we move those, we'll also put the redirects in place. 

Over the next few weeks Tonya and I will be going through the rest of the site and locking the rest of the projects, and then tagging them "unmigrated".  There are a couple of reasons for this:

1. Locking renders the project read-only and sends another email to the owners and prompts them to contact me if they missed the communication about migration. 

2. At the end we'll have a list of unmigrated projects, as well as the last time their code and documents were updated to publish on the new site. 

3. If there's something that obviously should be migrated but wasn't requested, I can contact owners and add them to the list myself. 

As we expect to have all of the active projects on the site locked by the end of the week, we'll be shutting down user registration here as well. 

Our CMS - editorial, blogs, wiki, forums, will stay put for now.  We're working on integrating this system with Kenai and expect to officially relaunch the new site with our new design in mid-February. 

The next wave of project migrations begins tonight.  This last couple of months have been quite a learning experience.  Things that seemed easy and straightforward became impossibly complicated, and impossible things went just fine.  I'm sure the next few months will bring more of the same.  We're learning as we go, and as a result we made a  couple of minor changes in the plan:

1. Due to the time needed to do CVS to SVN conversions, the Kenai team asked to get those knocked out first, so this wave will be the first 200 CVS projects requested and the maven2 repository. 

2. To reduce the downtime for projects during migration we decided to leave mailing list archives and uploaded documents on the old site for a few weeks.  You will have read-only access to them, you'll be able to use the mailing lists on the new site as soon as the projects go live and be able to upload new or updated documents to the new site immediately as well.  The email and doc archives will be backfilled on the new site in January, and then redirects for project pages will be put in place.

The most frustrating thing for both you and me has been the request process.  We tried to put together an automated system to process the requests as they came in, but it just didn't work.  The Kenai team ended up needing different data on the projects from me, and the system we set up ended up being useless and we switched to brute force.  Next time I need to move a few thousand projects from one forge to another, I'll get it right the first time, I promise.    

Meanwhile, I'm still getting some migration requests coming in.  I'm processing that list and we will move those projects after we receive the final tarball from Collab.  What this means for those projects is they will be dark for a few days while we wait for delivery of the final data from Collab.  When we receive that data we will upload them on the new site and put the redirects in place. went live last night with a few projects from the GlassFish Community.  I've updated the help section to include information about the migration including a list of projects that have requested to be moved here

We started sending out email to all registered users yesterday with a temporary password that will allow you to login and reset your passwords on the new site.  Please note that the passwords between the old and new sites will not be synchronized.  Tomorrow I'm going to start sending email out to project owners to advise those who haven't done so how to go about requesting migration via the opt-in form.

That's all for now, it's the end of a 13 hour day for me.  I expect there will be a few more of those in the coming weeks - but all for a great cause! 

The time is finally here.  16 GlassFish projects have been locked down on CollabNet and are scheduled to go live on the new site next week.  After that, the remaining 161 GlassFish projects are scheduled to go in another couple of weeks.  Once the GlassFish community has moved, we'll begin to move the remaining projects. 

This is an opt-in migration - we have thousands of junk, test, and abandoned projects on the site and we intend to leave them behind.  Any project owner can request that we move their projects, and any community leader can request that we move specific projects in the community.  Any project that is not specifically requested by name via the opt-in form by November 30, 2010 will be purged when the CollabNet site goes dark.  We will be keeping tarballs of the CollabNet contents and will be able to distribute them after the site goes dark, however projects that request migration are our top priority.  The opt-in form is here:

All you need to do is copy in the names of the projects you own or want to move, and we will be scheduling them on a first-come, first served basis in batches.

You will be notified as soon as we assign a date for your projects to move.  You can expect your projects to be read-only for some period of time while we do the migration.  The reason is pretty simple - CollabNet needs time to make the data dumps and deliver them to us.  Once we receive the data from CollabNet it will take us another two business days or so to get them uploaded on the new site.

I've written up some general info about the migration, and the GlassFish team has also been putting together documentation as they have started this process.  The initial information about what to expect from the migration process is below.  I'll publish links to the Getting Started Guide and a wiki when the new site is launched net week. 


Forge Migration

Project memberships and roles - All project members and roles will be migrated and mapped to roles that exist within the Kenai infrastructure.  These roles are Observer, Content Developer, Tester, Software Developer, and Administrator.

Users that do not belong to any projects will be migrated as well. The user email aliases will be changed from to will continue to work until the CollabNet site goes dark.  We do not yet know when the migration will be complete, but the earliest possible day is December 31, 2010. 

An email will be sent to every user as part of initial migration.  At first login to the new site all users will be prompted to update their password.

NOTE: During the migration process these passwords will not be synchronized with passwords on the old site and it will be necessary to log in to both sites separately in some cases while active projects are still moving from one site to the other.

Announcements - the project announcements page does not exist on Kenai infrastructure, and it is very rarely used by projects as a whole.  This page will not be migrated.  However, if you have content that you feel must continue to be available, we can help you move it to your project wiki on the new site.  This work will be done on a case by case basis, as requested.

Discussion forums - there are project-based discussion forums available on Kenai, but given the extremely low usage by current projects we are not making it a priority to migrate them.  If your project does have content in your project based discussion forums that you would like to migrate, we will help you move it on a case by case basis, as requested. The site-wide forums ( will be moved as part of the CMS in December.  Users do not need to take any action. 

Mailing lists - all mailing list content will be migrated and redirects will be put in place to access the archives on the new site.  All subscribers will be automatically resubscribed and non-members of will continue to be able to subscribe to mailing lists.

Post migration users will have to send email to the new mailing address for the list.  The old * addresses will no longer work.  The new address will be  Project owners should take a minute after migration is complete to look at the new mailing list moderation settings and send a note to the list to advise subscribers of the change.

CollabNet automatically created six mailing lists for each project on  No project uses all of those lists, and we will not be migrating the lists that have no content or subscribers. 

Mailing list bridges between the lists and the forums will continue to work exactly as they do now.

Documents and Files - this content will be moved into the "Downloads" section in the new project space and have a special URL. NOTE: Some metadata about the files may be lost in migration, but the files themselves with the correct names will be there.

SVN - SVN repositories will be migrated directly.  To access a repository the users must use the new location.

CVS - CVS is not supported on the new infrastructure for new projects.  As part of the migration process we will attempt to do an automated conversion to SVN.  If that conversion is successful, the code will be placed in the SVN repository for your new project space.  If that conversion fails, it will be placed in a CVS repository.  The CVS repository is not intended to be available permanently, and it will have a minimal feature set available to users.  Once migration is complete, owners will be able to do basic commits and checkouts, and can do conversions on their own projects as they have time, or request a tarball of the CVS repository to do with as they wish.  At migration checkin/out will be via SSH only.

Issue Tracker - Issues in's issue tracker will be converted to JIRA 4.  The mapping between the two systems is not perfect, but it will maintain bug numbers and all basic bug content.  URLs for older bugs might be redirected as time allows.  In general, all bug URLs can be replaced with the following substitution:

Old: https://<projectname><issueNum>


Project home page and web pages - CollabNet has supported several different ways for content to be read from the www folder in your repository to build out your site content.  The Kenai infrastructure provides various options to customize a project:

1) Wiki Home Page: allows owner to customize a project's home page with Kenai's wiki only but retains all Kenai default L&F.  See for details.

2) Website: allows to store free form project data or make it a default home page with a completely different look and feel.  See for details.  You can also get Website contents automatically updated via a repository.  See for details.

3) Custom Layout: allows a user to customize a project's home page and all Kenai infrastructure generated pages with a customized look and feel.  See for details.

All of your content will be migrated over in the repository and you will have access to it, but you will need to take some time to redesign your content using Kenai tools if you have customized it.

Existing Kenai Projects

Projects on will be given the option to move to early in 2011.  The specific date is undecided at the moment as we are concentrating on migrating and stabilizing first. 

If you have a project that currently exists partially on and partially on and you'd like to keep some portion of your content, please request that it be moved.  We will move the entire project, and then you can delete the pieces that you no longer need.  The rest of the project on can be imported early next year. 

LInked or Affiliated Projects

Historically linked or affiliated projects have been listed in the catalog but not granted a project space.  Starting with the migration, valid linked projects will be given a project home page as well.  Owners will have the option to simply put a note and the link on the page, or add more content if they like.  We require that that affiliated projects display the member button on their offsite homepage.  We review these projects occasionally to confirm they are still live and of interest to the community.  If you have a linked project on the current site we will contact you via email in the next week or so to confirm if you'd like a new page created on the new site, and to give you the new member button, which will have the new logo and looks much nicer than the old one. 

Content Management System

Our CMS covers all the areas of the site that aren't a part of the forge tools - our community infrastructure and pages, editorial content, forums, blogs, and wiki.

For the first few weeks of the migration the CMS will continue to exist as it has been on the CollabNet hosted site.  We expect to launch a new version with a new look and feel for the entire site in December 2010.  All major editorial and blog content will be unchanged, and all URLS will remain the same. 

The site-wide wiki will be phased out in 2011 since each project will be able to host its own wiki.  If you'd like to move your wiki content along with your project, we will distribute those files by request.  The conversion from twiki to mediawiki syntax is handled with a simple script.  Otherwise you will be contacted next year when we are ready to close down the wiki.  We will be redirecting pages as needed. 

The new forums are looking good.  We've been doing quite a bit of testing internally, and we didn't find any showstoppers last week, but we also didn't have very many people come try them out, so we decided to delay the launch for a week to try to get more testing in.  If you're interested in spending half an hour trying out the new forums, please send me an email at


Starting on Monday 10/4 we will have a test server set up with our new forums.  Why do we need new forums?  The Jive product we've been using was EOLed quite some time ago, is totally unsupported now, and is the cause of many of our recent short term site outages.  The new forums will be more tightly integrated with our content management system.  We put a banner message up on the forums pages to notify the most regular users.  If anyone would like to help test next week, even if it's just for an hour or so, please email me at and we'll get you set up.  If all goes well with the testing, the forums will be dark next weekend, and the new system will go live on Monday 10/11. 


I meant to be blogging about JavaOne for the last few weeks, but time got away from me.  There are so many great things happening with and so many cool things scheduled for JavaOne, and so much planning to be done, that I haven't had time to sit down and write it all down.  For most people JavaOne starts Sunday.  For me it starts tomorrow.  So now as the last load of laundry dries before I pack it up, here's a snapshot of what's been going on behind the scenes around here:

For -

  • A few weeks ago I hired a new program assistant, Tonya Colombe, to help me out with day to day site management and to help with the migration effort to our new infrastructure over the next few months.  You'll start to see her name around the site and dealing with community management issues.  Please say hello when you have a chance.
  • The long awaited migration to Kenai infrastructure is in the works.  The GlassFish Community is doing a test run over the next couple of weeks, and as soon as that's done, we'll start talking about scheduling the rest of the site.  I'll be blogging about it, project owners will receive emails about it, and we'll do a big ugly broadcast message on the site as well.  I know there will be a million questions on that, so I'm starting to write a FAQ now, and we'll link to it from here and the front page, and I'll be taking further questions on the blog after JavaOne as well. 
  • We are in the process of moving from our (EOLed and unsupported) Jive forums to a new message board system.  Users shouldn't see a big difference, but they will be much easier to maintain when we're done (being supported and all) and will also be much more tightly integrated with the rest of our CMS.  We expect to be testing on 10/4 and if all goes well we will go live with the new forums on 10/11.
  • We have a fantastic new site design to be rolled out along with the migration.  We'll be previewing the mockups in our kiosk at JavaOne, and I'll present them here after the conference is over.  I think you're going to like it. 

For JavaOne -

  • The kiosk and couches will be in the Mason Street Tent.  We're the last thing you'll walk by on the way to the beer, so you can't miss us.  At the kiosk we'll be previewing the new site mockups and talking about our plans for the future of
  • Our annual Community Leads meeting is scheduled for Saturday  - there will be leads from Tools, Mobile and Embedded, Robotics, GlassFish, NetBeans, and JUGs in attendance.  This is a working meeting where we'll talk about migration issues and start working on our roadmap for for the next year.
  • OTN (Oracle Technology Network) night is Monday night.  We're throwing a party and you should be there if you're attending JavaOne. 
  • The Java Posse will be doing a BOF in the Mason Street Tent Tuesday evening.  I'm very much looking forward to it. 
  • Kevin Farnham will continue the tradition of fantastic coverage on the front page of for those who can't attend, or for those who do attend but can't see everything they want to. 

If you come to JavaOne please come by the kiosk and say hello.  It's going to be a great week. 


For several years now I've been involved in on-again, off-again plans to do a major upgrade to the site.  This time it's really happening.  People are working on building out the new site now, and we're going to start rolling out the migration plan here once the first tests are complete. 

Our goal for migration is to reach parity - we need to offer nothing less than what we have now on the site in order for it to be useful to everyone.  However, I'm really excited that beyond that, the new site will be developed by an agile team, so we can try new things and be in a state of constant improvement across the site.  Adding new features won't be a years-long process any more. 

Since we've got this going I think it's a good time to ask you all, what do you think of the site?  I'm looking for constructive criticism here.  Tell me what is wrong and what could be fixed, or what you love and want to stay the same forever and always.  My goal here is to cast the widest possible net.  There are plenty of things on the site that annoy the heck out of me. 

Here's a bit of my list in no particular order:

 - duplication of content and hidden content - often the things I don't care about are available everywhere, but the thing I want (FAQ, help, general information) is almost impossible to find. I'd like to completely revamp the left nav and find a way to streamline access to that information.

 - dead and abandoned projects listed in the catalog - this is a failure of our community management system.  Some communities do a great job of curating their projects, but most don't.  Worse, we have inconsistent standards across communities.   I'd like to publish real standards for what all communities should use to decide if a project is incubating or published in the catalog, and then improve the workflow system we use to move these projects through, so it's as easy as possible for leads to stay on top of things.

 - the catalog sucks - our search system needs a major update.  I want to be able to search for projects with downloads, projects with active bug lists who might be looking for help, and by development activity (among other things). 

 - there's no way to know at a glance what kind of activity is happening in a project - we need activity stats available in an automated way so users can know if a project is dead or not without having to check through several pages of project infrastructure pages. 

That's just the beginning.  I've got opinions on just about everything here, but I'd like to hear yours and be able to respond to them and put them in the long term plan. 

So, what do you think?



First, CLS was an incredibly great weekend.  My job is weird enough that I went for a long time not knowing other people who really do what I do, and it's nice to know my peers and to watch the emergence of best practices come out of discussions like this.  In the next few weeks we'll start rolling out the migration plans for the site, and as you might imagine I'm a little terrified of what the next few months are going to bring.  CLS sessions on Change Management were quite helpful in providing me advice and resources to help get us through the process.  So now I'm a little less terrified.  That's a good thing. 

At OSCON I attended a couple of technical tutorials, but mostly stayed on the Community Track.  Highlights for me were Anna Ravenscroft on Diversity as a Dependency and Brian Fitzpatrick and Ben Collins-Sussman on Engineering Leadership.    I know that the Leadership one was recorded, but haven't seen the video pop up on line yet.  It's worth watching if you trip over it and are looking for project or team management advice. 

The heart and soul of the conference for me were three presentations about building and maintaining communities, and with an eye toward onboarding new developers.  The person that most influenced my thinking was Denise Paolucci of Dreamwidth Studios.  She has really put into practice and nailed down a lot of ideas and processes for bringing new developers into the project.  Mel Chua and Asheesh Laroia did a great presentation on the problem of how to make new developers who are interested in working a project aware of the bite sized bugs they can take on to get started - bug trackers are opaque at best and developing a system of tagging student level bugs and making them easy to find is a great place to start.  Finally Dries Buytaert did a great presentation on the Drupal project and how they built a vibrant community that extends well beyond the developers. 

I'm looking forward to distilling what I heard from these three presentations into FAQ, advice, and maybe some tools to help project owners here to bring in newer developers and students in a useful way.  People ask me about it and for a long time I had vague ideas along these lines, but no real strategies.  It's time to put those into practice.