Tigris.org Community Scope

• Tigris.org is a mid-sized open source community focused on building better tools for collaborative software development.
• You will not find thousands of unrelated projects here: every project fits into the Tigris mission.
• You will not find dead projects here: every project is welcomed into the community with a commitment to see it through and active developers cycle among related projects.
• Tigris.org is hosted by CollabNet, but the Tigris mission is one for the entire open source movement and one that has attracted senior open source developers from many organizations.

Maintaining the Tigris Vision: New Projects

In order to maintain and advance the Tigris mission, we invite new projects that strengthen the community scope. In order to keep the community strong and focused, we have established some basic ground rules for project creation:

• We are no longer accepting projects on any topic other than building software engineering tools.
• We are not accepting new student projects, unless the students are building a software engineering tool.
• We do not accept "personal projects". Every project must be building a software engineering tool that is useful to other people.
• We are not accepting new projects on these topics: games, content management systems, chat/IM.

If you have a project in mind that does not fit the Tigris.org mission, we encourage you to host your project on sourceforge.net, code.google.com, or a topic-specific community such as openoffice.org, netbeans.org, or dev.java.net.

Suggesting a project

If you'd like to create a project in the Tigris community, email a proposal to project-proposal, explaining your idea, including:

What is the goal of this project?

What is the scope of this project?

For example:

• Develop just enough functionality to scratch a particular itch
• Build a tool just like XYZ, but less broken
• Build the best XYZ-tool ever!

What are high-level features you are sure to build?

• What would you write on a billboard about your project? Users might only look for a few seconds.
• Use the issue tracker to track features and enhancement requests. It is not just for bugs, pre-populate it with feature descriptions so that potential contributors know what you would like them to work on.

What are the high-level assumptions or ground rules for the project?

For example:

• we will use programming language X on operating system Y for now.
• We will, or will not, consider certain functional areas like internationalization, high security, concurrency, etc. The list of functional areas will depend on what you are trying to do.