---
# System prepended metadata

title: Magesmiths Roadmap Meeting 22-11
tags: [roadmap]

---

---
title: Magesmiths Roadmap Meeting 22-11
tags: roadmap
--- 

# Roadmap Meeting 22-11
We started with a Roundtable discussion on what we thought should be in-scope vs out-of-scope, followed by aligning on a collective summary. 

## Roundtable 

### Jord - https://hackmd.io/gu-gTxnQRgGi6AohLit8UA
- We should build a decentralised meaning / content layer (e.g. Discourse), documenting the discussions and drama that give proposals meaning. The content  helps DAO users make sense of what they are voting on
- Enabling DAO to run & own their discussions gives the DAO a sense of identity, reflecting how the DAO discusses and governs beyond just a dashboard of 'Yes' and 'No' votes
- Discussion: There are benefits in having people choose the tools they want to use & there'll likely be a proliferation of services building on Ceramic (e.g. Boardroom). What are the hooks we need to build for other people to plug in a Web3 version of their Discourse or tools? 

### Adrienne 
From a project plan point of view, this is a list of features prioritised accordig to order of priorities. 

![](https://i.imgur.com/nq659a1.png)

### Spencer - https://hackmd.io/8vbv78PYQbiTVGLkVlbSgw
Beyond the core 5 things (Summoning, Membership, Proposals, Voting & Vaults), there are new things that need to be core to the app & within the initial scope. 
- Hub / Dashboard (e.g. A simple DAO switcher)
- DAO Settings 

The approach was to prioritise what Baal features needs to be in and out of our initial scope, creating a minimal viable scope. For instance, there are new Baal summoning features, but we should probably only replicate our current features and make them powered by Baal (e.g. Multi-summoners, Tokens, Grace period, Min voting period, Proposal velocity, Proposal deposit)

On Shamans, the initial focus is to be on the Yeeter and slowly bring it into the main app when we've more ideas on how to use the Shaman.

## Discussion 
**What is v3?** 
- V3's focus is on Baal. At some point later, we can focus on the transition and merge the indexing of V2 DAOs so that these DAOs can still be found on V3. 
- We should keep V2 running for a year for folks to upgrade. We expect most users to upgrade to V3 as it represents a better offering overall

**Importance of User Education / UX** 
- How do we explain current and future functionality in the UI, so that users don't have to refer to docs everytime they configure things? 

**What is the ETH Denver focus?**
We take the time to understand Baal and explain how Baal is supposed to work,  creating content for ETH Denver. Target audience is for users and developers (apps architecture) 

1. 'Shill' Workstream: 
    - Understand how things work in Baal & create non-tech content on how things work 
    - Create technical content for developer relations (stylised architecture & vision + how developers might build and integrate)

2. 'Build' Workstream: Design & build technical architecture, primitives, component libraries, testing and type layer

:::info
**Next steps:**
1. From a more actionable POV, we should create a Roadmap to ETH Denver to achieve both Shill & Build workstreams 
2. From a roadmap & alignment POV, we need to continue to step 7B on what is core vs non-core
:::