Community Guidelines

Building a compassionate, collaborative space for second chances

The Osiris Philosophy

Everyone deserves a second chance. Every project—no matter how small, incomplete, or "failed"—has value. We're here to support, not judge. To revive, not abandon. To build teams, not compete.

Core Principles

No Judgment Zone

Failed projects are learning experiences. Abandoned work is still valuable. We celebrate the courage to try and try again.

Collaboration Over Competition

Multiple people can adopt the same project. We form teams with diverse skills. Success is shared, not hoarded.

Respect & Empathy

Everyone's journey is different. Be kind to creators, supportive of adopters, and inclusive of all skill levels.

Constructive Communication

Give feedback that helps. Ask questions that build understanding. Cheer projects that inspire you.

Sharing Your Projects

What You Can Share

  • Code Projects: GitHub repos (public/private), abandoned apps, half-built tools, experimental code you never launched
  • Design Work: Figma files, mockups, design systems, UI kits, brand concepts that never shipped
  • Ideas & Concepts: Product visions, feature proposals, rough sketches needing builders
  • Anything Creative: If you made it and it deserves a second chance, share it. We welcome incomplete, messy, experimental work.

Sharing Guidelines

  • Be honest about why you abandoned it. Life happens. Be real.
  • Describe what's built and what's missing. Help adopters understand the state.
  • Only share work you own or have permission to share.
  • You can post anonymously. We protect your privacy.
  • Respond to comments and questions when possible (but no pressure).

What Not To Share

  • Work you don't own or don't have rights to share
  • Malicious code, security exploits, or illegal content
  • Active projects you're still maintaining (Osiris is for revivals)
  • Spam, ads, or purely promotional content

Adopting & Collaborating

The Adopter's Promise

  • Commit to the project — Don't adopt what you won't nurture. It's okay to adopt less and do more.
  • Credit the original creator — Always acknowledge who started this. Their work deserves recognition.
  • Communicate with your team — Update progress, ask questions, collaborate openly.
  • It's okay to step away — Life happens to everyone. If you need to leave, communicate it to your team.

Team Collaboration

  • Respect different roles: developers code, designers create, visionaries guide, supporters cheer.
  • Use @mentions respectfully. Don't spam or demand attention.
  • Upvote helpful comments. Cheer projects you believe in.
  • When disagreeing, focus on ideas, not people. Be constructive, not critical.

Community Standards

💜 We Celebrate

  • •Incomplete work and "failed" projects
  • •Honest admissions of abandonment
  • •People trying again after setbacks
  • •Diverse teams with complementary skills
  • •Contributors of all roles (not just coders!)

🚫 We Don't Tolerate

  • •Shaming anyone for "failed" or incomplete work
  • •Gatekeeping based on skill level or role
  • •Harassment, bullying, or toxic behavior
  • •Stealing work or claiming others' projects as your own
  • •Spam, self-promotion, or exploitative behavior

Role-Specific Guidelines

Developers

  • →Document your code changes and decisions
  • →Test before marking tasks complete
  • →Collaborate with designers and visionaries

Designers

  • →Share design files with clear annotations
  • →Consider accessibility and user experience
  • →Work closely with developers on implementation

Visionaries

  • →Provide clear product direction and goals
  • →Help prioritize features and roadmap
  • →Bridge communication between team members

Supporters

  • →Cheer projects that inspire you
  • →Test features and provide feedback
  • →Help with docs, promotion, or community building

When Guidelines Are Broken

We believe in compassion and second chances for people too. Most issues can be resolved through clear communication. However, repeated violations or serious misconduct will result in action.

Our process: Warning → Temporary suspension → Permanent ban (for severe cases)

Report issues to conduct@osiris.team. We review all reports within 48 hours and take appropriate action.