Add governance and code of conduct - #79
Conversation
a86dbaf to
48a225a
Compare
| @@ -0,0 +1,85 @@ | |||
| # Contributor Covenant 3.0 Code of Conduct | |||
|
|
|||
| This Code of Conduct applies to participation in the go/gpuallocator project and community. | |||
There was a problem hiding this comment.
updated to go-gpuallocator
| @@ -0,0 +1,78 @@ | |||
| # Governance for go/gpuallocator | |||
There was a problem hiding this comment.
updated to go-gpuallocator
| implementation work begins. A change is significant if it involves: | ||
|
|
||
| - Architectural changes | ||
| - Major new features or subsystems |
There was a problem hiding this comment.
Do we want it just for major new features/subsytems? In gpu-operator repo we say New features or subsystems
There was a problem hiding this comment.
Yes we were discussing earlier and will say Major new features or subsystems here for clarity. In the previous section we explicitly list "minor features" as routine.
There was a problem hiding this comment.
Sounds good. In that case, we'd also need to update the gpu-operator repo, right? Not a blocker for this PR, though.
Signed-off-by: Arjun <[email protected]>
| implementation work begins. A change is significant if it involves: | ||
|
|
||
| - Architectural changes | ||
| - Major new features or subsystems |
There was a problem hiding this comment.
Sounds good. In that case, we'd also need to update the gpu-operator repo, right? Not a blocker for this PR, though.
2 participants
No description provided.