Skip to content

docs: display the component-owner role more prominently in README.md #2800

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
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

pichlermarc
Copy link
Member

@pichlermarc pichlermarc commented Apr 25, 2025

How maintenance in the the contrib repo works is kind of hidden away, and many people assume it works similarly to the core repo where there's shared ownership across the whole repo, which is not completely the case here.

This puts info about component ownership more prominently into the README.md, and clarifies that packages here are community maintained for the most part.

I plan to follow-up with a new document with role descriptions (split from CONTRIBUTING.md) to clarify further, as well as a new document for component maintenance status lifecycle (including a process for removal of unmaintained components).

Copy link

codecov bot commented Apr 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.65%. Comparing base (41d0d4b) to head (80587da).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2800      +/-   ##
==========================================
+ Coverage   89.60%   89.65%   +0.04%     
==========================================
  Files         174      174              
  Lines        8450     8450              
  Branches     1660     1660              
==========================================
+ Hits         7572     7576       +4     
+ Misses        878      874       -4     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants