
Contributing Guide
Docs + Word8 pages
Free
A code of conduct only works when people know whom to contact and what happens next. This seven-page Google Docs sample pairs a short pledge and plain standards with named responders, a reporting scorecard and a graduated enforcement ladder, so nothing stays implicit until the first conflict.
The sample follows Junipera Software, a fictional project with a conduct team of three, a 48-hour first reply and a 30-day target for closing reports. Replace the project name, contacts, response times and consequences with the ones your maintainers will actually keep, then have your own advisers review the final text.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Replace Junipera Software, the pledge wording and the review dates with your project's own details.
Enter real conduct team names and a monitored email address, then change the reply and closing times to ones you can meet.
Edit the standards and the enforcement ladder to match the actions your maintainers are willing to take, and ask a qualified adviser to review them.
Delete the guide page, then share the document or link it from your contributing guide and repository.
Yes. Make a copy in Google Docs and it is yours to edit, with no sign-up on this site and no cost.
No. It is a sample of how a community policy can be organized. Have a qualified adviser review your final wording before you publish it.
No. Junipera Software, its conduct team and every figure are fictional and made up for the example. Replace them with your own details.
More Google Docs templatesMore developer workflows templates

Docs + Word8 pages
Free
Slides + PowerPoint11 slides
Free
Docs + Word7 pages
Free
Docs + Word7 pages
Free
Slides + PowerPoint12 slides
Free