From 91c715a8e309907d65e00ed5b6f8a40ef031de16 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Sat, 11 Jul 2026 12:58:14 -0500 Subject: [PATCH 01/12] feat: initial CC program writeup --- .../TIP-PROC-0006_core_contributor_program.md | 228 ++++++++++++++++++ src/SUMMARY.md | 3 +- 2 files changed, 230 insertions(+), 1 deletion(-) create mode 100644 src/Process/TIP-PROC-0006_core_contributor_program.md diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md new file mode 100644 index 00000000..afece408 --- /dev/null +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -0,0 +1,228 @@ +# P-TIP-PROC-6: Core Contributor Program + +| TIP | [P-TIP-PROC-6](#p-tip-proc-6-core-contributor-program) | +|---------------|--------------------------------------------------------| +| Title | Core Contributor Program | +| Last Modified | 2026-07-11 | +| Authors | Fox Piacenti <fox@vulpinity.com> | +| Status | Proposed | +| Type | Process | +| Created | 2026-07-11 | + +## Overview + +The Core Contributor (CC) program enables community members who have demonstrated the three Cs-- Conduct, Caliber, and +Commitment, to take ownership and responsibility of elements of the Tari project. + +Core Contributors (CCs) are empowered to make on-the-ground decisions about the project, +and [elect the Tari Council][CouncilElection]. + +## Motivation + +Tari is for everyone. It is a community project. To better distribute the work of the project, improve governance, +reduce silos, and set standards, the core contributor program enables community members with demonstrated Commitment, +Conduct, and Caliber ([the three Cs](#requirements)) to have greater stake in the project's success and say in the +project's direction. + +## Requirements + +All Core Contributors are expected to meet the three Cs: + +* Commitment: Core Contributors must demonstrate a firm commitment to the project, maintaining continuous contribution. +* Conduct: Core Contributors must be welcoming, helpful, and able to disagree without resorting to attacks. They must + demonstrate good judgment and give other community members a fair shake. They must not disparage others for personal + attributes beyond their control, should retain a polite demeanor, and should give feedback constructively. +* Caliber: Core Contributors must demonstrate competence in their domain. They must demonstrate excellence in their + community work, and must hold their fellow core contributors to high standards, mentoring prospective Core + Contributors and new contributors. + +Core Contributors may have additional requirements based on their [category](#categories) or +[rights](#contributor-powers-and-rights). + +Core Contributors are expected to maintain the three Cs and other requirements before and during their tenure. Core +Contributors who lapse in their commitment, conduct, and caliber [may be removed](#involuntary-exits). + +## Contributor Powers and Rights + +Core Contributors may be appointed and given power to handle any element of the project which is not the exclusive +responsibility of the council. For an example, a core contributor can be granted: + +* commit or maintainer rights on a code repository +* access to social media accounts +* forum/chat moderation powers +* DNS administration capabilities +* server and online service access +* seat licenses to software +* signature powers for specific wallets +* project management responsibilities +* ...or other assets which the Tari Foundation and Council hold in trust by the community. + +For counterexample, a core contributor may not be granted: + +* the right to vote on behalf of a council member +* the ability to bind the community, Tari Council, or the Tari Foundation to contract +* final say on high-level budgetary decisions, though they may advise them + +### Scoping + +As part of [their nomination](#nomination), a list of requested grants shall be made. Acceptance of nomination will be +acceptance of the requested grants, and only those grants unless further grants can be directly inferred. For example, +if all code CCs are given access to a specific Continuing Integration service or code assistance tool, then granting +committer access to a repository grants this as well. It would not, however, grant access to all other repositories. + +### Categories + +Core Contributors are organized into categories for administrative convenience. Categories may be granted access or +licenses to specific resources en masse, and may have categorical expectations and responsibilities as part of their +work. Core Contributors may be part of multiple categories, or may have no category. Core Contributors are permitted to +contribute in areas outside their category, but may not be granted specific rights and responsibilities of those +categories without membership. + +For example, Code CCs have merge rights over their respective repositories, and may be required to triage +and/or review pull requests on their repositories. A design contributor or project manager can still contribute pull +requests, review, and may assist in triage, but they would not be required to, nor would they have merge rights. + +The current categories are: + +* [Code](#code-ccs) +* [Product](#product-ccs) +* [Community](#community-ccs) +* [Project](#product-ccs). + +A brief overview of each category is below. Further refinement of expectations and requirements for each may be +submitted in subsequent TIPs. + +To distinguish between, for instance, all code contributors and specifically Core Contributors in the Code Category, we +will use 'code contributors' for the former and 'Code CCs' for the latter. + +#### Code CCs + +Code CCs are community members with demonstrated software engineering skills who have consistently delivered +high quality code contributions to the Tari project. Code CCs are inducted with commit rights to one or more +repositories. Commit rights involve the right and responsibility to commit high quality code to the official public +repositories of the project. + +Code CCs are expected to follow best practices in software engineering. These include, but are not limited to: + +1. Not committing directly to special branches (such as 'main') but using a pull request instead +2. Having all code reviewed by at least one human reviewer +3. Reviewing code of other contributors +4. Writing automated tests for code whenever reasonable automated tests can be written, and providing detailed testing + instructions when not +5. Including documentation and testing instructions with changes + +Code CCs may elect to use code generation tools according to their judgment. They must, however, bear +responsibility for generated code, and must review any code generated before requesting another contributor to review +their pull requests. They must not commit code they do not understand to their respective repositories, and are expected +to guard their repositories from code which does not follow best practices via the review process. + +#### Product CCs + +Product CCs guide the holistic implementation of features by providing UI/UX designs that contributors can +implement via code, and by carefully considering the whole impact of a feature for real-world users. They provide review +of new features and may provide art such as iconography which aids in communicating a product's functionality. + +Product CCs are expected to review product TIPs and feature requests to assist in their prioritization and +design. They assist the community by rethinking how we meet the needs of the ever-evolving real-world needs of users. + +#### Project CCs + +Project CCs are team members who are in charge of large community-wide projects and/or who perform critical +metawork that helps the Tari project run smoothly. Project CCs may do things like: + +* Coordinating work between contributors to deliver strategic objectives set by the council +* Assisting with administration of the project, such as managing access to resources, or onboarding/offboarding + Core Contributors and council members +* Coordinating dates, schedules, and other resources to ensure project delivery +* Ensure that TIP-defined processes are followed and contribute updates and new processes where appropriate +* Flesh out day-to-day processes implied but not explicitly defined by TIPs +* Run large-scale events beyond the scope of what Community CCs handle on their own + +#### Community CCs + +Community CCs help with day-to-day community affairs. Community CCs might do things like: + +* Moderate chats and forums +* Run day-to-day community events +* Craft messaging for social media and public announcements, ensuring messaging is tailored for each venue +* Provide art and design for marketing campaigns +* Work with Project CCs to run large-scale events +* Translate resources and run language-specific discussions and community events + +## Nomination + +Any member of the community may be nominated by a Core Contributor or may nominate themselves. Core Contributor +nominations shall be posted in an appropriate forum category. Any nomination should contain the following: + +* Who is being nominated +* What rights and contributor categories they are being nominated for +* Evidence that they meet [the requirements for being a Core Contributor](#requirements) +* Evidence that they hold competencies in any categories or for any rights they're being nominated for +* A date, 14 business days from the date of posting, by which any votes for or against their candidacy must be given + +For example: + +> I am nominating JimBob for the Core Contributor program as a Code CC, with commit rights to the simulations +> repository. +> +> JimBob has been a contributor of code to our repositories for several months, and proved his excellence when +> implementing spline reticulation. He is very helpful on the forums, always has a good attitude, and contributes +> quality code. You can review some of his pull requests here: +> +> Link 1 +> Link 2 +> Link 3 +> +> Please provide your vote and feedback by August 24th! + +Core Contributors should reply to the thread either with affirmative votes or with nos. Nos should be accompanied by +feedback. The attitude of feedback should not be 'never' but 'not yet', explaining what improvements the current Core +Contributors would need to see before approving their addition to the team. + +The nomination will be considered approved if five Core Contributors give an affirmative vote and there are not any 'no' +votes by the time the feedback period has ended. In the event (such as when initially starting the program) there are +not five Core Contributors, Tari Council members may vote for the contributor's candidacy. + +### Rights Expansion + +Expansion of rights is done similar to [nomination](#nomination). A forum post requesting rights or category expansion, +with reason given and evidence of competency supplied, shall be made. If after 7 working days there are at least three +affirmative votes and no negative votes, access shall be granted. Voting rights are the same as described in +[Nomination](#nomination). + +## Exiting the Program + +A Core Contributor who is either unable or unwilling to continue their work as a core contributor may exit the program. + +### Voluntary Exits + +Core Contributors are people. They may be called to new projects, may lose interest, or may lose any sponsorship that +assisted their role as contributor. Whatever the reason, a Core Contributor may submit their resignation to the Council +at any time. They will then be offboarded from the program. To leave in good standing, a notice period of at least two +weeks and good faith work to perform clean handoffs are required. + +### Involuntary Exits + +If a Core Contributor fails to meet the standards of Commitment, Conduct, and Caliber required of the program, and no +remediation is possible or forthcoming (such as a major breach of trust, a refusal to address critical feedback, or +extended lack of contribution) they may be removed from the program and have all access revoked by the +council. + +In the event an involuntary removal occurs, a public reason for this removal must be published by the council within +72 hours of the action taken. + +## Council Voting + +Core Contributors are the exclusive electors of the council. Council members who are not core contributors do not have +voting rights for council membership, as the core contributors are the workers who choose their leaders. Councilors are +encouraged to become Core Contributors either before or during their tenure, but this is not a requirement. + +Two months before a Councilor's term is up, nominations shall be solicited from the community for any who would like to +hold the position. The current incumbent must affirmatively and publicly indicate they wish to continue their tenure +during this time. Nomination closes one month plus one week before the councilor's term ends. + +After one week of setup for voting, elections shall begin, with two weeks for each Core Contributor to submit their +ranked choice (AKA 'instant run-off') ballot. The final two weeks between terms will be used for onboarding and +hand-off, with decision-making power only manifesting when the new electee's term begins. + +[CouncilElection]: ../TIP-0002_tari_community_charter.md#article-vii-nomination-and-selection \ No newline at end of file diff --git a/src/SUMMARY.md b/src/SUMMARY.md index bde51a7a..868903ab 100644 --- a/src/SUMMARY.md +++ b/src/SUMMARY.md @@ -5,7 +5,8 @@ - [P-TIP-PROC-1: Tari Improvement Proposals](TIP-0001_tari_improvement_proposals.md) - [A-TIP-PROC-2: The Tari Community Charter](TIP-0002_tari_community_charter.md) - [P-TIP-PROC-3: Community Forums](TIP-0003_community_forums.md) -- [A-TIP-0005: Adjust Bridge Limits](Process/TIP-PROC-0005_adjust_bridge_limits.md) +- [A-TIP-PROC-0005: Adjust Bridge Limits](Process/TIP-PROC-0005_adjust_bridge_limits.md) +- [P-TIP-PROC-0006: Core Contributor Program](Process/TIP-PROC-0006_core_contributor_program.md) - [RFC-0001: An overview of the Tari network](RFC-0001_overview.md) - [The Tari Base Layer](base_layer.md) - [RFC-0110: Base nodes](RFC-0110_BaseNodes.md) From f861cba411bd562e21a2bd1393f45a2a392b6cef Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Tue, 14 Jul 2026 10:11:49 -0500 Subject: [PATCH 02/12] fix: address notes on CC program --- .../TIP-PROC-0006_core_contributor_program.md | 90 +++++++++++++++++-- 1 file changed, 81 insertions(+), 9 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index afece408..a9705e20 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -53,7 +53,7 @@ responsibility of the council. For an example, a core contributor can be granted * DNS administration capabilities * server and online service access * seat licenses to software -* signature powers for specific wallets +* signature powers for specific wallets (if also approved by supermajority (2/3) council vote) * project management responsibilities * ...or other assets which the Tari Foundation and Council hold in trust by the community. @@ -86,6 +86,7 @@ The current categories are: * [Code](#code-ccs) * [Product](#product-ccs) +* [Ecosystem](#ecosystem-ccs) * [Community](#community-ccs) * [Project](#product-ccs). @@ -116,6 +117,14 @@ responsibility for generated code, and must review any code generated before req their pull requests. They must not commit code they do not understand to their respective repositories, and are expected to guard their repositories from code which does not follow best practices via the review process. +**Examples Code CC readiness:** + +* Delivering multiple major features at high quality +* Delivering many thoughtful code improvements every month for at least three months. +* Providing constructive code review with a keen eye for other contributors +* Writing up issues and bugs with clear descriptions and acceptance criteria +* Provides quality tests with code contributed + #### Product CCs Product CCs guide the holistic implementation of features by providing UI/UX designs that contributors can @@ -125,6 +134,47 @@ of new features and may provide art such as iconography which aids in communicat Product CCs are expected to review product TIPs and feature requests to assist in their prioritization and design. They assist the community by rethinking how we meet the needs of the ever-evolving real-world needs of users. +**Examples of Product CC readiness:** + +* Delivers multiple quality feature proposals with UI/UX Designs that are accepted for development +* Delivers multiple enhancements to existing features via improved UI/UX designs that are accepted for development +* Demonstrates skill in working with developers and project contributors to verify and validate feature changes against + designs + +#### Ecosystem CCs + +Ecosystem CCs grow Tari beyond its own repositories: the integrations, partnerships, and real-world adoption built on +top of the protocol. Ecosystem CCs might do things like: + +* Source and support integrations with exchanges, wallets, payment processors, and other protocols +* Source and develop partnerships with businesses and institutions that bring real-world usage to Tari +* Support third-party teams building on Tari with onboarding, technical liaison, and go-to-market help +* Represent Tari with enterprises, at industry events, and in adjacent ecosystems +* Advise the council on ecosystem strategy, deal structure, and market development + +**Examples of Ecosystem CC readiness:** + +* Demonstrates decorum, clarity, technical acumen and helpfulness in onboarding community members with wallets and other + Tari software +* Maintains a welcoming attitude toward others +* Performs live presentation demos of technology and products +* Makes quality referrals to and from the Tari community and other teams + +#### Infrastructure CCs + +Infrastructure CCs run Tari-project managed infrastructure. They are charged with keeping community resources in working +order. Infrastructure CCs might do things like: + +* Run and maintain boostrap/seed nodes +* Perform DevOps work on servers and web applications such as the forums +* Maintain mining guides and establish best practices for deploying Tari tools + +**Examples of Infrastructure CC readiness:** + +* Demonstrated ability to deploy and maintain services +* Assists community members in mining and software setup +* Writes guides and contributes documentation for practical deployments + #### Project CCs Project CCs are team members who are in charge of large community-wide projects and/or who perform critical @@ -138,6 +188,13 @@ metawork that helps the Tari project run smoothly. Project CCs may do things lik * Flesh out day-to-day processes implied but not explicitly defined by TIPs * Run large-scale events beyond the scope of what Community CCs handle on their own +**Examples of Project CC readiness:** + +* Self-starts projects and recruits community members to deliver value to the community +* Assists in coordinating workgroup activities +* Gives quality feedback on items like feature and initiative prioritization +* Is able to work amicably with a wide swath of people from varying backgrounds and viewpoints + #### Community CCs Community CCs help with day-to-day community affairs. Community CCs might do things like: @@ -149,6 +206,14 @@ Community CCs help with day-to-day community affairs. Community CCs might do thi * Work with Project CCs to run large-scale events * Translate resources and run language-specific discussions and community events +**Examples of Community CC Readiness:** + +* Conducts themselves in public chats/forums with decorum and a welcoming demeanor +* Assists in mediation when tempers flare, and does not stoke flames +* Helps newcomers and points them in constructive directions +* Brings useful discussion topics to the table +* Assists in running community events + ## Nomination Any member of the community may be nominated by a Core Contributor or may nominate themselves. Core Contributor @@ -156,9 +221,9 @@ nominations shall be posted in an appropriate forum category. Any nomination sho * Who is being nominated * What rights and contributor categories they are being nominated for -* Evidence that they meet [the requirements for being a Core Contributor](#requirements) +* Evidence that they meet [the requirements for being a Core Contributor](#requirements), as links and/or testimony * Evidence that they hold competencies in any categories or for any rights they're being nominated for -* A date, 14 business days from the date of posting, by which any votes for or against their candidacy must be given +* A date, 10 business days from the date of posting, by which any votes for or against their candidacy must be given For example: @@ -183,10 +248,15 @@ The nomination will be considered approved if five Core Contributors give an aff votes by the time the feedback period has ended. In the event (such as when initially starting the program) there are not five Core Contributors, Tari Council members may vote for the contributor's candidacy. +In the event of an explicit 'no' vote, the candidate may elect to appeal to the Tari Council. The Tari Council will +consider the application of the candidate, and vote on the applicant's candidacy. The candidate will be approved if the +Council decides in their favor with a supermajority (2/3). They will vote and publish their decision on admission within +10 business days, including reasoning and their view of the evidence in light of the standards in this document. + ### Rights Expansion Expansion of rights is done similar to [nomination](#nomination). A forum post requesting rights or category expansion, -with reason given and evidence of competency supplied, shall be made. If after 7 working days there are at least three +with reason given and evidence of competency supplied, shall be made. If after 5 working days there are at least three affirmative votes and no negative votes, access shall be granted. Voting rights are the same as described in [Nomination](#nomination). @@ -198,18 +268,20 @@ A Core Contributor who is either unable or unwilling to continue their work as a Core Contributors are people. They may be called to new projects, may lose interest, or may lose any sponsorship that assisted their role as contributor. Whatever the reason, a Core Contributor may submit their resignation to the Council -at any time. They will then be offboarded from the program. To leave in good standing, a notice period of at least two -weeks and good faith work to perform clean handoffs are required. +at any time. They will then be offboarded from the program. To leave in good standing, a notice period of at least ten +business days and good faith work to perform clean handoffs are required. ### Involuntary Exits If a Core Contributor fails to meet the standards of Commitment, Conduct, and Caliber required of the program, and no remediation is possible or forthcoming (such as a major breach of trust, a refusal to address critical feedback, or -extended lack of contribution) they may be removed from the program and have all access revoked by the -council. +extended lack of contribution) they may be removed from the program by a majority vote of the council and have all +CC rights revoked. In the event an involuntary removal occurs, a public reason for this removal must be published by the council within -72 hours of the action taken. +72 hours of the action taken. The removed may appeal to the council within 5 business days, and upon appeal, the council +will consider their evidence and will vote once more, requiring a supermajority (2/3) to maintain removal. +They shall vote and publish their verdict within 5 business days of the appeal being posted. ## Council Voting From cc3ff79a0dc3be05f8cb23acbaf853547744cd2c Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Tue, 14 Jul 2026 10:18:38 -0500 Subject: [PATCH 03/12] fix: project ccs anchor link --- src/Process/TIP-PROC-0006_core_contributor_program.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index a9705e20..4ff0bae0 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -88,7 +88,7 @@ The current categories are: * [Product](#product-ccs) * [Ecosystem](#ecosystem-ccs) * [Community](#community-ccs) -* [Project](#product-ccs). +* [Project](#project-ccs). A brief overview of each category is below. Further refinement of expectations and requirements for each may be submitted in subsequent TIPs. From 0057877992aef31c90943d7b1d09dc40fcb440b7 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Wed, 15 Jul 2026 05:42:17 -0500 Subject: [PATCH 04/12] feat: add corporate disclosure requirement to CC nomination --- src/Process/TIP-PROC-0006_core_contributor_program.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 4ff0bae0..1504e860 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -223,6 +223,7 @@ nominations shall be posted in an appropriate forum category. Any nomination sho * What rights and contributor categories they are being nominated for * Evidence that they meet [the requirements for being a Core Contributor](#requirements), as links and/or testimony * Evidence that they hold competencies in any categories or for any rights they're being nominated for +* **Any corporate entity which is sponsoring their contributions** * A date, 10 business days from the date of posting, by which any votes for or against their candidacy must be given For example: @@ -237,6 +238,8 @@ For example: > Link 1 > Link 2 > Link 3 +> +> JimBob's contributions are backed by CompanyName Inc. > > Please provide your vote and feedback by August 24th! From 382cb1104536b6c2a00cd723e3fcd40b7b753ec4 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Wed, 15 Jul 2026 15:32:50 -0500 Subject: [PATCH 05/12] fix: six month minimum participation for CC nomination --- src/Process/TIP-PROC-0006_core_contributor_program.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 1504e860..def2c0d4 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -42,6 +42,8 @@ Core Contributors may have additional requirements based on their [category](#ca Core Contributors are expected to maintain the three Cs and other requirements before and during their tenure. Core Contributors who lapse in their commitment, conduct, and caliber [may be removed](#involuntary-exits). +At a minimum, all Core Contributors must have at least six months of history and participation in the Tari project. + ## Contributor Powers and Rights Core Contributors may be appointed and given power to handle any element of the project which is not the exclusive From 931a96ca7516dd3fd08bc75928d9aa12aaecdcff Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Sun, 19 Jul 2026 19:14:06 -0500 Subject: [PATCH 06/12] fix: better phrasing on wallets, unanimity for CC vote override --- src/Process/TIP-PROC-0006_core_contributor_program.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index def2c0d4..3f7df4bb 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -55,7 +55,7 @@ responsibility of the council. For an example, a core contributor can be granted * DNS administration capabilities * server and online service access * seat licenses to software -* signature powers for specific wallets (if also approved by supermajority (2/3) council vote) +* signature powers for scoped project/budget wallets (if also approved by supermajority (2/3) council vote) * project management responsibilities * ...or other assets which the Tari Foundation and Council hold in trust by the community. @@ -255,8 +255,9 @@ not five Core Contributors, Tari Council members may vote for the contributor's In the event of an explicit 'no' vote, the candidate may elect to appeal to the Tari Council. The Tari Council will consider the application of the candidate, and vote on the applicant's candidacy. The candidate will be approved if the -Council decides in their favor with a supermajority (2/3). They will vote and publish their decision on admission within -10 business days, including reasoning and their view of the evidence in light of the standards in this document. +Council decides in their favor with full unanimity. Any override vote must be completed within 10 business days, and +must include publicly published reasoning for the override, and their view of the evidence in light of the standards +in this document. Otherwise, the answer is 'no.' ### Rights Expansion From 7b3b5104e37c7cb88747fe6acad4caeaa96e2668 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Mon, 20 Jul 2026 19:37:51 -0500 Subject: [PATCH 07/12] fix: nomination by CCs and TC only, simplify evidence/examples --- .../TIP-PROC-0006_core_contributor_program.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 3f7df4bb..e18667ba 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -119,10 +119,10 @@ responsibility for generated code, and must review any code generated before req their pull requests. They must not commit code they do not understand to their respective repositories, and are expected to guard their repositories from code which does not follow best practices via the review process. -**Examples Code CC readiness:** +**Example Evidence of Code CC readiness:** * Delivering multiple major features at high quality -* Delivering many thoughtful code improvements every month for at least three months. +* Delivering many thoughtful code improvements * Providing constructive code review with a keen eye for other contributors * Writing up issues and bugs with clear descriptions and acceptance criteria * Provides quality tests with code contributed @@ -136,7 +136,7 @@ of new features and may provide art such as iconography which aids in communicat Product CCs are expected to review product TIPs and feature requests to assist in their prioritization and design. They assist the community by rethinking how we meet the needs of the ever-evolving real-world needs of users. -**Examples of Product CC readiness:** +**Example Evidence of Product CC readiness:** * Delivers multiple quality feature proposals with UI/UX Designs that are accepted for development * Delivers multiple enhancements to existing features via improved UI/UX designs that are accepted for development @@ -154,7 +154,7 @@ top of the protocol. Ecosystem CCs might do things like: * Represent Tari with enterprises, at industry events, and in adjacent ecosystems * Advise the council on ecosystem strategy, deal structure, and market development -**Examples of Ecosystem CC readiness:** +**Example Evidence of Ecosystem CC readiness:** * Demonstrates decorum, clarity, technical acumen and helpfulness in onboarding community members with wallets and other Tari software @@ -171,7 +171,7 @@ order. Infrastructure CCs might do things like: * Perform DevOps work on servers and web applications such as the forums * Maintain mining guides and establish best practices for deploying Tari tools -**Examples of Infrastructure CC readiness:** +**Example Evidence of Infrastructure CC readiness:** * Demonstrated ability to deploy and maintain services * Assists community members in mining and software setup @@ -190,7 +190,7 @@ metawork that helps the Tari project run smoothly. Project CCs may do things lik * Flesh out day-to-day processes implied but not explicitly defined by TIPs * Run large-scale events beyond the scope of what Community CCs handle on their own -**Examples of Project CC readiness:** +**Example Evidence of Project CC readiness:** * Self-starts projects and recruits community members to deliver value to the community * Assists in coordinating workgroup activities @@ -218,8 +218,9 @@ Community CCs help with day-to-day community affairs. Community CCs might do thi ## Nomination -Any member of the community may be nominated by a Core Contributor or may nominate themselves. Core Contributor -nominations shall be posted in an appropriate forum category. Any nomination should contain the following: +Core Contributors must have a sponsoring nominator. Only existing Core Contributors and current council members may +nominate someone for Core Contributor status. Core Contributor nominations shall be posted in an appropriate forum +category. Any nomination should contain the following: * Who is being nominated * What rights and contributor categories they are being nominated for From 891359102586ec8e0be43a21cae6a635899431e3 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Mon, 20 Jul 2026 19:48:13 -0500 Subject: [PATCH 08/12] fix: narrative path --- src/Process/TIP-PROC-0006_core_contributor_program.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index e18667ba..e0093a07 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -17,6 +17,15 @@ Commitment, to take ownership and responsibility of elements of the Tari project Core Contributors (CCs) are empowered to make on-the-ground decisions about the project, and [elect the Tari Council][CouncilElection]. +To become a Core Contributor, you must be active in the community and consistently contributing with high quality. +Over time, you demonstrate your trustworthiness and, at the discretion of the team, are nominated to a CC position with +specific responsibilities. After a review of the evidence, you may then be inducted into the Core Contributors. + +There is no automatic path, where you contribute X amount of work in Y time, or check enough boxes to 'win' +Core Contributor status. Rather, it is given at the discretion and in trust by those who have earned that trust before +you. Some guidelines are given in this document to help team members judge readiness, but the judgment is ultimately up +to the current CCs whether to admit a new member. + ## Motivation Tari is for everyone. It is a community project. To better distribute the work of the project, improve governance, From 1f1dd48e7bac3330235eaa427194d6b4002f8680 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Wed, 22 Jul 2026 05:46:17 -0500 Subject: [PATCH 09/12] fix: unbundle access rights from CC membership --- .../TIP-PROC-0006_core_contributor_program.md | 36 +++++++------------ 1 file changed, 12 insertions(+), 24 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index e0093a07..80d60a1c 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -18,8 +18,8 @@ Core Contributors (CCs) are empowered to make on-the-ground decisions about the and [elect the Tari Council][CouncilElection]. To become a Core Contributor, you must be active in the community and consistently contributing with high quality. -Over time, you demonstrate your trustworthiness and, at the discretion of the team, are nominated to a CC position with -specific responsibilities. After a review of the evidence, you may then be inducted into the Core Contributors. +Over time, you demonstrate your trustworthiness and, at the discretion of the team, are nominated to a CC position. +After a review of the evidence, you may then be inducted into the Core Contributors. There is no automatic path, where you contribute X amount of work in Y time, or check enough boxes to 'win' Core Contributor status. Rather, it is given at the discretion and in trust by those who have earned that trust before @@ -55,7 +55,7 @@ At a minimum, all Core Contributors must have at least six months of history and ## Contributor Powers and Rights -Core Contributors may be appointed and given power to handle any element of the project which is not the exclusive +Core Contributors may be given power to handle any element of the project which is not the exclusive responsibility of the council. For an example, a core contributor can be granted: * commit or maintainer rights on a code repository @@ -74,12 +74,9 @@ For counterexample, a core contributor may not be granted: * the ability to bind the community, Tari Council, or the Tari Foundation to contract * final say on high-level budgetary decisions, though they may advise them -### Scoping - -As part of [their nomination](#nomination), a list of requested grants shall be made. Acceptance of nomination will be -acceptance of the requested grants, and only those grants unless further grants can be directly inferred. For example, -if all code CCs are given access to a specific Continuing Integration service or code assistance tool, then granting -committer access to a repository grants this as well. It would not, however, grant access to all other repositories. +Core contributor status does not automatically confer any particular power or access right. Access rights are granted on +an as-needed basis. Core Contributors are the first (and, in most cases, only) community members considered for access +to project resources. ### Categories @@ -89,10 +86,6 @@ work. Core Contributors may be part of multiple categories, or may have no categ contribute in areas outside their category, but may not be granted specific rights and responsibilities of those categories without membership. -For example, Code CCs have merge rights over their respective repositories, and may be required to triage -and/or review pull requests on their repositories. A design contributor or project manager can still contribute pull -requests, review, and may assist in triage, but they would not be required to, nor would they have merge rights. - The current categories are: * [Code](#code-ccs) @@ -105,14 +98,12 @@ A brief overview of each category is below. Further refinement of expectations a submitted in subsequent TIPs. To distinguish between, for instance, all code contributors and specifically Core Contributors in the Code Category, we -will use 'code contributors' for the former and 'Code CCs' for the latter. +will use 'code contributors' or 'contributors' for the former and 'Code CCs' for the latter. #### Code CCs -Code CCs are community members with demonstrated software engineering skills who have consistently delivered -high quality code contributions to the Tari project. Code CCs are inducted with commit rights to one or more -repositories. Commit rights involve the right and responsibility to commit high quality code to the official public -repositories of the project. +Code CCs are community members with demonstrated software engineering skills who have consistently delivered high +quality code contributions to the Tari project. Code CCs are expected to follow best practices in software engineering. These include, but are not limited to: @@ -232,16 +223,13 @@ nominate someone for Core Contributor status. Core Contributor nominations shall category. Any nomination should contain the following: * Who is being nominated -* What rights and contributor categories they are being nominated for * Evidence that they meet [the requirements for being a Core Contributor](#requirements), as links and/or testimony -* Evidence that they hold competencies in any categories or for any rights they're being nominated for * **Any corporate entity which is sponsoring their contributions** * A date, 10 business days from the date of posting, by which any votes for or against their candidacy must be given For example: -> I am nominating JimBob for the Core Contributor program as a Code CC, with commit rights to the simulations -> repository. +> I am nominating JimBob for the Core Contributor program as a Code CC. > > JimBob has been a contributor of code to our repositories for several months, and proved his excellence when > implementing spline reticulation. He is very helpful on the forums, always has a good attitude, and contributes @@ -269,9 +257,9 @@ Council decides in their favor with full unanimity. Any override vote must be co must include publicly published reasoning for the override, and their view of the evidence in light of the standards in this document. Otherwise, the answer is 'no.' -### Rights Expansion +### Category Expansion -Expansion of rights is done similar to [nomination](#nomination). A forum post requesting rights or category expansion, +Expansion of categories is done similar to [nomination](#nomination). A forum post requesting category expansion, with reason given and evidence of competency supplied, shall be made. If after 5 working days there are at least three affirmative votes and no negative votes, access shall be granted. Voting rights are the same as described in [Nomination](#nomination). From 3d1931137dd1291d7e1f4ebd67e65ec32e446c20 Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Wed, 22 Jul 2026 13:39:20 -0500 Subject: [PATCH 10/12] fix: business days to calendar days --- .../TIP-PROC-0006_core_contributor_program.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 80d60a1c..7cead5ba 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -225,7 +225,7 @@ category. Any nomination should contain the following: * Who is being nominated * Evidence that they meet [the requirements for being a Core Contributor](#requirements), as links and/or testimony * **Any corporate entity which is sponsoring their contributions** -* A date, 10 business days from the date of posting, by which any votes for or against their candidacy must be given +* A date, 14 days from the date of posting, by which any votes for or against their candidacy must be given For example: @@ -253,7 +253,7 @@ not five Core Contributors, Tari Council members may vote for the contributor's In the event of an explicit 'no' vote, the candidate may elect to appeal to the Tari Council. The Tari Council will consider the application of the candidate, and vote on the applicant's candidacy. The candidate will be approved if the -Council decides in their favor with full unanimity. Any override vote must be completed within 10 business days, and +Council decides in their favor with full unanimity. Any override vote must be completed within 14 days, and must include publicly published reasoning for the override, and their view of the evidence in light of the standards in this document. Otherwise, the answer is 'no.' @@ -272,8 +272,8 @@ A Core Contributor who is either unable or unwilling to continue their work as a Core Contributors are people. They may be called to new projects, may lose interest, or may lose any sponsorship that assisted their role as contributor. Whatever the reason, a Core Contributor may submit their resignation to the Council -at any time. They will then be offboarded from the program. To leave in good standing, a notice period of at least ten -business days and good faith work to perform clean handoffs are required. +at any time. They will then be offboarded from the program. To leave in good standing, a notice period of at least 14 +days and good faith work to perform clean handoffs are required. ### Involuntary Exits @@ -283,9 +283,9 @@ extended lack of contribution) they may be removed from the program by a majorit CC rights revoked. In the event an involuntary removal occurs, a public reason for this removal must be published by the council within -72 hours of the action taken. The removed may appeal to the council within 5 business days, and upon appeal, the council +72 hours of the action taken. The removed may appeal to the council within 7 days, and upon appeal, the council will consider their evidence and will vote once more, requiring a supermajority (2/3) to maintain removal. -They shall vote and publish their verdict within 5 business days of the appeal being posted. +They shall vote and publish their verdict within 7 days of the appeal being posted. ## Council Voting From c7e1bdd8cb43761f5f868b3779f88ca103ecb6fb Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Sat, 25 Jul 2026 18:40:03 -0500 Subject: [PATCH 11/12] fix: signature wording, bootstrap period --- src/Process/TIP-PROC-0006_core_contributor_program.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 7cead5ba..591dd820 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -64,6 +64,7 @@ responsibility of the council. For an example, a core contributor can be granted * DNS administration capabilities * server and online service access * seat licenses to software +* One key from a set of signature keys for multisig community wallets (if also approved by supermajority (2/3) council vote) * signature powers for scoped project/budget wallets (if also approved by supermajority (2/3) council vote) * project management responsibilities * ...or other assets which the Tari Foundation and Council hold in trust by the community. @@ -248,8 +249,8 @@ feedback. The attitude of feedback should not be 'never' but 'not yet', explaini Contributors would need to see before approving their addition to the team. The nomination will be considered approved if five Core Contributors give an affirmative vote and there are not any 'no' -votes by the time the feedback period has ended. In the event (such as when initially starting the program) there are -not five Core Contributors, Tari Council members may vote for the contributor's candidacy. +votes by the time the feedback period has ended. In the event there are not five Core Contributors, unanimous +affirmative votes must be collected. In the event of an explicit 'no' vote, the candidate may elect to appeal to the Tari Council. The Tari Council will consider the application of the candidate, and vote on the applicant's candidacy. The candidate will be approved if the @@ -257,6 +258,12 @@ Council decides in their favor with full unanimity. Any override vote must be co must include publicly published reasoning for the override, and their view of the evidence in light of the standards in this document. Otherwise, the answer is 'no.' +### Bootstrap Period + +Until the Core Contributor program has inducted 11 members over time, the council will hold voting rights during the +nomination process. After the 11th inducted member, the council shall no longer have the right to vote in +Core Contributor nominations, excepting through the appeals process mentioned in [Nomination](#nomination). + ### Category Expansion Expansion of categories is done similar to [nomination](#nomination). A forum post requesting category expansion, From 75701023e17b2090b463d37bc92efeeea49594be Mon Sep 17 00:00:00 2001 From: Fox Danger Piacenti Date: Sat, 25 Jul 2026 18:46:31 -0500 Subject: [PATCH 12/12] fix: amendment requirements --- src/Process/TIP-PROC-0006_core_contributor_program.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/Process/TIP-PROC-0006_core_contributor_program.md b/src/Process/TIP-PROC-0006_core_contributor_program.md index 591dd820..90150bbb 100644 --- a/src/Process/TIP-PROC-0006_core_contributor_program.md +++ b/src/Process/TIP-PROC-0006_core_contributor_program.md @@ -308,4 +308,8 @@ After one week of setup for voting, elections shall begin, with two weeks for ea ranked choice (AKA 'instant run-off') ballot. The final two weeks between terms will be used for onboarding and hand-off, with decision-making power only manifesting when the new electee's term begins. +## Amendments + +This document may only be amended or replaced via unanimous vote of the council and majority vote of the CCs. + [CouncilElection]: ../TIP-0002_tari_community_charter.md#article-vii-nomination-and-selection \ No newline at end of file