Community¶
Building a Connected Ecosystem¶
CyberEco is more than a collection of applications -- it is a community of people who believe technology should serve human well-being. We build in the open, make decisions transparently, and welcome contributions from everyone who shares our values of digital sovereignty, privacy, and human-centered design.
Community Guidelines
Be respectful, helpful, and inclusive. We are all here to build something meaningful together. Every voice matters, every contribution counts.
Ways to Participate¶
Connect with the CyberEco community through the channels that work best for you.
GitHub¶
Contribute to open source development
Our primary development hub. Browse the codebase, open issues, submit pull requests, and participate in discussions about the future of the ecosystem.
- Repository: github.com/cyber-eco/cybereco-hub
- Organization: github.com/cyber-eco
Community Forum¶
Ask questions and share knowledge
Our community forum is the place for longer-form discussions, feature proposals, and knowledge sharing. Use GitHub Discussions to propose ideas and engage with the broader community.
- Discussions: GitHub Discussions
Email Support¶
For technical issues or account problems, reach out to us directly.
- Email: info@cybere.co
How to Contribute¶
CyberEco follows an open-core model: our data layer packages (@cyber-eco/*) are open source (Apache-2.0), while the Hub platform itself is proprietary. We welcome contributions from developers, designers, and community members worldwide. Here is how you can help shape the future of digital sovereignty.
For Developers¶
Follow these steps to contribute code to CyberEco.
Step 1: Pick an Issue
Browse our GitHub issues labeled good first issue or help wanted. These are curated entry points designed to help new contributors get started quickly.
Step 2: Fork & Clone
Fork the repository and clone it to your local machine.
Step 3: Create a Branch
Create a feature branch from main with a descriptive name.
Before Submitting
Make sure your code passes all checks before opening a pull request:
For Community Members¶
You do not need to write code to make a meaningful contribution to CyberEco. Here are other ways to help.
| Contribution | Description |
|---|---|
| Provide Feedback | Test applications and report bugs or suggest improvements. Your experience as a user is invaluable. |
| Improve Documentation | Help write guides, tutorials, and explanations. Clear documentation makes CyberEco accessible to more people. |
| Translate Content | Help translate CyberEco to your language. We currently support English and Spanish, with more languages planned. |
| Spread the Word | Share CyberEco with others who value digital privacy and user sovereignty. Word of mouth is our strongest growth channel. |
| Share Ideas | Propose new features, new applications, or improvements in GitHub Discussions. The ecosystem roadmap is shaped by community input. |
Community-Driven Development¶
CyberEco follows an open development model where community participation directly influences the direction of the project.
Open Source¶
Our data layer packages (@cyber-eco/types, @cyber-eco/firebase, @cyber-eco/auth, @cyber-eco/services) are open source and published to npm. Anyone can inspect the code, suggest improvements, or build CyberEco-compatible applications using the published packages.
User Feedback Shapes the Roadmap¶
Feature priorities are informed by community input. We use GitHub Discussions and Issues to gather feedback, and we publish our roadmap publicly so everyone can see where we are headed and why.
Transparent Decisions¶
Architecture decisions, engineering trade-offs, and strategic direction are documented in our Strategic Documentation. When we make significant changes, we explain the reasoning publicly.
Governance Roadmap
As CyberEco matures, governance will transition from a core team model to a community-driven model. The CYE token will enable quadratic voting, proposal management, and transparent resource allocation -- giving every community member a meaningful voice.
Resources¶
- Getting Started -- Set up your development environment
- Architecture -- Understand the system design
- Roadmap -- See where we are headed
- Mission & Values -- Learn what drives us