As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however, your page view may include additional administrative links and options.  Your Project Resources toolbar also includes an additional Admin link enabling you to edit your project home page and appearance throughout the site.

If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may:

• invite additional developer participants
• update your project's home page
• publish project news
• upload project files and documents
• post to your project's mailing lists
• create subdirectories in your project's CVS repository
• check in source code
• use the issue tracker to enter and search project issues.

While still in a pending approval status you cannot perform the following tasks:

• add project members
• approve project membership requests
• grant project roles.

The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.

Project type will strongly influence the method in which you manage projects.  If your project is a proprietary endeavor with commercial licensing, project governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.

If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for establishing and communicating the project's parameters up front. As the project progresses, the project owner will need to nurture project participants toward an increasing sense of community and ownership.

A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.

Whichever scenario applies, answering the questions below will help you to communicate the fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects, most can be applied to collaborative and proprietary projects as well. Consider the following:

• What is the ultimate mission of the project?

• What decision making and conflict resolution methodology will be used for the project(for example, voting, consensus building, or final authority)? 

• What coding standards will be used  for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?

• What methods will be used to help project members gain responsibility and ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?

• What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?