Open bhack opened 2 years ago
Thanks for this issue. Following up with the API Owners.
@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.
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
/cc @theadactyl
cc @rohan100jain
@theadactyl To put on the agenda for the next TF steering committee mtg.
@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
We have an example of API ownership at: https://pytorch.org/docs/stable/community/persons_of_interest.html
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