Registering an OSS Project
Last updated
Last updated
Once your project is registered, it will be visible within the tea community, attracting potential supporters, contributors and users. You can also track the utilization and impact of your project, which can earn you rewards based on its value and receive vulnerabilities reports from other members of the tea community. Registering your project on the tea protocol showcases your commitment to the sustainability and integrity of open-source software.
Registering your OSS project on the tea protocol offers several benefits. It allows you to gain visibility within the tea community, attract potential contributors and users, and track the utilization and impact of your project. This data can be used to earn rewards based on the value of your project. Additionally, registering your project on the tea protocol incentivizes security researchers to disclose vulnerabilities ethically and responsibly.
The tea protocol introduces the concept of teaRank, which measures a project's utilization or dependents in the open-source ecosystem. A project's teaRank is calculated using the Proof of Contribution algorithm, which assesses the project's impact on the entire open-source software ecosystem.
Based on your project's teaRank, the protocol determines the number of rewards to be distributed on a daily basis. Higher teaRank, achieved through more (reputable) open-source software depending on your project, results in more rewards. However, earning rewards is not limited to teaRank alone. Projects can also earn rewards from community members who stake their TEA on them. When community members stake their TEA on your project, they signify their belief and support for your project and empower your project with additional incentives by distributing a portion of their staking rewards to your project's treasury.
To register an OSS project on the protocol you need to follow these steps:
IMPORTANT - YOU CAN ONLY REGISTER PROJECTS THAT YOU ARE A CORE CONTRIBUTOR TO AND FOR WHICH YOU HAVE PERMISSION TO PERFORM DIRECT COMMITS.
Visit the tea web app and log in to your tea protocol account.
Go to the "My OSS Projects" section.
Provide the project’s name.
Make sure to double check that it's the correct project by checking its package manager and URL.
Continue to your project's constitution configuration screen, where you can decide to add contributors. The quorum rules define the minimum number of contributors required to approve any treasury disbursement, any treasury deposits, manage vulnerability reports, govern voting, etc.
You will need to download your project's constitution file, and manually commit the file to your project's repository. For more information on what the constitution file is, check out this FAQ.
Once the file is committed, click on "Validate Constitution". Once the file's presence in the repo is confirmed and contents validated, the tea Protocol will deploy the project's treasury (on-chain account). You can find your project's on-chain address in the project details page.
If the tea Application shows an error message indicating that your project is missing a URL, the most likely cause is that you need to update the package metadata that you published to include your project's URL. For each package, we index a specific field to build the URL, and enable project registration.
Package Manager | URL Field | Source |
---|---|---|
NPM
repository
package.json
PyPI
project_urls.Source
You can use setup, or pyproject.toml to specify this
rubygems
source_code_uri
spec.metadata.source_code_uri in the gemfile, or gemspec
crates
repository
Cargo.toml, under the packages section
Homebrew
parsed.stable.url
Homebrew Formula: https://github.com/Homebrew/homebrew-core/tree/master/Formula
PKGX
url
Pkgx yaml files: https://github.com/pkgxdev/pantry/tree/main/projects