TARS Community Contributing

To get involved with TARS open source projects, you can first become a Contributor by participating in software construction and having at least one pull request merged into the source code. You'd better read TARS documentation and learn more about Open Source Guide

There are several ways for software developers to engage with the TARS community and become contributors

  1. Help other users and answer questions.
  2. Submit meaningful issues.
  3. Use TARS projects in production to increase testing scenarios.
  4. Improve technical documentations.
  5. Publish articles on applications and case studies related to TARS projects.
  6. Report or repair the bugs found in TARS software.
  7. Write source code analysis or annotate.

Contributing Your First Pull Request

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 from the TARS repository to your GitHub account.
  2. Git clone the repository to your local machine.
  3. Create a branch.
  4. Make changes to the code and test it on your local machine.
  5. Commit those changes and push to GitHub.
  6. Open a new pull request to submit your changes for review.
  7. We will check your changes after you submit it.
  8. Your changes will be merged into the master branch if accepted.

Now you did it! You’ve become a TARS Contributor, and you will receive a Contributor t-shirt!


A Committer is a contributor who has made distinct contributions to the TARS repositories and has accomplished at least one essential construction project or has repaired critical bugs. He or she can also take on some leadership opportunities.

The Committer is expected to

  1. Display excellent ability to make technical decisions.
  2. Have successfully submitted and merged more than five pull requests.
  3. Have contributed to the improvement of project code quality and performance.
  4. Have implemented significant features or fixed major bugs.
  5. After meeting the above requirements, you can submit a Committer request
    1. Provide your proof of the above criteria under Repo issue.
    2. Submit your pull request after you receive a response with instructions
    3. Once your application is accepted, you will become a TARS Committer!

As a Committer, you are able to

  1. Control the code quality as a whole.
  2. Respond to the pull requests submitted by the community.
  3. Mentor contributors to promote collaborations in the open source community.
  4. Attend regular meetings for committers.
  5. Know about project updates and trends in advance.

Maintainers are responsible for devising the subprojects in the TARS community. They will take the lead to make decisions associated with project development while holding power to merge branches. They should demonstrate excellent judgment and a sense of responsibility for subprojects’ well-being, as they need to define or approve design strategies suitable for developing subprojects.

The Maintainer is expected to

  1. Have a firm grasp of TARS technology.
  2. Be proactive in organizing technical seminars and put forward construction projects.
  3. Be able to handle more complicated problems in coding.
  4. Get unanimously approved by the technical support committee (TSC).

As a Maintainer, you have the right to

  1. Devise and decide the top-level technical design of subprojects.
  2. Define the technical direction and priority of sub-projects.
  3. Participate in version releases and ensure code quality.
  4. Guide Contributors and Committers to promote collaborations in the open source community.

Passionate about open source technology and community, Ambassadors promote and support extensive use of TARS technology to a wider audience of software developers. Ambassadors’ expertise and involvement in TARS projects will also acquire greater recognition in the community.

The Ambassador can

  1. Participate in TARS Foundation’s projects as a contributor, lecturer, or blogger.
  2. Engage with developers by presenting at community events or sharing technology articles on online media platforms.