---
tags: v3
---

# v3 Dragon Sync (3/7/2022)

## Questions

- Do we want to spin up a Wiki? How do we want to manage our docs?
- Do we want to continue with GitHub Projects until we potentially need something else?
- How would the Wiki relate to this? Does it need to be connected to a project or org?
- When do we turn something into a real issue? Allows you to select the actual repo to connect it to -> creates the actual issue in the repo

## Planning the Planning

- Turn Ven's Figma into a doc where folks can provide feedback
- This week we determine a scalable process and agree and then present to the team
- Determine workflow and meeting cadences
- Think about the Wiki in the repo
- Identify the tasks that we can start organizing
- What labels do we want to include in the Kanban workflow?
- Columns for testing and development?
- This depends on how we write the tasks
- Todo -> Doing -> Done
- Should mirror our workflow:
- Backlog -> Ready -> Needs Scoping -> Needs Design-> Ready for Dev -> In Dev -> In Review -> Done
- Focus on chunks of functionality and information in our ticket design
- Iterate as we go:
- Add in estimations and chunk issues as we go

## Cadence

- Weekly planning -- backlog and work in progress drives conversations
- Get into detail on tasks and assign and prioritize tasks
- Do we want to do a 2 week cycle?

- Needing a place to provide design feedback during the development processes -- how do devs communicate if there is something that comes up during a design?
- Comments on the issue?
- Comment in Discord?

## Actions

[] Establish our contributor workstreams, labels, and Kanban statuses
[] Determine organization method for the notes: Wiki?
[] Go through the team notes and curate these (unify our scope)
[] Determine who are contributors on v3 and in what way
[] Tackle this with Summon as the first flow through the steps