Tmp (#4)

* Add access request issue template and instructions to `development.md`.

Signed-off-by: zjgarvey <zjgarvey@gmail.com>

* Update with caveat of shared responsibilities.

Signed-off-by: zjgarvey <zjgarvey@gmail.com>

---------

Signed-off-by: zjgarvey <zjgarvey@gmail.com>

Author: zjgarvey

.github/ISSUE_TEMPLATE/request_permissions.yml

@@ -0,0 +1,54 @@
+name: 🔑 Request Github Access 🔑
+
+description: Request elevated repository permissions for torch-mlir.
+labels: ["Access Request"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We are glad you want to join our community!
+
+        Please view the [developer documentation](https://github.com/llvm/torch-mlir/blob/main/docs/development.md#requesting-repository-permissions) for requirements to request access.
+
+  - type: dropdown
+    id: Desired Role
+    attributes:
+      label: Which role are you requesting?
+      description: |
+        Triage: manage issues and pull requests
+        Write: Triage + can push code
+        Admin: Write + access to repository settings, including the ability to grant roles to new members.
+      multiple: false
+      options:
+        - Triage
+        - Write
+        - Admin
+      required: true
+  - type: textarea
+    id: Why do you want access?
+    attributes:
+      label:
+      description: |
+        Tell us why you want to get elevated permissions for the repository.
+
+        If you have a downstream use for torch-mlir, or a desire to help maintain part of the codebase, please indicate that here.
+
+        Working for a company or having a specific use-case is not required, but can be helpful context (e.g. for higher-level permissions).
+      placeholder: My downstream project has a use for ... and I want to help maintain ...
+    validations:
+      required: true
+  - type: textarea
+    id: Recent Pull Requests
+    attributes:
+      label:
+      description: Please link two of your recent pull requests in this repository (or a similar open-source repository).
+      placeholder: |
+        Example PR 1:
+        Example PR 2:
+      required: true
+  - type: textarea
+    id: optional-additional-context
+    attributes:
+      label: Additional context
+      description: Add any other context you think is relevant.
+      placeholder:

docs/code_owners.md

@@ -13,21 +13,25 @@ and Clang's
 ### All parts not covered by anyone else
 
 - Stella Laurenzo (@stellaraccident)
+- Zach Garvey (@zjgarvey)
 - Sean Silva (@silvasean) - emeritus
 
 --------------------------------------------------------------------------------
 
 ### `torch` dialect and other core IR pieces, Python bindings/API, JIT IR importer
 
 - Stella Laurenzo (@stellaraccident)
+- Zach Garvey (@zjgarvey)
 
 ### TorchToLinalg, Shape inference, Dtype refinement, MaximizeValueSemantics
 
-- Ramiro Leal-Cavazos (@ramiro050)
+- Ramiro Leal-Cavazos (@ramiro050) - emeritus
+- Zach Garvey (@zjgarvey)
 
 ### CI / Build system / Packaging
 
 - Anush Elangovan (@powderluv)
+- Maybe you!*
 
 ### TorchToTOSA
 
@@ -45,12 +49,24 @@ and Clang's
 
 - Antonio Kim (@antoniojkim)
 - Ke Deng (@ke1337)
+- Maybe you!*
 
 ### Bazel build
 
 - Sambhav Jain (@sjain-stanford)
 - Ahmed Taei (@asaadaldien)
+- Maybe you!*
 
 ### LLVM Integrate
 
-- Ashay Rane (@ashay)
+- Zach Garvey (@zjgarvey) **
+- Ashay Rane (@ashay) **
+- Maybe you!*
+
+### Roll Pytorch
+
+- Zach Garvey (@zjgarvey) **
+
+
+*Please submit a pull request to add/remove your name as a code owner.
+**This job is not the sole-responsibility of these people. If you are an active contributor, please help with updating core dependencies.

docs/development.md

@@ -1,5 +1,21 @@
 # Development Guide
 
+## Requesting Repository Permissions
+
+To request repository permissions, please file an issue with the template: [🔑 Request Github Access 🔑](https://github.com/llvm/torch-mlir/issues)
+
+There are essentially three levels of access:
+
+1. Anyone (including you!): Can access the codebase, create or comment on issues and pull requests.
+
+2. Triage: Can also manage issues and pull requests, request reviewers. If you have contributed to either this repo or other MLIR-based open source projects, please link two recent PR's to your access request issue. Please also indicate why you are requesting access.
+
+3. Write: Can push to the repo (Note: all commits should be reviewed and approved through a pull request). In addition to the requirements for Triage access, you should have a reputation for quality work and general engineering discipline within at least one part of this project.
+
+4. Admin: This project is relatively stable, and some admins have moved on to other projects. Request this access if your team, company, or research project has need to maintain a part of the project that isn't being actively engaged with by existing admins **and** you feel like the existing admins are not responsive enough to the repository access requests submitted by members of your team.
+
+Note: to add yourself as a code owner for an area of the codebase, simply submit a pull request to change `docs/code_owners.md`. You do not explicitly need any repository role in order to be a code owner.
+
 ## Setting Up Environment
 
 ### Clone the Repository