mengzhx/semantica
1
0
Fork 0
mirror of https://github.com/semantica-agi/semantica.git synced 2026-08-29 04:26:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
fbbe36983bc3ed28e5cfd0ac412c859e795fa497
semantica/docs/governance.md
T
KaifAhmad1 ba04b0bbc6 docs: remove email addresses and add discussion templates 
- Remove email addresses from support, security, contributing, and community docs
- Replace email contacts with GitHub Issues and Security Advisories
- Add discussion templates for Q&A, Ideas, Showcase, and General discussions
- Update SUPPORT.md with Discussions section
2025-12-03 11:19:07 +05:30

2.2 KiB
Raw Blame History

Governance

Project governance model for Semantica.

!!! info "Open Source" Semantica is maintained by Hawksight AI with community contributions.

👥 Roles

Maintainers (Hawksight AI team)

  • Review and merge pull requests
  • Manage releases and code quality
  • Community management and project direction

Contributors

  • Submit code, documentation, and bug reports
  • Help with issues and reviews
  • Recognized in CONTRIBUTORS.md

Community Members

  • Use Semantica and provide feedback
  • Share use cases and participate in discussions

🔄 Decision Process

Code Changes

  1. Proposal via GitHub Issues
  2. Community discussion
  3. Implementation (PR)
  4. Review by maintainers
  5. Approval (at least 1 maintainer)
  6. Merge after CI passes

Major Decisions

  • RFC in GitHub Issues
  • 1 week minimum discussion
  • Maintainers decide based on community feedback and technical feasibility

📦 Releases

Versioning (Semantic Versioning)

  • MAJOR: Breaking changes
  • MINOR: New features (backward compatible)
  • PATCH: Bug fixes (backward compatible)

Schedule

  • Major: Quarterly or as needed
  • Minor: Monthly or when ready
  • Patch: As bugs are fixed

🔍 Code Review

Criteria: Functionality, code quality, tests, documentation, performance, security

Timeline: Initial review within 48 hours, follow-up within 7 days

Guidelines:

  • Reviewers: Be constructive, explain reasoning
  • Contributors: Address comments, ask questions, be open to feedback

💬 Communication

  • GitHub Issues: Bug reports, features, questions
  • GitHub PRs: Code contributions
  • GitHub Security Advisories: Report security issues

🎯 Project Goals

  1. Usability - Easy to use and understand
  2. Reliability - Production-ready quality
  3. Performance - Efficient and scalable
  4. Extensibility - Easy to extend
  5. Community - Welcoming and inclusive

📄 License

MIT License - See LICENSE

Contact: GitHub Issues

Reference in New Issue View Git Blame Copy Permalink