This project is read-only.

Ways to Contribute

If you would like to contribute, consider these options:

  • Submit an bug report (for an guide on submitting good bug reports, read Painless Bug Tracking).
  • Verify fixes for bugs.
  • Submit a code fix for a bug.
  • Submit a feature request.
  • Help answer questions in the forums.
  • Submit a unit test.
  • Tell others about the project.
  • Tell the developers how much you appreciate the product!

Contributing Code

Make sure you can build the code. You might also read these two good blogs posts on contributing code: Open Source Contribution Etiquette by Miguel de Icaza and Don’t “Push” Your Pull Requests by Ilya Grigorik.

Before submitting a feature or substantial code contribution please discuss it with the team and ensure it follows the product roadmap. Note that all code submissions will be reviewed and tested by the Virto Commerce Team, and only those that meet the standards will be merged into the source.

Then follow these steps:

  1. Decide what feature or bug fix you plan to take on and start a discussion with the title of the bug so we know someone is already working on it. e.g. "I'm going to fix issue 59: Something's Broken." If you're just starting out, pick something small to fix such as:
    • Add a missing unit test.
    • Fix an FxCop issue.
    • Try something small first and work your way up to larger issues.
  2. Create a fork of the project on github.
  3. Clone the fork you created in the previous step to your machine.
  4. Make the relevant changes in your local clone (potentially adding a unit test if this is a bug fix).
  5. Please only contribute code which you wrote or have the rights to contribute. If you do need to add 3rd party code please discuss it with us first.
  6. Commit your changes in your local clone. You may end up repeating steps 4-5 multiple times as you work. When you are finished and ready to have us accept your change, go to step 7.
  7. Pull from origin and merge your changes with the latest from origin (fix any merge conflicts you might have).
  8. If multiple local commits have been made, squash them into a single commit using git rebase -i.
  9. Push your changes up to your fork.
  10. Go to the source control tab and send a pull request. Make sure the summary contains relevant bug numbers and a good description of your changes.
  11. If you need to revise your code, then do so locally and update the review. Repeat until we approve the review.
  12. Wait for your review to be approved. We'll try to get to it as soon as possible. Once the review is approved, someone from the team will push your changes to the main source repository. Then you can delete your fork.

Last edited Dec 24, 2014 at 9:01 AM by Woland, version 6