---------- Forwarded message ---------- From: <[email protected]> Date: Mon, Aug 3, 2009 at 09:56 Subject: Your CVSDude account is now on our new platform. To: stefan.teleman at gmail.com
If you have trouble reading our HTML email, please don't hesitate to ask support. Dear Stefan, Welcome to our new FrogSAFE (or "V4") platform technology (read more in our blog). Your "kdesolaris" account has been migrated. Most existing access Urls should work as normal, but if you find they stop working please check the list of "updated access Urls" below. You will also find our Migration Guide, with information about our new features. We recommend checking over your projects, access permissions etc to ensure they are correct. Our automatic migration script makes conservative guesses where options are upgraded in V4, and these might not always be what you want. For example, V3's "user admins" feature is being replaced by more privileged "admins", so instead of silently upgrading what your admin users can do we have left them as normal users, for you to re-upgrade in full knowledge of the new powers you are granting. Given this choice of "grant new powers or remove existing powers" we did not migrate "user admins", you will need to set up your new admins fore-warned that they have new privileges. For further information about getting started with V4, please visit help.cvsdude.com, and don't hesitate to use our support form if you have any questions or if you need a different week for your migration. Please ensure you notify your users if any of these changes will effect them. We hope you enjoy your upgrade, The CVSDude Team ________________________________ Updated Access Urls Home/Admin: This is really the only URL you need, as you can check the other URLs from the 'projects' tab here. You can continue to log in from http://cvsdude.com as usual Bookmark https://kdesolaris.home.cvsdude.com to jump directly to your organization's server Subversion: You can keep your svn pointing to http(s)://kdesolaris-svn.cvsdude.com/PROJECTNAME as usual If you need/want to update your working copies, point them to https://kdesolaris.svn.cvsdude.com/PROJECTNAME See the end of this email for hints on how to update links for your existing working copies Trac: You can continue to use https://kdesolaris-trac.cvsdude.com/PROJECTNAME Bookmark your new location at https://kdesolaris.trac.cvsdude.com/PROJECTNAME if updating bookmarks Bugzilla: This is now available per-project, if you had an existing bugzilla it has been moved into its own "bugz" project: https://kdesolaris.bugz.cvsdude.com/bugz DAV: This is now available per-project, if you had an existing DAV it has been moved into its own "DAV" project: https://kdesolaris.drive.cvsdude.com/projects/dav ________________________________ Migration Guide What You Need To Know About Migration The new admin interface can be found at https://kdesolaris.home.cvsdude.com. You should log in as your master account user (now the "owner user") and check over all your settings. Organizations & Owner-Users. The master account record is now two records: an "Organization" and a "User". After migration these will have the same name, so they can be used much like a master account. However, ownership of an organization's account can now be transfered to any user. Groups Version 4 does more with groups. User groups are "pushed" out from the main config to all services that support groups (including svn, trac, and even CVS). By setting per-service configuration options (access controls for Subversion, writers file for CVS, trac permissions for trac) based on groups it's easier to add new users with similar permissions. Simply select the user's groups as you create them. Administrator rights Version 4's admins can now do almost everything the account owner can do. They can create, edit and remove users, projects and more. There are some limits but these are basically safety checks like preventing delegated admins from editing the owner's details. As this is more power than "user-admins" had in v3, user-admins have not been migrated. You will need to set up your admin delegation again, in full knowledge of the additional trust you are placing in their hands. Project-centered model Services are now specific to a project; so you can define a project and simply say which services that project requires. As bugzilla is now specific to a project, users with bugzilla data will find it in a new 'bugz' project. Viewing a project displays its "home page", listing customizable information about the project, and access information for each of the project's services (svn, trac, etc). Access Permissions Each project has a list of users and groups who can see the project at all. Each service lists users and groups able to log into that service for that project, plus options for whether the service can be seen anonymously (without a login). This just says who can access the service at all; from there you need to have the right service-specific permissions set, much as you did in v3. For example, if you allow your "Developers" group access to Trac for a project, they can log into trac. Within Trac you will want to grant permissions like WIKI_EDIT, etc to let people do things once they're there. If you would like the public to be able to see your trac instance you will need to allow anonymous access to trac, then from within trac make sure the "anonymous" user has WIKI_VIEW permission. We suggest for most organizations setting up permissions based on groups; then you don't have to edit them each time you add a user. Just drop the user into the groups they need. Access Urls Some access Urls may change during migration. The current Url can be viewed from the "home page" for each project. It is worth testing the old Url as most will be kept backwards compatible. For web servies like Bugzilla and Trac, simply update your bookmarks. If you have existing working copies checked out for svn or cvs that you intend to keep using, you will need to update them to point at the new Url. Consider checking out a new copy first as this is simpler. If it's not practical, here is what you need to know: For Subversion, use the command: svn switch --relocate OLDURL NEWURL You can check on the old Url using the "svn info" command; for most people it will be only a small change to the Url. The better graphical Subversion clients like Tortoise have a "Relocate" option in the menus that does the same thing. For CVS, edit the CVS/Root file in EVERY folder in your working copy to point at the new access "Url". You might find the scripts here useful to do this in bulk: http://www.solarorange.com/docs/cvs/repositorymove.html. It is your responsibility to ensure these will work as expected for you. Support If you run into trouble, feel free to use the form on your "home" page to contact support and let us know about it. Please include any account names, Urls and details we might need to see the issue ourselves. Some patience may be required as we have not yet trained all our support staff with the V4 setup. To ensure your reply gets back to you, please check your email address is current and that your spam filters will not block "@cvsdude.net" and "@cvsdude.com" addresses. -- Stefan Teleman KDE e.V. stefan.teleman at gmail.com
