### Example GitHub Team Sync Configuration

Source: https://github.com/backstage/community/blob/main/github-teams/README.md

A sample YAML configuration file defining GitHub teams, their descriptions, parent teams, and members. Supports templating for team names.

```yaml
teams:
  - name: community-plugins-$plugin
    description: Maintainers of $plugin
    parent: community-plugins-owners
    members:
      - GitHubUserA
      - GitHubUserB
```

--------------------------------

### Run GitHub Team Sync Script

Source: https://github.com/backstage/community/blob/main/github-teams/README.md

Execute the team sync script with a specified configuration file.

```bash
node team-sync --config path/to/teams.yaml
```

--------------------------------

### Run github-sync-helper for Issue Triage

Source: https://github.com/backstage/community/blob/main/project-areas/community-plugins/README.md

Execute the github-sync-helper script to fetch and open issues updated in the last 7 days for the backstage/community-plugins repository. This is part of the issue triage process.

```bash
npx github-sync-helper@latest issues --repo backstage/community-plugins --days 7
```

--------------------------------

### Run GitHub Team Sync Script with Dry-Run

Source: https://github.com/backstage/community/blob/main/github-teams/README.md

Execute the team sync script in dry-run mode to preview changes without applying them. Requires the configuration file path.

```bash
node team-sync.js --config path/to/teams.yaml --dry-run
```

--------------------------------

### Sync GitHub Teams with YAML Configuration

Source: https://context7.com/backstage/community/llms.txt

A Node.js CLI script to synchronize GitHub teams within the Backstage organization based on a YAML configuration file. Requires Node.js v18+ and a GITHUB_TOKEN with org:write scope for actual changes.

```bash
# Install dependencies
cd github-teams
yarn install

# Run a dry-run to preview changes without applying them
node team-sync.js --config TEAMS/community-plugins-teams.yaml --dry-run
# Output:
# 📄 Using config: /path/to/TEAMS/community-plugins-teams.yaml
# 🔧 Syncing team "community-plugins-rbac":
#    ➕ (dry-run) Would add "newuser"
#    ✅ "AndrienkoAleksandr" already a member
#    ➖ (dry-run) Would remove "olduser"
# ✅ Team sync complete (dry-run mode).

# Apply actual changes (requires GITHUB_TOKEN with org:write scope)
GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxx node team-sync.js --config TEAMS/community-plugins-teams.yaml
# Output:
# 📄 Using config: /path/to/TEAMS/community-plugins-teams.yaml
# 🔧 Syncing team "community-plugins-rbac":
#    ✅ "AndrienkoAleksandr" already a member
#    ➕ Added "newuser"
#    ➖ Removed "olduser"
# ✅ Team sync complete.
```

```yaml
# TEAMS/community-plugins-teams.yaml — example config structure
teams:
  - name: community-plugins-rbac
    parent: community-plugin-owners
    description: Maintainers of community RBAC plugin
    members:
      - "AndrienkoAleksandr"
      - "christoph-jerolimov"
      - "divyanshiGupta"
      - "PatAKnight"
      - "dzemanov"
```

--------------------------------

### Open GitHub Issues Updated in Last 7 Days

Source: https://github.com/backstage/community/blob/main/project-areas/Maintainer-Guidance.md

Use this command to open all issues in a specific area that have been updated in the last 7 days. This is helpful for regularly scheduled sync meetings to review recent activity.

```bash
npx github-sync-helper issues --days 7 --labels area:catalog
```

--------------------------------

### Subscribe to Backstage Community Sessions Calendar

Source: https://context7.com/backstage/community/llms.txt

Provides links to subscribe to the Backstage Community Sessions calendar via Google Calendar or iCal, and links to view agendas and recordings.

```text
# Subscribe via Google Calendar email address:
c_qup9gbhn9sqpuao6trttd8mk5s@group.calendar.google.com

# Subscribe via iCal URL (for non-Google calendar apps):
https://calendar.google.com/calendar/ical/c_qup9gbhn9sqpuao6trttd8mk5s%40group.calendar.google.com/public/basic.ics

# View all past and upcoming session agendas (GitHub Issues):
https://github.com/backstage/community/issues?q=is%3Aissue+%22Agenda+for+Backstage+Community+Session%22+ 

# View recordings on YouTube:
https://www.youtube.com/playlist?list=PL8iP9yIjU0Q1bUK28-KrTUMl8n08CEPpf

# Propose a topic for the next session by commenting on the open issue:
https://github.com/backstage/community/issues?q=is%3Aissue+is%3Aopen+%22Agenda+for+Backstage+Community+Session%22+
```

