Add governance PIP43 - PIP44

Author: bartosjiri

governance/proposals/PIP43.md

@@ -0,0 +1,60 @@
+# PIP43: Phoenix Plan (pt. 1)
+
+PIP43: Phoenix Plan (pt. 1)  
+Author: MatterTurbulent#5161  
+Reviewer, submitter: Prye#4845  
+Required Quorum: 100M $PEOPLE (if not reached, the proposal will need to exceed 90% of the votes to pass)  
+Vote Duration: 5 days
+
+## Description
+
+On March 6 an exploiter drained 76ETH from the PeopleDAO treasury, constituting approximately 95% of the reserve funds. This plan articulates the changes the DAO should make in order to survive and continue operations, including:
+
+- Consolidation of remaining capital into the treasury
+- Increased alignment towards revenue-generating activities
+- Further austerity measures
+- Restructuring of teams, streamlining operations
+- Redefining treasury management processes
+
+### Consolidation of remaining assets:
+
+As of March 7th, the PeopleDAO treasury holds approximately $4.3k USD worth of various tokens (not including the $SAFE token which is currently locked up). The DAO should conduct the following actions to consolidate its remaining assets:
+
+1. Transfer treasury funds on other chains (Binance and Polygon) to Ethereum, approximately $5k USD
+2. Refund the UnumDAO donation, approximately $12.4k USD
+3. Seek to claim the remaining funds in PandaDAO treasury, approximately 14.3k USD
+4. Merge LanguageDAO treasury with PeopleDAO treasury, pending LanguageDAO's approval, approximately $1.3k USD
+
+Summing all the potential assets, in the best case scenario, the treasury will reach $33k USD. By the end of 2023, the $SAFE token might become transferable, possibly unlocking another $10k-50k USD.
+
+### Increased alignment towards revenue-generating activities:
+
+The DAO is poised to launch two NFT collections, Afro Piece and For The People, each of which represent revenue generating opportunities. Another Accelerator project, Perpex, could generate substantial revenue upon fundraising, estimated to occur in late-Spring/early-Summer.
+
+The DAO should enter an emergency operation mode, focusing teams and contributions towards launching these projects, and suspending non-related non-essential activities, namely:
+
+- Suspend onboarding activities
+- Conduct Accelerator-related AMAs rather than general DAO AMAs
+- Research and consider adopting other operational models, e.g. project-based structure
+- Implement KPI and other indicators to evaluate the impact of individual DAO activities
+
+### Further austerity measures:
+
+During the budgeting for Season 4 the DAO began implementing austerity measures in response to forecasts about limited runway. Teams budgeted for fewer and lesser rewards. The DAO should increase these austerity measures. The DAO should return to a centralized budgetary process rather than on a team-by-team basis, to ensure greater checks around spending.
+
+Core Team will coordinate with Team leads to ensure March rewards from the beginning of the month get paid out, but contributors should recognize that we don’t have the funds to issue the same output of rewards as months past.
+
+### Overhaul of treasury management processes:
+
+An overhaul of the current accounting task aggregation, summary, and execution is required. A new systematic approach will be introduced to cover up DAO's current operational security loophole that resulted in the exploitation. As such, the following temporary implementation will be adhered:
+
+1. Centralised compilation of pending rewards into a CSV file on GitHub
+2. Validation of the data, export of the file from Github into Safe
+3. Multisig group meeting and validation of the transaction
+
+Additionally, the DAO and multisig members will utilize extra support tools, such as browser extensions and decentralized applications, to gain further details and insights on all treasury changes. A private standard operating procedure will be defined and provided to all core members and multisig members to enforce standardized operations for all treasury management events.
+
+## Voting choices
+
+1. YES - Approve the proposal
+2. NO - Deny the proposal

governance/proposals/PIP44.md

@@ -0,0 +1,67 @@
+# PIP44: Phoenix Plan (pt. 2)
+
+PIP44: Phoenix Plan (pt. 2)  
+Author: Prye#4845  
+Reviewer: MatterTurbulent#5161  
+Required Quorum: 100M $PEOPLE (if not reached, the proposal will need to exceed 90% of the votes to pass)  
+Vote Duration: 5 days
+
+## Description
+
+Following the treasury incident, an opportunity has arised to rebuild the PeopleDAO’s internal processes. We would like to review learnings from other DAOs - one of these is MoonDAO’s transition from guild-based structure to project-based structure ([reference](https://twitter.com/LarrotizPablo/status/1638671447739760641)), which has also been adopted by other DAOs.
+
+During the first year of PeopleDAO’s existence, many different activities across the DAO and incubator/accelerator have been supported, however the organization has struggled to measure its impact and to provide significant return of investments. Moving forward, we believe that with the limited remaining resources, the DAO should focus on these two objectives, and the project-based structure greatly compliments this desire.
+
+### Areas of improvement
+
+#### Team composition
+
+- Before:
+  - Teams often consisting of large amount of low-context people with different levels of engagement and commitment for tasks
+  - Lack of strong entry criteria to join a team
+- After:
+  - Small teams built specifically for the given task
+  - Proven track-record and objective focus as requirement for joining a team
+
+#### Task definition and evaluation
+
+- Before:
+  - Tasks defined during seasonal planning with minimal focus on evaluation and implementation of key performance indicators
+  - Seasonal planning could result in evaluation loop being too long and ineffective
+  - Unknown impact of individual tasks and teams on the growth and return of investments for the DAO
+- After:
+  - Tasks defined with objectively measurable objectives as a requirement
+  - Task completion followed by evaluation as a condition for acceptance of other related tasks
+  - Evaluation loop shortened directly to the duration of the specific task
+  - Direct measurability of impact on DAO’s investments and growth
+
+#### Personal member progression
+
+- Before:
+  - Sometimes slow personal progression inside individual teams
+  - No defined procedures for rotation of team’s leadership
+  - Lack of personal performance tracking in the DAO
+- After:
+  - Ability to join different teams at various different positions in shorter period of time
+  - Opportunity for more inexperienced members to join low-impact/low-risk tasks as project leaders
+  - Tracking of personal performance based on evaluation of individual tasks
+
+### Implementation
+
+- The Operations Team will remain the only general-purpose team in the DAO
+  - The team is responsible for DAO's upkeeping and governance-related activities, such as accounting, elections and similar
+  - Membership in the team is subject to approval by DAO administrators and is evaluated on case by case basis according to the DAO's needs
+- A community member or group of members can become a self-assigned project lead by defining a project
+  - Projects are required to provide a clearly defined objectives and tasks, which have measurable indicators of completion, both in the personal and DAO-wide context
+  - Projects are required to provide a detailed breakdown of requested funds, including all spending items and member rewards
+  - Projects are required to seek and produce revenue-generating outcomes
+  - Project leads are required to assemble the project team from active contributors with proven track record in relevant area in order to maximalize the possibility of successful completion of the project
+  - All of above is a requirement for project proposal submission
+- DAO administrators are responsible for approving or denying project proposals
+  - Administrators are obliged to evaluate only proposals which have provided all required information (see above)
+  - Administrators are allowed to approve only proposals which produce revenue or other clearly defined means of positive return on investment for the DAO
+
+## Voting choices
+
+1. YES - Approve the proposal
+2. NO - Deny the proposal