# Data&Search team Onboarding

We have a (slightly outdated) get-started doc for engineering: https://github.com/AdeptMind/wiki/blob/master/getting_started.md

### Set-up checklist:
1, AWS set up (Siwei Yang)
- make sure you can access AWS console, and ssh into AWS instance: https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#Instances:instanceState=running;search=52.26.46.162,34.221.120.152
- 52.26.46.162 has mongo DB. We can use it for catalog-processing for development purposes
- 34.221.120.152 has more dependencies and tools set up, with more resources. We can use it for development for Catalog-Platform

2, gihub set up (Siwei Yang or Jing He)
- https://github.com/AdeptMind/Catalog-Platform

3, jira set up (Jing He or Ryan Wilson)
- https://adeptmind.atlassian.net/secure/RapidBoard.jspa?rapidView=38

4, meetings set up (Tony Li)
- daily stand up meeting, where we talk about day-to-day updates/planns/blockers
- weekly planning meeting, where we plan our sprint
- weekly engineering meeting
- weekly happy hour session

5, set up gmail/slack etc... （Siwei Yang/Maxwell Roach）

6, more set ups can be done later:
- kubectl
- vpn
- boxes (servers in our office)

### Catalog Update Pipeline first task

In order to fulfil search, Adeptmind hosts data on its private Elasticsearch cluster. We have a catalog update pipeline to maintain those Elasticsearch indices.

As a first task, we try to ask new engineers to work on something related to the catalog update pipeline, this will involve some coding, some operational/infrastructure tasks.

Tasks:
- Nicholas Ren: https://adeptmind.atlassian.net/browse/DECATHLON-78