Managing a project
Managing a project is not hard, but does require time and passion. Most of the important activities you need to think about are covered in the topic Growing a successful project.
This topic provides links to the information you need to understand the main components of a Nokia Project, and to manage and administer your project. Effectively it is another index into the project functionality and the documentation on this wiki.
Permissions, Users and Groups
All access to the project is controlled through groups. Groups are created with permissions that grant various view, modification and deletion rights; users are then added to these groups.
You can define your own group and permission structure if you want, but 90% of project owners are likely to be happy with the ones generated during project creation (to support the private or public project configurations). If so, then all you'll need to do is periodically add new users to the existing groups.
See ProjectsGroupPermissions for information on working with groups, permissions and users.
Tickets
Tickets are a good way to track defects, enhancements or tasks, and to mark them as completed when the work is done. They can be mapped to specific components, versions and milestones, and are automatically used by Trac to create your project roadmap.
Creating a ticket is straightforward - the best way to learn how to use them is to create one. If you need help, the official documentation is in the article TracTickets.
You can also customise the values of many of the ticket attributes in the Admin tab, Tickets section. Customisable values include: Components, Milestones, Priorities, Resolutions, Severities, Ticket Types, Versions and Milestones.
Discussion forums
Forums provide a place for you to discuss all aspects of your project with your users and team members. This is a great place to involve and motivate your community.
By default projects are created with a discussion board for "announcements" and a single board for general discussion. As an administrator you can create additional forums as needed in the Admin tab, Forums section, and also control forum visibility and permissions.
Version control
You project's version control URL is shown in the Storages admin panel. Give the address to your team members that are allowed to use version control. Details of how version control tool should be used is explained in the version control tool manual. Users with VERSION_CONTROL or TRAC_ADMIN right can read and write repository. Users with VERSION_CONTROL_READ can read the repository. With BROWSE_SOURCE privilege user can browse source in the project "Browse Source" tab.
In general all users should be allowed to browse and checkout the source, but only project members should be allowed to commit changes. See ProjectsVersionControl for more information
Software releases
Software releases are managed through the Downloads system. This is a tab where you can upload your releases and then mark them as "Featured" in order to make them visible as Featured Downloads on the project summary page.
The system also allows you to track the number of downloads of each release.
Share files with your team
The Files section makes it easy to share non-source files with your team. You can also use the wiki - the Files system is helpful particular for storing existing files and for capturing information that doesn't readily render in wiki.
Document your project
The wiki provides a great place for you to record information about your project - particularly information that will make it easier for your team members to get up to speed. WikiFormatting and TracWiki provide an overview of the main formatting options.
Make your project a success
The best way to recruit participants and make your project a success is to generate good publicity. This can be through simple approaches like having a pretty icon and project description through to giving truly excellent support to your users. We outline some other good ideas in Growing a successful project.
