ECSoC '26 Document // Rev 1.5

The Rules of the Game

ECSoC is a structured open-source cohort. Points are calculated and logged automatically by the ECSoC Sentinel GitHub bot to eliminate manual audits and ensure a fair public leaderboard.

Daily PR Limit
5 PRs / Project

Max 5 merged PRs per project per contributor each day. Extra merges won't yield XP.

Onboarding Credit
20 XP Base

Credited to all roles immediately upon profile registration and approval.

Mentorship Index
10 XP / Review

Awarded to mentors for each valid code review log submitted on the workspace.

How to Contribute

01
Apply & Profile Verification
Submit your profile details through the onboarding form at /apply.
  • Fill in developer stack, GitHub profile, and optional referral fields.
  • Coordinate with admins for review; receive 20 base XP on approval.
  • Unlock personal dashboard workspace and contribution history tracker.
02
Select Enrolled Projects
Navigate to the project listing directory at /projects.
  • Inspect technical requirement lists, repository specifications, and community links.
  • Fork the repository, configure the project locally, and confirm tests pass.
  • Join specific Discord/WhatsApp channels linked to coordinate with project admins.
03
Claim Issues & Workspace Preparation
Locate open issues marked with difficulty tags on the project repo.
  • Comment on the GitHub issue to state your intent and wait for maintainer assignment.
  • Create a local feature branch named according to the ticket (e.g., feature/issue-12).
  • Avoid duplicate work by checking pull request queues before starting coding.
04
Implement Changes & Local Checks
Write tests and implementation details according to contributing manuals.
  • Ensure code matches styling conventions (lint rules, typescript schemas).
  • Verify build locally using 'npm run build' or equivalent commands before pushing.
  • Commit code cleanly with explanatory commit messages.
05
Pull Request Submission & Tagging
Submit a pull request targeting the parent repository's default branch.
  • Explain changes, tests run, and link the corresponding issue.
  • Ensure the exact label 'ECSoC26' is applied to the PR before or during merge.
  • Do not use brackets or typos; the scoring engine checks for the exact text label 'ECSoC26'.
06
Merge Verification & Sentinel Scoring
Once the project admin merges your PR, ECSOC Sentinel automatically triggers.
  • Sentinel validates the label, parses complexity parameters, and runs anti-fraud rules.
  • XP is credited: 5 XP (L1), 10 XP (L2), or 15 XP (L3) based on difficulty.
  • Your rank is resolved on the public leaderboard within 5 minutes of merge.

Strict Daily Limit: 5 PRs per Project

You can submit up to 5 merged pull requests per project per day. This threshold operates independently across repositories.

✓ OK: 5 merges on Project A + 5 merges on Project B on the same calendar day.
✗ FAILED: Merging a 6th PR on Project A: Only the first 5 earn points, the 6th yields zero XP.

Scoring Engine Mechanics

Once a PR carrying the ECSoC26 label is merged:

Difficulty GradeSentinel Action LabelXP Scored
L1 (Easy)ECSoC26-L15 XP
L2 (Medium)ECSoC26-L210 XP
L3 (Difficult)ECSoC26-L315 XP

Bonus Endorsements

Project Admins (PAs) can award additional Bonus XP by applying one of these extra labels to your merged PR:

Bonus MetricGitHub LabelXP Increment
Outstanding Issue Scopegood-issue+10 XP
Exceptional PR Execution / Code Refactorgood-pr+15 XP
Stunning UI/UX Design & Executiongood-ui+25 XP
Complex Backend, Indexes or Database Schema Changesgood-backend+50 XP

Note: Bonus labels can only be assigned by Project Admins (PAs) for contributions that exceed the base parameters of a pull request.

Code of Conduct: Anti-Cheat & Fair Play

Academic and engineering honesty is vital for ECSoC. Attempts to manipulate scores will lead to immediate disqualification, complete points forfeit, and a permanent block across all future cohort cycles.

Permissible Collaboration

• Discussing architecture blueprints and optimization strategies.

• Co-debugging setup issues or sharing environment parameters.

• Referencing public document structures and API schemas.

Strictly Forbidden

• Copy-pasting other candidates' active PR codebase changes.

• Bypassing daily limits by creating duplicate user log profiles or fake git handles.

• Collaborating to merge empty or trivial commits to game leaderboard positions.

Frequently Asked Questions

Can I apply for multiple roles at the same time?
What occurs if my pull request is closed without being merged?
How quickly does Sentinel resolve score additions?
Is the ECSoC26 title label tag required?
What is the daily merge limit?
When do I get my referral points?