Community Guidelines

React Aligarh exists as a structured builder ecosystem where technical contribution determines standing. We do not operate on familiarity, tenure, or social presence. Every participant's position — from Participant to Core Team — is earned through demonstrable work that advances our collective mission.

We believe that great technical communities are built on proof-of-work, not personality. Your code, documentation, project leadership, and technical mentorship define your place here. Popularity without contribution carries no weight. Tenure without output commands no influence.

Each role carries specific privileges and corresponding responsibilities. Progression is neither automatic nor time-based — it requires demonstrated contribution at the current level before advancement is considered.

Technical collaboration requires environments where ideas can be challenged without personal attack, and where feedback focuses on work products rather than individuals.

Expected Behavior

• Technical disagreement without personal dimension — critique code, not character.
• Direct, honest feedback on work, delivered with clarity and specificity.
• Respect for others' time through prepared questions and documented research.
• Recognition of contribution regardless of role or tenure.

Not Tolerated

• Ad hominem attacks or dismissive language toward contributors.
• Social manoeuvring to influence decisions without technical merit.
• Derailing technical discussions with non-technical objections.
• Gatekeeping knowledge or access to suppress contribution.

We hold different expectations for those learning and those guiding — both are equally valued.

Recognition within React Aligarh is earned exclusively through demonstrable output. There are no shortcuts.

The integrity of what we build depends on the integrity of how we build it. These rules are non-negotiable.

• All contributions must be original work or properly attributed to the source.
• Plagiarism results in immediate removal and a permanent record of the violation.
• AI assistance must be disclosed in pull request descriptions — no exceptions.
• Real work only — synthetic contributions, padding, or low-effort filler is rejected.
• Open source licenses must be respected in all borrowed or adapted code.

Clear, purposeful communication is as important as clean code. These standards apply across all community channels.

• Technical discussions occur in public channels by default — transparency builds trust.
• Decisions include rationale, not just conclusions — show your thinking.
• Questions must show prior research effort — demonstrate what you tried first.
• Feedback is specific, actionable, and respectful — vague criticism helps no one.
• Keep threads on-topic — noise degrades the signal for everyone.
• Announcements and important decisions are documented, not just spoken.

Core Team members and Core Participants hold elevated responsibilities. With greater access comes greater accountability.

• Model technical excellence and uphold communication standards at all times.
• Make decisions transparently with documented rationale accessible to the community.
• Actively identify and develop future contributors — invest in the next generation.
• Remove barriers to contribution, not create them — your role is to enable, not gatekeep.
• Step back or step down when unable to fulfill responsibilities fully.

Violations are addressed proportionally and documented. All moderation actions are reviewed by the Core Team and subject to appeal through a structured process.

• First violation — private warning with specific citation of the violated guideline.
• Repeated violations — temporary suspension with defined reinstatement conditions.
• Severe violations — immediate and permanent removal from all community spaces.

React Aligarh is not for everyone — and that's intentional. We are a focused community with a specific purpose.

These guidelines exist to protect what we build together. They are enforced consistently, reviewed periodically, and evolved through Core Team consensus. Our culture of contribution-based recognition is our most valuable asset — we defend it actively.

Questions about these guidelines or reports of violations can be directed to our Core Team at any time.