Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Start on your RChain coop Membership.
  2. Read Getting Plugged In
  3. Update your information on /wiki/spaces/DOC/pages/65943.
  4. Set up your GitHub account with your primary email that you will use for the project.
  5. Send an email with your Github username to Michael Stay (Unlicensed) to add you as a collaborator to the RChain Github.
  6. Confirm your GitHub account also registers you in Travis (continuous integration: unit testing tool) to assure your builds in GitHub don't silently fail.
  7. Request access to the RChain GitLab (Kelly Foster fix this!)
  8. Set up your account for the RChain Atlassian tools: Confluence (wiki) and Jira (ticketing system)
  9. Add your public SSH key to the development team key directory
  10. All commits must be signed using GnuPG (GPG). Use How to sign commits to rchain/rchain to add your key to your GitHub account, and prepare to sign your commits.
  11. Schedule a 30-minute meeting with Medha Kelly for day 5 of this week. The agenda will be to add work items to your sprint board for work starting next week.

...

  1. Learn about expectations and requirements for doing technical interviews.
  2. Schedule a 30-minute meeting with Tysha Moore to with Kelly to discuss technical interviews before the end of this week. This is your opportunity to ask questions about expectations and process.
  3. By the end of the day, be familiar with the project structure, status of the project, the sprint process, and the current backlog.
    1. Project structure, roadmap, and milestones
    2. Sprint Process
    3. Review the sprintbacklogs: CORE (RNode and RSpace teams), RHOLANG (Rholang team), and ROSCALA (VM team)
  4. Get started with your on-boarding learning path. Use the self-assessment and content on the Reading List

...

Theme - plan and prepare for work next week

  1. Meet with Medha Kelly to make a plan for your work next week.
  2. Update your watches in the wiki based on your team assignment: ROS, RHOL, DOC or CORE space.  
  3. Review the Sprint Process and make sure your planned work is complete with story points.
  4. Review release plans, specifications, and code related to your work planned for next week.