Planning: April 18, 2022 - HausDAO/daohaus-monorepo-deprecated GitHub Wiki

Agenda

Retro Results

• Product Vision Meeting
• Protect Wednesday

Status

• A lot of progress last week
• Decided on Radix color system
• Establishing Git practices, issue and PR templates and automations
• 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

Priorities for This Week

• Define Global Styles
• Issue Template
• Component Library
• Kickoff Hub
• Sage set-up for Storybook
• Sage set-up for SDK
• Finish up Review Process

Robot Apartments

Are there any high priority bugs that need to be squashed this week?

Invisible Suburbs

Done

• Close out 2 Issues in Done

Testing

• Waiting on feedback from Bill on Split Shares into new contract, will create new cards for updates and deploys

Review

• Review issues in column

Development

• Review issues in column

Ready

• Review issues in column

Design

• Review issues in column
• Are there any designs to present?
• Schedule dev/design sync to break down Hub and decide what we want to do for this first version

Backlog

Thoughts

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

Notes

Retro Action Items

• Retro notes and action items will be coming soon
  • Product meeting is a good step toward addressing some feedback
  • "Protecting Wednesday" is another step toward addressing feedback: having a day for Magesmiths to focus on work on a day without meetings
• Set up new contributors as leads after a certain period where they establish consistency and avoid setting them up right away
• Key distinctions between component library and SDK?
  • Component library helps us build, whereas the SDK is likely more external facing for allowing the community to build on top of DH
  • Tools are the product and we're the first customers of the product (thinking along the lines of DX -- Developer Experience)
  • Jord and Keating on the SDK and data library instead of the component library
  • While we all work across the app packages, owners will ensure that our quality standards are being met
  • We should look at each of these areas as products
    • Who are we providing value to with each of these tools? Who is our customer for each package?

Weekly Priorities

• Supporting the component library and the SDK
• Storybook deployments for Sage and Rage
• v2:
  • Keating working on the Lit integration for the Boost
  • Add this to the v2 Board
  • Superfluid rework:
    • Not on the board, but deploying this week
  • Poster DAO Docs:
    • Needs to be added to the Board
  • What do we want to do about this? How do we want to approach bug escalation?

Hub App

• When should we start working on this? Waiting on design, but we should try to meet at the end of this week with design
• Could focus on scaffolding as a starting point
  • Create a card for scaffolding the Hub App