Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7675

Define policy about giving access to Confluence/JIRA to LSST collaborators

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Need to define policy about giving access to Confluence/JIRA to people closely collaborating with us (eg, collaborators at UK)

        Attachments

          Issue Links

            Activity

            jbecla Jacek Becla created issue -
            jbecla Jacek Becla made changes -
            Field Original Value New Value
            Epic Link DM-7654 [ 26850 ]
            Hide
            swinbank John Swinbank added a comment -

            Also HipChat/Slack.

            Show
            swinbank John Swinbank added a comment - Also HipChat/Slack.
            swinbank John Swinbank made changes -
            Assignee Jacek Becla [ jbecla ]
            gpdf Gregory Dubois-Felsmann made changes -
            Component/s Management [ 13500 ]
            tjenness Tim Jenness made changes -
            Assignee Jacek Becla [X] [ jbecla ] Wil O'Mullane [ womullan ]
            tjenness Tim Jenness made changes -
            Remote Link This issue links to "Page (Confluence)" [ 15322 ]
            Hide
            womullan Wil O'Mullane added a comment -

            We direct external community members to community.lsst.org and github for issues. Plus they can interact with DM science leads. We will update the guidelines to state this clearly.
            This would still allow us to provide SLACK/JIRA access to a limited number of people we interact with very frequently but it should be the exception not the rule.

            Show
            womullan Wil O'Mullane added a comment - We direct external community members to community.lsst.org and github for issues. Plus they can interact with DM science leads. We will update the guidelines to state this clearly. This would still allow us to provide SLACK/JIRA access to a limited number of people we interact with very frequently but it should be the exception not the rule.
            womullan Wil O'Mullane made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            mjuric Mario Juric made changes -
            Labels dm-sst
            swinbank John Swinbank made changes -
            Team DMLT / Management [ 11402 ] System Management [ 12217 ]
            Hide
            womullan Wil O'Mullane added a comment -

            John SwinbankHating to overload LDM0294 .. but its that the place to document this also ? Or is in the developer guidelines enough ? Seems like we need policy at a higher lever than developer.

            Show
            womullan Wil O'Mullane added a comment - John Swinbank Hating to overload LDM0294 .. but its that the place to document this also ? Or is in the developer guidelines enough ? Seems like we need policy at a higher lever than developer.
            swinbank John Swinbank made changes -
            Summary Define policy about giving access to Confluence/JIRA to LSST members Define policy about giving access to Confluence/JIRA to LSST collaborators
            Hide
            swinbank John Swinbank added a comment -

            In principle, I guess this ought to be at a higher level than a DM document — we're explicitly not talking about DM members here, but people outside the project altogether. The project as a whole ought to have a policy on this, not just us.

            However, that may be more trouble than it's worth, in which case I'd suggest maybe DMTN-020 would be a good place for this sort of administrative detail.

            Show
            swinbank John Swinbank added a comment - In principle, I guess this ought to be at a higher level than a DM document — we're explicitly not talking about DM members here, but people outside the project altogether. The project as a whole ought to have a policy on this, not just us. However, that may be more trouble than it's worth, in which case I'd suggest maybe DMTN-020 would be a good place for this sort of administrative detail.
            Hide
            womullan Wil O'Mullane added a comment -

            review ticket branch

            Show
            womullan Wil O'Mullane added a comment - review ticket branch
            womullan Wil O'Mullane made changes -
            Reviewers John Swinbank [ swinbank ]
            Status In Progress [ 3 ] In Review [ 10004 ]
            Hide
            swinbank John Swinbank added a comment -

            Text looks fine. I pushed some minor tweaks into u/swinbank/DM-7675 — I can force push to your branch if you want them.

            Show
            swinbank John Swinbank added a comment - Text looks fine. I pushed some minor tweaks into u/swinbank/ DM-7675 — I can force push to your branch if you want them.
            Hide
            swinbank John Swinbank added a comment -

            Force pushed per comment on GitHub & merged. Your work here is done!

            Show
            swinbank John Swinbank added a comment - Force pushed per comment on GitHub & merged. Your work here is done!
            swinbank John Swinbank made changes -
            Resolution Done [ 10000 ]
            Status In Review [ 10004 ] Done [ 10002 ]
            swinbank John Swinbank made changes -
            Component/s Management [ 13500 ]
            swinbank John Swinbank made changes -
            Risk Score 0

              People

              • Assignee:
                womullan Wil O'Mullane
                Reporter:
                jbecla Jacek Becla
                Reviewers:
                John Swinbank
                Watchers:
                Jacek Becla, John Swinbank, Mario Juric, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel