[go: nahoru, domu]
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

API ownership #412

Open
bhack opened this issue Feb 11, 2022 · 8 comments
Open

API ownership #412

bhack opened this issue Feb 11, 2022 · 8 comments
Assignees
@theadactyl

Comments

@bhack
Copy link
Contributor
bhack commented Feb 11, 2022

As we still maintain here the API governance I want to ask if it could be possible to expose for transparency the API ownership in our community.

We had a tangential discussion at tensorflow/tensorflow#51739 (comment) as we have still really a very limited public API ownership in CODEOWNERS files.

Also, there are cases in which emerges that we don't have an active API ownership for a specific subnamespace like in keras-team/keras-cv#74 (comment).

This topic could be partially related and extended also to the @yarri-oss comment at #384 (review)
@ematejska
Copy link
Contributor

Thanks for this issue. Following up with the API Owners.

@bhack bhack mentioned this issue Mar 10, 2022
Closed
@bhack
Copy link
Contributor Author
bhack commented Mar 10, 2022

@ematejska As you can see also in keras-team/keras-cv#146 (comment) it is always hard to interact/mention the right codeowner if we don't adopt a codeowner transparency.

@bhack
Copy link
Contributor Author
bhack commented Mar 15, 2022

The last case was confirmed keras-team/keras-cv#146 (comment) like in keras-team/keras-cv#74 (comment)

@bhack
Copy link
Contributor Author
bhack commented Mar 15, 2022

/cc @theadactyl

@wangpengmit
Copy link
Member

cc @rohan100jain

@bhack bhack mentioned this issue Mar 24, 2022
Closed
@ematejska
Copy link
Contributor

@theadactyl To put on the agenda for the next TF steering committee mtg.

@bhack
Copy link
Contributor Author
bhack commented Jul 12, 2022

@theadactyl To put on the agenda for the next TF steering committee mtg.

Check also the recent policy change in pytorch:
https://github.com/pytorch/pytorch/pull/78850/files

@bhack
Copy link
Contributor Author
bhack commented Sep 14, 2022

We have an example of API ownership at:
https://pytorch.org/docs/stable/community/persons_of_interest.html

@bhack bhack mentioned this issue Oct 1, 2022
Open
@bhack bhack mentioned this issue Feb 2, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@theadactyl theadactyl

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bhack @theadactyl @wangpengmit @ematejska