Skip to content

Instantly share code, notes, and snippets.

@TalAter

TalAter/issue_template_missions.md

Created February 11, 2018 10:12
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save TalAter/838c4be0ba11180a565c5d5cfab972da to your computer and use it in GitHub Desktop.
Save TalAter/838c4be0ba11180a565c5d5cfab972da to your computer and use it in GitHub Desktop.
Download ZIP
Raw
issue_template_missions.md

Thank you for your help ❤️

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new non-profit foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

Missions

The DAV project you are looking at is Missions. Missions is the client facing side of the marketplace connecting DAV users looking to ship packages, with autonomous vehicles such as drones.

How you can help

The Issue

The settings reducer sets the same user_id for all users.

Generate a unique id for each user and make sure it is persisted in localstorage between sessions (https://github.com/DAVFoundation/missions/blob/master/src/store.js#L8)

You can find a method for generating a random user id in https://github.com/DAVFoundation/missioncontrol/blob/master/server/simulation/random.js

Contributing to Missions

  • Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
  • Comment in this issue that you would like to do it.
  • Open the Missions GitHub page and click the ★ Star and then ⑂ Fork buttons.
  • Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/missions.git
  • Make changes in the LICENSE file
  • Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
  • Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/missions) and create a pull request for your changes.
  • Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #5)
  • Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment