This is an automated email from the ASF dual-hosted git repository.
kaxil pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 3c76a47f65c Remove accidentally adopted Magpie contributor-growth
plugin (#73927)
3c76a47f65c is described below
commit 3c76a47f65c261204a4640f55f4f87076066b0b1
Author: Jarek Potiuk <[email protected]>
AuthorDate: Wed Sep 30 00:14:46 2026 +0200
Remove accidentally adopted Magpie contributor-growth plugin (#73927)
The contributor-growth family and its configuration were accidentally
committed and merged into the project's Magpie floor as part of an
experiment, and were never meant to be recommended to every contributor.
The reconciliation stamp is dropped from the committed lock as well;
contributors re-establish it locally with the setup skill's reconcile
sub-action when a skill's pre-flight asks for it.
Generated-by: Claude Opus 5
---
.../committer-onboarding-config.md | 272 ---------------------
.apache-magpie-overrides/committer-readiness.md | 169 -------------
.../contributor-nomination-config.md | 186 --------------
.../contributor-sentiment-config.md | 66 -----
.../good-first-issue-config.md | 93 -------
.../onboarding-concierge-config.md | 70 ------
.apache-magpie.lock | 43 ----
7 files changed, 899 deletions(-)
diff --git a/.apache-magpie-overrides/committer-onboarding-config.md
b/.apache-magpie-overrides/committer-onboarding-config.md
deleted file mode 100644
index 4eb7fd33d0d..00000000000
--- a/.apache-magpie-overrides/committer-onboarding-config.md
+++ /dev/null
@@ -1,272 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Apache Airflow — committer-onboarding
configuration](#apache-airflow--committer-onboarding-configuration)
- - [Intake model](#intake-model)
- - [Intake-model-specific keys](#intake-model-specific-keys)
- - [Governance model](#governance-model)
- - [Governance-model-specific keys](#governance-model-specific-keys)
- - [Cross-references](#cross-references)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Apache Airflow — committer-onboarding configuration
-
-**This file enumerates the capability-flag vocabulary for the
-`committer-onboarding` skill.** It is the contributor-growth
-counterpart to `release-management-config.md`'s backend-flag model:
-an adopter declares the intake and governance model that suits their
-community, and the skill emits onboarding steps shaped for that model,
-without any skill-body edit.
-
-**Currently the `committer-onboarding` skill defaults to the ASF-PMC
-/ ICLA model** (the ASF default). This file establishes the flag
-vocabulary so that a non-ASF adopter can declare their model here;
-the skill will read these flags in a follow-on update. New adopters
-should copy this file into their own
-`<project-config>/committer-onboarding-config.md` and replace every
-`TODO`.
-
-Related scaffolds in the same adopter directory:
-
-- `committer-readiness.md` — activity thresholds the
- `contributor-to-committer` readiness tracker compares against
- (added by the `contributor-to-committer` skill).
-- [`contributor-nomination-config.md`](contributor-nomination-config.md)
- — nomination-brief thresholds and assessment window.
-- [`pmc-roster.md`](pmc-roster.md) — PMC-member roster used by
- `release-vote-tally` to classify binding vs non-binding votes.
-
----
-
-## Intake model
-
-Declares how new committers are formally onboarded to the project's
-IP policy after a vote passes.
-
-```yaml
-committer_intake:
- # Model under which new committers are formally onboarded to the
- # project's IP policy.
- # ASF default: icla — every new committer must file a signed ICLA
- # with the Apache Software Foundation before commit bits are
- # granted. The skill checks Whimsy and blocks the account-request
- # step if no ICLA is on file.
- # Override when:
- # dco — Developer Certificate of Origin (Linux Foundation model).
- # A per-commit `Signed-off-by:` line replaces the one-time CLA;
- # the skill links the DCO guide and verifies that the candidate's
- # recent merged PRs carry sign-off.
- # no-cla — No formal contributor agreement required (open/trust-
- # based model). The skill skips IP-check steps entirely.
- # Allowed values: icla, dco, no-cla
- # Consumed by: committer-onboarding (intake-check step).
- model: icla # icla | dco | no-cla (ASF project; COMMITTERS.rst requires a
CLA on file)
-```
-
-### Intake-model-specific keys
-
-Fill in only the block that matches your `model` above; leave the
-others absent or blank.
-
-#### `icla` model
-
-```yaml
-committer_intake_icla:
- # URL the skill links when asking the nominator to check the
- # candidate's ICLA status.
- # ASF default: Whimsy's committer lookup.
- # Non-ASF adopters using ICLA: point at your foundation's CLA
- # query endpoint.
- # Consumed by: committer-onboarding.
- lookup_url: https://whimsy.apache.org/roster/committer/
-
- # Whether ICLA filing is a hard prerequisite that the skill refuses
- # to bypass. When true, the skill blocks until the nominator
- # confirms the ICLA is on file; when false, the skill flags the
- # gap but allows the nominator to proceed with a warning.
- # ASF default: true.
- # Consumed by: committer-onboarding.
- mandatory: true
-```
-
-#### `dco` model
-
-```yaml
-committer_intake_dco:
- # Reference URL the skill links in onboarding communications
- # explaining what DCO sign-off means for contributors.
- # Linux Foundation / CNCF projects typically link
- # https://developercertificate.org/ plus their own CONTRIBUTING.md.
- # Consumed by: committer-onboarding.
- reference_url: null # n/a — Airflow uses the icla model, not DCO
-
- # Minimum number of the candidate's recently merged PRs that must
- # carry a valid `Signed-off-by:` line before the skill considers
- # the DCO check passed.
- # Set to 0 to skip the check (honour-system model).
- # Consumed by: committer-onboarding.
- min_signed_off_prs: 1
-```
-
-#### `no-cla` model
-
-```yaml
-committer_intake_nocla:
- # Free-text explanation shown in the onboarding checklist in place
- # of an IP-agreement check. Leave null for a default message.
- # Consumed by: committer-onboarding.
- explanation: null
- # e.g. "This project uses an Apache-2.0 inbound/outbound model; no
- # CLA or DCO sign-off is required — contributors retain copyright."
-```
-
----
-
-## Governance model
-
-Declares how committer and PMC (or equivalent) status is formally
-tracked, voted on, and applied after a vote passes.
-
-```yaml
-committer_governance:
- # Model under which committer and committee status is granted and
- # tracked.
- # ASF default: asf-pmc — the PMC votes on the dev@ list, submits a
- # secretary account-creation request via Whimsy, and the new
- # committer appears on the Apache Whimsy committee/committer roster.
- # Override when:
- # github-codeowners — CODEOWNERS file + GitHub maintainer-team
- # membership drives merge permissions; no formal committee vote
- # and no external account-creation request.
- # maintainer-roster — an adopter-managed roster file voted on by
- # existing maintainers, outside any foundation's governance
- # machinery.
- # Allowed values: asf-pmc, github-codeowners, maintainer-roster
- # Consumed by: committer-onboarding (roster-management steps).
- model: asf-pmc # asf-pmc | github-codeowners | maintainer-roster
-```
-
-### Governance-model-specific keys
-
-Fill in only the block that matches your `model` above.
-
-#### `asf-pmc` model
-
-```yaml
-committer_governance_asf_pmc:
- # Whether the project is an incubating podling or a graduated
- # top-level project. This switches between Whimsy's PPMC
- # self-service UI (podling) and `committee-info.txt` edits (TLP).
- # Allowed values: podling, tlp
- # Consumed by: committer-onboarding (roster-management path
- # selection).
- stage: tlp # podling | tlp (top-level project since January 2019,
airflow-core/docs/project.rst)
-
- # Whimsy URL the skill links the nominator to for roster management.
- # TLP default: committee detail page.
- # Podling default: PPMC roster page.
- # Consumed by: committer-onboarding.
- whimsy_roster_url: https://whimsy.apache.org/roster/committee/airflow
- # TLP example: https://whimsy.apache.org/roster/committee/<project>
- # Podling example: https://whimsy.apache.org/roster/ppmc/<project>
-
- # URL of the ASF's new-committer / new-PMC-member secretary request
- # form. The skill prints this and asks the nominator to fill it in.
- # ASF default: the standard secretary request page.
- # Consumed by: committer-onboarding.
- secretary_request_url: https://whimsy.apache.org/officers/acreq
-
- # Dev-list address the skill uses when drafting the welcome
- # announcement. Matches `dev_list` in project.md — kept here for
- # self-contained configuration.
- # Consumed by: committer-onboarding.
- dev_list: [email protected]
-```
-
-#### `github-codeowners` model
-
-```yaml
-committer_governance_github_codeowners:
- # GitHub team slug (in `org/team` form) that maps to the
- # committer/maintainer team. The skill invites the new committer
- # to this team after the vote passes.
- # Consumed by: committer-onboarding.
- maintainers_team: apache/airflow-committers
-
- # Path to the CODEOWNERS file in the upstream repo, relative to
- # the repo root. The skill optionally opens a PR adding the new
- # committer's handle to the file.
- # Leave null to skip the CODEOWNERS update.
- # Consumed by: committer-onboarding.
- codeowners_file: CODEOWNERS # or null
-
- # Whether a GitHub-discussion or a GitHub-issue thread is the
- # canonical "vote thread" for this model.
- # Allowed values: github-discussion, github-issue, off-band
- # `off-band` = the vote happened in Slack / email / another channel
- # and the skill just records the outcome.
- # Consumed by: committer-onboarding (vote-validation step).
- vote_channel: off-band # votes are held on the private PMC mailing list
-```
-
-#### `maintainer-roster` model
-
-```yaml
-committer_governance_maintainer_roster:
- # Path to the roster file (relative to <project-config>/) that
- # the skill updates when a vote passes.
- # Consumed by: committer-onboarding.
- roster_file: null # n/a — Airflow uses the asf-pmc model (roster in Whimsy)
-
- # Minimum number of approvals required from existing listed
- # maintainers before the skill considers the vote passed.
- # Consumed by: committer-onboarding (vote-validation step).
- min_approvals: 3 # ASF rule: at least 3 binding +1 votes and no veto
-
- # Channel where votes are held — used by the skill when
- # summarising the vote result.
- # Allowed values: github-discussion, github-issue, mailing-list,
- # slack-channel, off-band
- # Consumed by: committer-onboarding.
- vote_channel: mailing-list
-```
-
----
-
-## Cross-references
-
-- `committer-readiness.md` — activity thresholds for the
- `contributor-to-committer` readiness tracker (added by the
- `contributor-to-committer` skill).
-- [`contributor-nomination-config.md`](contributor-nomination-config.md)
- — nomination-brief thresholds and assessment window.
-- [`pmc-roster.md`](pmc-roster.md) — PMC-member roster for vote tally.
--
[`committer-onboarding`](../../.agents/skills/magpie-committer-onboarding/SKILL.md)
- — the skill that reads this configuration.
diff --git a/.apache-magpie-overrides/committer-readiness.md
b/.apache-magpie-overrides/committer-readiness.md
deleted file mode 100644
index 87c40d5201d..00000000000
--- a/.apache-magpie-overrides/committer-readiness.md
+++ /dev/null
@@ -1,169 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Apache Airflow — committer-readiness
configuration](#apache-airflow--committer-readiness-configuration)
- - [Assessment window](#assessment-window)
- - [Committer thresholds](#committer-thresholds)
- - [PMC thresholds](#pmc-thresholds)
- - [Project-specific notes *(optional)*](#project-specific-notes-optional)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Apache Airflow — committer-readiness configuration
-
-Per-project thresholds for the
-[`contributor-to-committer`](../../skills/contributor-to-committer/SKILL.md)
-readiness tracker. Copy into your `<project-config>/` directory and
-replace every TODO.
-
-**Thresholds are optional.** If this file does not declare thresholds,
-the skill falls back to `contributor-nomination-config.md` thresholds,
-or asks the maintainer at run time. Only declare thresholds here if
-your PMC has agreed on explicit criteria — they vary across projects
-and there are no meaningful universal defaults.
-
-**This file is separate from `contributor-nomination-config.md`** so
-that the readiness tracker and the nomination brief can be tuned
-independently. If your project uses the same bar for both, you can
-set this file's thresholds to the same values and keep a single place
-to update them.
-
----
-
-## Assessment window
-
-| Key | Value | Notes |
-|---|---|---|
-| `assessment_window_months` | `6` | How many months of activity to assess. 6
is common; slower-moving projects may prefer 12. |
-
----
-
-## Committer thresholds
-
-Calibrate against recent successful nominations on your project, not
-against framework defaults. The numbers below are a low bar for a
-mid-size active project.
-
-| Dimension | Default (low bar) | Project value | Notes |
-|---|---|---|---|
-| `prs_merged` | `5` | `40` | Merged PRs — the clearest signal of sustained
code contribution |
-| `reviews_total` | `3` | `20` | Total review acts — shows engagement with
others' work |
-| `reviews_substantive` | `2` | `3` | Reviews with real inline feedback (≥ 3
comments or > 50 char body) |
-| `issues_filed` | `0` | `2` | Set to 0 to treat as non-required; many valid
tracks don't involve filing issues |
-| `threads_commented` | `5` | `35` | PR/issue comment threads — basic
community presence |
-| `area_breadth` | `0` | `5` | Distinct `area:*` labels across merged PRs; 0 =
no breadth requirement |
-
----
-
-## PMC thresholds
-
-PMC membership requires demonstrated community leadership beyond code.
-Raise these well above the committer bar for any project that treats
-PMC as a senior track.
-
-| Dimension | Default (low bar) | Project value | Notes |
-|---|---|---|---|
-| `prs_merged` | `10` | `40` | |
-| `reviews_total` | `8` | `100` | PMC members are expected to help evaluate
others' work |
-| `reviews_substantive` | `4` | `8` | |
-| `issues_filed` | `0` | `2` | |
-| `threads_commented` | `10` | `150` | |
-| `area_breadth` | `2` | `8` | PMC members typically span multiple project
areas |
-
----
-
-## Automated and low-signal contributions
-
-How the readiness tracker discounts visibly automated or low-signal GitHub
activity.
-The full definition — detection heuristics, aggregation, and how the brief
reports raw and adjusted counts — is
[`automated-contributions.md`](https://github.com/apache/magpie/blob/main/skills/contributor-nomination/automated-contributions.md).
-
-The discount is a signal for the humans reading the brief, never an automatic
disqualification.
-Using AI tools, and disclosing that use, is not penalised; only restatement,
content maintainers pushed back on, and work closed after that pushback are
discounted.
-
-Each key is resolved from this file first, then from
`contributor-nomination-config.md`, then from the default below.
-
-| Key | Default | Project value | Notes |
-|---|---|---|---|
-| `automated_contribution_weight` | `0.25` | | Weight (0–1) of a merged or
open PR, issue, review or comment that drew maintainer pushback as looking
generated, unreviewed, restating, fabricated, or unwanted |
-| `restatement_comment_weight` | `0` | | Weight (0–1) of a comment or review
body that only restates the description, earlier comments, or the diff |
-| `closed_after_pushback_weight` | `0` | | Weight (0–1) of a PR or issue
closed unmerged after that pushback; `0` removes it from every metric |
-| `automated_pushback_phrases` | empty | | Extra phrases your maintainers use
when pushing back, added to the generic list |
-
-Set all three weights to `1` to turn the arithmetic off; flagged items are
still listed in the brief.
-
-### Project expectations for AI-assisted contributions
-
-List the documents in which your project states what it expects from
AI-assisted and automated contributions — a generative-AI contribution policy,
PR guidelines, a review or triage guide.
-Use paths relative to the repository root, or `https://` URLs, optionally with
a `#section` anchor.
-
-```yaml
-automated_contribution_expectations:
- - contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions
- -
contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated
- - contributing-docs/25_maintainer_pr_triage.md#for-contributors
-```
-
-When the list is present, the skill reads each document, judges contributions
against it first, and cites the document and section each flagged item
conflicts with.
-When it is empty or none of the documents can be read, the skill falls back to
the framework's generic heuristics and says so in the brief.
-The skill does not go looking for policy documents this list does not name.
-
----
-
-## Project-specific notes *(optional)*
-
-Free text surfaced at the top of every readiness brief. Use for norms
-the maintainer should see — e.g. multi-repo projects, non-GitHub
-contribution tracks that are particularly valued, or cultural notes
-about how the PMC calibrates nominations.
-
-```text
-Source: COMMITTERS.rst ("Guidelines to become an Airflow Committer" and
-"Guidelines for promoting Committers to Airflow PMC"). There is no strict
-numeric protocol; the PMC weighs combined contributions across areas.
-- The numeric thresholds are a floor for surfacing candidates, never a
- decision rule: activity volume alone does not make a candidate. Breadth
- across areas, dev list participation, release testing and sustained
- activity weigh as much as the counts.
-- Committer prerequisites: consistent contribution over at least three
- months; visibility on the dev list, Slack or GitHub issues/discussions
- (including non-binding votes and testing release candidates); helping
- other contributors (reviews, constructive feedback); contributions to
- community health.
-- Non-code paths count: it is possible to become a committer (and PMC
- member) without changing code, but only with visible presence in the
- community channels. Such exceptions are rare.
-- Areas the PMC looks at: Airflow Core, Task SDK, airflowctl, API, Docker
- image, Helm chart, dev tools (Breeze / CI), providers, security team work,
- issue triage, documentation.
-- PMC: committer for at least 3 months; currently active; consistent
- voting on release candidates for at least the past 3 release cycles;
- AIP engagement; reviews and merges; community involvement.
-- Airflow spans one main repository (apache/airflow) plus apache/airflow-site
- and apache/airflow-client-* repos; check activity across them.
-```
diff --git a/.apache-magpie-overrides/contributor-nomination-config.md
b/.apache-magpie-overrides/contributor-nomination-config.md
deleted file mode 100644
index fd26b638985..00000000000
--- a/.apache-magpie-overrides/contributor-nomination-config.md
+++ /dev/null
@@ -1,186 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Apache Airflow — contributor-nomination
configuration](#apache-airflow--contributor-nomination-configuration)
- - [Assessment window](#assessment-window)
- - [Thresholds *(optional — leave blank if not
configured)*](#thresholds-optional--leave-blank-if-not-configured)
- - [Committer thresholds](#committer-thresholds)
- - [PMC thresholds](#pmc-thresholds)
- - [Required areas by target *(optional)*](#required-areas-by-target-optional)
- - [Project-specific notes *(optional)*](#project-specific-notes-optional)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Apache Airflow — contributor-nomination configuration
-
-Per-project configuration for the
-[`contributor-nomination`](../../skills/contributor-nomination/SKILL.md)
-skill. Copy into your `<project-config>/` directory and replace
-every TODO.
-
-**Thresholds are optional.** If this file does not declare
-thresholds, the skill asks the maintainer for the project's
-typical bar at run time and reports raw numbers for the PMC to
-judge. Only declare thresholds here if your PMC has agreed on
-explicit criteria — thresholds vary enormously across projects
-and there are no meaningful framework defaults.
-
----
-
-## Assessment window
-
-| Key | Value | Notes |
-|---|---|---|
-| `nomination_window_months` | `6` | How many months of activity to assess. 6
is a common starting point; slower-moving projects may prefer 12. |
-
----
-
-## Thresholds *(optional — leave blank if not configured)*
-
-Declare only if your PMC has agreed on explicit criteria for
-what counts as sufficient activity on this project. These
-replace the run-time question to the maintainer about the
-project bar. Calibrate against your project's own contribution
-history — recent successful nominations are the best reference.
-
-### Committer thresholds
-
-The values below are a reasonable low bar for a mid-size active
-project, not a universal standard. Calibrate in either direction:
-
-- **Raise them** if your project is large or high-velocity and
- recent successful nominations reflect significantly more activity.
-- **Lower them** if your project is small, early-stage, or
- deliberately gives committership freely as a welcoming gesture.
- That is a valid project culture — these defaults should not
- imply otherwise.
-
-| Area | Default (low bar) | Project value | Notes |
-|---|---|---|---|
-| PRs merged | 5 | `40` | Reasonable floor for a mid-size project; set lower
if your project is small or welcomes contributors freely |
-| Reviews given | 3 | `20` | Shows engagement with others' work |
-| Substantive reviews | 2 | `3` | Reviews with real inline feedback |
-| Issues filed | 0 | `2` | Not required — many valid tracks don't involve
filing issues |
-| Comments | 5 | `35` | Basic community presence |
-| Mailing list presence | none | Visible on dev list, Slack or GitHub
issues/discussions, incl. non-binding votes and RC testing (COMMITTERS.rst) |
Qualitative — fill in if your project tracks this |
-
-### PMC thresholds
-
-| Area | Default (low bar) | Project value | Notes |
-|---|---|---|---|
-| PRs merged | 10 | `40` | |
-| Reviews given | 8 | `100` | PMC members are expected to help evaluate
others' work |
-| Substantive reviews | 4 | `8` | |
-| Community leadership signal | "present" | present — mentoring, answering
users, spreading the word, RC voting over 3+ release cycles (COMMITTERS.rst) |
Qualitative — some evidence of guiding others or shaping direction |
-
----
-
-## Automated and low-signal contributions
-
-How the nomination brief discounts visibly automated or low-signal GitHub
activity.
-The full definition — detection heuristics, aggregation, and how the brief
reports raw and adjusted counts — is
[`automated-contributions.md`](https://github.com/apache/magpie/blob/main/skills/contributor-nomination/automated-contributions.md).
-
-The discount is a signal for the humans reading the brief, never an automatic
disqualification.
-Using AI tools, and disclosing that use, is not penalised; only restatement,
content maintainers pushed back on, and work closed after that pushback are
discounted.
-
-Each key is resolved from this file, then from the default below.
-The readiness tracker falls back to these values when `committer-readiness.md`
does not set its own.
-
-| Key | Default | Project value | Notes |
-|---|---|---|---|
-| `automated_contribution_weight` | `0.25` | | Weight (0–1) of a merged or
open PR, issue, review or comment that drew maintainer pushback as looking
generated, unreviewed, restating, fabricated, or unwanted |
-| `restatement_comment_weight` | `0` | | Weight (0–1) of a comment or review
body that only restates the description, earlier comments, or the diff |
-| `closed_after_pushback_weight` | `0` | | Weight (0–1) of a PR or issue
closed unmerged after that pushback; `0` removes it from every metric |
-| `automated_pushback_phrases` | empty | | Extra phrases your maintainers use
when pushing back, added to the generic list |
-
-Set all three weights to `1` to turn the arithmetic off; flagged items are
still listed in the brief.
-
-### Project expectations for AI-assisted contributions
-
-List the documents in which your project states what it expects from
AI-assisted and automated contributions — a generative-AI contribution policy,
PR guidelines, a review or triage guide.
-Use paths relative to the repository root, or `https://` URLs, optionally with
a `#section` anchor.
-
-```yaml
-automated_contribution_expectations:
- - contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions
- -
contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated
- - contributing-docs/25_maintainer_pr_triage.md#for-contributors
-```
-
-When the list is present, the skill reads each document, judges contributions
against it first, and cites the document and section each flagged item
conflicts with.
-When it is empty or none of the documents can be read, the skill falls back to
the framework's generic heuristics and says so in the brief.
-The skill does not go looking for policy documents this list does not name.
-
----
-
-## Required areas by target *(optional)*
-
-Only declare if your project's PMC has a formal policy.
-Leaving this blank means the skill treats all contribution
-tracks (code, docs, testing, community) as equally valid paths.
-
-| Target | Required areas | Notes |
-|---|---|---|
-| `committer` | none | e.g. `none` — many projects accept doc/community
committers |
-| `pmc` | community or code | e.g. `review or community` |
-
----
-
-## Project-specific notes *(optional)*
-
-Free text surfaced at the top of every brief. Use for project
-norms the nominator should know — e.g. "This project has
-multiple active repositories; ask the maintainer to check
-contributor activity across all of them, not just `<upstream>`."
-
-```text
-Source: COMMITTERS.rst ("Guidelines to become an Airflow Committer" and
-"Guidelines for promoting Committers to Airflow PMC"). There is no strict
-numeric protocol; the PMC weighs combined contributions across areas.
-- The numeric thresholds are a floor for surfacing candidates, never a
- decision rule: activity volume alone does not make a candidate. Breadth
- across areas, dev list participation, release testing and sustained
- activity weigh as much as the counts.
-- Committer prerequisites: consistent contribution over at least three
- months; visibility on the dev list, Slack or GitHub issues/discussions
- (including non-binding votes and testing release candidates); helping
- other contributors (reviews, constructive feedback); contributions to
- community health.
-- Non-code paths count: it is possible to become a committer (and PMC
- member) without changing code, but only with visible presence in the
- community channels. Such exceptions are rare.
-- Areas the PMC looks at: Airflow Core, Task SDK, airflowctl, API, Docker
- image, Helm chart, dev tools (Breeze / CI), providers, security team work,
- issue triage, documentation.
-- PMC: committer for at least 3 months; currently active; consistent
- voting on release candidates for at least the past 3 release cycles;
- AIP engagement; reviews and merges; community involvement.
-- Airflow spans one main repository (apache/airflow) plus apache/airflow-site
- and apache/airflow-client-* repos; check activity across them.
-```
diff --git a/.apache-magpie-overrides/contributor-sentiment-config.md
b/.apache-magpie-overrides/contributor-sentiment-config.md
deleted file mode 100644
index 1e4e5e5b9bb..00000000000
--- a/.apache-magpie-overrides/contributor-sentiment-config.md
+++ /dev/null
@@ -1,66 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Contributor-sentiment thresholds](#contributor-sentiment-thresholds)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Contributor-sentiment thresholds
-
-Signal thresholds for `contributor-sentiment`, which measures whether the
-project got healthier to contribute to. Copy this file into your
-`<project-config>/` directory and change only the values you disagree with —
-**every key below is optional, and the default applies when it is absent or
-when the whole file is.**
-
-The skill compares a measurement window against a pre-adoption baseline and
-reports each signal as pass or fail. These caps decide where "fail" starts, so
-they are a statement about what the project considers a regression, not a
-tuning knob for making the report look better.
-
----
-
-```yaml
-contributor_sentiment:
-
- # Maximum allowed rise, in percentage points, in the fraction of first
- # responses classified as dismissive.
- tone_regression_cap_pp: 5
-
- # Maximum allowed rise, as a percentage, in median time to first reply.
- reply_increase_cap_pct: 50
-
- # Maximum allowed drop, in percentage points, in the share of first-time
- # contributors who opened a second PR.
- retention_decline_cap_pp: 10
-
- # Maximum allowed rise in the Gini coefficient of review load. Rising means
- # review work concentrating on fewer people.
- gini_increase_cap: 0.10
-
- # Default measurement window, in months, when the invocation names none.
- window_months: 6
-```
diff --git a/.apache-magpie-overrides/good-first-issue-config.md
b/.apache-magpie-overrides/good-first-issue-config.md
deleted file mode 100644
index 9d830a077d1..00000000000
--- a/.apache-magpie-overrides/good-first-issue-config.md
+++ /dev/null
@@ -1,93 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Apache Airflow — good-first-issue authoring
configuration](#apache-airflow--good-first-issue-authoring-configuration)
- - [Identifiers](#identifiers)
- - [Getting-started link](#getting-started-link)
- - [Out-of-scope topics](#out-of-scope-topics)
- - [AI-attribution footer](#ai-attribution-footer)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Apache Airflow — good-first-issue authoring configuration
-
-This file configures the
-[`good-first-issue-author`](../../skills/good-first-issue-author/SKILL.md)
-skill (Agentic Mentoring, `experimental`). Copy it into your own
-`<project-config>/good-first-issue-config.md` and replace every
-`<placeholder>` with your project's value. If a required key is missing,
-the skill aborts and points back here rather than guessing.
-
-## Identifiers
-
-| Key | Value | Notes |
-|---|---|---|
-| `good_first_issue_label` | `good first issue` | The label proposed on the
drafted issue. The skill proposes it; a maintainer applies it on confirmation. |
-| `max_effort_hours` | `4` | Upper bound on the estimated effort a good first
issue may carry. A candidate that clearly exceeds it is `scope-too-large`. |
-
-## Getting-started link
-
-A single link the drafted issue points a newcomer at. The skill links it
-rather than paraphrasing. The link must resolve from a GitHub issue body
-(not a repo-rendered file), so use an absolute URL: relative paths like
-`CONTRIBUTING.md` 404 when rendered inside an issue. The link must
-resolve before the skill drafts an issue; do not leave a placeholder URL
-in this row.
-
-| Trigger | Link | One-line label |
-|---|---|---|
-| Newcomer onboarding |
`https://github.com/apache/airflow/blob/main/contributing-docs/03a_contributors_quick_start_beginners.rst`
| Your first Airflow pull request (15-minute guide) |
-
-Pick the section of the contributing guide that is genuinely
-newcomer-shaped (a "Your first contribution" / "Getting started" section,
-not the top of the file, which usually lands on a doctoc TOC).
-
-## Out-of-scope topics
-
-The skill always declines (decision `unsuitable`) when a candidate touches
-one of these. Adjust for your project; the defaults below are typical of
-an Apache project.
-
-- Security-sensitive work (vulnerabilities, CVE-adjacent, embargoed)
-- Deprecation or removal timing (which release drops X)
-- Licensing questions (compatibility, header policy)
-- Architectural taste on a project-specific subsystem
-
-## AI-attribution footer
-
-Appended verbatim to every drafted issue body, disclosing AI authorship.
-
-```markdown
----
-
-_This issue was drafted with the help of an AI-assisted tool and reviewed by
an Apache Airflow maintainer before posting. If anything here is unclear or
looks wrong, say so on the issue: a real person is reading._
-```
-
-Replace `<PROJECT>` with the project's display name (read from
-[`<project-config>/project.md`](project.md)).
diff --git a/.apache-magpie-overrides/onboarding-concierge-config.md
b/.apache-magpie-overrides/onboarding-concierge-config.md
deleted file mode 100644
index 976267af3cb..00000000000
--- a/.apache-magpie-overrides/onboarding-concierge-config.md
+++ /dev/null
@@ -1,70 +0,0 @@
-<!--
- Licensed to the Apache Software Foundation (ASF) under one
- or more contributor license agreements. See the NOTICE file
- distributed with this work for additional information
- regarding copyright ownership. The ASF licenses this file
- to you under the Apache License, Version 2.0 (the
- "License"); you may not use this file except in compliance
- with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing,
- software distributed under the License is distributed on an
- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
- KIND, either express or implied. See the License for the
- specific language governing permissions and limitations
- under the License.
- -->
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update
-->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents** *generated with
[DocToc](https://github.com/thlorenz/doctoc)*
-
-- [Apache Airflow — onboarding-concierge
configuration](#apache-airflow--onboarding-concierge-configuration)
- - [Out-of-scope topics](#out-of-scope-topics)
- - [AI-attribution footer](#ai-attribution-footer)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
-<!-- SPDX-License-Identifier: Apache-2.0
- https://www.apache.org/licenses/LICENSE-2.0 -->
-
-# Apache Airflow — onboarding-concierge configuration
-
-Copy this file into your own `<project-config>/onboarding-concierge-config.md`
-and replace every `<placeholder>` with your project's value.
-
-| Key | Value | Notes |
-|---|---|---|
-| `contributing_guide_url` |
`https://github.com/apache/airflow/blob/main/contributing-docs/README.rst` |
Absolute `https://` URL of the project's primary contributing guide. Linked in
every answer. |
-| `maintainer_team_handle` | `@apache/airflow-committers` | GitHub team the
skill `@`-mentions on hand-off. Example: `@apache/airflow-committers`. |
-| `ai_attribution_footer` | *(see below)* | Literal markdown appended to every
drafted answer. |
-
-## Out-of-scope topics
-
-Topics that always trigger hand-off regardless of how the question is phrased.
-Remove rows that do not apply to your project; add rows for project-specific
-surfaces that AI should not improvise on.
-
-- `security` — vulnerability reports, CVE allocation, embargoed work
-- `deprecation` — timing decisions for removing or changing APIs
-- `license` — license compatibility, header policy
-- `architecture` — design-taste questions about project structure or evolution
-
-## AI-attribution footer
-
-```markdown
----
-
-_Note: This reply was drafted by an AI-assisted mentoring tool and may
-contain mistakes. Once you have addressed the points above, a
-Apache Airflow maintainer — a real person — will take the next look.
-We use this [two-stage
process](https://github.com/apache/airflow/blob/main/contributing-docs/25_maintainer_pr_triage.md#why-the-first-pass-is-automated)
so that our
-maintainers' limited time is spent where it matters most: the conversation
-with you._
-```
-
-Replace `<two_stage_process_doc_url>` with your project's documented
-mentoring/triage policy URL and `<PROJECT>` with the project's display name
-(read from `<project-config>/project.md`).
diff --git a/.apache-magpie.lock b/.apache-magpie.lock
index de70a8c7e54..d2715d8711f 100644
--- a/.apache-magpie.lock
+++ b/.apache-magpie.lock
@@ -9,46 +9,3 @@ plugins:
- magpie-utilities
- magpie-agent-guard
- magpie-release-management
- - magpie-contributor-growth
-
-reconciled:
- version: 0.9.0.dev202609261254
- at: 2026-09-26
- skills:
- activity-sweep: sha256:748187f2d78d9991
- announce-draft: sha256:1b0ebe953b9fa334
- archive-sweep: sha256:7cb626368f367e76
- audit-report: sha256:bed8d4c39f43581d
- backlog-stats: sha256:34d5f05ebb5ee5b3
- code-review: sha256:261649569ebac577
- committer-onboarding: sha256:0b1081376b51a75a
- contributor-to-committer: sha256:57f8813ba1ea4a69
- deduplicate: sha256:cee70e29c6fadb04
- good-first-issue-author: sha256:ac2d0fda09c67231
- good-first-issue-sweep: sha256:591ae352325ca83d
- isolated-setup-install: sha256:eb1b228a501f2772
- issue-import-from-scan: sha256:3aa895ba2115c1d9
- issue-import-via-forwarder: sha256:7be6fd9a774bbde5
- issue-invalidate: sha256:af16fa7d6f65328a
- keys-sync: sha256:bc9f77e9dcb305da
- mentor: sha256:3c380e6ecb0fb4c8
- newcomer-issue-explainer: sha256:8cfe453a3113abe2
- nomination: sha256:4dbd3136d81a2f87
- onboarding-concierge: sha256:4105a6571bcb70c2
- pr-stale-sweep: sha256:2c5b8030569b63e6
- pr-triage: sha256:4a3a20f254a3b7c7
- prepare: sha256:5cfba199f4348e98
- promote: sha256:e4f8b18462e8da1d
- quick-merge: sha256:ea4648413feb1eca
- rc-cut: sha256:3bbf726eae07fe4e
- reassess: sha256:26b90046cd97aef2
- reassess-stats: sha256:17acede01fa2f929
- reproducer: sha256:573d724afd671f6f
- sentiment: sha256:c325db1d99634a51
- stale-sweep: sha256:d2a78aaabcc57f26
- stats: sha256:6f0c574efb46849a
- triage: sha256:9b2993211bdc0e80
- verify-rc: sha256:eb35d109439cd24b
- vote-draft: sha256:3b74a3ec69e4b358
- vote-tally: sha256:b0b69aea022307a5
- welcome: sha256:a61c6575d69da08a
