community API ownership

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 https://github.com/tensorflow/tensorflow/pull/51739#issuecomment-946157182 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 https://github.com/keras-team/keras-cv/issues/74#issuecomment-1035597742.

This topic could be partially related and extended also to the @yarri-oss comment at https://github.com/tensorflow/community/pull/384#pullrequestreview-676549096

Feb 11 '22 15:02 bhack

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

Mar 07 '22 18:03 ematejska

@ematejska As you can see also in https://github.com/keras-team/keras-cv/pull/146#issuecomment-1063974863 it is always hard to interact/mention the right codeowner if we don't adopt a codeowner transparency.

Mar 10 '22 12:03 bhack

The last case was confirmed https://github.com/keras-team/keras-cv/pull/146#issuecomment-1068486128 like in https://github.com/keras-team/keras-cv/issues/74#issuecomment-1035597742

Mar 15 '22 21:03 bhack

/cc @theadactyl

Mar 15 '22 21:03 bhack

cc @rohan100jain

Mar 15 '22 21:03 wangpengmit

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

Jul 11 '22 17:07 ematejska

@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

Jul 12 '22 11:07 bhack

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

Sep 14 '22 10:09 bhack