chore: migrate community governance files to external repository 📋 (#1386)

* chore: migrate community governance files to external repository 📋

- move community meeting materials to areal-project/community
- relocate code of conduct to external repository

Signed-off-by: mingcheng <mingcheng@apache.org>

* docs: reformat community governance files with line breaks 📋

Signed-off-by: mingcheng <mingcheng@apache.org>

---------

Signed-off-by: mingcheng <mingcheng@apache.org>

Author: mingcheng

.github/PULL_REQUEST_TEMPLATE.md

@@ -24,7 +24,8 @@ Fixes #(issue)
 
 <!-- Mark with 'x' what you've done -->
 
-- [ ] I have read the [Contributing Guide](../CONTRIBUTING.md)
+- [ ] I have read the
+  [Contributing Guide](https://github.com/areal-project/community/blob/main/CONTRIBUTING.md)
 - [ ] Pre-commit hooks pass (`pre-commit run --all-files`)
 - [ ] Relevant tests pass; new tests added for new functionality
 - [ ] Documentation updated (if applicable; built with `./docs/build_all.sh`)
@@ -43,5 +44,6 @@ Fixes #(issue)
 
 ______________________________________________________________________
 
-**Need help?** Check the [Contributing Guide](../CONTRIBUTING.md) or ask in
-[GitHub Discussions](https://github.com/areal-project/AReaL/discussions)!
+**Need help?** Check the
+[Contributing Guide](https://github.com/areal-project/community/blob/main/CONTRIBUTING.md)
+or ask in [GitHub Discussions](https://github.com/areal-project/AReaL/discussions)!

CODE_OF_CONDUCT.md

@@ -1,155 +1,2 @@
-# Contributor Covenant 3.0 Code of Conduct
-
-## Our Pledge
-
-We pledge to make our community welcoming, safe, and equitable for all.
-
-We are committed to fostering an environment that respects and promotes the dignity,
-rights, and contributions of all individuals, regardless of characteristics including
-race, ethnicity, caste, color, age, physical characteristics, neurodiversity,
-disability, sex or gender, gender identity or expression, sexual orientation, language,
-philosophy or religion, national or social origin, socio-economic position, level of
-education, or other status. The same privileges of participation are extended to
-everyone who participates in good faith and in accordance with this Covenant.
-
-## Encouraged Behaviors
-
-While acknowledging differences in social norms, we all strive to meet our community's
-expectations for positive behavior. We also understand that our words and actions may be
-interpreted differently than we intend based on culture, background, or native language.
-
-With these considerations in mind, we agree to behave mindfully toward each other and
-act in ways that center our shared values, including:
-
-1. Respecting the **purpose of our community**, our activities, and our ways of
-   gathering.
-1. Engaging **kindly and honestly** with others.
-1. Respecting **different viewpoints** and experiences.
-1. **Taking responsibility** for our actions and contributions.
-1. Gracefully giving and accepting **constructive feedback**.
-1. Committing to **repairing harm** when it occurs.
-1. Behaving in other ways that promote and sustain the **well-being of our community**.
-
-## Restricted Behaviors
-
-We agree to restrict the following behaviors in our community. Instances, threats, and
-promotion of these behaviors are violations of this Code of Conduct.
-
-1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary
-   personal attention after any clear request to stop.
-1. **Character attacks.** Making insulting, demeaning, or pejorative comments directed
-   at a community member or group of people.
-1. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior
-   on the basis of immutable identities or traits.
-1. **Sexualization.** Behaving in a way that would generally be considered
-   inappropriately intimate in the context or purpose of the community.
-1. **Violating confidentiality**. Sharing or acting on someone's personal or private
-   information without their permission.
-1. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward
-   any person or group.
-1. Behaving in other ways that **threaten the well-being** of our community.
-
-### Other Restrictions
-
-1. **Misleading identity.** Impersonating someone else for any reason, or pretending to
-   be someone else to evade enforcement actions.
-1. **Failing to credit sources.** Not properly crediting the sources of content you
-   contribute.
-1. **Promotional materials**. Sharing marketing or other commercial content in a way
-   that is outside the norms of the community.
-1. **Irresponsible communication.** Failing to responsibly present content which
-   includes, links or describes any other restricted behaviors.
-
-## Reporting an Issue
-
-Tensions can occur between community members even when they are trying their best to
-collaborate. Not every conflict represents a code of conduct violation, and this Code of
-Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and
-minimize harm.
-
-When an incident does occur, it is important to report it promptly. To report a possible
-violation, **send an email to the project maintainer fuwth17@gmail.com**.
-
-Community Moderators take reports of violations seriously and will make every effort to
-respond in a timely manner. They will investigate all reports of code of conduct
-violations, reviewing messages, logs, and recordings, or interviewing witnesses and
-other participants. Community Moderators will keep investigation and enforcement actions
-as transparent as possible while prioritizing safety and confidentiality. In order to
-honor these values, enforcement actions are carried out in private with the involved
-parties, but communicating to the whole community may be part of a mutually agreed upon
-resolution.
-
-## Addressing and Repairing Harm
-
-If an investigation by the Community Moderators finds that this Code of Conduct has been
-violated, the following enforcement ladder may be used to determine how best to repair
-harm, based on the incident's impact on the individuals involved and the community as a
-whole. Depending on the severity of a violation, lower rungs on the ladder may be
-skipped.
-
-1. Warning
-   1. Event: A violation involving a single incident or series of incidents.
-   1. Consequence: A private, written warning from the Community Moderators.
-   1. Repair: Examples of repair include a private written apology, acknowledgement of
-      responsibility, and seeking clarification on expectations.
-1. Temporarily Limited Activities
-   1. Event: A repeated incidence of a violation that previously resulted in a warning,
-      or the first incidence of a more serious violation.
-   1. Consequence: A private, written warning with a time-limited cooldown period
-      designed to underscore the seriousness of the situation and give the community
-      members involved time to process the incident. The cooldown period may be limited
-      to particular communication channels or interactions with particular community
-      members.
-   1. Repair: Examples of repair may include making an apology, using the cooldown
-      period to reflect on actions and impact, and being thoughtful about re-entering
-      community spaces after the period is over.
-1. Temporary Suspension
-   1. Event: A pattern of repeated violation which the Community Moderators have tried
-      to address with warnings, or a single serious violation.
-   1. Consequence: A private written warning with conditions for return from suspension.
-      In general, temporary suspensions give the person being suspended time to reflect
-      upon their behavior and possible corrective actions.
-   1. Repair: Examples of repair include respecting the spirit of the suspension,
-      meeting the specified conditions for return, and being thoughtful about how to
-      reintegrate with the community when the suspension is lifted.
-1. Permanent Ban
-   1. Event: A pattern of repeated code of conduct violations that other steps on the
-      ladder have failed to resolve, or a violation so serious that the Community
-      Moderators determine there is no way to keep the community safe with this person
-      as a member.
-   1. Consequence: Access to all community spaces, tools, and communication channels is
-      removed. In general, permanent bans should be rarely used, should have strong
-      reasoning behind them, and should only be resorted to if working through other
-      remedies has failed to change the behavior.
-   1. Repair: There is no possible repair in cases of this severity.
-
-This enforcement ladder is intended as a guideline. It does not limit the ability of
-Community Managers to use their discretion and judgment, in keeping with the best
-interests of our community.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when an
-individual is officially representing the community in public or other spaces. Examples
-of representing our community include using an official email address, posting via an
-official social media account, or acting as an appointed representative at an online or
-offline event.
-
-## Attribution
-
-This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently
-available at
-[https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
-
-Contributor Covenant is stewarded by the Organization for Ethical Source and licensed
-under CC BY-SA 4.0. To view a copy of this license, visit
-[https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
-
-For answers to common questions about Contributor Covenant, see the FAQ at
-[https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
-Translations are provided at
-[https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
-Additional enforcement and community guideline resources can be found at
-[https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources).
-The enforcement ladder was inspired by the work of
-[Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+The latest version of this code of conduct can be found at
+https://github.com/areal-project/community/blob/main/CODE_OF_CONDUCT.md

CONTRIBUTING.md

@@ -1,214 +1,2 @@
-# Contributing to AReaL
-
-Thank you for your interest in contributing to AReaL! We welcome contributions from
-everyone, whether you're fixing bugs, improving documentations, adding new features, or
-helping with code reviews. This guide will help you get started.
-
-Please review our [Code of Conduct](CODE_OF_CONDUCT.md) before participating and our
-[Governance](GOVERNANCE.md) document to understand how the project is managed.
-
-## Table of Contents
-
-- [Quick Start](#quick-start)
-- [Tips for Using AI-Assisted Coding](#tips-for-using-ai-assisted-coding)
-- [CI/CD](#cicd)
-
-## Quick Start
-
-1. **Fork and Clone:**
-
-   ```bash
-   # Fork the repository on GitHub, then:
-   git clone https://github.com/YOUR-USERNAME/AReaL
-   cd AReaL
-   ```
-
-1. **Install Development Dependencies:**
-
-   Check our
-   [installation guide](https://areal-project.github.io/AReaL/en/tutorial/installation.html)
-   for detailed setup instructions.
-
-1. **Set Up Pre-commit Hooks:**
-
-   ```bash
-   # Install hooks (includes formatting, linting, and commit message checks)
-   pre-commit install --install-hooks
-   # Subsequent commits will automatically check your files and commit messages:
-   git commit -a -m 'feat(engine): my change'
-   ```
-
-1. **Find an Issue:**
-
-   - Browse
-     [good first issues](https://github.com/areal-project/AReaL/labels/good%20first%20issue)
-   - Check [help wanted](https://github.com/areal-project/AReaL/labels/help%20wanted)
-     issues
-   - Or create a new issue using our
-     [issue templates](https://github.com/areal-project/AReaL/issues/new/choose)
-
-1. **Make Your Changes:**
-
-   - Create a branch: `git checkout -b your-feature-name`
-   - Make your changes with proper formatting
-   - Test your changes following the next step
-
-1. **Test Your Changes:**
-
-   ```bash
-   # --sw: step-wise debugging
-   # --lf: run the last failed test first
-   pytest -sv --sw --lf tests/
-   ```
-
-   Our test suite includes:
-
-   - Running all examples to ensure they can execute one RL step
-   - Checking individual engine functionalities, including rollout, forward-backward,
-     and weight updates
-   - Verifying numerical consistency of our packed data format with HuggingFace padded
-     input, with and without Ulysses
-   - Testing staleness management functionality
-   - Ensuring GSM8K SFT loss decreases and RL rewards increase
-   - Running other unit tests for individual components
-
-   Some unit tests require multiple GPUs. The entry point scripts are located under
-   `tests/torchrun`. In the corresponding test files (e.g.,
-   `test_data_redistribution.py`), we use subprocesses to launch distributed experiments
-   with `torchrun` and wait for results.
-
-   If you have modified documentation, prepare doc in English and Chinese (use
-   [/translate-doc-zh](../en/reference/ai_assisted_dev.md#commands) if needed), then
-   build the docs and preview locally:
-
-   ```bash
-   ./docs/build_all.sh
-   ```
-
-1. **Submit a Pull Request**
-
-We suggest applying our provided agent harness command `/create-pr` whenever possible.
-Use that in `claude`, `opencode`, or any other coding agent CLI.
-
-**IMPORTANT**: For new features and code refactoring, please submit a corresponding
-issue or open a draft PR to discuss with the core developers before making any code
-changes. Directly opening a PR that conflicts with our future [roadmap](ROADMAP.md) may
-waste your effort.
-
-## Tips for Using AI-Assisted Coding
-
-See the full
-[AI-Assisted Development Guide](https://areal-project.github.io/AReaL/en/reference/ai_assisted_dev.html)
-for detailed documentation.
-
-## CI/CD
-
-### Pre-commit Checks
-
-Pre-commit checks run automatically on every PR. CI executes
-`pre-commit run --all-files` to verify formatting (Ruff, clang-format, mdformat) and
-linting. Commit messages are also validated against
-[Conventional Commits](https://www.conventionalcommits.org/) format (e.g., `feat: ...`,
-`fix: ...`, `docs: ...`, `gov: ...`).
-
-As long as you have `pre-commit install --install-hooks` set up locally, your code will
-be checked before each commit and your commit messages will be validated automatically.
-
-### Tests
-
-Tests for PRs are triggered when the PR is manually tagged with `safe-to-test`. The test
-suite runs on ephemeral GCP compute engines with 2 A100 GPUs (40GB memory).
-
-> **IMPORTANT:** To re-run tests, **DO NOT** click the "Re-run workflow" button on
-> GitHub. Instead, remove the `safe-to-test` tag and then add it back.
-
-**Writing Tests for New Features:**
-
-If you have implemented a new feature, we highly recommend writing tests and adding them
-to our pytest workflow. Place your test files under `tests/test_*.py` and mark them with
-our pre-defined pytest markers:
-
-- `slow`: Tests that take more than 30 seconds to run. These will not run in the CI/CD
-  workflow unless also marked with `ci`.
-- `ci`: Tests that should run in the CI/CD workflow (only needed for `slow` tests).
-- `gpu`: Tests that use a single GPU.
-- `multi_gpu`: Tests that use more than one GPU.
-
-Our CI/CD runs tests selected by `pytest -m "not slow or ci"`. Since our CI machines
-only have two GPUs, please skip tests that require more than 2 GPUs to prevent CI
-failures. For example:
-
-```python
-import pytest
-from areal.infra.platforms import current_platform
-
-# ordinary tests are supposed to run fast, and will run in CI
-def test_fast_operation():
-    ...
-
-# slow operations that will NOT run in CI
-@pytest.mark.slow
-def test_slow_operation():
-    ...
-
-# slow operations BUT must be tested in CI
-@pytest.mark.slow
-@pytest.mark.ci
-def test_slow_operation():
-    ...
-
-# skip tests for more than 2 GPUs
-@pytest.mark.skipif(current_platform.device_count() < 4, reason="This test requires 4 GPUs")
-def test_some_multi_gpu_functionality():
-    ...
-```
-
-### Image Building
-
-The image building workflow can be triggered manually from any branch by users with
-write permissions to the repository.
-
-**Triggering the Workflow:**
-
-You can trigger the workflow from any branch using either method:
-
-1. **Via GitHub UI:**
-
-   - Go to **Actions** → **"Build and Test Docker Image"**
-   - Click **"Run workflow"** dropdown
-   - Select the branch you want to build from
-   - Click **"Run workflow"**
-
-1. **Via GitHub CLI:**
-
-   ```bash
-   # Build from main
-   gh workflow run build-docker-image.yml --ref main
-
-   # Build from a feature branch
-   gh workflow run build-docker-image.yml --ref feature/my-changes
-
-   # Build from current branch
-   gh workflow run build-docker-image.yml --ref $(git branch --show-current)
-   ```
-
-**Pipeline Stages:**
-
-The workflow executes the following stages sequentially:
-
-1. **Build**: Builds the Docker image and pushes it with `:test` tag
-1. **Test**: Automatically runs the full test suite using the `:test` image
-1. **Promote**: If tests pass, promotes the image by retagging `:test` → `:dev`
-1. **Cleanup**: Always deletes the `:test` image from the registry (success or failure)
-
-Building the image from scratch takes approximately 1-2 hours, plus additional time for
-running the test suite.
-
-**Normal PR Testing:**
-
-The PR-based test workflow (triggered by the `safe-to-test` label) remains unchanged and
-uses the `:dev` image. This allows testing PRs against the last known-good image.
-
-______________________________________________________________________
-
-Thank you for contributing to AReaL! 🙏
+The latest version of this file can be found at
+https://github.com/areal-project/community/blob/main/CONTRIBUTING.md