Occasionally, an individual or group may wish to host many projects on SourceForge.net, each under their own project space rather than all under a single project.
Users may submit a project proposal to serve as an umbrella project to administer all of the other related projects. The umbrella project can be used for things like defect management and documentation, and the individual projects be used for things like SCM. This sort of project split helps minimize the overhead of managing permissions for separate subteams and large teams.
Umbrella projects are registered in the standard manner. We evaluate requests for umbrella projects on a case-by-case basis. All of our project hosting policies apply to umbrella projects. Please indicate that you are making an umbrella project when registering the new project. Likewise, if you are making an existing project into an umbrella project, please indicate that when you create the child projects.
Umbrella projects do not have any action taken by SourceForge.net staff to cause them to be an "Umbrella" project. It is a logical designation and a concept to be used by project teams for organizational purposes of their project.
To notify the SourceForge.net team of the desire for a project submission to be an Umbrella project, simply detail this in the project registration description and detail the child projects that will fall under the Umbrella.