Skip to main content
Last updated January 13, 2011 20:30, by leawang

Where's my project?

When migrated, projects will move from <project> to <project> (no more .dev, no more https!). For example, will move to

Each project is given a default home page and each project can create a custom web-page. The default page is also found at:<project>.

By default, this page has the common look and feel for Kenai. We will have a complete redesign for the site in December, 2010.

How to log in

Your Collab user ID is migrated to the new Kenai infrastructure. You should receive an e-mail with instructions. If you do not, you can browse to, click login, then click "lost password?" link: enter your user ID from collab and you can reset your password via the e-mail link.
Account update instructions start being sent around Nov. 9. There are several hundred thousand notices, so this process will take some time. Please do not be alarmed if you don't receive this e-mail immediately.


Your e-mail user ID will become (During the transition, will route through the Collab e-mail system and you'll continue to get notifications for Collab based updates and changes.)

Mail content will be migrated and is included in each projects documentation.
Project links are of the form:<project-name>/lists/<list-name>/archive

More details about e-mail can be found here:

Note About SPAM Filters
If you use a SPAM filter, you may need to adjust your e-mail settings to prevent these messages from being identified as SPAM.

Where is my repository?

You can find the new repository URL by browsing to<project>/sources

The check-out URLs to your repositories will be listed in that table. For example, in the Mimepull project, the SVN repository is located at

Note for projects using CVS
Kenai only offers limited support for CVS. We have attempted to convert as many projects which formerly used CVS to SVN. You can tell if your project has been converted by the repository name. For example, the MQ repository is converted as part of this migration. The new repository is named Migrated CVS, but it is a subversion repository (you can tell from the repository URL). The repository location would be:

For projects which will remain in CVS after the migration, these projects are called CVS Repository, for example:

You must be logged in to view the CVS access URL. (Your project can elect to migrate your repository to SVN manually) Note: CVS is not an option for new projects. CVS is only supported for migrated legacy project use.
CVS requires an SSH Key. You add this to your profile, Click Edit My Profile, select SSH Keys tab. You can find details about creating and working with SSH keys at this help page. You can find more details about using CVS.

What about my working directory?

SVN users may be able to avoid creating a new working copy of their project's source tree. See the documentation about the svn switch command and --relocate option.

Before you try that or create a new working copy from a checkout of the new repo, make a copy of your current diffs. Go ahead... I will wait.

Welcome back.

If the repository has changed from a CVS repo to an SVN repo, you will need to create a new working directory.

Manage your project

Kenai project features are enabled in the "features" page. You can browse to that page via:<project-name>/features

(You must have proper permissions to view and change these settings)
We recommend you read the documentation about the features available at Kenai:

Project Roles

Roles will be mapped during the migration process, as follows:

  • Unauthenticated (aka Anonymous or Guest)
  • Authenticated (anyone who has account and logged in)
  • Observer (anyone who wishes to watch a public project on
    • ->
  • Content Developer
    • collab.content-developer -> kenai.content-developer
  • Tester (Not existing in If not applicable, don't use the role)
  • Software Developer
    • collab.developer -> kenai.developer
  • Project Admin
    • Collab.admin -> Kenai.admin
  • Project Owner (1 per project, This is administratively assigned at conversion. Each project will need to designate the new owner, after conversion is completed.)
    • First collab.admin -> kenai.owner, fix manually after migration

You will find more information about roles and permissions associated with each at these links:

Project Bug Reports

All existing bug reports will be migrated to Jira. This was chosen for several reasons, the primary one being that we needed to preserve the bug-ids from IssueTracker.
Mapping via IDs between IssueTracker to Jira will be possible.
If you haven't used Jira, have a look at the Jira User Guide:'s%20Guide?clicked=jirahelp

We are using version 4.0

Jira offers many opportunities for customizations. We are evaluating what customizations are available, and how we can best tailor Jira for our use.

Bug Priority Mapping

Issue Tracker used Priority 1 (Highest) through 5 (lowest). Jira maps these values into words:





What about external links?

The Kenai team will do the best they can, to use DNS and Request forwarding, to ensure that external links yield something, if not exactly what might be expected, something close. Here are some examples of links that should be automatically forwarded.

At the top level, the project URL will automatically forward:

If using the default web-site:
https://<project> ==><project>
If using the custom web-site
http://<project> ==> <project> (your custom site)

Bugs: Issue Tracker will forward to Jira

https://<project> ==><project>.

Mailing lists:

https://<project> ==><project>/lists


https://<project> ==><project>

Source code: (not an exact match, but from Kenai URL below, you can see a list of repositories and you can select the repository you wish to browse)

https://<project><project> ==><project>/sources

What to do if there's a problem with your project

First off, look for the help pages at Much of what we'll need to learn is how the Kenai infrastructure works. If that fails, you can contact the Kenai development team. There is a link at the bottom of default pages, is a "contact us" link. You can use that for general Kenai related questions. Finally, if you have a problem specific to the migration, send an e-mail to:
You can also find information in the Kenai forums. These are at

Please Confirm