Login | Register
My pages Projects Community openCollabNet

There will be a brief maintenance window every Friday at 17:00 Pacific.
For further details, see CollabNet's maintenance and upgrade policy.

Tigris Vision

Overall Vision of the Tigris Project

Next

Much of the success of open-source development has resulted from each developer adding value within his or her individual area of expertise.

The Tigris platform provides the infrastructure needed for key developers to collaborate effectively across geographic distances and organizational boundaries.  These rapidly assembled teams can quickly react to technical challenges or create new opportunities.

The Tigris platform can benefit software development organizations in two main ways.  First, Tigris can provide a complete solution for open source development hosting.  Hosting an open source project can help existing software development organizations leverage the skills and interest of the open-source community.

Tigris is also positioned to be a focal point for the community around the further development of the Tigris platform and the associated suite of tools.  We will support the community by supporting known open-source best practices as well as developing new tools that further enhance collaboration as well as integrating existing tools into a coherent platform.

Axioms

Prev | Next

Axioms are "atomic" statements that are not argued. These statements underly the definitions and discussion that follows.

A1. The first goal of collaboration is to produce and maintain a set of desired artifacts.

A2. The second goal of collaboration is the satisfaction of the participants.

A3. Collaborative space consists of artifacts. The dimensions of that space are defined by the types of artifacts available.

A4. Collaborative time consists of events and milestones.

A5. Participants play roles in collaborartions (a many-to-many relationship). Participants may play different roles in different collaborations.

Definitions

Prev | Next

Collaboration: An activity where multiple people work together to define and maintain artifacts. Each project has goals (requirements artiacts) and deliverables (implementation artifacts). Project deliverables are consumed by the participants and other members of the community. When working together, people must share artifacts and coordinate their activities over time.

Community: A group of people who are interested in a set of projects. Most people in the community are not partipants in any project.

Domain: A space (website) with mulltiple, related projects that are of interest to a community.

Project: The unit of space for collaboration. Projects have members who play roles. Projects contain artifacts.

Artifact: a database record or document containing data that is relevant to the project. Since members collaborate over time, artifacts must be

Events: Changes to the state of artifacts or participants. E.g. checking in a file, addnig a new item, adding a member.

Milestones: Conditions on the state of artifacts. E.g., all M1 features implemented, all P1 issues closed.


Tigris Collaborative Components

Prev | Next

The unique nature of the Open Source software development cycle has led to the evolution of "Best Practices" that support specific needs of developer's and the overall community.

Some of the key Open Source "Best Practices" that are to be supported under Tigris are:

  • Technical Communications
  • Version Control, Document Management, and Distribution
  • Quality Assurance
  • Build and Test Management
  • Project Management
  • Knowledge Management

    Support for Open Source best practices will be embodied in a set of collaborative components that we plan to use to build all the tools in the Tigris tool set.

    Tigris Collaborative Components

The Open Source Community's Best Practices

Prev | Next

The unique nature of the Open Source software development cycle has led to the evolution of "Best Practices" that support specific needs of developer's and the overall community.

Some of the key Open Source "Best Practices" that are to be supported under Tigris are:

  • Technical Communications
  • Version Control, Document Management, and Distribution
  • Quality Assurance
  • Build and Test Management
  • Project Management
  • Knowledge Management

    Support for Open Source best practices will be embodied in a set of collaborative components that we plan to use to build all the tools in the Tigris tool set.

    Open Source Best Practices