Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-150

Set JIRA component lead to the component best expert

    XMLWordPrintable

    Details

    • Type: RFC
    • Status: Implemented
    • Resolution: Done
    • Component/s: DM
    • Labels:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            tjenness Tim Jenness added a comment -

            Wil O'Mullane who is responsible for associating triggered tickets for this RFC? Is that now Gabriele Comoretto [X]?

            Show
            tjenness Tim Jenness added a comment - Wil O'Mullane who is responsible for associating triggered tickets for this RFC? Is that now Gabriele Comoretto [X] ?
            Hide
            womullan Wil O'Mullane added a comment -

            Once KT and Gabriele sort out the products/components yes I think Gabriele Comoretto [X] can take over this.

            Show
            womullan Wil O'Mullane added a comment - Once KT and Gabriele sort out the products/components yes I think Gabriele Comoretto [X] can take over this.
            Hide
            tjenness Tim Jenness added a comment -

            Gabriele Comoretto [X] can you create a triggered ticket for this RFC please?

            Show
            tjenness Tim Jenness added a comment - Gabriele Comoretto [X] can you create a triggered ticket for this RFC please?
            Hide
            gcomoretto Gabriele Comoretto [X] (Inactive) added a comment -

            DM-17439 and DM-17440 created.

            Show
            gcomoretto Gabriele Comoretto [X] (Inactive) added a comment - DM-17439 and DM-17440 created.
            Hide
            womullan Wil O'Mullane added a comment -

            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.

            Show
            womullan Wil O'Mullane added a comment - 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.

              People

              Assignee:
              womullan Wil O'Mullane
              Reporter:
              jbecla Jacek Becla
              Watchers:
              Gabriele Comoretto [X] (Inactive), Gregory Dubois-Felsmann, John Swinbank, Jonathan Sick, Kian-Tat Lim, Tim Jenness, Wil O'Mullane
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Planned End:

                  Jenkins

                  No builds found.