Skip to content
Snippets Groups Projects
Commit afc0f55b authored by Chase Southard's avatar Chase Southard :cyclone: Committed by James Lopez
Browse files

Remove references to LicenseDot from the onboarding issue templates

parent e44f29f5
No related branches found
No related tags found
1 merge request!44Remove references to LicenseDot from the onboarding issue templates
......@@ -15,7 +15,7 @@ This issue is meant to guide you over the first few days in the role. Please rea
- [#s_growth_engineering](https://gitlab.slack.com/archives/CNLHTE457) - Growth section engineering discussions
- [Relevant keeping yourself informed channels](https://about.gitlab.com/handbook/marketing/strategic-marketing/getting-started/communication/#slack-channels)
1. [ ] :wave: Your [onboarding buddy](#onboarding-buddy) will be _Onboarding buddy_. Please reach out for help installing the apps or for anything technical
1. [ ] Setup call with _Onboarding buddy_ to discuss key points about Customer/License application.
1. [ ] Setup call with _Onboarding buddy_ to discuss key points about Customer application.
1. [ ] :calendar: Meetings: [Subscribe to the Fulfillment calendar](https://calendar.google.com/calendar/embed?src=gitlab.com_7199q584haas4tgeuk9qnd48nc%40group.calendar.google.com&ctz=Europe%2FMadrid) by clicking on the :heavy_plus_sign: at the bottom right of that page. There's a weekly social with PMs and other counterparts (we chat about random things and how are things outside of GitLab). The rest are 1:1s and similar.
1. [ ] :books: Check out the [direction](https://about.gitlab.com/direction/fulfillment/) of Fulfillment
1. [ ] :tools: Read about how we work in [Fulfillment](https://about.gitlab.com/handbook/engineering/development/fulfillment/#how-we-work)
......@@ -28,13 +28,11 @@ This issue is meant to guide you over the first few days in the role. Please rea
- [Fulfillment Frontend Engineer](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/blob/master/.gitlab/issue_templates/role_baseline_access_request_tasks/department_development/role_frontend_engineer_fulfillment.md)
1. [ ] :computer: Download and install:
1. [ ] [CustomersDot](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/doc/installation_steps.md)
1. [ ] [LicenseDot](https://gitlab.com/gitlab-org/license-gitlab-com/#setup)
1. [ ] :books: Read the [CustomersDot README](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/README.md) and [LicenseDot README](https://gitlab.com/gitlab-org/license-gitlab-com/-/blob/master/README.md)
1. [ ] :books: Read the [CustomersDot README](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/README.md)
1. [ ] :books: Read up on the release process for [GitLab.com (SaaS)](https://about.gitlab.com/handbook/engineering/releases/#gitlabcom-releases-1) and [GitLab self-managed](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2)
1. [ ] :books: Read up on the release process for [CustomersDot](https://about.gitlab.com/handbook/engineering/development/fulfillment/#customersdot)
1. [ ] :books: Read up on the release process for [LicenseDot](https://gitlab.com/gitlab-org/license-gitlab-com/#deployment)
1. [ ] :books: Complete the required [reliability training](https://gitlab.edcast.com/pathways/development-department-learning-and-development-reliabilit/cards/8343423)
1. [ ] :coffee: Have some coffee chats with at least [ 2 team members from each of the 3 teams](https://about.gitlab.com/handbook/engineering/development/fulfillment/#want-to-know-more-about-us)
1. [ ] :coffee: Have some coffee chats with at least [2 team members from each of the 3 teams](https://about.gitlab.com/handbook/engineering/development/fulfillment/#want-to-know-more-about-us)
- Purchase:
1. [ ] Coffee Chat with ___
1. [ ] Coffee Chat with ___
......@@ -50,7 +48,7 @@ This issue is meant to guide you over the first few days in the role. Please rea
1. From the main dropdown (where you select to see `Your Events`, `Who's Out`, etc) select Settings > Calendar Sync
1. Click on `Add Calendar` button and paste the Fulfillment calendar ID
1. Submit it and the Fulfillment calendar ID should appear in the `Additional calendars to include?` section
1. [ ] Add yourself as a reviewer for customers and license apps - [See an example](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/87129).
1. [ ] Add yourself as a reviewer for customers app - [See an example](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/87129).
1. [ ] Go to [Sentry Team Settings page](https://sentry.gitlab.net/settings/gitlab/teams/) and join `#gitlab-internal` Sentry team to gain access to `customersgitlabcom` and `customersstggitlabcom`. To access Sentry Team Settings page you need access to dev.gitlab.org which is part of [role based entitlements](https://gitlab.com/gitlab-com/team-member-epics/access-requests/-/blob/master/.gitlab/issue_templates/role_baseline_access_request_tasks/department_development/role_frontend_engineer.md) for engineering. The issue to give access rights was already created by the bot. Check it out and wait till you get access before proceeding with this task.
1. [ ] Ready to pick something to work on? During your first weeks, [you can pick anything that is a low-hanging fruit from the board](https://gitlab.com/groups/gitlab-org/-/boards/1164943?label_name[]=%F0%9F%8D%8E&label_name[]=backend&label_name[]=devops%3A%3Afulfillment). Make sure you assign yourself to the issue, apply the [right workflow labels](https://about.gitlab.com/handbook/engineering/development/fulfillment/#organizing-the-work) and the current milestone. Ping your onboarding buddy or your manager for any help.
1. [ ] Please review [this onboarding issue](https://gitlab.com/gitlab-org/fulfillment-meta/-/blob/master/.gitlab/issue_templates/onboarding.md) and update the template with some improvements as you see fit to make it easier for the next newbie!
......@@ -72,8 +70,7 @@ This issue is meant to guide you over the first few days in the role. Please rea
1. [ ] Invite team member to #fulfillment-social Slack channel
1. [ ] Provide help as an admin to get Zuora setup during Installation
1. [ ] Key points to discuss in follow up
1. [ ] Customer and License application Database & Integration (orders, customers, etc)
1. [ ] Use of License application
1. [ ] Customer application Database & Integration (orders, customers, etc)
1. [ ] Zuora Subscriptions & Callbacks
1. [ ] Amendment Service
1. [ ] Salesforce use and its integration with application
......
......@@ -19,7 +19,7 @@ This issue is meant to guide new UX members as they get familiar with the role.
- [ ] Review and bookmark [workflow documentation](https://www.figma.com/file/DCq7K8Srsv79tbH1yRkGbl/Document-user-flows-%5Bgitlab-org%2F-%2Fepics%2F3603%5D?node-id=1%3A2) that the UX team creates and maintains
## Setting up your environment
- [ ] :computer: Download and install [CustomersDot](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/doc/installation_steps.md) and [LicenseDot](https://gitlab.com/gitlab-org/license-gitlab-com/#setup). Both installation processes can be a little complicated, please feel free to reach out to someone in the `#s_fulfillment` Slack channel for help at any time.
- [ ] :computer: Download and install [CustomersDot](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/staging/doc/installation_steps.md). The installation processes can be a little complicated, please feel free to reach out to someone in the `#s_fulfillment` Slack channel for help at any time.
- [ ] Ask for a Zuora admin in the `#s_fulfillment` Slack channel to set up your Zuora sandbox account.
## Social
......@@ -30,13 +30,13 @@ This issue is meant to guide new UX members as they get familiar with the role.
- [ ] Create a new issue in this project and name it something like "UX Walkthrough of Fulfillment Flows". Complete the following user tasks in GitLab SaaS as if you are a user and jot down your thoughts and ideas about how you think we can improve. Remember this is the only time you'll do these tasks with the eyes of a new user! Your onboarding buddy can answer questions about testing in production.
- [ ] Create gitlab.com user by signing up for a new account, create a group/project and start a trial
- [ ] Create another group and make a purchase
- [ ] Paid group, add users, upgrade bronze to silver
- [ ] Set your paid account to auto-renew
- [ ] Paid group, add users, upgrade bronze to silver
- [ ] Set your paid account to auto-renew
- [ ] Manually renew and change the number of users
- [ ] Review your findings with your PM and other designers on the team. Create new issues for anything you discovered that is not already known. This task will take some time, but at the end of it you will be familiar with the area of the product we work on, as well as the roadmap, and known and unknown UX problems to solve.
- [ ] Pick one of the tasks to do in your local environment so you can get familiar with how this works.
## Start your first issues
## Start your first issues
- [ ] Ready to work on something? During your first weeks, your PM will select a few issues for you to work on that aren't too complex so that you can learn the user flows and how everything works together. Make sure you assign yourself to the issue, apply the [right workflow labels](https://about.gitlab.com/handbook/engineering/development/fulfillment/#organizing-the-work) and the current milestone. Ping your onboarding buddy or your manager for any help.
- [ ] Please review this onboarding issue and update the template with some improvements as you see fit to make it easier for the next newbie!
......@@ -49,10 +49,10 @@ This issue is meant to guide new UX members as they get familiar with the role.
## Manager
1. [ ] Add team member [to the Fulfillment calendar](https://calendar.google.com/calendar/embed?src=gitlab.com_7199q584haas4tgeuk9qnd48nc%40group.calendar.google.com&ctz=Europe%2FMadrid)
1. [ ] Add team member to the retrospective (update [membership](https://gitlab.com/gl-retrospectives/fulfillment) and [config file](https://gitlab.com/gitlab-org/async-retrospectives/-/blob/master/teams.yml)) -
1. [ ] Add team member to the retrospective (update [membership](https://gitlab.com/gl-retrospectives/fulfillment) and [config file](https://gitlab.com/gitlab-org/async-retrospectives/-/blob/master/teams.yml)) -
1. [ ] Add team member to the daily [Geekbot](https://geekbot.com/dashboard/standup/33240/manage/members) updates
1. [ ] Set up 1:1s with the new team member
1. [ ] Update team page and product category page with the right team and manager
1. [ ] Update team page and product category page with the right team and manager
1. [ ] Request a manager update in BambooHR
1. [ ] Add team member to `@fulfillment-group` on GitLab.com
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment