Closed lukaszgryglicki closed 4 years ago
didn't notice this until just now
I am surprised many of these aren't in the groups, I'll take a crack at triaging later, noting to self here to bump for recency
OK, would be great to assign them somewhere or just create a fallback group "Other" I'm in LA now BTW.
@spiffxp any feedback there? Leave it "as is" or just create "Other" repo group, or maybe just create one repo group for each unassigned repo?
Yet again this fell off my radar, and I'm not going to get to it in the next few days, but bumping for recency again. Need to dig up the script I used to generate the last grouping.
Opened https://github.com/kubernetes/community/issues/3305 so I can /assign for a better shot at finding this next time
Created https://github.com/cncf/devstats/pull/167 to assign all k8s repos to repo groups
Great, please see this comment
This should also include this issue.
Fixed by #192
New repos should be assigned to repo groups: https://github.com/kubernetes/community/issues/3305#issuecomment-583975176
New dashboard showing repository groups - repositories assignments implemented: https://github.com/cncf/devstats/issues/235#issuecomment-585110324
Blocked, awaiting data from the community.
Working on this, see. It will be implemented on the test server first.
Implemented on both test & prod servers, closing.
@spiffxp New K8s repo groups defined here leaves many repositories unassigned to any repository group. What we can do:
Unassigned repos are:
cc @dankohn