User story: As a team member who has a leadership role on a product, I want a way to identify myself as a "lead" while also describing my role.
Currently our expectation of the "role" value on any given team member is that "leads should be designated as 'lead'". My hypothesis after looking at several team's implementation of about.yml is that "lead" is more of a boolean value: Many teams seem to have different "leads" for different parts of the project. The EKIP project, for example, lists three people who might be "leads": The 18F product lead and two DOI Activation Team Co-Leads. In that case, "lead" also isn't a very descriptive marker for any of those three team members. Listing any of them simply as "lead" dilutes the work
In some cases we may want to list a non-18F team member who is working closely with the 18F team, for the MyUSCIS project, for example, we might want to list who the dev team lead is for a given product even if that person is at USCIS, USDS, or another agency.
If we make a third field "lead" and expect true or false and assume false by default, that might be a more robust way of identifying who the leader is on a given project.
User story: As a team member who has a leadership role on a product, I want a way to identify myself as a "lead" while also describing my role.
Currently our expectation of the "role" value on any given team member is that "leads should be designated as 'lead'". My hypothesis after looking at several team's implementation of about.yml is that "lead" is more of a boolean value: Many teams seem to have different "leads" for different parts of the project. The EKIP project, for example, lists three people who might be "leads": The 18F product lead and two DOI Activation Team Co-Leads. In that case, "lead" also isn't a very descriptive marker for any of those three team members. Listing any of them simply as "lead" dilutes the work
In some cases we may want to list a non-18F team member who is working closely with the 18F team, for the MyUSCIS project, for example, we might want to list who the dev team lead is for a given product even if that person is at USCIS, USDS, or another agency.
If we make a third field "lead" and expect
true
orfalse
and assumefalse
by default, that might be a more robust way of identifying who the leader is on a given project.