Version 3



    Send an email to helpdesk@ requesting a new subversion repository.  Mention if it needs anonymous Subversion and Fisheye configuration (typically they do).  Denote who the admin(s) of the project are to be.


    Mailing Lists


    Send an email to helpdesk@ requesting new lists.  Denote who the moderator should be.




    Subversion space


    Use Subversion to copy the template project from



    to the new project's directory


    For instance, assuming you have a working copy, and you're in the members/ directory:


    svn cp template new_project


    Edit the new_project/project.xml file, paying particular attention to the projectId element.


    Commit these changes.  It's always wise to use xmllint after making changes to a project.xml.


    To make the project visible and active, edit



    Add a line for the new project, and either denote a new or existing role, depending on the way the project needs to be configured.  Use the projectId.


    <project level="community" edit-permission="new_project-admin">new_project</project>


    Roles in Portal


    Login to the portal admin screen, and create a new role matching the one from the projects.xml if a new one is needed.


    Find each project member, and grant them the role.  This will enable them to edit content through the web and administer the project settings and configuration.


    Roles in Subversion


    Since we manage CMS through Subversion, a bundle of lines need to be created for the SVN ACLs.





    The easiest way is to simply copy the lines from an existing project.


    First, create a new SVN role and allow them full read access to the CMS repository.  new_project is the projectId of the new project for this example.


    Add this line under the / path




    Then, for the project's own CMS directory (created by copying the template/ directory), grant the role full read/write access


    Add a block for the project's path:




    And grant access:




    Then, historically, we give them R/W access to an externals directory.  Historically, no one really uses it.






    Finally, create the role member list:





    Create a new project in JIRA and use the Default Notification Scheme and Default Permission Scheme to start.  This throws all notifications to the general JBoss list, and requires Committer role to work on the project.


    Make sure the JIRA is denoted in the project's project.xml in CMS.




    Tell the project leads they can create pages as they need.  Suggest using sub-directories for organization and namespaces.




    Email helpdesk@, ask for new forum provisioning and denote who should be the moderator.