Pythonlings Community Dev Sprint — August 22–23, 2026

[abhiksark]

Welcome

Pythonlings is hosting a public, beginner-friendly community development sprint on August 22–23, 2026 (Asia/Colombo). The sprint backlog is intentionally split into small, well-scoped work across documentation, curriculum, reliability, CI, the CLI, and the Textual TUI.

Getting set up

1. Read the contribution guidance and Code of Conduct.
2. Install the project with pip install -e ".[dev]", then run python -m pytest -q before starting.
3. Choose an unassigned sprint issue. You may leave a short coordination note, but issues are not reserved: for in-repository work, the first PR that meets every acceptance criterion and passes its checks is the one considered for merge.
4. Keep each PR focused, explain the user-facing result, and include the verification output requested by its issue.

Collaboration rules

• Ask implementation questions, share discoveries, and celebrate progress in this Discussion.
• Do not create a GitHub Project or promise a release as part of sprint work.
• External-directory work needs extra coordination: leave a preflight comment on the Pythonlings issue, wait for the upstream maintainer to approve the route, and submit only one human-authored PR to each upstream repository.
• Please do not submit a listing where the directory eligibility rules are not met. Research issues record evidence and objective revisit conditions instead.

Help and safety

• General help and design discussion: use this thread.
• Bug reports, feature ideas, and curriculum proposals: use the repository issue forms.
• Security vulnerabilities: follow the private reporting guidance in SECURITY.md; do not disclose them in public issues or this Discussion.

The umbrella tracker links every sprint issue once the backlog is published. Welcome — especially if this is your first open-source contribution!