Contributing

Want to hack on Origin? Awesome!

Origin is an Open Source project and we welcome contributions of all sorts. There are many ways to help, from reporting issues, contributing code, and helping us improve our community.

We use a monorepo for almost all of our development – see Origin on GitHub.

You are most likely interested in these projects inside the monorepo:

Other repos of interest:

Discord

We work in public and our company Discord is open to all. If you have questions or need help getting started, our Discord #engineering channel is the absoulute best place to get assistance from our team of engineers and developers.

Weekly Engineering Call

We have an open weekly engineering call on Google Hangouts every Wednesday at 12:30 Pacific Time. Add to Calendar

Origin Engineering Call

Join the call here: https://meet.google.com/pws-cgyd-tqp

Everyone is welcome to join, even if you’re just lurking. All we ask is that you mute when not speaking to minimize background noise. All our meeting notes are public and can be reviewed here:

Dive Right In

If you’re ready to start hacking on Origin right now and you just need an issue to focus on, check out our open issues especially those tagged as a good first issue.

We use two week development sprints and you can see what we’re currently prioritizing on our Github project board.

Read our development process and community guidelines first and have fun!

Development Process

Getting your local environment running is easy with Origin Box. We recommend using this Docker container for any development or testing that involves running a local blockchain.

Our branching strategy is similar to GitFlow, but we do all of our development in the master branch and have a stable branch for code that has been released.

Your development flow should look like:

  1. Find an interesting issue and communicate! Please let the #engineering Discord channel know what you want to work on.
  2. Ping a core team member member on Discord and ask to be added to our contributors team. Otherwise, you’ll need to fork the relevant repository and push feature branches to your own fork.
  3. Add a comment to the issue or self-assign so we don’t have multiple contributors unintentionally working on the same task.
  4. Start with the master branch and check out a new feature branch unless you’re contributing to an existing feature.
  5. Follow the appropriate coding style and write some awesome code.
  6. Pull the latest commits from master and confirm that your code works with any other work that has been merged since you started.
  7. Push your branch to the upstream repository (i.e. https://github.com/OriginProtocol/[repo]) so that other contributors can easily work off of it if necessary.
  8. Please request a review in the PR by clicking on the gear icon next to “Reviewers” in the right column.

The master branche is locked so that only members of the core team are able to merge your pull requests. Pull requests that are peer reviewed by other trusted contributors will be fast-tracked and merged faster! Check in the #engineering Discord channel for appropriate reviewers.

Coding Style

We use a variety of programming languages in our repositories. When contributing, please follow existing coding conventions and refer to the CONTRIBUTING.md file in the repository, if one exists.

For JavaScript, we use NPM’s style, which is automatically enforced via prettier.

For Solidity, we use two space indents.

Troubleshooting a Development Environment

Protocol Design

When considering protocol or implementation design proposals, we are looking for:

Please note that protocol design is hard and meticulous work. You may need to review existing literature and think through generalized use cases.

Community Guidelines

We want to keep the Origin community awesome, growing and collaborative. We need your help to keep it that way. To help with this we’ve come up with some general guidelines for the community as a whole:

Reporting Issues

If you find bugs, mistakes or inconsistencies in the Origin project’s code or documents, please let us know by filing an issue at the appropriate issue tracker (we use multiple repositories).

Security Issues

The Origin Protocol and its implementations are still in early development, which means there may be problems with the protocol or in our implementations. We take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!

If you find a vulnerability please send your report privately to security@originprotocol.com or contact Josh Fraser via Keybase. Please DO NOT file a public issue.

If the issue is a protocol weakness or something not yet deployed, feel free to discuss it openly.

Community Improvement

Origin is just as much about community as it is about our technology.

We need constant help in improving our documentation, building new tools to interface with our platform, spreading the word to new users, helping new users getting setup and much more.

Please get in touch if you would like to help out. Our general channel on Discord is a great place to share ideas and volunteer to help.

Full Time Positions

Origin occasionally hires developers for part time or full time positions.

We have a strong preference for hiring people who have already started contributing to the project. If you want a full time position on our team, your best shot is to engage with our team and start contributing code. It is very unlikely that we would offer you a full time position on our engineering team unless you’ve had at least a few pull requests merged.

If you are interested, check out the Origin Protocol job listings. If you’d like to help in other ways, please propose your ideas in the Origin Discord.