add governance docs

.github/workflows/Issue Template/configure.yml

@@ -0,0 +1,13 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Contributing guidelines
+    url: https://github.com/cardano-updates/blob/master/CONTRIBUTING.md
+    about: Some rules & processes we honor.
+
+  - name: Feature ideas
+    url: https://github.com/cardano-updates/discussions/categories/ideas
+    about: Maybe someone else had the same or a similar idea already?
+
+  - name: All issues
+    url: https://github.com/cardano-updates/issues
+    about: Check whether your issue is not already covered here.

.github/workflows/Issue Template/feature_idea.yml

@@ -0,0 +1,43 @@
+name: Feature idea cardano-updates
+description: Idea or request for some feature for cardano-updates
+labels: [':thought_balloon: idea']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        **Thank you for contributing to our project!** :green_heart:
+
+        Instead of opening this issue, consider [starting a new idea discussion](https://github.com/IntersectMBO/cardano-updates/discussions/new?category=ideas).
+        That way, we can discuss & refine your idea together, before we adopt it as a feature into the roadmap.
+
+  - type: textarea
+    id: why
+    attributes:
+      label: Why
+      description: Why do we need or want this feature
+      placeholder: |
+        Give context and describe the problem, challenge or opportunity you see
+    validations:
+      required: true
+
+  - type: textarea
+    id: what
+    attributes:
+      label: What
+      description: What is this feature roughly about
+      placeholder: |
+        For example describe a new API endpoint, a change in messaging formats,
+        a new configuration option, ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: how
+    attributes:
+      label: How
+      description: How could we realize this feature
+      placeholder: |
+        Which technical solutions, libraries or systems should be used, which
+        components need to change, steps how to implement this, ...
+    validations:
+      required: true

.github/workflows/pull_request_template.md

@@ -0,0 +1,3 @@
+## List of changes
+
+- Add / Fix / Change / Remove

CHANGELOG.md

@@ -0,0 +1,3 @@
+# cardano-updates Changelog
+
+All major changes to this project will be documented in this file.

CODEOWNERS.md

@@ -0,0 +1,8 @@
+# cardano-updates Codeowners
+
+# These owners will be the default owners for everything in the repository.
+* 
+
+# General reviewers per PR
+#                        handle     handle  
+                        name        name

SECURITY.md

@@ -0,0 +1,18 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Please report (suspected) security vulnerabilities to [email protected]. You will receive a
+response from us within 48 hours. If the issue is confirmed, we will release a patch as soon
+as possible.
+
+Please provide a clear and concise description of the vulnerability, including:
+
+* the affected version(s) of cardano-updates,
+* steps that can be followed to exercise the vulnerability,
+* any workarounds or mitigations
+
+If you have developed any code or utilities that can help demonstrate the suspected
+vulnerability, please mention them in your email but ***DO NOT*** attempt to include them as
+attachments as this may cause your Email to be blocked by spam filters.
+See the security file in the [Cardano engineering handbook](https://github.com/input-output-hk/cardano-engineering-handbook/blob/main/SECURITY.md).