---
# System prepended metadata

title: "v3 Haus Keeping \U0001F9F9 (Friday) - March 5, 2022"
tags: [v3]

---

---
###### tags: `v3`
---

# v3 Haus Keeping 🧹 (Friday) - March 5, 2022

### 3 Month Roadmap Plan

- 3 month related to v3 in general
- High-level scope for alignment/orientation
- Milestones defined i[n this v3 scope overview](https://hackmd.io/5SC9PYvvRZ-8bIfYGqFSZw) => serves as an internally digestible roadmap for the team

### CCO member coms

- We have all the addresses but haven't yet assigned them to users on Discord
- - We have a responsibility to update the 75-80 CCO contributors *so they don't ragequit*, and also gather their ideas


## High-Level Overview

### [Milestone 1](https://hackmd.io/5SC9PYvvRZ-8bIfYGqFSZw?view#Milestone-1)

- Digest the specifics over the next 2 weeks
- Try to align on the high-level today to publish internally
- Move towards a more public articulation of the roadmap, especially important now with our big changes. What does it mean to take a step back on "feature richness" on v3? Putting changes in public will make this easier.
    - Amounts to a high-level articulation of the general plan/scope
    - Avoid concrete deadlines => big picture
- A more focused roadmap (with dates and clear milestones) is still useful for internal use.
- **Lay the foundations for parallel workstreams**
- Design: UX elements moving towards UI

### [Milestone 2 Alpha](https://hackmd.io/5SC9PYvvRZ-8bIfYGqFSZw?view#Milestone-2---Alpha-Release)

- Milestones lead us to alpha releases (Haus Components v0.1 & Haus SDK v0.1). 
- Current milestones focus on "skeleton apps" (POC), laying foundation for our platform, refining PM processes (how design passes to devs to articulate tasks to keep things rolling). All leads to an agile PM cycle.
- Will be working on Internal IA, subgraphs, setting up a few different apps and libraries.
- Moving towards a "testable" output => UX prototypes
- Regarding "Read-only": if a Baal can be summoned, how do we look at proposals if we can't create them? Is there a different way to create them that is distinct from the app? How do we create proposals?
    - Might want write ability for creating a proposal: contract isn't friendly to manual efforts.
    - Use a minion form that encodes for us, or it's own standalone rage app to help dev efforts.
        - Will need to soon list proposal detail schema, so we will need to build upon this
- Important for internal value, but no harm in releasing it to the public (with the caveat that we are not actively maintaining).
- As the tasks are created, let's remember to identify opportunities to onboard new contributors (across the team circles) to maximize efficiency on the build.
    - Designers: might want additional UX + UI folk
    - PMs: eventually replace Sam, Adrienne, and e2t for the nuts and bols/button pushing/lower level organizational labors
    - Scribes: document what is happening/learning to communicate to the larger community to accompany the product releases
    - Devs: testing on front end, continuous integration, general QA
        - War Camp organize a recruiting meeting to identify needs of various circles over the next 6 months

### [Milestone 3 Beta](https://hackmd.io/5SC9PYvvRZ-8bIfYGqFSZw?view#Milestone-3---Beta-Release)

- The Beta release of the core app
- Some work towards Meta OS
    - Work can happen immediately in an agile manner (to avoid waterfaling)
    - Tasked as a bounty on Dework?
    - Might be framed as a shared initiative with GnosisOS, etc.

### [Milestone 4 Full Release](https://hackmd.io/5SC9PYvvRZ-8bIfYGqFSZw?view#Milestone-4---Full-Release)

- Migration app
- Lots of marketing
- Revgen stuff:
    - Boost marketplace
    - Curation
    - Services marketplace
    - Connections to Uberhaus
    - Additional protocol dev

### Additional Considerations

- Process of deprecation: a plan for phasing out old features
    - Minions: difficult problem since they still hold value
    - Mintgate (and other smaller boosts)
    - Sacrifice a new feature every week
    - Reach out to the community of devs to triage - create a shortlist of features to deprecate
    - Doesn't need a new role; *does* need to become an explicit part of our process.
- Updating the website that describes the product
    - Copy that describes the v3 updates: new narrative
    - Fresh designs: a dedicated visual designer to support the Ranger side of things
    - JP provide Magesmith support for Rangers tasks like this
- Work towards an outtage alert system? Is this possible and would it be valuable?
    - From the Marketing POV: would be nice to identify what is not our fault due to the centralized nature of our stack
