--- title: "How to Participate" section: "community" description: "How to contribute to the Open Agentic ITSM Framework: discussion, content contribution, and community participation" version: "0.2-draft" status: "draft" license: "CC BY 4.0" last_updated: "2026-08-13" --- The Open Agentic ITSM Framework is a community resource. Its value grows when practitioners, architects, researchers, and vendors contribute their experience and challenge its assumptions. This page explains how to do that. --- ## Governance Model Status The framework's community governance is presently lightweight by design. The framework is new, the community is forming, and imposing a heavy governance structure before there is a community to govern would produce bureaucracy without benefit. The current model is simple: the framework is hosted on GitHub, contributions are made through standard GitHub mechanisms (Issues and Pull Requests), and the founding author reviews and merges contributions based on the standards defined in the [Contribution Rules](contribution-rules.md). As the community grows, as the framework reaches version 1.0, and as the need for more formal governance becomes clear, the model will evolve. That evolution will itself be a community process, proposed and discussed openly before implementation. If you have strong views on how the governance model should develop, open an Issue with the label `governance` and make your case. --- ## Ways to Participate ### Raise Issues The simplest and most valuable contribution is identifying something that is wrong, unclear, incomplete, or missing. Open a GitHub Issue for: - Factual errors in any section - Unclear or ambiguous language that should be improved - Missing topics or domains that should be covered - Outdated information (vendor capabilities, market data, research citations) - Structural feedback on how the framework is organized - Questions that the framework should answer but does not Issues do not require you to provide the solution. Identifying the problem is a contribution. **Issue labels in use:** - `error` for factual inaccuracies - `unclear` for language or structure that needs improvement - `missing-content` for topics not covered - `outdated` for information that needs updating - `vendor-landscape` for vendor landscape contributions - `governance` for discussion of the framework's own governance - `question` for questions addressed to the community ### Submit Pull Requests To contribute content directly, submit a Pull Request. Every PR must: 1. Reference a GitHub Issue that describes the problem being addressed 2. Comply with the [Contribution Rules](contribution-rules.md), including the IP requirement 3. Follow the document formatting conventions (FrontMatter tags, markdown structure, no em-dashes, no emojis, professional register) 4. Include accurate citations for any new factual claims 5. Be vendor-neutral in framing Pull Requests for entirely new pages or major structural changes should be discussed in an Issue before submission to avoid redundant effort. ### Participate in Discussions The GitHub Discussions feature is used for open-ended community conversation that is not tied to a specific Issue or PR. Topics include: - How organizations are applying the framework in practice - Research findings relevant to the framework's content - Proposed extensions or adjacent topics - Introductions from new community members ### Apply the Framework and Report Back The most valuable long-term contribution is using the framework in real deployments and reporting what you learn. Did the process gap tables in the domain pages accurately reflect your experience? Did the metrics in Section 6 work as described? Did the governance model in Section 7 identify requirements you had missed? Application experience, whether positive or negative, is exactly what the framework needs to improve. Report it through Issues or Discussions with the label `deployment-experience`. --- ## What to Expect When You Contribute The founding author reviews all Issues and Pull Requests on a regular basis. The current target response time for Issues is five business days. Pull Requests targeting factual corrections or minor improvements will be reviewed and merged within ten business days. Larger contributions require more time for review. Contributors whose Pull Requests are merged will be acknowledged in the framework's changelog. Contributors who make significant ongoing contributions may be invited to take on a named maintainer role as the governance model formalizes. All community interactions should follow basic standards of professional respect. Disagreement about content is welcome. Personal criticism is not. --- ## Contact For questions about contribution that are not answered here, open a GitHub Issue with the label `question` or contact the project through the information in the repository README.