Contributor Proposal — template
Title (use this format): [Contributor Proposal] <Project / Feature Name> — <Short Tagline>
Tags: proposal, contributor, repo:<repo-name>, status:proposal
1) One-line summary
What you will build / integrate (1 sentence).
2) Alignment with GoodDollar goals
Which ecosystem goals does this address? (pick one or more: Increase G$ utility, Ship integrations, Shift claimers→earners, Expand merchants)
3) Motivation & user value
- Problem this solves (who experiences it, and why it matters)
- Expected users / target community
4) Scope & deliverables (concrete)
List the specific outputs you will deliver (examples: PR to GoodSDKs adding X; claim button integration in repo Y; demo app + README). Prefer bullet points and acceptance criteria.
5) Technical approach (short)
- High-level approach / architecture
- Key libraries, SDKs, or repos involved (link to GitHub issue/PR if exists)
- Any known risks or open questions
6) Timeline & milestones
- Estimated total effort (hours / days)
- Milestone 1 — description — ETA
- Milestone 2 — description — ETA
(keep milestones to 2–4 items)
7) Testing & QA plan
- How you will test functionality (unit tests, manual test steps, demo script)
- Any security considerations
8) Open-source & license
- Repo(s) where work will live (links)
- License (must be compatible with GoodDollar repos)
9) Communication & progress updates
- Frequency of updates (e.g., weekly on KarmaGAP, PR links, Telegram)
- Preferred channel for questions
10) Budget & payment expectations (if requesting funds)
- Requested amount in G$ (or hours × rate)
- Payment milestone triggers (e.g., on PR merge, on milestone completion)
11) Links / references
- GitHub issue / PR:
- Demo / prototype (if any):
- Related docs / spec:
Quick checklist (for reviewers)
- Clear alignment with ecosystem goals
- Scope + acceptance criteria present
- Timeline + milestones reasonable
- Repo & license linked
- QA/test plan included
Committee Application — template
Title (use this format): [Committee Application] <Your Name> — <Primary Role>
Tags: committee, application, governance, mentor
1) Short intro (1–2 lines)
Name, primary role/skill, timezone (helpful for scheduling).
2) Proven experience (evidence-oriented)
List recent, provable work or achievements (links required where possible):
- Relevant PRs / merged contributions (repo + PR link)
- Projects / roles demonstrating governance, mentoring, or review work
- Public profiles (GitHub, LinkedIn, portfolio)
3) Why you want to join the Committee
- What you will contribute to governance & the builders pool
- How your skills help the program goals
4) Proposed availability & compensation request
- Hours per week or month you can commit
- Preferred task types (select any):
governing proposals,code reviews,mentor contributors,triage issues,other (specify) - If requesting payment: hourly rate or fixed stipend (specify in G$ if known)
5) Conflicts / commitments / references
- Other active roles that may conflict (if any)
- Two references (GitHub/Discord/contact) who can vouch for your work
6) Policies & responsibilities acknowledgement
(Short statement to copy/paste)
I acknowledge the Committee responsibilities (govern proposals, review code, assist contributors), agree to keep communication transparent, and will follow the Builders Pool covenant and repo contribution rules.
7) Links / evidence
- Top 3 links (PRs, repos, long-form writeups, mentor sessions)
Quick checklist (for reviewers)
- Has provable contributions / references
- Availability suits program needs
- Clear task preferences (govern/review/mentor)
- Acknowledgement statement included