Developer 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 will request an LSST single sign-on account for you. This gives you access to:

• The internal project website, including travel requests: http://project.lsst.org
• Email (for AURA employees): https://mail.lsst.org/owa
• The JIRA project management app: http://jira.lsstcorp.org/
• The Confluence wiki: https://confluence.lsstcorp.org
• The DocuShare document archive: http://docushare.lsstcorp.org

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.

NCSA resources

You’ll also need account(s) for the LSST infrastructures hosted at NCSA:

• Development Servers (lsst-dev)
• MySQL Database (lsst-db)
• Nebula OpenStack

If you are missing any of these accounts, you can request one by sending the following to lsst-account _at_ ncsa.illinois.edu:

• First and last name
• Email
• Sponsoring LSST manager
• LSST-DM subteam or project

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 & Recommentations page for recommendations on setting up two-factor authentication and credential helpers for GitHub.
• Using Git Large File Storage (LFS) 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.

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 should be subscribed to these lists as soon as you get an LSST acccount:

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

DM calendars

DM maintains calendars of meetings and staff travel on Google. To get access, send your Google username to our admin in #dm-admin-support on Slack.

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.
5. Once you’re on Slack, send your Google username to #dm-admin-support to access DM calendars.

Checklist for T/CAMs

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. Add the new hire to the DM Team Google spreadsheet with time allocation information.
3. Ask your new hire for a profile photo and add it to https://confluence.lsstcorp.org/display/DM/The+Team.
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.

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 Weekly Digest editor and travel coordinator.
4. Provide Google calendar access to DM Meetings and DM Travel.

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