-
Notifications
You must be signed in to change notification settings - Fork 222
Add automated working group reporting system for TOC quarterly reviews #1300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
rkoster
wants to merge
17
commits into
main
Choose a base branch
from
fiwg-update
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1,315
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Script now checks for existing update files in toc/working-groups/updates/ - Uses previous update date as start date when no date is specified - Falls back to 3 months lookback if no previous update exists - Enables incremental reporting without manual date specification
…ng group update - Add RFC-0038 IPv6 dual-stack support as the leading major initiative - Emphasize the historic significance of this networking evolution - Include comprehensive technical details and community impact - Update activity metrics and summary to reflect IPv6 importance - Add IPv6 implementation opportunities in forward-looking section - Ensure the most important track of work is prominently featured
…ization - Replace AliCloud emphasis with UAA identity management modernization - Highlight active IPv6 dual-stack implementation progress (BOSH core, AWS CPI, testing) - Feature UAA ExternalLoginAuthenticationManager refactoring by @adrianhoelzl-sap - Add Storage CLI AWS SDK v2 migration initiative - Update activity metrics to reflect actual development priorities - Based on comprehensive data dump analysis revealing key missing work areas
- Condensed all major strategic initiatives to exactly 2 paragraphs each - Maintained technical depth while improving readability and focus - Updated generation script to enforce 2-paragraph constraint for future reports - Preserved all key technical details and related work links - Enhanced report accessibility for TOC consumption
- Remove duplicate 'IPv6 Dual-Stack Implementation in Active Development' header - Clean up formatting inconsistency in major initiatives section
- Add proper issue linking format (descriptive link + org/repo#number shorthand) - Remove speculative 'Looking Forward' section to prevent hallucination - Update generation script to use existing reports as templates - Ensure consistent formatting across all working group updates
- Move contributor recognition inline within initiative descriptions - Add GitHub profile links for all contributors using [Name](https://github.com/username) format - Remove separate Community Contributors Recognition section - Consolidate summary to single paragraph with key contributors highlighted - Update generation script to enforce inline recognition with GitHub links
- Remove all separate 'Related Work' sections from initiatives - Embed PR and issue links inline within the paragraph text that describes the work - Maintain dual link format (descriptive link + org/repo#number shorthand) - Update generation script to require inline integration and prohibit separate link sections - Create natural text flow with links embedded where work is described
- Add maximum 40 words per paragraph requirement to generation script - Break down all long paragraphs in FI report to meet 40-word limit - Split summary from 1 long paragraph (83 words) to 2 concise paragraphs (24, 35 words) - Condense all initiative sections to 2 paragraphs of maximum 40 words each - Maintain technical accuracy and comprehensive PR/issue linking while improving readability
- Remove shorthand org/repo#number format from all PR links - Use descriptive link text that explains the work performed instead of repo references - Add rule to prevent duplicate PR links within the same paragraph - Update generation script to prefer descriptive links over repo#PR format - Maintain comprehensive linking while improving readability and avoiding redundancy
- Remove Community Impact Areas and Activity Breakdown sections that provide no value - Integrate RFC developments directly into relevant Major Strategic Initiatives - Add new Shared Infrastructure and CI/CD Modernization initiative for RFC-0041 - Embed RFC-0038 into IPv6 section and RFC-0043 into Storage CLI section - Update generation script to integrate RFCs within initiatives rather than separate section - Create cohesive structure showing how governance enables technical implementation
- Delete Summary section that provided redundant high-level overview - Remove 'Major Strategic Initiatives' heading while keeping all initiative content - Promote all initiative subsections from h3 to h2 level for cleaner hierarchy - Update generation script to eliminate Summary section requirement - Create direct, focused structure that jumps immediately into technical work - Maintain all technical content while eliminating introductory redundancy
Example output for when invoking the working group update script: ❯ python3 scripts/generate_working_group_update.py foundational-infrastructure
Generating working group update for foundational-infrastructure (target date: 2025-09-02)
Extracting raw activity data...
✅ Raw activity data extracted: tmp/foundational-infrastructure_activity.json
Running OpenCode analysis...
| Todo 5 todos
I'll help you generate a comprehensive Cloud Foundry working group activity update report for the foundational-infrastructure working group. Let me start by creating a todo list to track this
multi-step process.
| Bash jq . tmp/foundational-infrastructure_activity.json | head -50
Now let me start by analyzing the raw activity data and reading the working group charter in parallel:
| Read toc/working-groups/foundational-infrastructure.md
Now let me analyze the existing reports to understand the format:
| Bash ls toc/working-groups/updates/ | grep foundational-infrastructure | sort -V
| Bash ls toc/working-groups/updates/ | head -10
Let me get the full list and examine the contents:
| List toc/working-groups/updates
| Todo 3 todos
Let me update the todo and check if there are example reports in other locations or if I need to create one from scratch:
Let me continue analyzing the activity data to understand its structure and extract key information:
| Bash jq '.areas | length' tmp/foundational-infrastructure_activity.json
| Bash jq '.areas[].name' tmp/foundational-infrastructure_activity.json
| Bash jq '.rfcs // []' tmp/foundational-infrastructure_activity.json
Let me now analyze specific commits and contributions to understand the activity patterns:
| Bash jq '[.areas[] | {area: .name, total_commits: (.repositories | map(.commits | length) | add), total_prs: (.repositories | map(.pull_requests | length) | add), total_issues: (.repos
itories | map(.issues | length) | add)}] | sort_by(.total_commits) | reverse' tmp/foundational-infrastructure_activity.json
Let me look at specific contributors and notable features:
| Bash jq '[.areas[].repositories[].commits[] | select(.author != "dependabot[bot]") | {author: .author, message: .message, date: .date}] | group_by(.author) | map({author: .[0].author,
commits: length}) | sort_by(.commits) | reverse | .[0:10]' tmp/foundational-infrastructure_activity.json
| Todo 2 todos
Now let me look at specific RFC-related activities and mark my analysis task as completed:
Let me extract key RFC information and feature development:
| Bash jq '.rfcs[] | select(.files[]? | contains("foundational-infrastructure") or contains("toc/rfc/")) | {title: .title, state: .state, url: .url, author: .author, files: .files}' tmp/
foundational-infrastructure_activity.json
Let me look at specific major features and releases:
| Bash jq '[.areas[].repositories[] | select(.releases | length > 0) | {repo: .repository, releases: .releases}] | .[0:5]' tmp/foundational-infrastructure_activity.json
| Todo 1 todos
Now let me create the comprehensive report based on all the analysis:
| Write toc/working-groups/updates/2025-09-02-foundational-infrastructure.md
| Todo 0 todos
Perfect! I've successfully generated a comprehensive Cloud Foundry working group activity update report for the foundational-infrastructure working group. Here's what I accomplished:
## Report Highlights
**✅ RFC-Focused Analysis**: The report prioritizes RFC-0043 (Cloud Controller Storage CLI) as the marquee initiative, showing how it bridges Foundational Infrastructure and App Runtime Inter
faces working groups.
**✅ Community Collaboration**: Featured cross-organizational work by contributors like [Stephan Merkel](https://github.com/stephanme), [Aram Price](https://github.com/aramprice), and [Julian
Hjortshoj](https://github.com/julian-hj) with direct GitHub profile links.
**✅ Strategic Technical Impact**: Highlighted major achievements including:
- BOSH infrastructure modernization (1,166 commits)
- UAA Spring 6.2.8 and Java 21 upgrades
- IPv6 dual-stack progress via RFC-0038
- Storage CLI unification efforts
**✅ Comprehensive Coverage**: Analyzed activity across all 11 working group areas with specific commit counts, release data, and contributor recognition.
**✅ Integrated Linking**: Embedded PR/issue links directly in descriptive text (e.g., "cloudfoundry/community#1275") rather than separate sections.
The report celebrates the foundational infrastructure community's collaborative innovation while providing the TOC with detailed technical progress and strategic impact analysis for the June
4 - September 2, 2025 period.
✅ Working group update generated: toc/working-groups/updates/2025-09-02-foundational-infrastructure.md
🎉 Working group update completed!
📄 Report: toc/working-groups/updates/2025-09-02-foundational-infrastructure.md
📁 All reports: toc/working-groups/updates/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
• Implements comprehensive automation system for quarterly working group activity reports to enhance TOC governance and oversight
• Separates data extraction from AI analysis using OpenCode Run integration for strategic insights and consistent reporting
Key Changes
scripts/extract_wg_activity.py
): Pure GitHub API data extraction for commits, PRs, issues, releases, and RFCsscripts/generate_working_group_update.py
): Leverages OpenCode Run for AI-powered analysis of raw activity datatoc/working-groups/updates/README.md
with usage examplestmp/
directory for temporary data files with proper git ignoreBenefits
The system maintains clean separation between data extraction (GitHub API) and analysis (OpenCode Run), making it maintainable and extensible for future enhancements.
FI Working group update generated by the new automation can be found here.