Developer Contribution Guidelines
Standardized software engineering pathways for student contributors in Batch 23.
1. Public Technical Communication
"Ask Once, Help All"
Private DMs for technical help are strictly discouraged. All bug reports, technical queries, and architectural questions must be asked in public channels or GitHub Discussions so the entire batch learns together.
2. Clean Branching & Commit Standards
Conventional Commits & Clean History
Always create a feature branch off the main branch (e.g. feat/auth-flow or fix/nav-alignment). Write descriptive commit messages and ensure your code compiles cleanly without linter warnings.
3. PR Review & Checklist
Self-Review & Test Verification
Verify that all unit tests pass before requesting review. Include screenshots or terminal outputs in PR descriptions. Comment on issues tagged with 'good-first-issue' to request assignment before starting work.
4. Permanent Collaborator Pathway
Earn Direct Branch Write Access
Once you achieve 3 merged non-trivial Pull Requests and active participation in community discussions, you earn the Permanent Collaborator badge and direct write access to project repositories!