Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[ecosystem] Document registry curation policy and responsibilities #5937

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[ecosystem] Document registry curation policy and responsibilities #5937

wants to merge 2 commits into from
+44 −3

Conversation

chalin
Copy link
Contributor

@chalin chalin commented Jan 15, 2025 •
edited
Loading

  • A proposed solution for What to do with registry entries that become out-of-date #5938, but I'm open to alternatives (let's discuss alternatives in the issue).
  • Adds a mention that registry-entry authors are responsible for keeping their data up-to-date
  • Failing that, we reserve the right to update and/or remove entries. We'll contact entry authors on a best effort basis
  • Adds a page on "Keeping registry information current"

Preview:

@chalin chalin requested a review from a team as a code owner January 15, 2025 17:44
@chalin chalin marked this pull request as draft January 15, 2025 18:00
@chalin
Copy link
Contributor Author

chalin commented Jan 15, 2025 •
edited
Loading

Marking as draft. Let me tweak this to clearly name the data lists other than the registry (such as adopters). ✅

@chalin chalin marked this pull request as ready for review January 15, 2025 18:16
@chalin chalin force-pushed the chalin-im-rw-registry-curation-2025-01-15 branch from 82e4994 to e7b1c28 Compare January 15, 2025 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
docs registry
Projects
SIG Comms: PRs & Issues
Status: No status
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@chalin