Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions .github/ISSUE_TEMPLATE/departure.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
name: Departure Notice
about: Formal notice for a community member stepping down from a role
title: "Departure Notice: [Your Name]"
labels: ["departure", "community"]
---

This template helps community members formally announce that they are stepping down from
a role in the AReaL project. See
[Voluntary Departure](../../COMMUNITY_MEMBERSHIP.md#voluntary-departure) for the full
process. Thank you for your contributions!

## Basic Information

- **Name**:
- **GitHub ID**: @
- **Current role(s)**: <!-- Maintainer / Approver / Member -->
- **Date of notice**: <!-- YYYY-MM-DD -->
- **Effective departure date**: <!-- YYYY-MM-DD, at least 7 days after the notice -->

## Reason for Departure (optional)

<!-- A brief explanation, if you are comfortable sharing. -->

## Handover

Please check all that apply and provide details where necessary.

- [ ] Code review assignments / area ownership
- [ ] Ongoing pull request ownership
- [ ] Release management responsibilities
- [ ] Repository access / permissions to be revoked
- [ ] Other: <!-- Please specify -->

## Future Involvement (optional)

- [ ] I would like to remain a casual contributor when time permits.
- [ ] I prefer a clean break with no future involvement.
- [ ] I am open to returning in the future if circumstances change.

## Additional Notes

<!-- Anything else you would like to share with the community. -->

______________________________________________________________________

### For Maintainers

- [ ] Remove repository access and team memberships.
- [ ] Reassign ongoing responsibilities.
- [ ] Move the member to the emeritus section of the relevant `roles/` file.
- [ ] Acknowledge the departure with a thank-you message.
65 changes: 65 additions & 0 deletions .github/ISSUE_TEMPLATE/nominate.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
---
name: Role Nomination
about: Nominate a candidate for a community role (Member, Approver, or Maintainer)
title: "Nomination: [Candidate's Name] for [Role]"
labels: ["nomination", "community"]
---

Use this template to nominate a candidate for a community role. See the
[Community Membership](../../COMMUNITY_MEMBERSHIP.md) and
[Contributor Ladder](../../COMMUNITY_LADDER.md) documents for the full process.

> **Self-nomination**: Member candidates may nominate themselves. Approver and
> Maintainer candidates **cannot** self-nominate — the nominator and the nominee must be
> different people. Approver nominations must come from an existing Approver or
> Maintainer, and Maintainer nominations must come from an existing Maintainer. If you
> are self-nominating for Member, fill in the same GitHub ID in both the Nominee and
> Nominator sections and note that this is a self-nomination.

## Nominee Information

- **GitHub ID**: <!-- Nominee's GitHub username -->
- **Name**: <!-- Nominee's full name -->
- **Company / Organization**: <!-- Nominee's current organization -->
- **Role applied for**: <!-- Member / Approver / Maintainer -->

## Nominator Information

- **GitHub ID**: <!-- Your GitHub username -->
- **Current role**: <!-- Contributor / Member / Approver / Maintainer -->
- **Self-nomination?**: <!-- Yes (Member only) / No -->

## Requirements for the Nominee

- [ ] Nominee's GitHub account has 2FA enabled.
- [ ] Nominee has a history of contributions (code, reviews, issue discussions).
- [ ] Nominee meets the qualifications for the role in the
[Contributor Ladder](../../COMMUNITY_LADDER.md).
- [ ] Nominee has read and agrees to the [Code of Conduct](../../CODE_OF_CONDUCT.md).

## Nominator's Checklist

- [ ] For Approver/Maintainer nominations, I am not the nominee (no self-nomination),
and I hold a role eligible to nominate for this position.
- [ ] I have discussed this nomination with the nominee, and they agree to be nominated
(not required when self-nominating for Member).
- [ ] I confirm the nominee meets the requirements listed above.

## Contributions to AReaL

<!-- List the nominee's contributions to AReaL (PRs, issues, reviews, docs, etc.) with
links. -->

## Nomination Justification

### Why this candidate

<!-- Explain why this candidate is being nominated and what makes them a good fit. -->

### Future plans

<!-- Outline the nominee's plans and goals for the project if accepted. -->

## Endorsements (optional)

<!-- List any Maintainers or Approvers who endorse this nomination. -->
3 changes: 1 addition & 2 deletions .github/workflows/pulse.yml
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,7 @@ jobs:
pip install pre-commit
# Run the Markdown formatting hooks on the generated report only.
# pre-commit exits non-zero when it reformats a file, so don't fail the job.
pre-commit run mdformat end-of-file-fixer trailing-whitespace \
--files reports/${{ env.DATE }}.md || true
pre-commit run --files reports/${{ env.DATE }}.md || true

- name: Create Pull Request
uses: peter-evans/create-pull-request@v8.1.1
Expand Down
160 changes: 6 additions & 154 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,155 +1,7 @@
# Contributor Covenant 3.0 Code of Conduct
# 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).
We are the
[PyTorch Foundation Ecosystem project](https://landscape.pytorch.org/?item=training--distributed--areal),
and we are committed to providing a welcoming and safe environment for all participants.
We expect all participants to adhere to the
[PyTorch Foundation Code of Conduct](https://github.com/pytorch-fdn/Foundation/blob/main/PyTorch%20Foundation%20Code%20of%20Conduct.md)
Loading
Loading