# TP 0.6: Turbo Teams Proposal

- Space: [TURBO](https://snapshot.box/s:vote.turbocouncil.eth.md)
- Author: 0x15d64dA1ADcd6A636E57217B18F0ce75270B11cd
- State: Passed
- Voting type: Basic
- Start: 2023-08-04 14:30 UTC
- End: 2023-08-07 14:30 UTC
- Votes: 11
- Open in Snapshot: https://snapshot.box/#/s:vote.turbocouncil.eth/proposal/0x6e29947b4e690ba0b8079965dcc873ff86e987d97e18867abf388697887b9403

## Results

- For: 75,857,290.6 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

## Introduction
During Council TownHall #1, we discussed the Council's role, and it became clearer that the Council should take over less tasks & responsibilities and instead work towards creating the infrastructure for a fully scalable decentralised community that actively contributes & participates. As a result, I am proposing this Turbo Proposal [TP 0.6] to establish a bottom-up contribution system.

## Proposal
Creating clear rules and a pathway for community-contributions to enhance the Turbo Project.

## Motivation
So far there hasn't been enough clarity around how the community can effectively contribute. I believe that defining clear rules for the community to independently organise into Official Turbo Teams to manage Turbo-related work can allow for more community involvement and decision-making.

Establishing Official Turbo Teams promotes a stronger community-led approach which ensures the project remains truly community-driven, enabling faster decision-making without requiring every choice to pass as an official Turbo Proposal [TP X.Y]. It also provides a clear path for potential community contributors to actively support the project's development.

The creation of Official Turbo Teams within the community will allow to decentralize the management of the project in core areas that persist despite changes in activities or contributors. The Turbo Teams system aims to encourage long-term engagement, planning, and development.

## Specification
1. Official Turbo Teams are foundational teams of people from within the community that willingly dedicate their time to drive initiatives aimed at contributing to Turbo's development.

2. The establishment of a new Team requires community approval, and there must be a clear need for it that cannot be fulfilled by an existing Team.

3. Dissolving a Team requires a community proposal.

4. Each Team will have a min of 3 and max of 5 Advisors, with one Advisor serving as Team Lead for accountability and representation in public meetings.

- If a Team Lead steps down, a new one will be appointed.

5. Any individual can nominate themselves to become an Advisor.

- Advisors will be elected to guide the Team and onboard new contributors, among other responsibilities.

- Advisors are responsible for managing Team operations.

- Advisors can approve the creation and dissolution of sub-teams within the Team (e.g., a Team could be Marketing, with a sub-team for Social Media).

- Advisors manage funds and operational costs independently using a Team-related wallet.

- Advisors may be removed at any time by a community proposal or by a majority vote among the Advisors of a particular Team.

- Team members and Advisors may be contributing to more than one Team

## Notes
These rules can be updated by passing a Turbo Improvements Proposal [TIP].
This proposal [TP 0.6] will be ran via Snapshot and last for 72 hours.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

