Fixes #197

Separate the issue template in two parts, one for observable issues, and the other for explored websites. We will see how it goes ...

Author: Riduidel

.github/ISSUE_TEMPLATE/BUG_REPORT.yaml

@@ -0,0 +1,32 @@
+name: Bug Report
+description: File a bug report.
+title: "🐞: "
+labels: ["type:bug", "state:pending", "priority:now"]
+assignees:
+  - Riduidel
+type: bug
+body:
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: How do you trigger this bug? Please walk us through it step by step.
+      placeholder: |
+        1.
+        2.
+    validations:
+      required: true
+  - type: textarea
+    id: what-did-you-expect
+    attributes:
+      label: What did you expect?
+      description: Provide all the details about what you were expecting
+      placeholder: Tell us what you see!
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell

.github/ISSUE_TEMPLATE/INDICATOR_SOURCE.yaml

@@ -0,0 +1,76 @@
+name: New indicator source
+description: Provides details about a potential indicator data source
+title: "🐞: "
+labels: ["type: feature", "state: pending", "priority: 2day"]
+assignees:
+  - Riduidel
+type: bug
+body:
+- type: input
+  id: source_website
+  attributes:
+    label: What is the source website url?
+    description: "Give the url of the indicator source website"
+    placeholder: "https://linkedin.com, https://youtube.com"
+  validations:
+    required: true
+- type: checkboxes
+  id: source_website_has_api
+  attributes:
+    label: Do the source website provides a way to get data ?
+    options:
+      - label: No (this implies scraping)
+      - label: Yes, through HTTP REST API
+      - label: Yes, through HTTP GraphQL API
+      - label: Yes, through Google BigQuery dataset (this will be costly)
+      - label: Yes, through a data dump (sqlite included)
+  validations:
+    required: true
+- type: textarea
+  id: source_website_documentation
+  attributes:
+    label: Where is access to source website documented?
+    description: "Give us all the good ways to access the source website data"
+    value: |
+      Website api access is documented in []
+
+      The following websites provide examples to data access
+        * 
+        * 
+
+      There are examples using specifically Java code (or Java client API) in
+        * 
+        * 
+
+  validations:
+    required: true
+- type: checkboxes
+  id: supposed_indicators_mapping_ease
+  attributes:
+    label: Will it be easy to map indicators to technologies?
+    description: You may select more than one.
+    options:
+      - label: Yes, website provides an api mapping to "known" technologies names
+      - label: Yes, website uses repository urls
+      - label: Quite, website uses a controlled naming analogous to our
+      - label: No, website uses fuzzy naming which may be mapped to technologies
+  validations:
+    required: true
+- type: textarea
+  id: supposed_indicators
+  attributes:
+    label: What indicators can we build using this website?
+    description: "Name the indicators that we will be able to build"
+    value: |
+      * Number of confabulations
+      * Supercalifragilisticexpialidocious number
+  validations:
+    required: true
+- type: textarea
+  id: potential_priority
+  attributes:
+    label: Why is it important to add these indicators?
+    description: "Is the website representative of developer usage?"
+    value: |
+      This website is important because it impacts a huge number of users ...
+      This website is important because it provides very good sociological informations ...

.github/ISSUE_TEMPLATE/general_issue.md

@@ -1,3 +1,3 @@
-delete from "indicator" i where i.indicator_date > '2025-07-01'::date;
-delete from "github_stars" g where g.star_date > '2025-07-01'::date;
-delete from "github_forks" g where g.fork_date > '2025-07-01'::date;
+delete from "indicator" i where i.indicator_date > '2025-08-01'::date;
+delete from "github_stars" g where g.star_date > '2025-08-01'::date;
+delete from "github_forks" g where g.fork_date > '2025-08-01'::date;

src/build/resources/sql/clean_database.sql

@@ -93,6 +93,8 @@ tech-lab-ingester:
   # Values in this key should be in the form "platform:name"
   priorized-technologies:
     - NPM:react
+    - NPM:vue
+    - NPM:@angular/core
   export:
     INDICATOR_COMPUTATION:
       csv: