This is an automated email from the ASF dual-hosted git repository.

snoopdave pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/roller.git


The following commit(s) were added to refs/heads/master by this push:
     new ce7ed3be8 Add a roller-board-report developer skill for the quarterly 
board report (#229)
ce7ed3be8 is described below

commit ce7ed3be8775b8de053f1ffc8ec7b54fecc21c4a
Author: David M. Johnson <[email protected]>
AuthorDate: Sat Oct 31 18:37:37 2026 -0400

    Add a roller-board-report developer skill for the quarterly board report 
(#229)
    
    * Add a roller-board-report developer skill for the quarterly board report
    
    Claude-Session: https://claude.ai/code/session_01C5X1Z1eoSH7o25gZskPGzb
    
    * Board report skill: whole-day git window, one line per author, meeting 
day wording
    
    * Board report skill: rewrap schedule paragraph
---
 skills/README.md                                   |  1 +
 skills/roller-board-report/SKILL.md                | 99 ++++++++++++++++++++++
 .../references/asf-reporting.md                    | 83 ++++++++++++++++++
 .../roller-board-report/references/data-sources.md | 38 +++++++++
 .../scripts/quarter-activity.sh                    | 88 +++++++++++++++++++
 5 files changed, 309 insertions(+)

diff --git a/skills/README.md b/skills/README.md
index 1f2aa1a0b..7f0edb9fb 100644
--- a/skills/README.md
+++ b/skills/README.md
@@ -30,6 +30,7 @@ of living in one committer's head.
 |---|---|
 | [`roller-release`](roller-release/SKILL.md) | Preparing, building, signing, 
verifying, staging, voting on and publishing a release, plus the release 
website and announcement drafts. |
 | [`roller-security`](roller-security/SKILL.md) | Security report triage, 
private case tracking, CVE preparation, reporter coordination and disclosure 
planning. |
+| [`roller-board-report`](roller-board-report/SKILL.md) | Drafting, reviewing 
and submitting the quarterly report to the ASF board, and following up on board 
feedback. |
 
 ## Reading them
 
diff --git a/skills/roller-board-report/SKILL.md 
b/skills/roller-board-report/SKILL.md
new file mode 100644
index 000000000..0a5039684
--- /dev/null
+++ b/skills/roller-board-report/SKILL.md
@@ -0,0 +1,99 @@
+---
+name: roller-board-report
+description: Prepare, review and submit the Apache Roller quarterly report to 
the ASF board through reporter.apache.org, and handle board feedback on earlier 
reports.
+---
+
+<!--
+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
+
+    https://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.
+-->
+
+# Apache Roller board reports
+
+The PMC reports to the ASF board in February, May, August and November. The
+chair owns the report. This skill collects facts and drafts text; loading it
+does not authorize sending mail or submitting the report.
+See [ASF reporting](references/asf-reporting.md) for policy and mechanics.
+
+## Establish inputs
+
+Record the report due date, the board meeting date and the reporting window
+(from the day after the previous meeting to now). Take the dates from the
+board-chair reminder mail or the wizard's Base Data, not from memory.
+
+## Read what came before
+
+1. Read the previous report in the
+   [Roller board minutes](https://whimsy.apache.org/board/minutes/Roller.html).
+   The most recent meeting may not be there yet; use the agenda tool for it.
+2. Read board comments: the wizard's "Comments on recent board reports" and
+   any "Board feedback on <date> Roller report" mail. Answer every comment that
+   asks a question in this report. Take other comments into account.
+
+## Gather facts
+
+Use [data sources](references/data-sources.md). Start with
+`scripts/quarter-activity.sh <since> [<until>]` from this skill, run from the
+Roller checkout after `git fetch origin --tags`. Then check the wizard's
+Membership Data, the reporter statistics page 
(`https://reporter.apache.org/wizard/statistics?roller`) and mailing list 
volume.
+Record the date of the latest release; the board has asked for it.
+
+## Draft
+
+Use the wizard's sections: Description, Project Status (with "Issues for the
+board"), Membership Data, Project Activity and Community Health. Copy the
+wizard's Membership Data text unchanged.
+
+- Give the chair's assessment of project health, not only statistics.
+- Give the latest release and its date, and the next planned release.
+- Name new contributors and say whether the PMC is considering them for
+  committer or PMC membership. State only what the PMC has actually done.
+- Say "None" under "Issues for the board" unless there is one.
+- Keep the tone plain and factual. No jokes or filler to reach a length.
+
+Write the draft to a local file outside the repository and give it to the
+chair to edit. Sharing it on private@ for comment is optional; ask first.
+
+## Keep security details out
+
+Board reports become public minutes. Do not name undisclosed vulnerabilities,
+CVE IDs before publication, affected features, severities, reporters or
+disclosure dates in the public text. Public text may say that reports were
+received and handled through the ASF security process and which release will
+carry the fixes. Put anything the board needs beyond that inside
+`<private>...</private>`, which the agenda tool keeps out of published minutes;
+confirm the convention in the current agenda tool before relying on it. If in
+doubt, leave it out and offer details on request. Use the companion
+`roller-security` skill for case status, and take counts only.
+
+## Submit
+
+Submit only after the chair approves the final text in chat.
+
+1. Open `https://reporter.apache.org/wizard/?roller` in the chair's browser
+   (ASF login required). Confirm the Base Data shows the expected meeting.
+2. Enter each section, then go to "Review and Publish". Show the chair the
+   rendered text and confirm it matches the approved draft.
+3. Publish only on an explicit yes. Then check that Base Data shows "Filed to
+   agenda", or check the Roller entry in the board agenda for that meeting.
+
+If the wizard fails, use the agenda tool, or mail [email protected] with the
+subject `[REPORT] Roller`, after the chair agrees. If a report cannot be ready
+on time, tell the board that instead of skipping it.
+
+## After the meeting
+
+Watch for "Board feedback on <date> Roller report". Note each comment for the
+next report and reply on board@ only when the chair asks.
diff --git a/skills/roller-board-report/references/asf-reporting.md 
b/skills/roller-board-report/references/asf-reporting.md
new file mode 100644
index 000000000..fa0997ee3
--- /dev/null
+++ b/skills/roller-board-report/references/asf-reporting.md
@@ -0,0 +1,83 @@
+<!--
+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
+
+    https://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.
+-->
+
+# ASF board reporting
+
+Verify against the authoritative sources each quarter; this is a summary.
+
+## Sources
+
+- Reporting guide: <https://www.apache.org/foundation/board/reporting>
+- Report wizard: <https://reporter.apache.org/wizard/?roller>
+- Board agenda tool: `https://agenda.apache.org/meetings/<YYYY-MM-DD>#roller`
+- Past Roller reports: <https://whimsy.apache.org/board/minutes/Roller.html>
+- Board calendar: 
<https://svn.apache.org/repos/private/committers/board/calendar.txt>
+
+## Schedule
+
+Roller reports in February, May, August and November. The board usually meets
+on the third Wednesday of the month; check the board calendar for the date.
+Reports are due one week before the meeting; a late report is postponed to the
+next meeting. The board-chair reminder mail, sent to the chair with private@ in
+copy, gives both dates.
+
+## Submission mechanisms
+
+In order of preference:
+
+1. The reporter wizard. It prefills the description and membership data and
+   files the report to the agenda.
+2. The agenda tool.
+3. A commit to the dated agenda in the private board SVN repository.
+4. Mail to [email protected] with the subject `[REPORT] Roller`.
+
+## Report sections
+
+The wizard uses this template:
+
+```
+## Description:
+## Project Status:
+Current project status:
+Issues for the board:
+## Membership Data:
+## Project Activity:
+## Community Health:
+```
+
+The board wants the chair's own observations and assessment, not only raw
+statistics. If a full report is not possible, report that; postponing by a
+month is acceptable.
+
+## Private text
+
+Approved reports are published in the board minutes. Text in
+`<private>...</private>` is kept out of the published minutes. Keep undisclosed
+security details out of the public text.
+
+## Feedback
+
+Directors comment in the agenda tool during the review week. The secretary
+mails the comments to the chair and private@ as "Board feedback on <date>
+Roller report", and the wizard lists them under "Comments on recent board
+reports". Comments that ask a question are answered in the next report unless
+the comment says otherwise. Questions about comments go to board@.
+
+Past comments that still apply:
+
+- Include the dates of the latest release(s).
+- Keep security issue details private.
diff --git a/skills/roller-board-report/references/data-sources.md 
b/skills/roller-board-report/references/data-sources.md
new file mode 100644
index 000000000..adbe8b5ea
--- /dev/null
+++ b/skills/roller-board-report/references/data-sources.md
@@ -0,0 +1,38 @@
+<!--
+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
+
+    https://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.
+-->
+
+# Data sources for the report
+
+| Fact | Source |
+|---|---|
+| Meeting date, due date, filed status | Wizard Base Data; board-chair 
reminder mail |
+| Committer and PMC counts, last additions | Wizard Membership Data (copy as 
is) |
+| Commits, contributors, merged PRs, tags | `scripts/quarter-activity.sh 
<since>` |
+| Mailing list volume | 
<https://lists.apache.org/[email protected]> and the reporter 
statistics page <https://reporter.apache.org/wizard/statistics?roller> (it may 
count automated GitHub mail; check the list archive) |
+| Release dates | Announcement mails on announce@ or user@; the downloads 
page; Git tags as a fallback (a tag date is the RC date, not the release date) |
+| Previous report | <https://whimsy.apache.org/board/minutes/Roller.html> |
+| Board comments | Wizard "Comments on recent board reports"; "Board feedback 
on <date> Roller report" mail |
+| Security activity | The private triage workspace through the 
`roller-security` skill. Counts and target release only |
+
+## Notes
+
+- Roller develops on two lines: `master` and the maintenance branch
+  `roller-6.1.x`. Count both, and do not double-count merges between them.
+- A first-time author in the window is a contributor to name in Community
+  Health. Check whether they are already a committer before calling them new.
+- Reporter statistics can lag or miss GitHub-only activity. Prefer Git and
+  GitHub for code activity.
diff --git a/skills/roller-board-report/scripts/quarter-activity.sh 
b/skills/roller-board-report/scripts/quarter-activity.sh
new file mode 100755
index 000000000..640f240b8
--- /dev/null
+++ b/skills/roller-board-report/scripts/quarter-activity.sh
@@ -0,0 +1,88 @@
+#!/usr/bin/env bash
+# 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
+#
+#     https://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.
+
+#
+# Summarize Roller activity for a board report window.
+#
+#   quarter-activity.sh <since> [<until>]     dates as YYYY-MM-DD
+#
+# Run from a Roller checkout after `git fetch origin --tags`. Prints commits
+# per author on each line of development, authors whose first commit falls in
+# the window, tags created in the window, and merged pull requests (with gh).
+# Read-only: it does not fetch, write or contact anything except GitHub via gh.
+
+set -uo pipefail
+
+since="${1:?usage: quarter-activity.sh <since> [<until>]}"
+until="${2:-$(date +%Y-%m-%d)}"
+# git reads a bare date as that date at the current time of day, so pin the
+# window to whole days
+git_since="$since 00:00:00"
+git_until="$until 23:59:59"
+branches=(origin/master origin/roller-6.1.x)
+repo="apache/roller"
+
+git rev-parse --git-dir >/dev/null 2>&1 || { echo "not a git checkout" >&2; 
exit 1; }
+
+refs=()
+for b in "${branches[@]}"; do
+    git rev-parse --verify -q "$b" >/dev/null && refs+=("$b")
+done
+[ ${#refs[@]} -gt 0 ] || { echo "none of ${branches[*]} exist; fetch origin 
first" >&2; exit 1; }
+
+echo "Window: $since .. $until"
+echo
+
+for b in "${refs[@]}"; do
+    n=$(git rev-list --count --no-merges --since="$git_since" 
--until="$git_until" "$b")
+    echo "== Commits on $b (no merges): $n"
+    git shortlog -sn --no-merges --since="$git_since" --until="$git_until" 
"$b" | sed 's/^/  /'
+    echo
+done
+
+echo "== Commits on both lines, counted once"
+git shortlog -sn --no-merges --since="$git_since" --until="$git_until" 
"${refs[@]}" | sed 's/^/  /'
+echo
+
+echo "== Authors whose first commit is in the window"
+found=""
+while IFS= read -r email; do
+    [ -n "$email" ] || continue
+    if [ -z "$(git log --all -1 --format=%h --until="$git_since" 
--author="<$email>")" ]; then
+        name=$(git log "${refs[@]}" -1 --format=%aN --author="<$email>")
+        echo "  $name <$email>"
+        found=1
+    fi
+done < <(git log --no-merges --since="$git_since" --until="$git_until" 
--format=%aE "${refs[@]}" | sort -u)
+[ -n "$found" ] || echo "  (none)"
+echo
+
+echo "== Tags created in the window"
+git for-each-ref --sort=creatordate --format='%(creatordate:short) 
%(refname:short)' refs/tags \
+    | awk -v s="$since" -v u="$until" '$1 >= s && $1 <= u { print "  " $0 }'
+echo "  (a tag date is when the tag was made, not the release announcement 
date)"
+echo
+
+echo "== Merged pull requests"
+if command -v gh >/dev/null 2>&1; then
+    gh pr list --repo "$repo" --state merged --limit 300 \
+        --search "merged:$since..$until" \
+        --json number,title,baseRefName,author \
+        --template '{{range .}}  #{{.number}} [{{.baseRefName}}] {{.title}} 
({{.author.login}}){{"\n"}}{{end}}' \
+        || echo "  gh failed; check authentication"
+else
+    echo "  gh not installed; skipped"
+fi

Reply via email to