The Second Step after OnBoarding

After a rigorous procedure of making accounts and gaining access to many other services of edX, there are some stuff with which you need to be familiarized. First of all, you need to double check if you have completed your onboarding correctly. You can see them all here Accounts Needed For a New Team Memberarchived.

And for the next part, I’d write down all the queries and new stuff I found post-onboarding.

• Slack Channels to join

  • There are tons of channels to join in order to cooperate with your team. I’d like to list some of them that can be necessary to join:

    1. escalations

    2. sustaining-mavericks

    3. sustaining-spartans

    4. edx

    5. sustaining-team

    6. mavs-notification

    7. edx_in_arbisoft

  • There are some other technical channels which I found interesting

    1. dev

    2. security-engineering

    3. site-reliability-engineering

    4. warroom

  • And finally there are some fun channels whose purpose is to take a break and interact with the people without any technical questions:

    1. diy

    2. food

    3. gaming

    4. memes

    5. plants

• How to triage an incoming issue?

  • S&E Automated Triage Rulesarchived this link helped me a lot when it comes to learning about how this process works.

  • Also, in order to learn the basics of how to triage and development is done, consult Triage & Development Jira Workflow Definitionsarchived

• How to make your first PR

  • When you’ve done some work on the ticket or found a fix for a bug etc, you can go and make a Pull Request on it.

  • Normally there are a number of things you need to add on the PR:

    • Link to the Jira Ticket

    • A brief description of the ticket which includes the details and the findings you’ve done through the investigation or development

    • A brief detail about the fix and how it will affect the repository

    • Ask for at least two reviewers to review your changes

      • Depending upon the PR, you can be asked to make a sandbox to test the behavior of your changes (Explained below)

    • Discuss and improve your code based on what a reviewer suggests you to do

    • Get two approvals from the reviewers

    • Evaluate that your integrations test have been passed for that PR

    • Squash and rebase your branch with the base branch

    • Once all of this is done, you can merge your first PR

• How to create a sandbox?

  • Sandbox is created so that we can reevaluate the behavior of our changes in a branch

  • You need to have access to the VPN for that

  • A very self-explanatory guide is already made on this https://openedx.atlassian.net/wiki/pages/createpage.action?spaceKey=SRE&title=Sandboxes

• Creating an IT Ticket

  • More often, one has to make an IT Ticket whenever there are some technical issues or when you need access to some edX services

  • Click here to make an IT Ticket. Fill out the required and related info into it and add your manager. Send the request after that.

  • An IT personnel will be on it’s way to help you out.

This is a continual document. I’d add more stuff into it off and on.