hackforla / hackforla/311-data

Onboard & Offboard: UI/UX Design

Open
#1,580 11 comments 0 reactions 1 assignee Assigned to @Joy-Truex View on GitHub
Complexity: Small Feature: GitHub Board/Onboarding role: UI/UX Design size: 0.25pt
Dominant language
JavaScript
Stars
73
Forks
74
PR merge metrics
No merged PRs in 30d

Description

### Overview
We need to have a checklist of items to do when a UI/UX Designer onboards and offboards so that the process can be consistent and fast.

### Date Updated
Created: 2023-09-13
Updated: 2024-10-23

### Action Items
- [ ] Check to see if the org template for this process has new steps in it, and if it does, update this issue and its template with content and add the last date you updated the template below
- [ ] Copy template to comment below
- [ ] Add name of person
- [ ] Check off as done

```
#### Onboard
- [ ] Slack channel membership
- [ ] `#311-data`
- [ ] `#311-data-uiux`
- [ ] Google Drive (could ask PM to do this)
- [ ] Add to drive as Contributor
- [ ] Add to Google calendar invites
- [ ] Wednesday All-Team meeting
- [ ] Roster (On Google Drive)
- [ ] Send link
- [ ] Team member adds themselves
- [ ] Check for Public
- [ ] GitHub (send PM new joiner's Github ID)
- [ ] Add to write team
- [ ] Add to read team
- [ ] Confirm that their name is on their Github
- [ ] Update team page on Wiki (Can only do after Roster)
- [How to activate-inactivate team members from roster and wiki](https://github.com/hackforla/311-data/wiki/How-to-activate-inactivate-team-members-from-roster-and-wiki)
- [ ] 311 Figma Page
- [ ] invite them by email (don't just share link)
- [ ] modify their permissions to `can edit`

Roster Required Fields

- Status: Active (required)
- Role: UX/UI Designer
- Dashboard: M (representing "member". Required)
- email: required
- number/texting: optional
- Slack Name: required
- SlackID: required (click your slack picture > ellipses > copy member id)
- everything else: optional


```

```
#### Offboard
- [ ] Remove from Google calendar invite
- You need to log into the 311-data@hackforla.org account in order to remove the person from all future events
- Choose to remove from "This and all following events"
- Send the following cancelation message:
- ``You have been removed from this event because you are listed as an inactive member of the 311 Data project team. If you have been removed by mistake, please reach out to a product manager.``
- [ ] Wednesday All-Team meeting (ad-hoc)
- [ ] Thursday PM meeting
- [ ] Google Drive Permissions
- [ ] demote access from Contributor to Viewer in 311 Data folder
- [ ] Roster
- [ ] mark as inactive
- [ ] GitHub
- [ ] demote member to read only team and remove from write team
- [ ] Check their Assignment status on the Issue tab, to make sure they are no longer assigned to any issues)
- [ ] Update team page on WIKI
- [How to activate-inactivate team members from roster and wiki]

```
### Resources/Instructions

* [1password.com](https://1password.com/)
* [Google Drive Link](https://drive.google.com/drive/folders/0AK9EyXeY81U5Uk9PVA)
* [311 Data Team Roster](https://docs.google.com/spreadsheets/d/1OsLDl7Ciwj7WjtzbgDz38g4kpOMNlUhdjlgzQxtQTvM/edit?usp=drive_link)
* Check public and 2FA at [people page](https://github.com/orgs/hackforla/people)
* [GitHub Team URL](https://github.com/hackforla/internship)
- [base (read)](https://github.com/orgs/hackforla/teams/311-data)
- [write](https://github.com/orgs/hackforla/teams/311-data-write)
* Shortcut for adding a profile to the desktop: chrome://settings/manageProfile
* WIKI: https://github.com/hackforla/311-data/wiki
* Figma [311 Data Figma](https://www.figma.com/files/team/1039983981189012111/311-data?fuid=604439038560392673)
* [Forward emails to team members](https://github.com/hackforla/product-management/wiki/Forward-emails-to-team-members)
* [311-Data Issue tab](https://github.com/hackforla/311-data/issues)
* [311-Data Team Meeting Agenda](https://github.com/hackforla/311-data/issues/1545)
* [311-Data PM Meeting Agenda](https://github.com/hackforla/311-data/issues/1546)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.