give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "After some work (particularly DM-8441 from SQuaRE and the DM Admin, and commit [e4de50d|https://github.com/lsst-dm/dm_dev_guide/commit/e4de50d85cf7bd355aaf2646cfc646f491dd968b] from NCSA), it seems that we aren't converging as a project on what happens in onboarding. I think the root of the issue is that there hasn't been sufficient communication between the key stakeholders. The purpose of this ticket is to:    # Host an initial discussion between all the stakeholders in the implementation of DM onboarding, namely T/CAMs, the DM admin, Project IT, and NCSA. The aim of this discussion is to eliminate all ambiguities in the expectations and responsibilities of each stakeholder in the onboarding process. I'm explicitly diverting this discussion from email because I think we need a permanent and citable record to sustain a multilateral understanding.  # Capture that discussion in a final resolution to the (new hire-oriented) [onboarding process described in the Developer Guide|https://developer.lsst.io/getting-started/onboarding.html#].  # Serve as a reference for other JIRA tickets that implement work beyond new hire-oriented documentation.    ----    To start the discussion, here are issues with onboarding that I've observed from recent changes to the DM onboarding page, and in other discussions.      h3. NCSA accounts (lsst-dev, lsst-db, Nebula).    My understanding while researching DM-8441 was that the [Project onboarding form|https://project.lsst.org/onboarding/form] triggered coordination between Project IT and NCSA to automatically provision a lsst-dev account for DM hires (and that this was a new process).    The [Project IT account management page|https://confluence.lsstcorp.org/display/IT/Account+Management] confirms this in the documented process for giving a hire LSST credentials after the onboarding form is submitted:    bq. DM Users: In the email supplying their new user with credentials, direct them to The Team and add to <EMAIL> (hidden list). Also notify <EMAIL> of DM hires. Point new user to https://lsstc.slack.com/ for Slack account.    Commit  [e4de50d|https://github.com/lsst-dm/dm_dev_guide/commit/e4de50d85cf7bd355aaf2646cfc646f491dd968b]), from the NCSA perspective, contradicts this, effectively re-asserting that it is the *responsibility of the new hire* to email lsst-account@ncsa asking for credentials.    What is the actual process here?    If the Project IT instructions are correct, then we shouldn't keep the NCSA version of the new hire instructions that now cause both the new hire and project IT to duplicate effort in getting NCSA credentials.    If the point of mentioning the lsst-account@ncsa email for obtaining credentials on the onboarding page is to help existing staff who do not yet have NCSA accounts, I think it'd be good to have:    - A sentence at the top of the Developing Infrastructure pages giving this email address where they can obtain credentials and other assistance. Or,  - Change the language in [the section on NCSA infrastructure in the Developer Guide|https://developer.lsst.io/getting-started/onboarding.html#ncsa-resources] to say that credentials are being created for you; but that you can email that address if there are problems.      h3. Coordination between LSST IT and NCSA on usernames    It seems that there's disagreement as to whether this process actually exists. I think this further suggests that we'd benefit from a better documented internal workflow between Project onboarding and NCSA onboarding.      h3. DocuShare account creation    It seems that DocuShare accounts are not automatically given to LSST DM staff. If this is the case, then we should change the [LSST Account|https://developer.lsst.io/getting-started/onboarding.html#lsst-account] section to break out DocuShare from the list of core Project platforms, stating that you'll get an account if applicable. Possibly this should be a call that the T/CAM makes while going through [their checklist|https://developer.lsst.io/getting-started/onboarding.html#checklist-for-t-cams]. Better yet, there could be a checkbox on the Project on-boarding form that indicate whether the hire needs a DocuShare account or not.    h3. DM calendars    The current instructions for new hires say:    bq. send your Google username to #dm-admin-support to access DM calendars.    I think a better instruction is to point them to https://project.lsst.org/content/dm-team-calendar and indicate that they can add the DM calendar from there to their own Google calendar.      ----      Overall, I would advocate that the internal onboarding workflows reduce the burden on the new hire, and be more rigorously triggered by the submission of the Project onboarding form. Not only can NCSA onboarding be streamlined, but we should also have a process where submission of the onboarding form triggers a Slack invite.    ----    There is also the issue of catching up new hires that haven't been properly onboarded. (Don't have an lsst-db credential, for example). My recommendation is each account provider should compare their account list to the DM staff roster and initiate the account creation process for staff that are lacking an account. I think an active approach to correcting onboarding issues is better than a passive one."
Answer: 596786.0