proposal outreach

Socialize the proposal before the vote

A clear proposal is necessary, but it is not enough. Proposers also need to help the community understand the work, test the assumptions and see how feedback changed the final submission.

why it matters

Good proposals need a review path

Treasury proposals ask the community to make a public funding decision. That decision is easier when the proposal has already been discussed with the people most likely to use, maintain, evaluate or oppose the work. Socializing a proposal is not just promotion; it is part of due diligence.

The goal is to make review constructive before the final version is locked. A strong socialization process gives reviewers enough context to ask useful questions, gives proposers time to respond, and gives DReps and voters a public trail of how concerns were handled.

practical steps

What to do before submission

01

Share before it feels finished

Post an early draft with specific questions. It is easier for reviewers to help before scope, budget and milestones feel locked.

02

Name the people affected

Identify users, maintainers, DReps, SPOs, working groups and projects that should understand the proposal before it reaches a vote.

03

Make feedback easy

Give reviewers a short summary, the full proposal, the budget, milestone evidence and a clear place to leave comments.

04

Respond in public

When feedback changes the proposal, leave a visible trail of what changed and why. When it does not, explain the tradeoff.

05

Ask for opposition early

A useful review process should surface objections while there is still time to improve the proposal or narrow its scope.

06

Keep evidence close

Link repositories, reports, adoption signals, demos, audits and prior funding history from the proposal and from discussion threads.

resources

Places to start