-
Notifications
You must be signed in to change notification settings - Fork 15
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
Update the maintainers/editors for v1? #80
Comments
@earth2marsh The Please comment here or open a PR if it needs to be changed. |
I'm suddenly wobbly about what "editors" means! Contributors suggests people who submit PRs that then get merged. It could also include people who join discussions/issues/Slack/Zoom discussions. Maintainers maps onto the TSC in terms of people who review/approve merges for OAS. (CODEOWNERS also intersects a bit?) So what then does Editors mean? It seems like it serves like it credits the people behind the document (not unlike RFC authors). Is that accurate? If so, what are the criteria for inclusion? |
My take, aligned with my top ten Google results:
Translated to our current setup:
For OAS this is reflected in the three different files For Overlay the |
@ralfhandl is the CONTRIBUTORS.md file actually used for anything or does it just sit there separate from the spec publishing process? |
@ralfhandl, what do you expect me to do here? |
Nothing, wrong button 🙄 |
Exactly 😎 |
I'd like to propose removing the contributors file. Pull requests are not the only valued activity on our projects, and it doesn't send the correct message IMO. |
@lornajane agreed, I've filed OAI/OpenAPI-Specification#4148 to track. |
The maintainers list lists an older TSC member list. It might be updated, removed, or pointed to the OpenAPI Specification's document (reduce future toil).
There is a separate editors list that might also deserve a review before v1 launch?
The text was updated successfully, but these errors were encountered: