TERMS OF SERVICE & CONDUCT
// SECTION 01
Acceptance of Terms
GUIDELINE #01.01
Binding Community Contract
By accessing the GREVIX portal, participating in community hackathons, or submitting recruitment applications, you agree to be bound by these Terms of Service.
GUIDELINE #01.02
Student & Academic Alignment
GREVIX is a student-driven software and research collective. Members agree to uphold academic honesty and ethical software development standards in all initiatives.
GUIDELINE #01.03
Eligibility Requirements
Participation in core technical projects is open to enrolled university students, self-taught developers, and accredited academic research collaborators.
GUIDELINE #01.04
Modifications to Terms
GREVIX reserves the right to amend community terms at any time. Continued engagement following published amendments constitutes binding acceptance.
GUIDELINE #01.05
Jurisdiction & Good Faith
All community interactions and disputes are governed under principles of good-faith open-source collaboration and applicable local regulations in India.
// SECTION 02
Member Code of Conduct
GUIDELINE #02.01
Zero Tolerance for Harassment
GREVIX enforces a strict zero-tolerance policy against discrimination, harassment, toxic communication, or offensive behavior across all platforms and Discord servers.
GUIDELINE #02.02
Constructive Peer Review
Pull request reviews, architecture feedback, and code critiques must remain respectful, constructive, and focused objectively on technical merit.
GUIDELINE #02.03
Responsible Vulnerability Disclosure
Security vulnerabilities discovered in community projects must be confidentially reported to lead maintainers before public disclosure.
GUIDELINE #02.04
Prohibition of Malicious Code
Intentionally committing backdoors, malware, keyloggers, cryptominers, or destructive payloads to community repositories results in immediate expulsion and reporting.
GUIDELINE #02.05
Conflict Resolution Protocol
Interpersonal or project leadership disputes are mediated by designated core team leads through transparent, structured conflict resolution channels.
// SECTION 03
Intellectual Property & Open-Source
GUIDELINE #03.01
Open-Source Default License
Unless explicitly specified otherwise, code assets built within GREVIX core projects are distributed under permissible open-source licenses (e.g. MIT or Apache 2.0).
GUIDELINE #03.02
Contributor License Assignment
By submitting code pull requests to GREVIX repositories, contributors grant the community a non-exclusive, worldwide, royalty-free license to use and distribute the code.
GUIDELINE #03.03
Author Attribution Protection
Original student authors retain permanent attribution credit in git commit histories, repository release notes, and project documentation catalogs.
GUIDELINE #03.04
Third-Party Library Compliance
All open-source dependencies used in GREVIX projects must comply with compatible licensing rules. Copyleft or proprietary license violations are prohibited.
GUIDELINE #03.05
Brand & Logo Usage
The GREVIX wordmark, visual logos, and reticle brand assets may not be used for unauthorized commercial products without written consent from core leadership.
// SECTION 04
Events & Hackathons Standard
GUIDELINE #04.01
Original Work Rule
Projects submitted to GREVIX Genesis Hackathons or coding sprint challenges must be built during the official competition window. Pre-built code must be declared.
GUIDELINE #04.02
Plagiarism & Anti-Cheating
Submitting plagiarized repositories or attempting to game automated quiz/hackathon leaderboards results in instant team disqualification.
GUIDELINE #04.03
Judging Impartiality
Hackathon evaluation is conducted by technical mentors according to published scoring rubrics. Judging decisions rendered are final.
GUIDELINE #04.04
Prize Distribution
Sponsorship rewards, mentorship grants, or certificates earned during official events are disbursed upon verification of participant eligibility.
GUIDELINE #04.05
Media & Project Showcase
Hackathon participants grant GREVIX permission to feature project demonstrations, screenshots, and team summaries in public community showcases.
// SECTION 05
Membership & Application Protocol
GUIDELINE #05.01
Accurate Information Requirement
Applicants must provide genuine, functional email addresses and legitimate GitHub profiles when submitting recruitment applications.
GUIDELINE #05.02
Duplicate Application Rejection
Multiple submissions using duplicate email addresses or identical GitHub profile URLs are blocked automatically to preserve system integrity.
GUIDELINE #05.03
Application Review Timeline
GREVIX core leads aim to evaluate submitted candidate profiles within 14 days, sending notification updates via the provided email.
GUIDELINE #05.04
Termination of Membership
Core leadership reserves the right to revoke community membership or repository write access for severe violations of code of conduct guidelines.
GUIDELINE #05.05
Voluntary Resignation
Members may resign from active research teams at any time by notifying team leads and transferring ongoing project maintenance duties.
// SECTION 06
Disclaimers & Liability Limits
GUIDELINE #06.01
"As-Is" Software Provision
All open-source tools, experimental codebases, and website content are provided "as-is" without warranty of any kind, express or implied.
GUIDELINE #06.02
Limitation of Liability
GREVIX, its student maintainers, and community contributors shall not be liable for any direct, indirect, or incidental damages arising from software usage.
GUIDELINE #06.03
Service Availability
We do not guarantee uninterrupted local server uptime or error-free web operation during community infrastructure maintenance.
GUIDELINE #06.04
Third-Party Platforms
GREVIX is not responsible for outages, policies, or data practices of third-party platforms including GitHub, Discord, or web browsers.
GUIDELINE #06.05
Inquiries & Legal Contact
For legal notices, terms clarification, or governance queries, contact official leadership at
teamgrevixorg@gmail.com.