If you found a bug (which I'm sure there will be plenty), or if you want to add your own pet feature, then follow these steps:
- Fork the ebassi/graphene repo
- Fix bugs or add new features and push them to your clone
- Open a pull request
- Wait for me to give feedback on the pull request
- Celebrate when your code gets merged
That's pretty much it.
Please, respect the coding style when writing patches for Graphene. The coding style can be immediately gleaned from the existing code, but here is a short version:
- Indentation is made of spaces, and only spaces — no tabs
- Each indentation level is 2 spaces
- Curly braces for blocks go on a separate indentation level
- Except for functions
- Do not use curly braces for single-statement blocks
- When declaring or defining a function, arguments go on separate lines
- When calling a function never break a line between the function name and the opening parenthesis, and between the opening parenthesis and the first argument
- Leave a space between functions and parenthesis
A more comprehensive coding style document is available in the CODING STYLE file.