TARS Community Contributing

TARS Community has Maintainer, Committer and Contributor with their responsibilities.

To encourage more people to join TARS community and refine it, the community consists of many special interest team (SIT). There are two different kinds of SIT, Technical Special Interest Team (TSIT) and General Special Interest Team (GSIT).

Technical Special Interest Team

TSIT (Technical Special Interest Team) is responsible for the development and maintenance of a certain TARS module and guarantee code quality.
The Tech Leads of every SIT invite contributors join it and teach them. Members of SIT will train technical skills and optimize the module simultaneously. They can gradually become a community-recognized Committer or even a Tech Lead. Generally speaking, each SIT will periodically organize meetings to discuss recent progress and problems encountered. All meeting discussions are open to the community, so that interested persons can participate and discuss together.

The existing TSIT is categorized by different programming languages, including C ++ SIT, PHPSIT, GoSIT and so on. 1-3 Tech Leads per SIT. Downwards, it can be subdivided into more subSIT and split according to specific functional requirements. Determined by Tech Lead.

General Special Interest Team

GSIT is a community developer gathered to achieve a specific goal. Some may span multiple SITs, while some may only focus on a specific SIT to do a specific thing.

GSIT has a life cycle and can be dissolved once the goal is completed. In general, GSIT will also have periodic meetings to summarize the current project progress and determine the next implementation plan.


Community contributors who have one or more PRs merged in the project repo.
For persons who have never or rarely participated in open source projects, we recommend reading the TARS document and learning more about open source, like open source guide.

Ways of participation

  1. Answer technical questions
  2. Testing projects
  3. Improve technical documentation
  4. Submit valuable issues
  5. Report or fix unknown / known bugs
  6. Write articles or practical cases for the project

Contribute your first PR!

We encourage everyone to participate in the community through various ways such as project testing, documentation, and bug reporting. Contribute your first PR now!

  1. Fork the project
  2. Clone your fork (If you cloned a while ago, get the latest changes from upstream)
  3. Create a new topic branch
  4. Coding and testing
  5. Commit your changes and push your topic branch up to your fork
  6. Open a Pull Request with a clear title and description
  7. Code review by project members. They will check whether there is bug or typo in your code or description. Please pay attention to comments in your PR. If everything is okay, your PR will be merged. Congratulations to become the TARS contributor!

Outstanding contributors who completed at least one feature or fixed major bugs independently.

How to be a Committer

  1. Good technical judgment
  2. Submitted and merged a certain number (> 5) of PR
  3. Make outstanding contributions to TARS performance improvement or implement important features or fix major bugs
  4. Submit committer application
    1. Open issue in AUTHORS file and prove your PR records in the issue (especially for major feature / fix fixed)
    2. According to format of AUTHORS, open PR
    3. If you are qualified, we will merge your PR
    4. Congratulation to be the TARS Committer!

Rights and responsibilities

  1. Overall control of the code quality of the project
  2. Respond to PRs and Issues by the community in time
  3. Guide Contributors
  4. Participate in Committer meetings and have priority to know about project development

The planner and designer of the project who have the authority to merge trunk branches.
They must show good judgment and responsibility for the health of the subproject. The maintainer must set these technical responsibilities directly or by delegating these responsibilities and make or approve design decisions for subprojects.

How to be a Maintainer

  1. Have a very deep understanding of TARS technical goals and directions
  2. Actively organize technical seminars and propose constructive suggestions
  3. Can handle complex problems in code implementation
  4. PMC / Tech Lead voted unanimously

Rights and responsibilities

  1. Make technical design and decisions of sub-projects.
  2. Set the technical direction and priority of subprojects
  3. Set version release plan and project development route
  4. Guide Contributors and Committers
  5. Ensure the quality of the subproject