Skip to content

Latest commit

 

History

History
executable file
·
55 lines (30 loc) · 3.23 KB

GOVERNANCE.md

File metadata and controls

executable file
·
55 lines (30 loc) · 3.23 KB

Governance

OpenRigLogic is maintained by Epic Games. This document describes how OpenRigLogic is governed: who makes decisions and how they are made.

Roles

Contributor

Anyone who has had a pull request merged. Contributors participate in discussions, propose changes, and review pull requests. No formal nomination is required.

Core maintainer

Stewards of the project responsible for direction, security, and releases. They are responsible for triaging issues, reviewing pull requests, and are able to merge changes. Core Maintainers make final calls when consensus fails.

The current Core Maintainers are listed in MAINTAINERS.md. Initially these are employees nominated by Epic as having a proven history working with the code base before it became available as an open source project.

How contributions are accepted

  1. Open an issue - describe what you want to build or fix. For non-trivial changes, wait for a maintainer to weigh in before investing significant effort.
  2. Discuss - We aim to provide an initial response to issues within four weeks, though response times may vary.
  3. Open a pull request - follow the guidelines in CONTRIBUTING.md. Use the PR template.
  4. Review - approval from at least one Core Maintainer is required.
  5. Merge - a Core Maintainer merges the PR.

An objection blocks a PR. If it cannot be resolved through discussion, it is escalated to the Core Maintainers for a final decision.

Decision-making

For most decisions, consensus in the GitHub Issue or PR discussion is sufficient. When consensus fails, Core Maintainers decide. Decisions are made in public - in issues or PRs.

Major decisions - license changes, changes to this document, or changes to the project's fundamental scope - are announced publicly with at least 2 weeks for community input before any change is made. These announcements will be made in the MetaHuman category of the Unreal Engine forums.

Maintainer lifecycle

Removal

A Maintainer may be removed for a sustained Code of Conduct violation. Removal requires Core Maintainer consensus and is a last resort - the enforcement ladder in the Code of Conduct applies first.

Epic Games' role

Epic maintains OpenRigLogic . OpenRigLogic is MIT-licensed and Epic does not intend to change that.

Security

See SECURITY.md. Security issues are handled through Epic's existing security program - do not open public GitHub Issues for vulnerabilities.

Code of conduct

All community spaces are governed by the Code of Conduct. Report violations to metahuman-devkit-moderation@epicgames.com.

If an alleged violation involves a Core Maintainer, the remaining Core Maintainers handle the investigation without that person's participation.

Amending this document

Changes to this document are announced publicly with at least 2 weeks for community input before any change takes effect. These announcements will be made in the MetaHuman category of the Unreal Engine forums.