Skip to content

Latest commit

 

History

History
65 lines (42 loc) · 2.6 KB

File metadata and controls

65 lines (42 loc) · 2.6 KB

Contributing to Meta-organvm: Umbrella Organization

Thank you for your interest in contributing to the organvm system.

Code of Conduct

All participants are governed by our Code of Conduct.

How to Contribute

Scope

This organization covers: Cross-organ coordination, system-wide governance, umbrella documentation.

Getting Started

  1. Fork the target repository
  2. Create a branch (feature/your-feature or fix/your-fix)
  3. Follow existing code style — check each repo's README for stack details
  4. Write tests — maintain or improve coverage
  5. Submit a PR with clear description of changes

What We Accept

  • Bug fixes with tests
  • Documentation improvements
  • Performance optimizations
  • Security patches (see SECURITY.md)
  • Feature proposals via Issues (discuss before implementing)

What Requires Discussion First

  • System-wide governance changes, cross-organ coordination policies, umbrella documentation structure

Licensing

Changes to meta-organvm affect all 7 organ organizations. Proposals require broader review and must demonstrate cross-organ impact.

Development Standards

  • TypeScript: strict mode, named exports, async/await
  • Python: PEP 8, type hints, f-strings
  • Tests required for all new functionality
  • Commit messages: imperative mood, <72 chars title
  • README structure and depth must follow README standards

First-Time Contributors

Look for issues labeled good first issue across our repositories:

Getting Help

  • GitHub Discussions — ask questions, propose ideas, share feedback
  • Issues — report bugs or request features on the relevant repository
  • Check existing documentation in each repo's README

Part of the organvm eight-organ system