Proposing a contribution sprint #

This page is for advocates who want people to contribute together for a few hours. A sprint is your own initiative, like a meetup (Proposing a meetup); no sprints are documented as official events. Its result is real pull requests and confirmed issues.

Contents #

1. Choose a theme
2. Prepare tasks
3. The agenda
4. During the sprint
5. Wrap-up

Choose a theme #

Prepare tasks #

• A list of small, real tasks, each doable in under an hour, with a link (a help page to check, a set of strings, an issue to reproduce).
• A test installation per participant, or instructions to make one (Install in one command).
• GitHub accounts ready (with two-factor authentication).
• A shared, public task list (a forum thread works) without personal data.

The agenda #

CONTRIBUTION SPRINT: <theme>                <date>, <time>, <place | online>   (organized by <you>)
0:00  Welcome, how to contribute (commit messages, pull requests, licenses)        15 min
0:15  Pick a task; pair newcomers with experienced people                          15 min
0:30  Work                                                                         2 h
2:30  Show and tell: what each pair did                                            20 min
2:50  Next steps; thanks                                                           10 min

During the sprint #

• Commit messages start with Added:, Updated:, Fixed:, Removed: or Renamed: (CONTRIBUTING.md).
• One small pull request per task.
• No secrets or personal data in changes, logs or screenshots.
• Security findings go privately (Security reports stay private).

Wrap-up #

1. Post the list of pull requests and confirmed issues in the forums.
2. Thank participants, by public handle and with consent (Recognition ideas).
3. Note what blocked people and improve the guides.

Related pages #

• Proposing a meetup
• Mentoring a first contribution
• Event checklists
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.