Merge pull request #233 from JdeRobot/revert-232-revert-231-dph/v2

DetectionMetrics v2

Author: dpascualhe

.github/workflows/main.yml

@@ -1,4 +1,10 @@
-.clang_complete
+.vscode
 
-# Py byte files
-*.py[cod]
+.mypy_cache
+__pycache__
+
+.venv
+dist
+poetry.lock
+
+local/*

.gitignore

@@ -2,7 +2,7 @@
 
 Thanks for your interest on contributing!
 
-This file contains a set of rules to contributing to the project and the 
+This file contains a set of rules to contributing to the project and the
 rest of the projects developed by JdeRobot.
 If you have any doubt about how to contribute contact one of the maintainers
 of the project. They will be pleased to tell you how you can contribute with your
@@ -19,7 +19,7 @@ Please report any unacceptable behavior to any of [the maintainers](#i-have-a-qu
 
 <a name="#prerequisites"></a>
 ## Prerequisites before contributing
-In order to contribute to JdeRobot projects, please read carefully the project README.md/webpage (if available) before 
+In order to contribute to JdeRobot projects, please read carefully the project README.md/webpage (if available) before
 starting contributing to understand the purpose of the project and where you can contribute.
 
 <a name="#how-to-contribute"></a>
@@ -40,22 +40,24 @@ The two following points are different depending on the permissions you have to
  write a good description of the changes made and refer to the issue solved to make things easier to the maintainers. Include any additional resource that would be interesting (references, screenshots...). Link the PR with the issue
 
 * **Testing and merging pull requests**
-Your pull request will be automatically tested by Travis CI. If any jobs have failed, you should fix them. 
+Your pull request will be automatically tested by Travis CI. If any jobs have failed, you should fix them.
 To rerun the automatic builds just push changes to your branch on GitHub. No need to close that pull request and open a new one!
 Once all the builders are "green", one of DetectionMetrics's developers will review your code. Reviewer could ask you to modify your pull request.
  Please provide timely response for reviewers (within weeks, not months), otherwise you submission could be postponed or even rejected.
- 
+
 * **[If you have write permission] Don't accept your own pull requests:** Wait for a project maintainer to accept the changes you made. They will probably comment the pull request with some feedback and will consider if it can be merge to the master branch.
  Be proactive and kind!
 
 <a name="#contact"></a>
 ## I have a question
 If you have any question related to how to contribute to the project or anything related to the organization,
-you can contact the main project maintainers sending them an email. Indicate the project you are talking about in the 
+you can contact the main project maintainers sending them an email. Indicate the project you are talking about in the
 subject of the email, please.
 
 Emails:
 
+<d.pascualhe@gmail.com>
+
 <sergiopaniegoblanco@gmail.com>
 
 <vinay0410sharma@gmail.com>