docs: contribution guide.

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,81 @@
+name: 🐛 Bug Report
+description: Submit a bug report to help us improve.
+title: "bug: "
+labels:
+  - ["bug:unverified", 'status:needs triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for your help in improving kernl by reporting bugs.
+
+        Before you create your issue.
+
+          - Make sure the bug has not already been reported in the issue tracker.
+          - Make sure it is reproducible.
+          - Make sure you have enough material to fuel the search and resolution.
+
+        Please fill out the form below to help us better understand the problem.
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Steps to reproduce
+      description: Steps to reproduce the bug.
+      placeholder: |
+        1. Step 1...
+        2. Step 2...
+        3. Step 3...
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen.
+      placeholder: Write what you thought would happen.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      description: A concise description of what you're experiencing.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Your environment
+      description: Include as many relevant details about the environment you experienced the bug in.
+      value: |
+        - Operating system and version (e.g. Ubuntu 20.04.2 LTS):
+        - Python version (e.g. Python 3.8.10):
+        - Python package manager (e.g. pip 21.1.2):
+        - etc.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Self-service
+      description: |
+        If you think you can help fix this bug, please check the box below. This lets us know that someone wants to work on it.
+        If you check this box, please send a Pull Request within 7 days of a maintainer's approval so we can delegate this task.
+      options:
+        - label: I would be willing to help fix this bug myself.
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://www.kernl.ai/contribution-guide/code-of-conduct/)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,43 @@
+name: 📚 Documentation
+description: Report an issue related to documentation
+title: "docs: "
+labels: [documentation, 'status: needs triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your help to improve kernl.
+
+        This template is strictly used for documentation requests. 
+
+        For example:
+        - Adding or modifying documentation.
+        - Adding or modifying tutorials.
+        - ...
+
+        > This issue should not touch the code base.
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of what the issue is.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Self-service
+      description: |
+        If you feel like you could contribute to this issue, please check the box below. This lets us know that someone wants to work on it.
+        If you check this box, please send a Pull Request within 7 days of a maintainer's approval so we can delegate this task.
+      options:
+        - label: I would be willing to contribute to this issue myself.
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://www.kernl.ai/contribution-guide/code-of-conduct/)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,64 @@
+name: 💅 Feature
+description: Submit a detailed feature request with a concrete proposal.
+title: "feature: "
+labels: [feature, "status: needs triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your help to improve kernl.
+
+        Important stuff:
+
+        - We expect you to submit a real feature request and not just a basic idea.
+        - The proposal doesn't have to be perfect, but it does have to be sufficiently elaborate. We will discuss and correct it if necessary.
+        - For a more "casual" feature request, consider using the discussion forum.
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: A clear and concise description of what the feature is (be as complete as possible).
+    validations:
+      required: true
+
+  - type: input
+    attributes:
+      label: Is this request already on the discussion forum?
+      description: Please post the link, it is useful to determine the interest in this feature.
+
+  - type: textarea
+    attributes:
+      label: Motivation
+      description: Please outline the motivation for the proposal and why it should be implemented.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Have you tried to implement it?
+      description: |
+        Please explain how you tried to create this feature by yourself and how you succeeded.
+
+        If you can't create it yourself for technical reasons, please tell us why. We are ready to help you.
+
+        > If your feature request is just an idea at the moment, please use the discussion forum.
+
+  - type: checkboxes
+    attributes:
+      label: Self-service
+      description: |
+        If you answered the above question with "no" because you think you can contribute directly to the repository, please check the box below. This lets us know that someone wants to work on it.
+        If you check this box, please send a Pull Request within 7 days of a maintainer's approval so we can delegate this task.
+
+        > Note that for feature issues, we always ask that you fill out this form completely so that we can reach a consensus and not waste your time.
+      options:
+        - label: I would be willing to contribute to this feature myself.
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this feature, you agree to follow our [Code of Conduct](https://www.kernl.ai/contribution-guide/code-of-conduct/)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/proposal.yml

@@ -0,0 +1,47 @@
+name: 💥 Proposal
+description: Propose a non-trivial change to kernl
+title: "proposal: "
+labels: [proposal, 'status: needs triage']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your help to improve kernl.
+
+        An example of a proposal might be:
+
+        - A significant improvement.
+        - Significant refactoring.
+        - A major version upgrade of a critical dependency.
+        - ...
+
+        You are free to write a proposal. But you must explain why you think this change is really beneficial, and what steps we should take to make it happen.
+
+        > This is not a feature request, or a bug fix.
+
+  - type: textarea
+    attributes:
+      label: Motivation
+      description: A clear and concise description of what the proposal is.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Self-service
+      description: |
+        If you feel like you could contribute to this proposal, please check the box below. This lets us know that someone wants to work on it.
+        If you check this box, please send a Pull Request within 7 days of a maintainer's approval so we can delegate this task.
+
+        > Proposals usually involve significant changes to the code. Please reach a consensus with those responsible before implementing them.
+      options:
+        - label: I would be willing to contribute to this proposal myself.
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this proposal, you agree to follow our [Code of Conduct](https://www.kernl.ai/contribution-guide/code-of-conduct/)
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.gitignore

@@ -4,3 +4,6 @@ venv/
 __pycache__/
 *.egg-info/
 site/
+
+# Misc
+.DS_Store

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# 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
+<open.kernl.ai@gmail.com>.
+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

README.md

@@ -175,3 +175,11 @@ We leverage mostly 3 technologies:
 ## Acknowledgments
 
 Code of OpenAI Triton kernels takes inspiration from examples from OpenAI Triton tutorials or xformers library.  
+
+## Contributing
+
+If you would like to contribute, for example to code or documentation, please see our [contribution guide](https://www.kernl.ai/contribution-guide/contributing/).
+
+## Code of Conduct
+
+Please see our [Code of Conduct](https://www.kernl.ai/contribution-guide/code-of-conduct/) for any questions about the community we are trying to build and what to do if you need help with someone who is acting unprofessionally.