semantica/docs/governance.md at 2aff515e57ff353acd606520a05b7ecd910cd2dc

mirror of https://github.com/semantica-agi/semantica.git synced 2026-08-29 04:26:20 +00:00

Files

T

KaifAhmad1 453eeb7ca9 fix: rename contributing/license pages to avoid Mintlify reserved slug conflict

mint export fails with 'file does not exist' for pages named 'contributing'
and 'license' — these are reserved by Mintlify's GitHub integration layer.
Renamed to contributing-guide.md and project-license.md and updated all
nav entries and cross-links throughout the docs.

Also adds .gitattributes LF rules to prevent CRLF issues from Windows devs.

2026-05-23 00:14:23 +05:30

3.0 KiB

Raw Blame History

title, description, icon

title	description	icon
Governance	Project governance model — roles, decision process, release cadence, and code review guidelines.	scale-balanced

Semantica is maintained by Hawksight AI with community contributions under an open governance model.

Roles

Maintainers (Hawksight AI team)

Review and merge pull requests
Manage releases and code quality
Set project direction and community standards

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

Open a GitHub Issue describing the change. Community discussion on approach and scope. Submit a pull request with the change. At least one maintainer reviews the PR. Merged after CI passes and maintainer approval.

Major Decisions

RFC posted in GitHub Issues
Minimum 1-week community discussion period
Maintainers decide based on community feedback and technical feasibility

Releases

Semantica follows Semantic Versioning (MAJOR.MINOR.PATCH):

Level	Trigger	Cadence
MAJOR	Breaking changes	Quarterly or as needed
MINOR	New features (backward compatible)	Monthly or when ready
PATCH	Bug fixes (backward compatible)	As bugs are fixed

Code Review

Review criteria: functionality, code quality, tests, documentation, performance, security.

Timeline: initial review within 48 hours; follow-up within 7 days.

Guidelines for reviewers: be constructive, explain reasoning, suggest alternatives.

Guidelines for contributors: address comments promptly, ask questions when unclear, be open to feedback.

Communication

GitHub Issues — bug reports, feature requests, questions
GitHub PRs — code contributions
GitHub Discussions — community conversation
Security Advisories — report security issues privately

Project Goals

Usability — Easy to use and understand
Reliability — Production-ready quality
Performance — Efficient and scalable
Extensibility — Easy to extend with plugins and custom modules
Community — Welcoming and inclusive

License

MIT License — see LICENSE and the License page.

3.0 KiB Raw Blame History