I propose we ensure every component in JIRA has a component lead, and we set it to the best expert of that component.
We considered assigning components to TCAMs in the past (see RFC-51), primarily because TCAMs could then catch issues with story points / PMCS etc, but I'd argue that TCAMs should be actively monitoring all activities that are happening in their area (RSS feed etc), so assigning components to TCAMs does not bring any extra value here.
The component list and their leads are here: https://jira.lsstcorp.org/plugins/servlet/project-config/DM/components
Based on discussion in the comments, this proposal now includes keeping the list OUTSIDE of JIRA.
Thanks to Gregory Dubois-Felsmann for reminding me about BaBar package coordinators and making me open this RFC. Gregory said:
BaBar "package coordinators" were meant to be, in general, the most knowledgable developer associated with a package - someone who could answer questions and make technical decisions about a package. I thought that was a good concept.
- is blocked by
DM-9880 Update LDM-294 as the new DM management plan
RFC-145 Always set Team field in jira
RFC-151 Turn OFF automatic story assignment in JIRA
- is triggering
DM-17440 Consolidate list of components in Jira DM project.
- To Do
DM-17439 Document all DM products
- relates to
RFC-51 JIRA Automatic Assignment to default to system T/CAM
- mentioned in
Once KT and Gabriele sort out the products/components yes I think Gabriele Comoretto [X] can take over this.
Gabriele Comoretto [X] can you create a triggered ticket for this RFC please?
Shipped or retired - we have a working approach. Components have been added as needed.
TCAMs can set the component leas as they wish. Also the ticket behavior can be set to default to blank or component lead.
Teamless tickets are picked up (by Tim) on Mondays and assigned.
this has means no tickets are left hanging which was the point of the RFC.
Wil O'Mullane who is responsible for associating triggered tickets for this RFC? Is that now Gabriele Comoretto [X]?