Merge branch 'master' into 2424-update-contributing

Author: jsjoeio

.github/CODEOWNERS

@@ -1,3 +1 @@
-* @code-asher @nhooyr
-
 ci/helm-chart @Matthew-Beckett @alexgorbatchev

.github/ISSUE_TEMPLATE/extension-request.md

@@ -3,7 +3,7 @@ name: Extension request
 about: Request an extension missing from the code-server marketplace
 title: ""
 labels: extension-request
-assignees: cmoog
+assignees: ""
 ---
 
 <!--

doc/assets/screenshot.png

@@ -4,6 +4,7 @@
 
 - [Known Issues](#known-issues)
 - [How to access code-server with a self signed certificate on iPad?](#how-to-access-code-server-with-a-self-signed-certificate-on-ipad)
+  - [Servediter iPad App](#servediter-ipad-app)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
@@ -51,3 +52,14 @@ refuse to allow WebSockets to connect.
 5. Go to `Settings -> About -> Certificate Trust Settings` and enable full trust for
    the certificate.
 6. Now you can access code-server! 🍻
+
+### Servediter iPad App
+
+If you are unable to get the self signed certificate working or you do not have a domain
+name to use, you can use the Servediter iPad App instead!
+
+**note**: This is not an officially supported app by the code-server team!
+
+Download [Serveediter](https://apps.apple.com/us/app/servediter-for-code-server/id1504491325) from the
+App Store and then input your server information. If you are running a local server or mabye a usb-c
+connected Raspberry Pi, you will input your settings into "Self Hosted Server".

doc/ipad.md

@@ -0,0 +1,37 @@
+# Triage
+
+## Filter
+
+Triaging code-server issues is done with the following issue filter:
+
+```
+is:issue is:open no:project sort:created-asc -label:blocked -label:upstream -label:waiting-for-info -label:extension-request
+```
+
+This will show issues that:
+
+1. Are open.
+2. Have no assigned project.
+3. Are not `blocked` or tagged for work by `upstream` (VS Code core team)
+   - If an upstream issue is detrimental to the code-server experience we may fix it in
+     our patch instead of waiting for the VS Code team to fix it.
+   - Someone should periodically go through these issues to see if they can be unblocked
+     though!
+4. Are not in `waiting-for-info`.
+5. Are not extension requests.
+
+## Process
+
+1. If an issue is a question/discussion it should be converted into a GitHub discussion.
+2. Next, give the issue the appropriate labels and feel free to create new ones if
+   necessary.
+   - There are no hard and set rules for labels. We don't have many so look through and
+     see how they've been used throughout the repository. They all also have descriptions.
+3. If more information is required, please ask the submitter and tag as
+   `waiting-for-info` and wait.
+4. Finally, the issue should be moved into the
+   [code-server](https://github.com/cdr/code-server/projects/1) project where we pick
+   out issues to fix and track their progress.
+
+We also use [milestones](https://github.com/cdr/code-server/milestones) to track what
+issues are planned/or were closed for what release.