Partnering With The Greenpill Dev Guild

How partners, funders, chapters, and aligned builders can work with the Greenpill Dev Guild.

The Greenpill Dev Guild builds public-goods infrastructure for impact measurement, capital allocation, and community coordination. We work best with partners who bring a clear field context, user need, data source, funder requirement, community, or deployment environment.

Good partner fits

• Regen communities and chapters that need tools for documenting work, coordinating contributors, or reporting impact.
• Funders and evaluators that need clearer evidence, reporting, funding pathways, or grant-delivery support.
• Infrastructure partners with data, identity, attestation, funding, storage, or coordination primitives that can help guild projects.
• Implementation partners who want to co-build open-source surfaces with a clear user group and maintenance path.

What to send

Email contact@greenpill.builders with:

• Who you are and which organization or community you represent.
• The concrete problem or opportunity.
• Which guild project or area you think it touches, if known.
• Relevant timelines, deadlines, or funding constraints.
• Links to public context, docs, demos, data samples, or prior work.
• Any privacy constraints we should respect before discussing publicly.

Do not send private keys, secrets, private user data, or security vulnerabilities. Vulnerabilities go to security@greenpill.builders.

What happens next

1. A steward or maintainer does an initial fit check.
2. If there is a real product, research, funding, or implementation thread, we capture the signal in Linear as a Customer Need, Research Issue, Product Issue, or funding lifecycle item.
3. If the work becomes public execution, it links out to the relevant GitHub repo issue or pull request.
4. If the collaboration needs non-public evidence, drafts, or partner materials, those live in Drive.
5. If there is no clear fit, we will say so directly and avoid creating idle backlog.

Linear is the project-management source of truth for partner needs and accepted work. GitHub is used when the work becomes public implementation or a guild-wide RFC.

Funding and paid work

Some guild work is volunteer open-source contribution. Paid work depends on an active grant, sponsor commitment, or steward-approved budget. Funding terms, deliverables, acceptance criteria, and review path must be agreed before treating any issue or partner request as paid work.

Open issues, roadmap ideas, community requests, and partner conversations are not automatically funded work.

Public and private surfaces

• Public by default: open-source code, public issues, pull requests, accepted RFCs, high-level community updates.
• Private when needed: partner strategy, budgets, unannounced funding conversations, sensitive metrics, personnel matters, and raw meeting notes.
• Never public as an issue: security vulnerabilities, private user data, secrets, or confidential partner information.

Contact

• General partnerships: contact@greenpill.builders
• Stewardship and governance: steward@greenpill.builders
• Security disclosures: security@greenpill.builders