This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git
The following commit(s) were added to refs/heads/main by this push:
new 17349f1 docs(MISSION): editorial polish ahead of Board resolution
drafting (#169)
17349f1 is described below
commit 17349f18520e4d212ec613602ac8a2e34555237f
Author: Jarek Potiuk <[email protected]>
AuthorDate: Fri May 15 18:13:14 2026 +0200
docs(MISSION): editorial polish ahead of Board resolution drafting (#169)
Three editorial corrections to "Initial PMC composition (target)"
and "Source and IP" sections, made now so the next iteration of
MISSION.md is the document that gets attached to (and quoted in)
the forthcoming Board resolution. None of these change project
direction — they tighten phrasing that read fine in a working
draft but would land awkwardly in a Board-facing artefact:
- Size target: "7–9 members" → "7 or more members" — the 19-
candidate ASF-member roster already exceeds the prior upper
bound; the floor is the load-bearing number for the resolution.
- Coverage criterion rewritten: drop "two committers per friendly-
pilot PMC for the user-side reality check" and "at least one
committer with explicit responsibility for contributor
experience"; replace with (a) PMC roster drawn from a diverse
set of ASF projects rather than concentrated in one or two,
with preference for PMCs whose own work centres on developer
experience (build tools, language ecosystems, community
development, contributor-facing workflows), and (b) a majority
of members actively working on developer experience in their
home project. The old wording read as design-time aspirations;
the new one reads as roster-selection criteria the Board can
check against the named members.
- Source and IP section: replace the hypothetical "could be
donated" framing with the concrete picture — substantial
project-agnostic code is being moved over from Apache Airflow
(where the security-issue handling, PR triage, mentoring, and
drafting framework that became <PROJECT_NAME> was first
developed and proven), Apache Groovy, and other ASF projects
whose maintainers have been early adopters; all transferred
code clears the standard ASF software-grant process.
Generated-by: Claude Code (Claude Opus 4.7)
---
MISSION.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MISSION.md b/MISSION.md
index 1ef0e4e..e01da4e 100644
--- a/MISSION.md
+++ b/MISSION.md
@@ -155,9 +155,9 @@ The ASF mission line — *"to provide software for the public
good"* — has alw
PMC composition matters more than most because the project's social stakes are
higher than its technical stakes. The PMC will be filled from existing ASF
members, and potentially Apache Airflow PMC members where implementation of
Triage, Mentoring, and Drafting is already live and used — coordinated with
Membership before the resolution is adopted.
-- **Size:** 7–9 members.
+- **Size:** 7 or more members.
- **Diversity:** at least three distinct organisational affiliations; no
single employer holding a majority.
-- **Coverage:** at least two committers from each friendly-pilot PMC (Airflow,
Arrow, ATR, or similar) for the user-side reality check; at least one committer
with explicit responsibility for contributor experience, mentoring, and
onboarding rather than just engineering; ASF Privacy and ASF Legal engaged from
project start, given the contributor-data surface.
+- **Coverage:** PMC members drawn from a diverse set of ASF projects rather
than concentrated in one or two, with preference for PMCs whose own work
centres on developer experience (build tools, language ecosystems, community
development, contributor-facing workflows); a majority of members are actively
working on developer experience in their home project; ASF Privacy and ASF
Legal engaged from project start, given the contributor-data surface.
- **Chair:** Jarek Potiuk, subject to PMC vote per Bylaws.
ASF members for the roster:
@@ -205,7 +205,7 @@ on the project from day one:
## Source and IP
-Green-field project. Existing project-agnostic code in the Apache Airflow PMC
— already designed to be reusable in and outside the ASF — could be donated to
speed implementation; some related ideas are implemented in Gofannon.
+Green-field project, with substantial project-agnostic code being moved over
from existing ASF projects — Apache Airflow (where the security-issue handling,
PR triage, mentoring, and drafting framework that became `<PROJECT_NAME>` was
first developed and proven; already structured under Apache-2.0 for reuse
inside and outside the ASF), Apache Groovy, and other ASF projects whose
maintainers have been early adopters. All transferred code clears the standard
ASF software-grant process; som [...]
## External dependencies
