Skip to content

Pre Planning: April 14, 2022

Jump to bottom
earth2travis edited this page Apr 14, 2022 · 4 revisions

Agenda

Feedback

  • A lot of progress this week
  • Kickstart Summon and Hub flows with Jord and Keating as leads of independent streams
  • Sam will lead the SDK and data library
  • Component library package in place may need an owner
  • Schedule dev/design sync to break down Hub and decide what we want to do for this first version

Questions

  • How are we setting up the color system?

Blockers

  • How can we be sure that the component library is set up in a way that is flexible and resilient?

Retro Updates

Git Practices

  • Establish Git practices in show-and-tell and create Wiki page

Topics

- Git process for commits
- Git process for branching
- Git process for PRs
- Review: inputs and outputs

Design

  • How can design work with Ven acting as a director and delegate
    • What can we do to support this?
      • Bigger product vision meetings
      • Pre-emptive discussions (such as the upcoming Hub meeting) where we define specific features
        • We can do this for Core UI as well

Core UI

  • How do we start chunking this?
    • Do we need a Gantt chart for each project/week?
  • What do we want to do next?
    • Do we need/want to introduce Linear projects/cycles at this point?
      • Chart view for a week by week focus
      • Linear has project/cycle mapping --
        • May want to look into this. JP will import our issues as an exploration point
  • How do we want to break this up?
    • Proposal View
      • Description, Basic info, Action Details
      • How does Baal show this?
    • MetaOS and Core UI -- distinctions
      • Solving this as a problem in the DAO space, but is MetaOS a distraction?
    • DAO Overview isn't the MetaOS and is still useful to include in the Core UI
    • Member Details Page

Invisible Suburbs

Done

  • Close out Issues in Done

Review

Development

  • What needs to be done to move these issues to Review?
  • Determine how to indicate the issue is ready for Review
    • Can we create a GitHub Action to automate this?

Ready

  • Prioritize
  • Verify issues are complete
    • Should any issues be moved to Backlog?
  • Determine how to indicate the Ready process is complete and the issue is ready for Development
  • What might be a better name for this column?

Design

  • Determine which issues should be pulled into Review
  • Are there any designs to present in Planning?

Backlog

  • Prioritize
  • Determine how to indicate the issue is ready for Design

Create Issue Template for Components

What is required for:

  • Design
  • Development
  • Review

Priorities for Next Week

Thoughts

  • Process for each column on the Kanban board
  • Look at the next phase in the process as customers

Outstanding

  • Planning: March 28, 2022 meeting ToDo

Home

Resources

Projects

Process

Meetings

Wish List

Clone this wiki locally