cluster-api-provider-aws: unknown field "emeritus_maintainers" in the OWNERS file
there is a new tool for parsing the kubernetes/community/sigs.yaml file and it reports an error in the OWNERS file in this repository:
ERROR: unable to parse owners file at https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-aws/master/OWNERS url - error unmarshaling JSON: while decoding JSON: json: unknown field “emeritus_maintainers”
solution
-
move the entries under
emeritus_maintainershttps://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/OWNERS#L19-L24 toemeritus_approvers. -
remove the
emeritus_maintainerskey.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (18 by maintainers)
It can take some time before a tool like that becomes stable. I think what matters in this case is that there is no such field (_maintainers) defined in the YAML spec of the bot that reads the owners files. On Jan 28, 2022 11:58, “Gergely Brautigam” @.***> wrote:
@Skarlso - what do you think to this then:
emeritus_approversemeritus_maintainerstoemeritus_approversI think we should still acknowledge emeritus reviewers/approvers in general. So how about we add a section in the README.md under the
Our contributorsheading (before the image of all the contributors) where we add something likeThank you to all our contributores and a special thank you to our emetritus maintainer: XXXXX and emeritus reviewers XXXXX?There is only an _approvers field. Leaving the decisions to the current maintainers. On Jan 28, 2022 13:19, “Gergely Brautigam” @.***> wrote:
@Skarlso - when you make this change could you move the existing
emeritus_approversinto theemeritus_reviewerslist? And then changeemeritus_maintainerstoemeritus_approvers?