Creating a New Project¶
So - you are a freshly registered Tuleap user and you want to make your developer or project leader life easier. In other words you want to:
- Avoid the pain and cost of creating your own project infrastructure (with servers and backup)
- Avoid paying a premium price for commercial version control, defect tracking and task management tools
- Quickly setup a project environment that you can share with your colleagues, your partners, your contractors or your customers where ever they are while keeping your information safe and under control.
- Make your organization globally more productive and efficient by possibly letting others re-use your software and build on it.
If any of these points is appealing to you then you should definitely host your software project on Tuleap. Let’s see how you can do that.
Before you create a new project you must be a registered user (see Type of users). You then login and select the item “+ New Project” in the “Projects” dropdown of Tuleap Main Menu.
The project registration is an easy process:
Give the project short name and the project full name. Carefully read the restrictions that apply to both names before you type anything. The full name can be changed at any time in the life of the project. The short name cannot . So think about it twice before you make a decision!
You already registered a Tuleap project and would now like to reuse the same configuration (services, trackers, documents, references, …) ? Make your old project a template project (see Project Type) and you will find it here in the list of available project templates. Check your old project as template and your new registered project will be staffed as you are used to. If you don’t want to reuse a specific template just keep the Default Tuleap Template checked and go on.
The new project will use exactly the same configuration as the template. This includes that:
- the new project inherit the same dashboards and widget for project home page
- the new project is classified into the same trove categories as the template project (see Software Map (or Project Tree)).
- the same services are enabled (see Service Configuration). Unavailable services won’t be present. Disabled services will be disabled by default.
- the same reference patterns are defined (see Reference Overview).
- the same project specific user groups exist (see User Groups).
- all trackers with the option “instantiate for new projects” are copied with their associated fields, field values, field dependencies, reports, and permissions (see ?).
- the same forums are created (but the messages are not copied).
- the documents, as well as the document tree will be present.
- the SVN admin settings are copied but the emails and the SVN access permissions are not copied.
- the Git admin settings and global permissions are copied, but the emails and the Git access permissions are not copied.
- the file packages and their permissions are copied
- the CVS admin settings are copied (preamble, tracking mode, CVS Watch Mode), but the emails and the CVS permissions are not copied.
This is where the rubber hits the road! Tell us about your project. Give an accurate description. This is really important if you want to maximize the chance of re-use by others. Also list any information related to Intellectual Property like Invention Proposal or Patents related to the software whether pending or already filed. Give the list of software needed (whether internal or 3rd party) to make your own software run properly. And the last field is entirely for you. Write down all the things that you consider as crucial for your project or for the community of users.
Some categories can be mandatory for project creation. These categories are managed by your system administrator. More information about categorization in Software Map (or Project Tree).
Most of the time the only valid choice here is the default one: “SYS_ORG_NAME Code eXchange Policy”. As explained earlier in this document the Tuleap Team assisted by SYS_ORG_NAME lawyers have carefully crafted the Tuleap Policy and it is very unlikely that you need to create your own. If you do you’ll have to talk to us and to the SYS_ORG_NAME Legal Department to validate it. A number of truly Open Source licenses are also mentioned in the list. Finally you can also choose you own licensing conditions.
Last chance to review the submitted information before you send it to the Tuleap Team for validation. Don’t worry: the project members can later update all pieces of information shown on this page.
After you validate the project registration, the Tuleap Team reviews the information you submitted and decides to approve it or not. This process can take up to 24 hours but in most cases it’s less than a couple of hours. So far all projects have been accepted so there is little to fear … Shortly after the Tuleap Team approval you’ll receive an e-mail summarizing the characteristics of your project including a pointer to your new “Project Dashboard” page. Bookmark it in a safe place!
The first thing to do after you receive the confirmation for your project registration is to visit the “Project Dashboard” page (URL included in the e-mail) and finish the configuration of your project. The 2 following actions are the most frequent ones that have to be taken after a project is registered:
Categorize your project in the Software Map
If you haven’t done it during the project registration process, you should do it now! Your project categorization appears on your “Project Dashboard” page. To categorize your project select the “categorize it now” link and fill out the category form fields.
Build the project team
Once a project is created, the creator is assigned the role of project administrator on this project. It is her responsibility to define who are the project members and what their permissions are. This can be done by accessing the “Project Admin” page, typing the names of all the registered users promote as team members and then define their permissions.
|||Actually it can but you have to ask the Tuleap Team to do it for you.|