Skip to content

Governance page #122

Description

@truthixify

Tier: S (1-2 days) | Type: content

Context. The Drips-funded contributor model is unusual and reviewers keep asking how decisions get made: who ships to main, how waves are scoped, how disputes are resolved, how mainnet parameters would be changed. Nothing on the marketing site answers this today. A written governance page is a prerequisite for larger institutional partners.

Scope.

  • New /governance route.
  • Sections: decision-making process, maintainer list (opt-in, honors src/data/contributors-optout.json), wave scoping process, dispute + escalation path, mainnet parameter change process (placeholder if not finalized).
  • Links to /grants and /contributors.
  • Data-driven maintainer list from src/data/team.json filtered by role.

Acceptance.

  • /governance route added and linked from footer
  • Every named maintainer has documented opt-in for the listing
  • Build passes
  • Lighthouse Perf/SEO stay >= 90

Files. src/pages/Governance.tsx (new), src/App.tsx, src/components/Footer.tsx.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programcontentMarketing content / writingdripsFunded via Drips NetworkfeatureNew feature workhelp wantedExtra attention is neededstellar-waveAuto-created for Wave 8trustwave-8Auto-created for Wave 8wwwAuto-created for Wave 8

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions