Onboarding Checklist

Welcome to Data Management. This page gives you an overview of the accounts you’ll have as a member of DM.

Note

Some things you can set up yourself, but many accounts require action by your manager. We’ve given them a handy Checklist for T/CAMs at the bottom.

LSST account

Your manager — or T/CAM, in LSST jargon — will request a single sign-on account for you. This gives you access to:

• The internal project website, including travel requests: http://project.lsst.org
• An e-mail address of the form username@lsst.org:
  • AURA employees will be able to access the AURA e-mail system at https://mail.lsst.org/owa
  • For non-AURA employees, this will forward to your institutional address (as registered with the Contacts Database)
• The Jira project management tool: http://jira.lsstcorp.org/
• The Confluence wiki: https://confluence.lsstcorp.org
• The DocuShare document archive: https://docushare.lsst.org
  • The IT Team have some further information about Docushare. Note in particular the comments on licensing.

You can always update your LSST password at https://lsstsspc.lsst.org/lsstsspc.

Finally, read over the LSST Project’s New Employee Onboarding page. That will get you up to speed with the LSST Project; the rest of this page is specific to DM.

Data Facility resources

You’ll also need an account for the LSST Data Facility services, hosted at NCSA, which include:

• Development Servers (lsst-dev)

This account will be automatically issued along with your LSST account.

GitHub and LSST organizations

If you don’t have one already, create an account on https://github.com.

Next, ask your T/CAM to add you to the lsst and lsst-dm GitHub organizations, along with any relevant team organizations (send your GitHub username to your T/CAM).

See also

• Git Configuration Standards & Recommendations page for recommendations on setting up two-factor authentication and credential helpers for GitHub.
• Using Git LFS (Large File Storage) for data repositories page for configuring Git LFS for DM.

Community.lsst.org

https://community.lsst.org is LSST’s public-facing discussion and support forum. Browse the forum-howto tag to learn how to use the platform.

Create an account, and let your T/CAM know your username to get access to internal discussion categories.

Slack

Slack is LSST’s real-time chat platform. It is used across the project and by external science collaborations. Please be aware of our guidance on Providing Support to the Community when interacting with the latter.

Ask your T/CAM for access to the ‘lsstc’ Slack team. You can access it online at https://lsstc.slack.com, and through Slack’s mobile and desktop apps. Slack’s online help is a great way to learn Slack’s features.

Channels set up specifically for Data Management related discussion have a ‘dm-’ prefix. Some important channels are:

• announce-everyone for project-wide announcements.
• lsst-travel for help with travel on project business.
• lsst-newchannels for notifications of new channels.
• software-dev for anything about writing software.
• dm for general DM discussion.
• dm-square for developer support services.
• dm-jenkins for automatic notifications from our Continuous Integration system.
• dm-tavern for “water cooler” type talk.
• dm-tea-time for more serious but still non-LSST conversation.
• dm-admin-support to contact DM’s administrator.

Your team may also have specific channels, and you can send private messages to individuals.

Google account for Hangouts

Many small meetings are conducted on Google Hangouts, which requires you to have an account with https://google.com. The meeting convener will pass around a Hangouts room URL to attendees.

Mailing lists

We don’t use mailing lists for conversations, but they’re still used for notifications about RFCs and conversations happening on https://community.lsst.org. You will automatically be be subscribed to these lists as soon as you get an LSST acccount:

• dm-devel
• dm-announce
• dm-staff (internal list)

Calendars

Important DM meetings are listed on this Google Calendar, to which you may wish to subscribe. More information is available about the various DM Calendars which are available.

Checklist for hires

In summary, here are the things you can do to get started:

1. Send a profile photo to your T/CAM for our team page.
2. Send your GitHub username to your T/CAM.
3. Send your https://community.lsst.org username to your T/CAM.
4. Follow emailed directions to set up your LSST account (including email), NCSA account, and Slack account.

Checklist for T/CAMs

Onboarding

Here’s what T/CAMs need to do to get their new hire started:

1. Fill out the Project onboarding form.
   • There’s no need to upload a photo to DocuShare, see the next step instead.
   • Under “User should belong to which Mailing Lists,” add dm-devel and dm-announce. IT automatically adds DM hires to dm-staff.
2. Ask your new hire for a profile photo and add it to https://confluence.lsstcorp.org/display/DM/The+Team.
3. Add the new hire to the DM Team Google spreadsheet with time allocation information.
4. Add the hire as a member of the ‘Data Management’ team in each these GitHub organizations:
   • github.com/lsst.
   • github.com/lsst-dm.
5. Add the hire as a member of these Community forum groups:
   • LSST.
   • LSSTDM.
6. Give the hire’s email address to a Slack administrator: @brianv0, @jonathansick, and @frossie, can make Slack accounts.

Your new hire should automatically be issued a Data Facility (NCSA) account along with their LSST account. However, if for some reason this doesn’t happen, send the following information to lsst-account _at_ ncsa.illinois.edu (and CC lsst-sysadmins _at_ lsst.org):

• First and last name of new hire
• Email
• Sponsoring LSST manager (ie, your name)
• Team within DM (one of DM Science, Architecture, Alert Production, Data Release Production, SUIT, Data Access and Database, Data Factility, Long Haul Networks, SQuaRE)

Departing

When a member of your staff leaves the project, they can end up in one of two states:

Offboarded

An offboarded member of staff loses access to all LSST services. They retain builder status if they have accrued enough time with the project. To transition a member of staff to this status, fill out the offboarding form and ensure they are set to 0% contribution in the team spreadsheet.

Friendly

“Friendly” individuals are no longer on the LSST payroll, but continue to collaborate with the project. As such, they retain access to services such as Jira, Confluence, etc. However, they will be removed from the dm-staff mailing list. Do not fill out an offboarding form for friendlies. Instead, simply set their contribution to 0% in the spreadsheet and send an e-mail to the DM Admin to let her know. Refer to Document-27073 for more information on friendly status.

In addition, the LSST Communications Team request that you notify the dm-staff mailing list of any departures from your team following the template in Document-26947.

Checklist for the DM Admin

Here’s what the awesome DM admin does:

1. After the onboarding form is received, send a welcome email to the hire with bullet points about the travel profile, Google calendar access, ContactDB info, and other miscellaneous project into. CC this to the supervisor.
2. Add a photo to the DM staff gallery, if not already done by the T/CAM.
3. Notify the LSST Digest editor and travel administrator.
4. Provide Google calendar access to DM Meetings and DM Travel/Vacation (for DMLT members only).

For details on LSST IT’s account onboarding procedures, see Account Management in the IT Support Confluence.