🏛️ [EPIC] : Fund14 Technical Readiness

[mike-mcnulty]

Summary

Ideascale replacement and integrations with legacy stack

JIRA Epic

https://input-output.atlassian.net/browse/NPG-7772

Description

Intent

Deliver the core proposal submission and commenting functionality in the new Catalyst UX to replace Ideascale. Integrate the new backend and application with legacy components (eg Reviews module, scripting, mobile voting app). We need to complete end to end integration testing of the Fund14 production stack by mid February, so that we can spent the next 4 weeks performing rigorous fund readiness testing with operations and SRE (eg dry runs, load testing, mainnet testing).

Description

New Stack

• ADMINS will coordinate with devs, QA and SRE to hardcode all operating parameters (with no treasury space / campaign builder UI).
• PROPOSERS will register proposer role onchain; create, edit (incl saving versions), share (discovery), and submit (voting) proposals
• COMMENTERS will register proposer role onchain; browse proposals by category in the discovery space (drafts), and provide feedback through proposal-level comments (consider sort / filter; no search, unless we can reuse some existing)
• Voting snapshot
• Proposals backend

//As fallback, - ALL USERS will submit role0 registrations to mainnet (with role specific contributions tracked by the backend to retroactively associate with role keys in the future).

Legacy Stack

• ADMINS will make sure that all legacy scripting and tools (prev cat-core/catalyst-toolbox) works with the intermediate stack intended for production in Fund14; also make plans to automate the most costly operations, prioritize them, and map features to the new stack
• REVIEWERS will use the standalone reviews/moderation module to review proposals from Voices
• VOTERS will use the legacy voting app to search, sort, and filter, and vote on proposals from vit-ss that include review/moderation data from the standalone reviews/moderation module
• FUNDED PROJECTS will have their proposal and milestone details from vit-ss pre-loaded in the standalone milestone module

Outcome

As a user, I get a fit-for-purpose proposal editing and feedback experience, so that I can do my best work in Catalyst.

As an operator, I get to fire Ideascale, so that I can lower costs, reduce friction, and remove external blockers to continuous improvement.

As an ecosystem, we want to improve the quality of proposals and deliberation, so that we can maximize the impact of funds allocated.

Out of Scope

• Voices / Voting Space
• Voices / Treasury Space / Campaign Builder
• Voices / Create Team
• Voices / Delegation & Dreps

Design Tasks

#1254

Architecture Tasks

#1257

Backend Tasks

#1256

Frontend Tasks

#1255

QA Tasks

#1258

SRE Tasks

#1259

Operations Tasks [move into jira? assign to lucio? ewa?]

• Transition plan - integrate old voting app with new voting stack (no propose)
• Rebuild ideascale reviews process into moderation module
• Reviews / moderation module get proposal data from voices backend
• Reviews / moderation module API for voices to get moderated reviews data [F15 enabler]
• Milestone module get proposal data from voices backend
• Go to market and community activation, incl transition support
• Catalyst Voices rebrand??
• Highlight MUST HAVE kyc / compliance requirements for Voices in Fund14
• Investigate automation opportunities in legacy payments pipeline
• Document capabilities to support catalyst natives customers between initial ideascale replacement and full multi ecosystem support in Voices