Community Guidelines

These Community Guidelines outline the expectations for everyone building, sharing, and collaborating on Grove. Our mission is to ensure student projects — whether hackathon builds, research prototypes, or side projects — get discovered, credited, and carried forward.

By using the Service, you agree to follow these Guidelines alongside our Terms and Conditions and Privacy Policy. Where these Guidelines provide practical community standards, our Terms describe legal requirements.

We believe student work should be represented honestly and transparently.

• Credit real contributors: Only add people to project listings or team rosters who actually contributed to the work.
• Show genuine progress: Unfinished work is welcome, but be honest about what is built versus what is planned.
• Own your work: Never post work created by others without clear authorization or claim sole authorship over group efforts.
• No deceptive metrics: Do not inflate project views, likes, or comments through automated bots or artificial coordination.

Collaboration is the core of our community. Treat fellow builders with respect and professional courtesy.

• Constructive feedback: When reviewing or commenting on someone's project, offer thoughtful, encouraging, and constructive input.
• Private collaboration requests: Send collaboration messages only when you have a genuine proposal to build together. Do not use requests for commercial sales, spam, or unsolicited promotions.
• Respect boundaries: If a member declines a collaboration request or team invitation, respect their decision and do not continue contacting them unnecessarily.
• Zero tolerance for harassment: Bullying, hate speech, harassment, threats, or inappropriate personal comments will result in immediate moderation action.

Keep project listings informative, safe, and focused on building great products.

• Clear descriptions: Provide accurate taglines, technology tags, repository links, and descriptions so visitors can understand your project.
• No malicious software or links: Projects must not contain malware, phishing scripts, exploit tools, or harmful links.
• Intellectual property: Respect copyright, licenses, and university IP policies. Do not upload confidential research or embargoed data.
• Appropriate media: Ensure images, demo videos, and screenshots adhere to standard campus and community safety standards.

Teams are a shared identity for collaborative work.

• Voluntary participation: Joining or leaving a team is voluntary for all members.
• Leader responsibilities: Team leaders and founders must maintain accurate member roles and manage team settings responsibly.
• Project continuity: When a founder or member leaves a team, the work and contributions remain credited to their respective creators.

We actively review reports to maintain a safe, welcoming space for all student builders.

• Reporting issues: If you encounter content or behavior that violates these guidelines, report it directly to vionix37@gmail.com.
• Proportionate action: Minor violations may receive warnings or content edits, while repeated or severe misconduct will result in account suspension or termination.
• Appeals: If you believe a moderation action was made in error, contact us with relevant details for review.

If you have questions about these Community Guidelines, feedback, or need support, reach out to us at vionix37@gmail.com.