Information for developers

• General information for developers
  • Guidelines for contributing
  • Bugs
  • Developer communication
  • Dependencies
  • Running the tests
  • Writing New Tests
  • Catching errors with Pyflakes and Pylint
  • Checking test coverage
• Installing and configuring git
  • Installing git
  • Configuring git
• Contributing to PyClaw code development
  • Getting PyClaw from the development repository
  • Making a patch, for quick fixes
  • Making a fork, for substantial contributions
• Development workflow
  • Workflow summary
  • Consider deleting your master branch
  • Update the mirror of trunk
  • Make a new feature branch
  • The editing workflow
  • Ask for your changes to be reviewed or merged
  • Some other things you might want to do
• Maintainer workflow
  • Integrating changes
• Conventions for coding and documenting PyClaw
  • Code layout
  • Docstring conventions
  • Naming conventions
  • Order of the test cases instruction
  • Add regression test to check new piece of code
  • Add documentation when new code is added
  • Write Comments as You Code
  • Some fortran tips
• git resources
  • Tutorials and summaries
  • Advanced git workflow
  • Manual pages online