--------------------------------

### Backstage Contributor Ladder Summary (YAML)

Source: https://context7.com/backstage/community/llms.txt

Defines the contributor ladder for the Backstage project, outlining roles, requirements, and how to join or gain privileges. This structure is used for managing project membership and contributions.

```yaml
# Contributor Ladder Summary
roles:
  - name: Contributor
    requirements:
      - Follow CNCF Code of Conduct
      - Follow contributing guide
    how_to_start: Submit PRs, comment on issues, attend meetups

  - name: Organization Member
    requirements:
      - 10+ accepted PRs or equivalent contributions
      - Contributing for at least 3 months (OR team member of existing maintainer team)
    how_to_join:
      url: https://github.com/backstage/community/issues/new?template=org_member.yaml&title=Org+Member%3A+%3Cyour-github-login%3E

  - name: Reviewer
    requirements:
      - Is an Organization Member
      - At least 2 helpful PR reviews submitted
      - Maintains 5+ reviews/year
    how_to_join:
      url: https://github.com/backstage/community/issues/new?template=reviewer.yaml&title=Reviewer%3A+%3Cyour-github-login%3E
    privileges:
      - Member of @backstage/reviewers team
      - Higher priority on own PRs

  - name: Plugin Maintainer
    requirements:
      - Contribute and own a plugin in backstage/community-plugins
      - Listed as CODEOWNER; approved by Community Plugin Maintainers
    privileges:
      - Write access to community-plugins repository
      - Approve and merge PRs for owned plugin
      - Automatic Organization Member status

  - name: Project Area Maintainer
    requirements:
      - Organization Member
      - 5+ meaningful contributions to the project area
      - 16+ hours/month commitment
    privileges:
      - Approve and merge PRs in their area
      - Drive area roadmap

  - name: Core Maintainer
    requirements:
      - 6+ months as Project Area Maintainer
      - Broad knowledge across multiple areas
      - Majority approval from existing Core Maintainers
      - 7+ days/month commitment
    privileges:
      - Merge PRs in any area
      - Represent project publicly
      - Communicate with CNCF on behalf of project
      - Vote in maintainer decision-making

```

--------------------------------

### Open GitHub Issues Updated Recently

Source: https://context7.com/backstage/community/llms.txt

A tool to open GitHub issues updated within a specified time window directly in the browser, useful for triage meetings. Issues are identified by their 'area:<name>' label.

```bash
# Open all issues in the 'catalog' area updated in the last 7 days
npx github-sync-helper issues --days 7 --labels area:catalog

# Open all issues in the community-plugins repo updated in the last 7 days
npx github-sync-helper@latest issues --repo backstage/community-plugins --days 7

# Open all issues across multiple areas updated in the last 14 days
npx github-sync-helper issues --days 14 --labels area:scaffolder

# Each matching issue is automatically opened in the default browser for review.
# Typical responses during triage:
#   - Assign to a maintainer for async response
#   - Add label `will-fix` to prevent stale-bot closure
#   - Write a short response live during the meeting
```

--------------------------------

### Backstage SIGs Contact Information (Text)

Source: https://context7.com/backstage/community/llms.txt

Lists active Special Interest Groups (SIGs) within the Backstage community, including their focus areas, Discord channels, meeting schedules, and links to notes or GitHub teams. This is for informational purposes and joining SIGs requires no formal membership.

```text
Active SIGs and their contact points:

SIG Adoption
  Focus:    Improving the Backstage adoption journey (docs, tutorials, onboarding)
  Discord:  #adoption  (https://discord.com/channels/687207715902193673/1045031039061479536)
  Meetings: Currently paused — reach out on Discord for ad-hoc meetings
  Notes:    https://docs.google.com/document/d/1zeYSzXYgh897bxPQmwy2btOwCFlEjlUDLf00riySLRc/edit

SIG Community Plugins
  Focus:    Governance and health of the community-plugins repository
  Discord:  #community-plugins

SIG Docs
  Focus:    Documentation improvements for Backstage
  Discord:  #documentation  (https://discord.com/channels/687207715902193673/687994765559463940)
  Meetings: Biweekly Fridays at 16:00 Europe/Stockholm
  Video:    https://meet.google.com/iwm-oeoj-nvi
  Notes:    https://docs.google.com/document/d/1yVdnxtrpA6tPTGl9gbeHME7bEkQQTnfrjG3H7loEKrI/edit
  GitHub:   @backstage/documentation-maintainers

SIG Framework
  Focus:    Core framework direction and architecture

SIG Scaffolder
  Focus:    Scaffolder plugin and software templates

```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.