---
# System prepended metadata

title: Keep September Boring
tags: [v3]

---

---
tags: v3
---

# Keep September Boring

- Address [43 issues](https://github.com/orgs/HausDAO/projects/18/views/1?filterQuery=no%3Amilestone) out-of-scope for MCON
- [v3 Testing](https://github.com/orgs/HausDAO/projects/20/views/1)
- [Robot Apartments](https://github.com/orgs/HausDAO/projects/4/views/2)
- Improve features we implemented fallbacks for

## Building

- ACE

## Testing

- Admin and proposals
- Fixing Hub and Summon bugs

## Documentation

- Refine docs for target persona

## Live Coding

- Showing how to build apps with toolbox
- Recording fishbowl sessions
- Getting devs up to speed with tools
- Improving documentation

## Questions

- Do we want to create a seperate proposal for v2?
- How can we open Invisible Suburbs to the community? Core team could also earn the bounties too.

## Resources

- [Proposed process](https://docs.google.com/document/d/1UIBzPAoOi5LL3iQH0QcGoeYIu5HoVXV8QAXv0FDTW2c/edit#)
- [Spreadsheet for allocation](https://docs.google.com/spreadsheets/d/1IoTrhFpJRbwPwWBaw-ZF-qLxSahuEnNqAbHvlRtqKBU/edit#gid=17821322120)

## What should Magesmith's priorities be for September?

- Iterate, test, and tighten up MVP's libs/apps and docs.
- Define some product strategy direction for beta to v1 + bolt ons we would like to support.
- Design a transaction builder bolt on.
- V2 to v3 upgrade docs, process and support - maybe a tool if the build lift is low.
- V3 beta support, testing and feedback gathering.
- V2 support + get back to deprecation and decentralization.
- Docs, polish, making sure our packages all work and are documented! If all of that is good, we should then create additional resources
- Ship DAOhaus V3
- Proposal / admin interface build out. Defining the next phases of the product direction to have a better roadmap
- More dev interfaces (TXBuilder app), cleaner ops, test tools, finish and refine core.
- shipping
- I'll be honest and say I feel like September's direction may be taken over by MCON and whatever comes out of it, but viewing September as short-term goals, I think priorities should be finishing up incomplete portions of V3 beta and polishing this initial release.
- V3x Stable release, maintenance plan with skeleton crew
- MCONNNNNNN!!! building the UI, connecting UI to contracts, MERGEEEE PARTY
- Yes
- Finish any outstanding items for beta V3.
- Dotting I's, crossing t's and tying bows on work-in-progress

## What should Magesmith's priorities be for Q4?

- Same as above and/or what isn't finished in september. Would be cool to have a few bolt ons more out in the wild.
- And a more stable V1 release of core libs/apps
- Moving from beta to a broader release
- V3 Increase adoption & integration with 3rd party apps/protocols
- Ensure DAOhaus v2 runs smoothly
- Solid Admin interface, documentation, and sdk that sets up anyone building off of it at a protocol-level is set up for success
- Much of the priorities from September will bleed over. We need to refine our tool system and test with developers who build on top of our infra. Spend some time cleaning our libraries and refactoring code that was rushed in.
- By the end of Q4, we should have built a Rapid application prototyping system that can build a decent MVP in a week.
- We should also have a list of apps that would be good to build on top of DAOhaus infra.
- Stretch goal might be a no/low code proposal building interface for simple DAO operations.
- continuous shipping
- Expanding V3 features, creating really nice and polished community resources/documentation for V3 and for collabing with/building off of DH, and hopefully beginning partnership/spinoff projects that can bring financial stability.
- Majority of product builders should transfer to Labs or Consultation groups
- refine the UI, refine the Design, complete a modular dao framework
- We've gone fast and built a lot of great stuff. That said we have some technical debt that we've been back logging until after mcon. I'd like to continue building it V3 but also pick up efforts for find raising, and documentation.
- Once beta V3 is shipped Magesmiths should get feedback and create a new roadmap for V3 and focus on building the developer community. I think it would also be cool to start to do custom dao consulting work in order to get some revenue.
- Breaking up work into smaller product-based teams
