projects
projects copied to clipboard
coala
Create project for About-Code wrapper project
https://gitter.im/coala/aboutcode?at=5a84211a5cc187264539b970
The initial concept doesnt need to be very detailed, as others can add more details until applications close.
@jayvdb I can and will help on the mentoring side.
-
What would be your initial brain dump on this? a bear? on licenses? copyrights? packages?
-
What would be the "failure"/linting conditions or the fixes that could be applied?
-
FWIW, I had started some work on this https://github.com/nexB/scancode-toolkit/blob/c27627d1e76d4dc33efe05bfb51302a3f40a4585/src/scancode/plugin_espedexify.py This could be relevant on the fixes side.
-
On the linting side, https://github.com/nexB/scancode-toolkit/tree/214-license-policy is a plugin to apply some policy on the detected licenses and could be a base for linting
@pombredanne , we prefer to use command line options , which are filled from a config file .coafile which includes all rules for all linters.
This usually only covers the basic functionality of the linter. The goal is to make it easy for a project to start using a linter . When they want more advanced functionality, they will then need to use a linter specific config, and possibly run the linter directly.
The other important question is whether scancode can be run on a single file, or needs to be run on all files together. coala is better at the former, but can handle the latter also with more difficulty.
So we need to know what command line options are available to use on the command line for basic usage.
@jayvdb Is this still open for contributions? I am interested in taking it up as a GSoC project.
