Closed micahhausler closed 2 years ago
IDK if we need to collect PII, github handle should be enough right?
I am not a lawyer, but do we want to ask for a given name for maintainers/committers? Thinking about upholding export control laws and such
Me neither but I don't see how taking given name would be useful w/o verifying somehow... which I don't even want to get into. I'll go snooping through cncf docs to see if any guidance is provided. I feel like wanting given names will open up a whole can of identity/verification questions/worms that may not really be necessary :thinking: .
I think its fine to keep it optional
We are not enrolling members into this file without their request/approval. I think it is perfectly understandable that if you want a position of authority in an OSS project, you will have to divulge your name.
Whether or not that name is persisted in the config file or GitHub history is another matter. It is understandable that consumers of the project should want to know the authorship and affiliations of contributors to the project, although this does not have to be considered a right.
I think we can test this when the time comes, but otherwise expect names in the files.
Other considerations:
Adding another ping on this issue since https://github.com/tinkerbell/proposals/pull/50 has been merged
Closing this now that we have CODEOWNERS in most repos
The Tinkerbell Governance document lists four roles
Maintainers are currently listed in this repository, but Members and Committers are not. @jacobweinstock has an open proposal for adding a section on inactivity, but it is currently manual to figure out who qualifies as inactive.
In order to avoid the appearance of any capriciousness or unfairly singling anyone out, I propose adding a machine-readable (probably YAML) file in this repo enumerating Members, Committers, and Maintainers that a script or periodic job can run to identify (and ideally notify) current community members of any pending role changes.
This file could also function as a place where new community members can identify who qualifies as a possible sponsor for them
To start this out, it could be a simple file
I'm happy to take a first crack at this, but I'm not clear on who qualifies as a Committer as there aren't any filled out
OWNERS
files in any GH repos, but GH org member is easy enough to figure out.CC @thebsdbox @tstromberg @mmlb