chore: remove resource requirements

website/src/pages/roadmap.md

@@ -187,72 +187,6 @@ While not prioritized as an upcoming workstream, we think it’s worth calling o
 - Scaling explorations
   - e.g SNARK Folding Schemes ([Nova integration](https://github.com/privacy-scaling-explorations/maci/issues/904))
 
-# Resource requirements
-
-### Hiring
-
-- **ASAP**
-
-  - 2 engineers to drive MACI development
-    - JavaScript/TypeScript is a must, Solidity & Circom knowledge nice-to-have
-    - Could be full-stack devs, or specialists (e.g. 1 frontend dev, 1 backend / smart contract dev)
-
-- **Soon™ (2nd half of 2024?)**
-  - As we begin to tackle “future areas of research & development”… additional roles we’d potentially like to hire for:
-    - Full-stack engineer (QF stack: frontend & smart contract development)
-    - Cryptography/circuit engineer (ElGamal work, Nova integration)
-    - Researcher (MACI scalability, mechanism design, QF research)
-
-### Audit
-
-- Given we plan to release a v1.2 in Q1 2024 (& potentially another version later in the year!), we’ll want auditing resources for this (via either internal or external security team)
-
-### Design
-
-- MACI identity & branding workshop to assist with user personas & messaging
-- Nice-to-have: website design help & logo design
-
-### QF matching funds
-
-- If we hit our goal of 12 QF rounds, we expect matching pool amounts totaling ~$350,000
-
-### Event budget
-
-- ~$25,000 budget to run hackathon bounties & workshops
-
-# Major decision points
-
-_Initiatives & potential events in 2024 that will influence our priorities & progress_
-
-### 1) QF landscape analysis
-
-The results from this upcoming research initiative will influence our strategic direction in terms of
-
-- A) exploring MACI integrations with other projects
-- B) building the user-facing application(s) ourselves
-
-### 2) Ability to grow our team
-
-Our success with recruiting & hiring will obviously influence our bandwidth & ability to execute
-
-Our ambitious goals require the need for certain expert knowledge & skillsets
-
-# Major risks
-
-_Potential hurdles or challenges that would prevent our team from completing our priorities_
-
-### 1) Integration risks
-
-While projects have already expressed interest (e.g. Gitcoin, Gnosis Guild), we have limited control over the ultimate decisions on community integrations. Projects may re-prioritize or determine they don’t have the internal engineering resources to push these initiatives forward.
-
-### 2) QF event risk
-
-Ultimately there’s macro events beyond our control that could cancel IRL events & QF rounds. As we continue to subtract ourselves in terms of the influence & control we exercise over QF rounds, we naturally will have less decision-making power over the outcomes of these rounds.
-
-### 3) Technical complexity
-
-MACI is a complex codebase that was originally built by expert cryptographers, most of which who are no longer with the project. Some of the research & development improvements we intend to make have some unknown technical complexity. Not all problem spaces are completely understood, which pose a risk of delaying or obstructing progress as we learn more.
-
 # Feedback
 
 Questions? Concerns? Ideas? We’d love to hear from you!