- optimized makefile

- generate changelog in release
- added make help
- refactoring bin scripts
- linting + excluding old dockerfiles

Author: fabiocicerchia

.dockerignore

@@ -0,0 +1,2 @@
+*
+!/tpl

.github/workflows/linter.yml

@@ -23,3 +23,4 @@ jobs:
         env:
           VALIDATE_ALL_CODEBASE: true
           DOCKERFILE_HADOLINT_FILE_NAME: .hadolint.yml
+          FILTER_REGEX_EXCLUDE: nginx/(1.17.10|1.18.0|1.19.0|1.19.1|1.19.2)

CODE_OF_CONDUCT.md

@@ -14,22 +14,22 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 

CONTRIBUTING.md

@@ -6,18 +6,17 @@ the developers managing and developing this open source project. In return,
 they should reciprocate that respect in addressing your issue, assessing
 changes, and helping you finalize your pull requests.
 
-
 ## Using the issue tracker
 
 The issue tracker is the preferred channel for [bug reports](#bugs),
 [features requests](#features) and [submitting pull
 requests](#pull-requests), but please respect the following restrictions:
 
-* Please **do not** derail or troll issues. Keep the discussion on topic and
+- Please **do not** derail or troll issues. Keep the discussion on topic and
   respect the opinions of others.
 
-
 <a name="bugs"></a>
+
 ## Bug reports
 
 A bug is a _demonstrable problem_ that is caused by the code in the repository.
@@ -58,17 +57,17 @@ Example:
 > causing the bug, and potential solutions (and your opinions on their
 > merits).
 
-
 <a name="features"></a>
+
 ## Feature requests
 
 Feature requests are welcome. But take a moment to find out whether your idea
-fits with the scope and aims of the project. It's up to *you* to make a strong
+fits with the scope and aims of the project. It's up to _you_ to make a strong
 case to convince the project's developers of the merits of this feature. Please
 provide as much detail and context as possible.
 
-
 <a name="pull-requests"></a>
+
 ## Pull requests
 
 Good pull requests - patches, improvements, new features - are a fantastic
@@ -135,7 +134,7 @@ included in the project:
    ```
 
 8. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-    with a clear title and description.
+   with a clear title and description.
 
 9. If you are asked to amend your changes before they can be merged in, please
    use `git commit --amend` (or rebasing for multi-commit Pull Requests) and
@@ -145,8 +144,8 @@ included in the project:
 **IMPORTANT**: By submitting a patch, you agree to license your work under the
 same license as that used by the project.
 
-
 <a name="maintainers"></a>
+
 ## Maintainers
 
 If you have commit access, please follow this process for merging patches and cutting new releases.