kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Reformat Technical Lead expectations 

We now split up the huge sentence into a list of bullet points under the
headline of the expectations of technical leads.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
This commit is contained in:
Sascha Grunert 2020-11-04 15:11:58 +01:00
parent 95a2849624
commit c7662b13c0
No known key found for this signature in database
GPG Key ID: 8CE029DD1A866E52
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
contributors/chairs-and-techleads/technical-lead.md
View File

@ -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