diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2020-11-05 00:34:53 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-05 00:34:53 -0800 |
| commit | 46f114f1481fec20b08daef0c6e0923c164d5afd (patch) | |
| tree | c439177c92d6d02988065e82b760cdad18f915d7 | |
| parent | 7952a8c88689e9caeb3dbdc7fcfb3ea7eeaa74ec (diff) | |
| parent | c7662b13c0583ee5018e8b07f009c577b818597d (diff) | |
Merge pull request #5295 from saschagrunert/tl-expectations
Reformat Technical Lead expectations
| -rw-r--r-- | contributors/chairs-and-techleads/technical-lead.md | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/contributors/chairs-and-techleads/technical-lead.md b/contributors/chairs-and-techleads/technical-lead.md index e66f98a1..94bc42bc 100644 --- a/contributors/chairs-and-techleads/technical-lead.md +++ b/contributors/chairs-and-techleads/technical-lead.md @@ -28,10 +28,14 @@ internal to the SIG and, more significantly, external to the entire Kubernetes project. Before being able to align any technical direction, it is necessary to establish a technical vision within the SIG. The technical vision should be continuously updated and turned into reality, whereas larger features of the -vision can be outlined in dedicated roadmaps. This means Technical Leads have to -be involved in the source code base of the SIG to be able to take the right -decisions, identify risk and maintain a high level of trust with other members -of the SIG. +vision can be outlined in dedicated roadmaps. + +Expectations of Technical Leads are: + +- They're involved in the source code base of the SIG to be able to take the + right decisions. +- They actively identify risk and maintain a high level of trust with other + members of the SIG. Technical Leads have the responsibility to track the technical quality of the deliverables of the team if a roadmap exists. They are volunteering to provide |