chore: Move v3 to main

.github/ISSUE_TEMPLATE/decision-record.md

@@ -0,0 +1,35 @@
+---
+name: Decision record
+about: Decision record
+---
+<!-- Follow the decision making process (https://kyma-project.io/community/governance) -->
+
+Created on {YYYY-MM-DD} by {name and surname (@Github username)}.
+
+## Decision log
+
+| Name | Description |
+|-----------------------|------------------------------------------------------------------------------------|
+| Title | {Provide a brief summary of the decision.} |
+| Due date | {Specify the date by which the SIG or WG members need to make the decision. Use the `YYYY-MM-DD` date format.} |
+| Status | {The status of the document can be `Accepted`, `Declined`, or `Proposed` when it is waiting for a decision. This section should contain one of these three words followed by the date on which the status of the document is agreed on. Follow the `YYYY-MM-DD` format for the date. For example, write `Proposed on 2018-03-20` or `Accepted on 2018-03-23`. Add the new status when it changes. Do not overwrite previous status entries.}|
+| Decision type | {Type in `Binary`, `Choice`, or `Prioritization`. The `Binary` type refers to the  yes/no decisions, the `Choice` type means that the decision involves choosing between many possibilities, such as a name for a new product, and the `Prioritization` type involves ranking a number of options, such as choosing the next five features to build out of one hundred possible options.} |
+| Affected decisions | {Specify the ID of the decision issue or a link to the previous decision record which is affected by this decision. Use the `#{issueid}\|{decision-record-URL}(replaces\|extends\|depends on)` format. For example, write `#265(replaces)` or `#278(depends on)` which means that the decision you propose replaces the issue 265 or depends on the issue 278. Specify as many references as possible and separate them with a comma. Write `None` if no other decision is affected.}|
+
+## Context
+
+<!-- Briefly describe what the decision record (DR) is about.
+Explain the factors for the decision, what are the forces at play, and the reasons why the discussed solution is needed.
+Remember that this document should be relatively short and concise. If necessary, provide relevant links for more details.
+If the decision concerns more solutions, mark them with separate subsections. Use H3 for the subsection headings.  -->
+
+## Decision
+
+<!--Avoid using personal constructions such as "we." Use impersonal forms instead.
+For example, `The decision is to...`. If it is necessary to indicate the subject, use `SIG/WG members` instead of "we." -->
+
+## Consequences
+
+<!-- Briefly explain the consequences of this decision for the Kyma project.
+Include both the advantages and disadvantages of the discussed solution.
+-->

.github/ISSUE_TEMPLATE/documentation-improvement.md

@@ -31,4 +31,4 @@ about: Suggest an improvement or report a bug in the documentation
 
 **Attachments**
 
-<!-- Attach any files, links, code samples, or screenshots that will convince us to your idea. -->
+<!-- Attach any files, links, code samples, or screenshots that will convince us to your idea. -->

.github/ISSUE_TEMPLATE/new-sig-or-wg-proposal.md

@@ -0,0 +1,80 @@
+---
+name: SIG or WG proposal
+about: Propose a new SIG or WG
+---
+
+<!-- Thank you for your contribution. Before you submit the issue:
+1. Search other groups for relevance of your topics.
+2. Read the governance model (https://kyma-project.io/community/governance).
+3. Collect at least five candidates for this group.
+-->
+
+**Proposal type**
+<!-- Remove the type that does not fit. -->
+* Special Interest Group (SIG)
+* Working Group (WG)
+
+**Name**
+* Full name of the group:
+<!-- Specify the abbreviated name for slack channels, issue labels, and pull request labels.
+The abbreviate name must be no longer than six characters. -->
+* Abbreviated name:
+
+**Earliest start date**
+<!-- Specify the earliest date for this group to start their work. This is required to make a timely decision on the group creation. -->
+* {YYYY-MM-DD}
+
+**Visibility**
+<!-- Remove the type that does not fit. -->
+* Internal
+* Public
+
+**Keywords** (optional)
+<!-- List several keywords or labels that relate to the working domain of this group. -->
+* ...
+* ...
+* ...
+
+**Proposers**
+<!-- List the names and the GitHub usernames of people who are authors of this proposal. -->
+* ...
+* ...
+* ...
+
+**Purpose and goals**
+<!-- Describe the purpose and the goals of this group.  -->
+
+**Benefits**
+<!-- Provide the reasons for organizing this group. Describe how the Kyma project or the Kyma community can benefit from the work of this group. -->
+
+**Expected results**
+<!-- Describe what you expect as deliverables of this group and how they relate to the purpose and the goals of this group. Provide a provisionary timeline or phases if possible. -->
+
+**Expected membership and governance**
+<!-- Provide the details even if they are not final yet. -->
+* Meeting frequency: <!-- Define if the group meets daily, weekly, bi-weekly, or monthly. -->
+* Membership: <!-- Provide the approximate number of initial members. -->
+* Duration: <!-- This field is mandatory for a WG. -->
+
+**Previous approach** (optional)
+<!-- Describe if and how these topics were previously addressed and why you think this group can improve them.-->
+
+**Measures of success** (optional for SIG)
+<!-- List the criteria to assess if the group's work is successful and adds value.
+Describe the methods of performing and documenting the regular self-assessment by the group. -->
+* ...
+* ...
+* ...
+
+**Assessment frequency**
+<!-- Define how often the group evaluates its work. Remove the type that does not fit. -->
+* Monthly
+* Quarterly
+* Biannually
+* Annually
+
+**Exit criteria**
+<!-- List the conditions and risks that can lead to dissolving the group. Be specific and do not make general statements. -->
+* ...
+* ...
+* ...

.github/ISSUE_TEMPLATE/security-vulnerability.md

@@ -1,5 +1,5 @@
 ---
-name: Security Vulnerability
+name: Security vulnerability
 about: Report vulnerability in the project
 ---
 
@@ -30,11 +30,11 @@ For example:
 [CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) **7.1 (High)**
 
 Placeholder details:
-* {CVSS Vector String}: 
-  Vector String representation of the CVSS metrics, as displayed by the CVSS calculator. 
+* {CVSS Vector String}:
+  Vector String representation of the CVSS metrics, as displayed by the CVSS calculator.
   For example: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
 * {CVSS Calculator URL}:
-  A deeplink to the CVSS calculator with the metrics that you propose. 
+  A deeplink to the CVSS calculator with the metrics that you propose.
   Automatically appears in your browser's URL bar after you filled in the metrics.
   Contains the {CVSS Vector String}.
   For example: https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

.github/dependabot.yml

@@ -1,22 +1,26 @@
-# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+# https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
 
 version: 2
 updates:
   - package-ecosystem: "gomod"
     directory: "/"
     labels:
-      - "go"
       - "area/dependency"
+      - "kind/chore"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     commit-message:
-      prefix: "chore(dependabot)"
-  - package-ecosystem: "docker"
-    directory: "/"
-    labels:
-      - "docker"
-      - "area/dependency"
-    schedule:
-      interval: "daily"
-    commit-message:
-      prefix: "chore(dependabot)"
+      prefix: "gomod"
+      include: "scope"
+    ignore:
+      # ignore minor k8s updates, e.g. 1.27.x -> 1.28.x
+      - dependency-name: "k8s.io/*"
+        update-types: ["version-update:semver-minor"]
+      - dependency-name: "sigs.k8s.io/*"
+        update-types: ["version-update:semver-minor"]
+      - dependency-name: "helm.sh/helm/v3"
+        update-types: ["version-update:semver-minor"]
+    groups:
+      k8s-io:
+        patterns:
+          - "k8s.io/*"

.github/pull-request-template.md

@@ -3,6 +3,8 @@
 2. Read and submit the required Contributor Licence Agreements (https://github.com/kyma-project/community/blob/main/CONTRIBUTING.md#agreements-and-licenses).
 3. Test your changes and attach their results to the pull request.
 4. Update the relevant documentation.
+
+If the pull request requires a decision, follow the [decision-making process](https://github.com/kyma-project/community/blob/main/governance.md) and replace the PR template with the [decision record template](https://github.com/kyma-project/community/blob/main/.github/ISSUE_TEMPLATE/decision-record.md).
 -->
 
 **Description**

.github/workflows/lint-markdown-links.yml

@@ -1,23 +1,14 @@
 name: Lint Markdown Links
 run-name: ${{github.event.pull_request.title}}
-
-on:
-  pull_request:
-  schedule:
-    # Run every day at 5:00 AM
-    - cron: "0 5 * * *"
-
+on: [ pull_request ]
 jobs:
   markdown-link-check:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
       - uses: gaurav-nelson/github-action-markdown-link-check@v1
         with:
-          use-quiet-mode: 'yes'
           use-verbose-mode: 'no'
           config-file: '.mlc.config.json'
           folder-path: '.'
           max-depth: -1
-          check-modified-files-only: 'yes'
-          base-branch: 'main'