-
```
Rewrite code and comments to adapt Python Conventions according to PEB 8:
Code: http://www.python.org/dev/peps/pep-0008/
DOC-style: http://www.python.org/dev/peps/pep-0257/
```
Original issue rep…
-
It would be nice to have a CONTRIBUTING.md document to define the process for contributing new changes to this project.
Some things that we could document include:
- bash coding standards. Whet…
-
```
Make sure all code is PEP 8 compatible and passes all lint tests.
```
Original issue reported on code.google.com by `ricardok...@gmail.com` on 15 Jun 2009 at 11:14
-
Issue placeholder to enforce a coding standard throughout to project.
Also add proper contribution guidelines for Pull Requests to the Readme and/or repository.
-
- fonts.scss should be remanded to variables.scss since it contains color variables, font variables.
- Variables.scss should be imported only once and not in every sass file. Try to find a way in whi…
-
The plugin code should follow WordPress coding standards.
-
I think the library should follow PSR2 coding standards. I've added tests to reflect the current coding standards based of PSR2 standards - and added automatic tests in TravisCI to see whether we adhe…
-
Raising the issue because it is likely to have an impact on file structure.
Both the WordPress coding standard and the PSR require one class per file which is not how the code is structured right n…
-
Something I've often seen teams neglect but is important for long-term maintenance and ease of collaboration is standardizing on coding and style standards, like https://google.github.io/styleguide/sh…
-
Review and then integrate https://github.com/mrmark/joule-plugincheck as a new command, like `moodle-plugin-ci codereview`
The project should be moved into `moodlerooms` Github account and should be …