-
Notifications
You must be signed in to change notification settings - Fork 43
Governance page #122
Copy link
Copy link
Closed
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programcontentMarketing content / writingMarketing content / writingdripsFunded via Drips NetworkFunded via Drips NetworkfeatureNew feature workNew feature workhelp wantedExtra attention is neededExtra attention is neededstellar-waveAuto-created for Wave 8Auto-created for Wave 8trustwave-8Auto-created for Wave 8Auto-created for Wave 8wwwAuto-created for Wave 8Auto-created for Wave 8
Description
Activity
Metadata
Metadata
Assignees
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programcontentMarketing content / writingMarketing content / writingdripsFunded via Drips NetworkFunded via Drips NetworkfeatureNew feature workNew feature workhelp wantedExtra attention is neededExtra attention is neededstellar-waveAuto-created for Wave 8Auto-created for Wave 8trustwave-8Auto-created for Wave 8Auto-created for Wave 8wwwAuto-created for Wave 8Auto-created for Wave 8
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.
/governanceroute.src/data/contributors-optout.json), wave scoping process, dispute + escalation path, mainnet parameter change process (placeholder if not finalized)./grantsand/contributors.src/data/team.jsonfiltered by role.Acceptance.
/governanceroute added and linked from footerFiles.
src/pages/Governance.tsx(new),src/App.tsx,src/components/Footer.tsx.