Replies: 4 comments
-
IMHO the strategy is to find a solution to progressively improve these metrics: |
Beta Was this translation helpful? Give feedback.
-
Our primary goal with updating the RoadMap: https://github.com/keras-team/keras-cv/blob/master/.github/ROADMAP.md and narrowing our focus to only welcome contributions guiding us towards these is to improve on this - and keep the repository in a better state. Hopefully this helps, as I agree with you that at this moment review latencys and such are too high. |
Beta Was this translation helpful? Give feedback.
-
Yes but the wish of growing he contributors doesn't scale if you will not progressively increase the mentioned inclusion metrics. See the last two graphs at: And the metrics at: So the narrowing of the roadmap IMHO is just one singe factor of the problem. |
Beta Was this translation helpful? Give feedback.
-
I start to have the impression that we are already approaching again to a review bottleneck as in many other community repositories.
I suggest that we invest a little bit more time on the governance strategy to engage the "external" community to the review and maintainership process:
https://github.com/pytorch/pytorch/pull/78850/files
Beta Was this translation helpful? Give feedback.
All reactions