Initial release

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,44 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Checklist**
+_Put an `x` in the boxes that apply_
+
+-   [ ] I have run the latest release.
+-   [ ] I have inspeced the status of docker containers.
+-   [ ] I have run the sanity check described in after-installation.md.
+-   [ ] I have inspected all error messages.
+-   [ ] I have inspected the log files in the /var/log/fiware directory.
+-   [ ] I have run the `make collect` command.
+-   [ ] I have provided a Github Star to this repository.
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+You need to show why you think this issue is a bug.
+
+**Your system environment**
+Run `make collect` in a directory where you ran the lets-fiware.sh script and paste the results here.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Server (please complete the following information):**
+- OS and OS version:
+- Docker version:
+- Docker Compose version:
+
+**Additional context**
+Add any other context about the problem here.
+To resolve this issue, you need to provide complete information about your scenario.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,38 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'backlog'
+assignees: ''
+
+---
+
+**Describe your feature request**
+
+Explain clearly and concisely whether your idea fits within the scope and purpose of this project.
+Make a strong case to convince yourself of the merits of this feature.
+
+**Describe the solution you'd like**
+
+A clear and concise description of what you want to happen.
+
+**Describe why you need this feature**
+
+- [ ] To approach a new use case.
+- [ ] To integrate a new Generic Enabler / othe open source component.
+- [ ] To improve or simplify an scenario.
+- [ ] Other reason (describe it)
+
+**Additional information**
+
+Add any other information, diagrams or screenshots about the feature request here.
+
+**Do you have the intention to implement the solution**
+
+- [ ] Yes, I have the knowledge to implement this new feature.
+- [ ] Yes, but I will need help.
+- [ ] No, I do not have the skills.
+
+**Other information**
+
+- [ ] I have provided a Github Star to this repository.

.github/pull_request_template.md

@@ -0,0 +1,34 @@
+## Proposed changes
+
+Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
+If it fixes a bug or resolves a feature request, be sure to link to that issue. Please send a pull request to
+the `v0.0.1-next` branch.
+
+## Types of changes
+
+What types of changes does your code introduce to the project: _Put an `x` in the boxes that apply_
+
+-   [ ] Bugfix (non-breaking change which fixes an issue)
+-   [ ] New feature (non-breaking change which adds functionality)
+-   [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+-   [ ] Update docker image version.
+-   [ ] Update only documentation, not any source code.
+
+## Checklist
+
+_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
+them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
+merging your code._
+
+-   [ ] I have read the [CONTRIBUTING](https://github.com/lets-fiware/FIWARE-Small-Bang/blob/main/CONTRIBUTING.md) doc
+-   [ ] I have signed the [CLA](https://github.com/lets-fiware/FIWARE-Small-Bang/blob/main/FIWARE-Small-Bang-individual-cla.pdf)
+-   [ ] I have updated the change log (CHANGELOG.md)
+-   [ ] I send this pull request to the `v0.0.1-next` branch.
+-   [ ] I have added tests that prove my fix is effective or that my feature works
+-   [ ] I have added necessary documentation (if appropriate)
+-   [ ] Any dependent changes have been merged and published in downstream modules
+
+## Further comments
+
+If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
+did and what alternatives you considered, etc...

.github/workflows/cla.yml

@@ -0,0 +1,33 @@
+name: "CLA Assistant"
+on:
+  issue_comment:
+    types: [created]
+  pull_request_target:
+    types: [opened,closed,synchronize]
+
+jobs:
+  CLAssistant:
+    runs-on: ubuntu-latest
+    steps:
+      - name: "CLA Assistant"
+        if: (github.event.comment.body == 'recheck' || github.event.comment.body == 'I have read the CLA Document and I hereby sign the CLA') || github.event_name == 'pull_request_target'
+        uses: cla-assistant/github-action@v2.1.1-beta
+        env: 
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          # the below token should have repo scope and must be manually added by you in the repository's secret
+          PERSONAL_ACCESS_TOKEN : ${{ secrets.PERSONAL_ACCESS_TOKEN }}
+        with: 
+          path-to-signatures: 'signatures/version1/cla.json'
+          path-to-document: 'https://github.com/lets-fiware/FIWARE-Small-Bang/blob/main/FIWARE-Small-Bang-individual-cla.pdf' # e.g. a CLA or a DCO document
+          # branch should not be protected
+          branch: 'main'
+          allowlist: fisuda,bot*
+          use-dco-flag: false #'Set this to true if you want to use a dco instead of a cla'
+
+         #below are the optional inputs - If the optional inputs are not given, then default values will be taken
+          #remote-organization-name: enter the remote organization name where the signatures should be stored (Default is storing the signatures in the same repository)   
+          #remote-repository-name:  enter the  remote repository name where the signatures should be stored (Default is storing the signatures in the same repository)
+          #create-file-commit-message: 'For example: Creating file for storing CLA Signatures'
+          #signed-commit-message: 'For example: $contributorName has signed the CLA in #$pullRequestNo'
+          #custom-notsigned-prcomment: 'pull request comment with Introductory message to ask new contributors to sign'
+          #custom-allsigned-prcomment: 'pull request comment when all contributors has signed, defaults to **CLA Assistant Lite bot** All Contributors have signed the CLA.'

.github/workflows/stale-issues.yml

@@ -0,0 +1,20 @@
+name: Close inactive issues
+on:
+  schedule:
+    - cron: "21 3 * * *"
+
+jobs:
+  close-issues:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v4
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          stale-issue-message: "This issue is stale because it has been open for 14 days with no activity."
+          close-issue-message: "This issue was closed because it has been inactive for 7 days since being marked as stale."
+          stale-issue-label: "stale"
+          exempt-issue-labels: 'bug,enhancement'
+          days-before-issue-stale: 14
+          days-before-issue-close: 7
+          days-before-pr-stale: -1
+          days-before-pr-close: -1

.gitignore

@@ -0,0 +1,26 @@
+data/
+sites-enable/
+config/
+.work/
+.env
+docker-compose.yml
+docker-idm.yml
+docker-cert.yml
+cert.sh
+.vscode/
+Makefile
+coverage/
+*.swp
+:wq
+node-red_users.txt
+password.txt
+.mock
+whitelist
+.install
+ngsi-go-config.json
+ngsi-go-token-cache.json
+ngsi-v*
+!extras/node-red/docker-compose.yml
+*.jar
+setup_ngsi_go.sh
+.install

.remarkrc

@@ -0,0 +1,9 @@
+{
+  "settings": {
+    "bullet": "-",
+    "paddedTable": true
+  },
+  "plugins": [
+    "remark-preset-lint-recommended"
+  ]
+}