chore: Preparing the contribution

.github/ISSUE_TEMPLATE/bug.yaml

@@ -0,0 +1,53 @@
+# SPDX-FileCopyrightText: 2023 Iván SZKIBA
+#
+# SPDX-License-Identifier: AGPL-3.0-only
+
+name: Bug report
+description: Use this template for reporting bugs. Please search existing issues first.
+labels: [bug]
+body:
+  - type: textarea
+    attributes:
+      label: Brief summary
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: '## Environment'
+  - type: input
+    attributes:
+      label: k6 version
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: xk6-dashboard version
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: OS
+      description: e.g. Windows 10, Arch Linux, macOS 11, etc.
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Docker version and image (if applicable)
+  - type: markdown
+    attributes:
+      value: '## Detailed issue description'
+  - type: textarea
+    attributes:
+      label: Steps to reproduce the problem
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behaviour
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual behaviour
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,9 @@
+# SPDX-FileCopyrightText: 2023 Iván SZKIBA
+#
+# SPDX-License-Identifier: AGPL-3.0-only
+
+blank_issues_enabled: true
+contact_links:
+  - name: Discussions
+    url: https://github.com/szkiba/k6x/discussions/
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/enhancement.yaml

@@ -0,0 +1,22 @@
+# SPDX-FileCopyrightText: 2023 Iván SZKIBA
+#
+# SPDX-License-Identifier: AGPL-3.0-only
+
+name: Enhancement
+description: Use this template for suggesting enhancements to existing features.
+labels: [enhancement]
+body:
+  - type: textarea
+    attributes:
+      label: Enhancement Description
+      description: A clear and concise description of the problem or missing capability
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Suggested Solution (optional)
+      description: If you have a solution in mind, please describe it.
+  - type: textarea
+    attributes:
+      label: Already existing or connected issues / PRs (optional)
+      description: If you have found some issues or pull requests that are related to your new issue, please link them here.

.github/ISSUE_TEMPLATE/feature.yaml

@@ -0,0 +1,22 @@
+# SPDX-FileCopyrightText: 2023 Iván SZKIBA
+#
+# SPDX-License-Identifier: AGPL-3.0-only
+
+name: Feature Request
+description: Use this template for suggesting new features.
+labels: [feature]
+body:
+  - type: textarea
+    attributes:
+      label: Feature Description
+      description: A clear and concise description of the problem or missing capability
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Suggested Solution (optional)
+      description: If you have a solution in mind, please describe it.
+  - type: textarea
+    attributes:
+      label: Already existing or connected issues / PRs (optional)
+      description: If you have found some issues or pull requests that are related to your new issue, please link them here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+## What?
+
+<!-- A short (or detailed) description of what this PR does. -->
+
+## Why?
+
+<!-- A short (or detailed) explanation of why these changes are made and needed. -->
+
+## Checklist
+
+<!-- 
+If you haven't read the contributing guidelines https://github.com/szkiba/k6x/blob/master/CONTRIBUTING.md 
+and code of conduct https://github.com/szkiba/k6x/blob/master/CODE_OF_CONDUCT.md yet, please do so
+-->
+
+- [ ] I have performed a self-review of my code.
+- [ ] I have added tests for my changes.
+- [ ] I have run linter locally (`go run mage.go lint`) and all checks pass.
+- [ ] I have run tests locally (`go run mage.go test`) and all tests pass.
+- [ ] I have commented on my code, particularly in hard-to-understand areas.
+<!-- - [ ] Any other relevant item -->
+
+## Related PR(s)/Issue(s)
+
+<!-- - <https://github.com/szkiba/k6x/...> -->
+
+<!-- Does it close an issue? -->
+
+<!-- Closes #ISSUE-ID -->
+
+<!-- Thanks for your contribution! 🙏🏼 -->

.github/PULL_REQUEST_TEMPLATE.md.license

@@ -0,0 +1,4 @@
+SPDX-FileCopyrightText: 2023 Iván SZKIBA
+SPDX-FileCopyrightText: 2023 Raintank, Inc. dba Grafana Labs
+
+SPDX-License-Identifier: AGPL-3.0-only

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CODE_OF_CONDUCT.md.license

@@ -0,0 +1,5 @@
+SPDX-FileCopyrightText: 2014 Contributor Covenant
+SPDX-FileCopyrightText: 2023 Iván SZKIBA
+
+SPDX-License-Identifier: AGPL-3.0-only
+SPDX-License-Identifier: CC-BY-4.0

CONTRIBUTING.md

@@ -0,0 +1,86 @@
+# Contributing to k6x
+
+Thank you for your interest in contributing to k6x!
+
+Before you begin, make sure to familiarize yourself with the [Code of Conduct](CODE_OF_CONDUCT.md). If you've previously contributed to other open source project, you may recognize it as the classic [Contributor Covenant](https://contributor-covenant.org/).
+
+If you want to chat with the team or the community, you can [join our community forums](https://community.grafana.com/c/grafana-k6/extensions/).
+
+## Filing issues
+
+Don't be afraid to file issues! Nobody can fix a bug we don't know exists, or add a feature we didn't think of.
+
+The worst that can happen is that someone closes it and points you in the right direction.
+
+That said, "how do I..."-type questions are often more suited for community forums.
+
+## Contributing code
+
+If you'd like to contribute code to k6x, this is the basic procedure. Make sure to follow the [style guide](#style-guide) described below.
+
+1. Find an issue you'd like to fix. If there is none already, or you'd like to add a feature, please open one, and we can talk about how to do it.  Out of respect for your time, please start a discussion regarding any bigger contributions either in a GitHub Issue, in the community forums **before** you get started on the implementation.
+
+   Remember, there's more to software development than code; if it's not properly planned, stuff gets messy real fast.
+
+2. Create a fork and open a feature branch - `feature/my-cool-feature` is the classic way to name these, but it really doesn't matter.
+
+3. Create a pull request!
+
+4. We will discuss implementation details until everyone is happy, then a maintainer will merge it.
+
+### Development setup
+
+To get a basic development environment for Go and k6x up and running, first make sure you have **[Git](https://git-scm.com/downloads)** and **[Go](https://golang.org/doc/install)** (see our [go.mod](https://github.com/szkiba/k6x/blob/master/go.mod) for minimum required version) installed and working properly.
+
+We recommend using the Git command-line interface to download the source code for the k6x:
+
+* Open a terminal and run `git clone https://github.com/szkiba/k6x.git`. This command downloads xk6-dashboard's sources to a new `k6x` directory in your current directory.
+* Open the `k6x` directory in your favorite code editor.
+
+For alternative ways of cloning the k6x repository, please refer to [GitHub's cloning a repository](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository) documentation.
+
+#### Running the linter
+
+We make use of the [golangci-lint](https://github.com/golangci/golangci-lint) tool to lint the code in CI. The actual version you can find in our [`.golangci.yml`](https://github.com/szkiba/k6x/blob/master/.golangci.yml#L1). To run it locally run:
+
+```bash
+go run mage.go lint
+```
+
+#### Running the test suite
+
+To exercise the entire test suite, please run the following command
+
+```bash
+go run mage.go test
+```
+
+#### Code style
+
+As you'd expect, please adhere to good ol' `gofmt` (there are plugins for most editors that can autocorrect this), but also `gofmt -s` (code simplification), and don't leave unused functions laying around.
+
+Continuous integration will catch all of this if you don't, and it's fine to just fix linter complaints with another commit, but you can also run the linter yourself:
+
+```bash
+go run mage.go lint
+```
+
+Comments in the source should wrap at 100 characters, but there's no maximum length or need to be brief here - please include anything one might need to know in order to understand the code, that you could reasonably expect any reader to not already know (you probably don't need to explain what a goroutine is).
+
+#### Commit format
+
+We don't have any explicit rules about commit message formatting, but try to write something that could be included as-is in a changelog.
+
+If your commit closes an issue, please [close it with your commit message](https://help.github.com/articles/closing-issues-via-commit-messages/), for example:
+
+```text
+Added this really rad feature
+
+Closes #420
+```
+
+#### Language and text formatting
+
+Any human-readable text you add must be non-gendered and should be fairly concise without devolving into grammatical horrors, dropped words, and shorthands. This isn't Twitter, you don't have a character cap, but don't write a novel where a single sentence would suffice.
+
+If you're writing a longer block of text to a terminal, wrap it at 80 characters - this ensures it will display properly at the de facto default terminal size of 80x25.

CONTRIBUTING.md.license

@@ -0,0 +1,3 @@
+SPDX-FileCopyrightText: 2023 Iván SZKIBA
+
+SPDX-License-Identifier: AGPL-3.0-only