Skip to content

Latest commit

 

History

History
31 lines (22 loc) · 1.42 KB

communication.md

File metadata and controls

31 lines (22 loc) · 1.42 KB

Communication Guidelines

How to get help

  • When you run into a problem, and you need to get help from another developer, you must immediately provide complete information about the problem.
  • Provide the person with any error messages or terminal output
  • Provide the person with the complete steps to reproduce the problem on their own
  • If you are using a command line, copy and paste the text instead of taking a screenshot
  • The person you are asking for help should never have to solicit this information from you!
  • Use asciinema to demonstrate lengthy command line interactions with your peers

Communication Channels

Github

  • All issues and feature requests should be tracked in github. Wherever possible and appropriate, put conversation regarding our software projects in github. This will maximize transparency for our organization's work, as well as provide better tracking of the project's development.

Slack

  • The preferred communication channel for within Blue Robotics

Google Meeting Room

  • For meeting by voice

Email

  • Contact your coworkers regarding subjects relating to Blue Robotics via the @bluerobotics.com domain.

TeamViewer

  • For remote desktop with clients or coworkers
  • Contact Jacob about our business license

Mumble

  • The ardupilot developers have a weekly call on mumble