chore: remove 2023 section

website/src/pages/roadmap.md

@@ -62,84 +62,6 @@ Our vision to eventually enable QF rounds, running e.g. every quarter, at the lo
 4. 2025: support additional QF mechanisms
 5. 2025 & beyond: TBD
 
-# Where are we now?
-
-Despite the MACI project existing in some form for 4+ years now, we still see MACI & QF largely at the “research & development” stage. We’ve built an MVP and have shipped a production product to market (starting with [MACI v1.0](https://mirror.xyz/privacy-scaling-explorations.eth/V0QkCAtsYUd5y7RO7L5OAwmawhY9LTJ7jlOZ4KW1J7M)) but we’re still very much in the stage of testing, iterating & refining. We’re looking to gain adoption from projects, whether experimental or in production, in order to gain product feedback & quickly iterate on improvements. We still have lots of potential research areas to explore in order to make MACI usable from the mass market.
-
-## 2023 year in review
-
-Overall, 2023 has been a turbulent year on the MACI team with up & downs.
-
-A few major initiatives & themes worth calling out, which influence our 2024 roadmap strategy.
-
-## Successes in 2023
-
-### P0tion v1.0 release & early traction
-
-Originally planned as tooling to support MACI’s trusted setup ceremony, eventually we generalized this project & codebase to provide infrastructure that supports any Groth16 Phase 2 Trusted Setup ceremony.
-
-The project was publicly launched in August & has already seen early traction in the community. 4 ceremonies have already been run, including the **[MACI v1 Setup Ceremony](https://ceremony.pse.dev/projects/Maci%20v1%20Trusted%20Setup%20Ceremony)**! More projects continue to indicate interest, both by running ceremonies on our hosted infrastructure ([ceremony.pse.dev](https://ceremony.pse.dev/)) as well as forking the project to run their own ceremonies, which has attracted ~260s of contributions.
-
-**References**
-
-- [Github](https://github.com/privacy-scaling-explorations/p0tion)
-- [Website](https://ceremony.pse.dev/)
-- [Wiki](https://p0tion.super.site/)
-- [v1.0 release post](https://mirror.xyz/privacy-scaling-explorations.eth/TuLZRdgCQsydC8JJgCNH4F7GzifRBQ6fr31DHGLFVWM)
-
-### Community QF rounds
-
-The goal of our QF project has been to serve as a reference implementation on how to integrate MACI as well as support the practical adoption of this community-funding technology.
-
-This year we continued to build out our [fork-able QF stack](https://github.com/privacy-scaling-explorations/qf) & partnered with a variety of Ethereum community organizers to run 6 successful QF/QV rounds, with a total of $58,000 of matching pool funds disbursed to community projects:
-
-1. [ETH Porto](https://eth.movimentotransformers.org/#/): $10,000
-2. [ETH Dam](https://qf.super.site/case-studies/ethdam): $15,000
-3. [ETH Honduras](https://qf.super.site/case-studies/eth-honduras-23): $10,000
-4. [ETH Argentina](https://qf.super.site/case-studies/eth-argentina-23): $20,000
-5. [EthCon Korea](https://qf.ethcon.kr/): $0 (completely community-run!)
-6. [ETH Taiwan](https://www.zkpvoting.tw/#/): $3,000
-
-[Learn more about some of community QF rounds in our case studies](https://qf.super.site/case-studies).
-
-We also connected with tens of other grassroots Ethereum communities. Although other rounds “failed” to launch in 2023, we established relationships & opened doors to potential future rounds. We learned valuable insights about what makes a successful community partner, what level of skill & participation is required to make a round work. Other orgs we explored rounds with included ETH Rome, ETH Mexico, ETH Brasil, ETH Colombia & ETH Gunu.
-
-**References**
-
-- [GitHub](https://github.com/privacy-scaling-explorations/qf)
-- [Website](https://qf.super.site/)
-
-## Challenges in 2023
-
-### Lack of MACI adoption
-
-Despite publishing the [MACI v1.0 release](https://medium.com/privacy-scaling-explorations/release-announcement-maci-1-0-c032bddd2157) over 2 years ago, not a single project has integrated MACI v1.x in a production environment (aside from [QFI](https://github.com/privacy-scaling-explorations/qf), the internal PSE project).
-
-While attempts have not been well documented, we’re aware of a handful of anecdotal accounts of developer teams demonstrating interest in MACI, attempting to integrate it, but eventually giving up after weeks of effort due to a variety of issues (steep learning curve, poor documentation, lack of code commenting or readability, limited support from the MACI team).
-
-### MACI repo & community neglect
-
-Although our core team has been working hard on various initiatives, our communication, priorities & activities have not been visible to the community. Most communication has been in private TG groups & collaboration on core team development has primarily been in closed GH project boards. This creates a lack of certainty around the investment in & maintenance of the project.
-
-The [MACI repo](https://github.com/privacy-scaling-explorations/maci) has been largely neglected in 2023. As of early October, there were >90 open issues & >30 opens PRs, many of which are months or years old, and most of which had no response from our core team. This does not inspire confidence from the community that this project is actively maintained, or that the core team is open to community contributions.
-
-While we’ve had a public TG group (with >250 people), there’s not much activity from the core team there & we haven't reliably responded to questions or inquiries from the community.
-
-### Half-baked research & development
-
-The team took on several ambitious areas of research & development (particularly research). While we made progress in areas, most of these projects have not come to fruition in terms of being published or integrated into the MACI product:
-
-- We had grantees working on [ElGamal research & development](https://github.com/privacy-scaling-explorations/maci/issues/796) but they were not closely supervised & their work is largely WIP that hasn’t been integrated into the project
-- We kicked off work on the [MACI coordinator service](https://github.com/privacy-scaling-explorations/maci-coordinator). We implemented an API to assist with coordinator proof generation. Work began on a frontend React app but progress stalled & the work has not been completed:
-- Research on [Group Wise Matching in Quadratic Funding](https://github.com/privacy-scaling-explorations/maci/issues/905)
-- Research on [Nova Integration with MACI](https://github.com/privacy-scaling-explorations/maci/issues/904)
-
-It seems team members were mostly assigned to their own independent initiatives, which led to these isolated workstreams. Individuals found it hard to gain feedback & support from the team. Moving forward, we want to align individual goals with larger team goals in order to encourage closer collaboration on the projects we push forward.
-
-### Team turnover
-
-In 2023 we lost some core team members which contributed to resource constraints, stalled projects, & general confusion within team around priorities. This also led to morale issues with productivity, frustrations & uncertainty of the future direction. Yet ultimately the team & project perseveres! We’re hopeful with the new structure & growth opportunities, we can achieve an impactful 2024.
-
 # 2024 workstreams
 
 _To achieve our mission, we’re focused on 4 major workstreams that comprise our roadmap._