Add documentation on meeting best practices. #61
Conversation
This adds some best-practices around holding meetings, as discussed in the governance meeting.
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
plz review @vdemeester @dlorenc |
tekton-robot
added
the
size/S
|
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
tekton-robot
added
the
approved
* New project logos and brand guidelines Closes tektoncd#61 Closes tektoncd#67 Signed-off-by: Tracy Miranda <[email protected]> * Add subproject icon logos Signed-off-by: Tracy Miranda <[email protected]>
This adds some best-practices around holding meetings, as discussed
in the governance meeting.
This is #43 rebased - i have somehow blanked out how to push directly to the contributor's branch but this seems fine so 🤷♀️