1. Contributions to the vblade are welcome.
  2. In contributing, though, please stay true to the original simplicity
  3. of the software. Many open source projects suffer from the "creeping
  4. feature demon" phenomenon. If you think the vblade needs a great new
  5. feature, first seriously try to think of a way to accomplish your goal
  6. without adding to the vblade itself.
  7. Patches should be clean (to the point and easy to read) and should do
  8. one thing. Send multiple patches if necessary. Patches should be
  9. generated with "diff -uprN" if possible, and should be designed to be
  10. applied with "patch -p1".
  11. When possible, the best way to submit a patch is by sending it to the
  12. aoetools-discuss list. You can subscribe at the aoetools project web
  13. page on sourceforge.net.
  14. When you send your patch, here are some things to cover:
  15. * What version of the vblade did you use to generate the patch?
  16. (Hopefully it was the latest.)
  17. * What was your motivation for creating the patch? That is, what
  18. problem does it solve?
  19. * What testing did you perform to ensure that your patch did not
  20. introduce bugs and accomplished what you intended?