Rage - HausDAO/daohaus-monorepo-deprecated GitHub Wiki

We rage to build the machine.

Rages are about testing new ideas, tools and processes fast! They are about learning to cut a new path through the jungle and sharing what you figure out to make it easier for those who come after you.

Rage Report Template

Rage Reports

Rages Needed (As of 3/17/2022)

  • Summon App (done -- report in progress)
  • Hub App
    • Sam for Subgraph work, Jord for frontend
  • Proposal Form (Core UI)

The Rage Machine

(Rage App Lifecycle)

Process Summary

Rage Identified! -> Rage scoped and added to Project Board -> Identify if the Rage has subtasks

  • This occurs at the technical speccing for the Rage

Leading up to a Rage

  1. "Define" the Rage
  • Any issue connected with the Rage will include the rage label:
    • Examples: rage hub-app
  • Add details to the Rage Template (coming soon - WIP):
  • Basic Details/Overview
    • Resources Needed
      • Identify what's needed for this Rage: Subgraph? Figma mock? Contracts?
    • What is the Purpose? / Hypothesis Being Tested
      • Rage Report can reflect on this hypothesis and learnings along the way
    • Team
      • Certain Rages will likely be a single person, but some may have a team (such as Andy and Jord on the Summoner Rage App)
  1. Team creates issue cards for the Rage and determines priority

Rage is Raging (WIP)

  • During this stage, the Rage is underway and the team works through any issues on the Project Board that are related to the Rage

Rage is Finished

  1. Rage finishes
  2. Rage report shared on the Friday after
  3. Added to Wiki
  4. If cards come out of the demo, add these to Board/next work cycle
    • ie: From Summon, want to do a Rage on how to pull out transactions to add to the SDK? -> May have additional cards for the next work cycle
  5. If everything is ready, move to Sage version
    • This then enters the project lifecycle:
      • Backlog -> Design -> Speccing -> etc
      • Would contain more classic user stories with features