Naming, installation, documentation, tests, improvements

[valeriocos]

The work done so far it's really good. However, the repo (which is a PoC ATM) could evolve to a mature tool. In this context, it may be worth improving:

• naming: script.py and Maintenance tools for GrimoireLab are too vague. It would be better to look for more helpful/precise names (to let the user understand what the tool does).
• installation: does it make sense to provide a setup.py to install the tool?
• documentation: It would be great to add a complete example including how the tool is executed (already there), and what to do next with the output (e.g., git commit)
• tests: although the tool is simple, it would be good to add some tests (and maybe coveralls and travis badges).
• improvements: do you think it's possible to automate the use of the output of this tool? For instance, does the tool could automatically open a pull request in a target repository? How difficult could be to include the logic in a GitHub app, thus a bot could be registered to an organization to check that the copyright and authors correctly listed in the repo files?

[vchrombie]

Hi @valeriocos

Thank you for all your valuable suggestions. I would surely work on it to make it into a good tool.