CommonBerry is an organization dedicated to fostering serious, long-term open-source projects built with meticulous planning and sustainable maintenance in mind. We are not a repository for experimental code or hobby scripts; rather, we are a curated collection of production-grade software engineered for reliability and longevity.

Projects under the CommonBerry umbrella adhere to stringent quality standards, ensuring a consistent and high-caliber output:

• Rigorous Planning: Every project is conceived with comprehensive architectural design and a clear roadmap for future development.
• Consistent Code Quality: We enforce strict coding guidelines and best practices to maintain uniformity and readability across all repositories.
• Semantic Versioning: All projects follow Semantic Versioning (SemVer) to clearly communicate changes and facilitate predictable updates.
• Active Maintenance: A strong commitment to ongoing maintenance, bug fixes, and feature enhancements is paramount for all hosted projects.

CommonBerry currently hosts the following projects, each exemplifying our commitment to excellence:

• coreOps: A complete, modern rewrite of the procps-ng utility suite in Rust, commencing with bee, an advanced memory monitor.
• Invoice: A professional command-line interface (CLI) for freelance project management, joining CommonBerry at its Release Candidate 1 (RC1) stage.

To be considered for inclusion in CommonBerry, projects must meet the following rigorous criteria:

• Architecture Documentation: Comprehensive documentation outlining the project's architecture, design decisions, and component interactions.
• Defined Roadmap: A clear and actionable roadmap detailing future development, milestones, and long-term vision.
• Test Coverage: A robust suite of tests demonstrating high code coverage and ensuring software reliability.
• Maintainer Commitment: A demonstrated commitment from maintainers to provide long-term support, maintenance, and continuous development for the project.

Our philosophy prioritizes quality and sustainability above all else. Projects are accepted into CommonBerry based solely on their technical merit, adherence to our quality standards, and the demonstrated commitment of their maintainers to long-term support. This organization is expressly not a dumping ground for personal experiments or unmaintained code. Such projects, while potentially valuable, belong elsewhere. CommonBerry is exclusively for production-grade software.

Contribution guidelines are specific to each project. Please refer to the individual project repositories for detailed instructions on how to contribute.

For inquiries, organizational matters, or to propose new projects that align with our stringent criteria, please refer to the contact information provided within the individual project repositories or relevant communication channels established by the CommonBerry maintainers.