Skip to content

create Developer-specific onboarding issue #1063

Closed
@sydneywalcoff

Description

@sydneywalcoff

Dependency

Overview

Using the information gathered in #1064, we want to create a Developer-specific onboarding checklist.

Action Items

#1064 draft

Overview

As a new developer on the Expunge Assist team, fill in the following fields as you complete each onboarding item.

Action Items

  • assign yourself to this issue using the gear in the sidebar
  • replace role: missing label with role: development
  • add Issue to Expunge Assist Project Tracking using the gear in the sidebar
  • move to In Progress (active) column
  • add yourself to the slack channels
    • #expunge-assist-dev
    • #expunge-assist
    • #expunge-assist-design-content
  • add yourself to the Google Drive Team Roster
  • make a figma account (Figma.com)
  • reach out to the team leadership (lead or PM) to get Github, Google, and Figma access
  • attend your first dev meeting
    • Thursdays 6pm - short standup
    • if you are unable to make the dev meeting, reach out to the dev lead to work out a solution
  • read the Contributing.md
  • read the About Section of How To Create Issues to get an understanding of our how our issues are built
  • take your first issue
    • only have one issue in progress at a time. Once you have a PR open, you can take a new issue.
    • most of our issues are 1pt, but do occasionally get higher than that. Start small and work your way up
  • add an update to your issue
    • updates are required at least once a week
 1. Progress
2. Blockers
3. Availability
4. ETA
  • create your first Pull Request

Resources/Instructions

Stuff You Should Bookmark

Stuff You Just Need During Onboarding

Resources

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions