PowerShell/PowerShell-RFC

RFC (Request for Comments) documents for community feedback on design changes and improvements to PowerShell ecosystem

Owned by Microsoft

View on GitHub ↗Jump to charts ↓

PowerShell/PowerShell-RFC has 450+ stars and 100+ forks on GitHub, is written in PowerShell, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 6 minutes ago
Added to GitGenius on October 12th, 2026
Created on July 27th, 2015
Open Issues & Pull Requests: 40 (+0)
GitHub issues: Enabled
Number of forks: 142
Total Stargazers: 469 (+0)
Total Subscribers: 93 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 0.6 hours
90th percentile: 2.1 hours
Tracked items: 4

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 329 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

PowerShell-RFC is a repository for Request for Comments documents that enable community feedback on design changes and improvements to the PowerShell ecosystem.

The repository addresses the need for structured discussion around proposed changes to PowerShell rather than relying on lengthy issue threads. It provides a formal RFC process where community members and the PowerShell Team can collaborate on design decisions. The approach involves submitting RFC documents that outline proposed changes, gathering community feedback, and having the PowerShell Team review submissions in regular meetings to respond to and evaluate proposals.

This repository is intended for anyone involved in PowerShell development or governance who wants visibility into upcoming changes or wishes to propose improvements to the ecosystem. It suits projects and organizations that depend on PowerShell and want a voice in its direction, as well as contributors interested in shaping the language's future. The RFC process is designed to be more structured and asynchronous than real-time issue discussions, allowing for thoughtful consideration of significant design decisions.

The project maintains an active review cadence with the PowerShell Team meeting regularly to evaluate feedback on submitted RFCs. The repository includes clear governance documentation outlining the RFC process itself, along with established community guidelines through a Code of Conduct and Security Policy, indicating a mature approach to managing community participation and handling sensitive reports.