Contributor Onboarding (First chapter or two)

ci/vale/styles/Vocab/main/accept.txt

@@ -34,6 +34,9 @@ colocated
 https
 http
 [cC]yber
+[oO]nboarding
+repo
+Kanban
 subnet
 subnets
 subnetwork
@@ -43,7 +46,6 @@ IP
 IPs
 IPv4
 IPv6
-repo
 unmanaged
 VLAN
 VLANs

src/SUMMARY.md

@@ -4,6 +4,11 @@
 
 [Notice](./notice.md)
 
+- [Contributor Onboarding](./onboarding/main.md)
+    - [GitHub Tickets](./onboarding/github.md)
+    - [Markdown](./onboarding/markdown.md)
+    - [Git](./onboarding/git.md)
+    - [Pull Requests](./onboarding/pr.md)
 - [Network](./network/main.md)
     - [Supernode 1](./network/supernode1.md)
     - [Exit Node](./network/exit-node.md)

src/onboarding/git.md

@@ -0,0 +1,3 @@
+# Git
+
+In progress.

src/onboarding/github.md

@@ -0,0 +1,61 @@
+# GitHub Tickets
+
+GitHub is a service that provides code hosting and versioning. We also use it for its collaborative features, such as issue/bug tracking and project boards. This documents explains how to use GitHub to keep track of tasks.
+
+## Repositories
+
+The main repository for the Toronto Community Network can be found on GitHub under [tomeshnet/toronto-community-network](https://github.com/tomeshnet/toronto-community-network).
+
+![homepage](./images/homepage.png)
+
+A repository (or "repo") is a collection of files, issues, and project boards grouped under a name. The name of this one is `toronto-community-network` and that it was created by the [tomeshnet](https://github.com/tomeshnet) organization.
+
+An overview of the files and folders is displayed in the middle of the screen, and below that the README is shown, which is a file that explains what the repository is for. If you click on `README.md` you'll see it has the same contents as the text on the homepage.
+
+## Issues
+
+![issues](./images/issues.png)
+
+This tab provides a list of all the issues that have been created for this repository. Issues are usually used bug reports or feature requests for a software project, but Toronto Mesh uses them specifically to keep track of tasks or potential plans. All issues have numbers, referenced with a hashtag, such as [#32](https://github.com/tomeshnet/toronto-community-network/issues/32).
+
+For any issue, there is an initial comment explaining what the issue is for, and a discussion going on below about the issue, with reactions, editing, links, etc. The initial comment will change and get edited by others over time as new information is known.
+
+![issue initial comment](./images/issue_initial.png)
+
+Toronto Mesh uses issue templates, so some text is filled out already when a user opens an issue. At time of writing there is only one template, used for tasks, which can be seen if you [open an issue](https://github.com/tomeshnet/toronto-community-network/issues/new?template=task_template.md). More templates may be added in the future.
+
+Issues also have assignees, which can be seen in the sidebar. These are the users responsible for completing this task. A user can assign themselves or other people.
+
+Issues can either be open or closed, which denotes their completion. Issues are closed once they are no longer relevant, or when the original task or bug has been fixed.
+
+## Labels
+
+Issues can have labels, projects, and milestones, which are shown on the sidebar. If a label is clicked, all the issues with that label can be viewed. For example, here are all the communications issues:
+
+![communications issues](./images/issue_comms_label.png)
+
+On the sidebar there is a filter for labels if needed.
+
+![filter labels modal](./images/filter_labels.png)
+
+
+## Projects
+
+[#32](https://github.com/tomeshnet/toronto-community-network/issues/32) is also linked to a project, as can be seen in the sidebar.
+
+![sidebar project](./images/sidebar_project.png)
+
+Click that text or click the Projects tab at the top to see the project. Repositories can have multiple projects, but in this repository there is just one. Here is what it looks like:
+
+![project view](./images/project.png)
+
+A GitHub Project is a type of [Kanban](https://en.wikipedia.org/wiki/Kanban_%28development%29) board for organizing issues.
+Each of the cards are issues, which can be in different columns. We use a standard setup with To Do, Doing (aka "In Progress"), and Completed columns.
+We also have a Backlog column on the far left for low-priority tasks. Issues can be moved from column to column as needed, to indicate their status. Issues will automatically be moved to Completed when they are closed.
+
+Issues in the project can also be filtered by label by clicking on a label, for example all the communications issues in the project can be seen [here](https://github.com/tomeshnet/toronto-community-network/projects/1?card_filter_query=label%3Acommunications).
+
+
+## Creating your first issue
+
+TODO

src/onboarding/main.md

@@ -0,0 +1 @@
+# Contributor Onboarding

src/onboarding/markdown.md

@@ -0,0 +1,3 @@
+# Markdown
+
+In progress.

src/onboarding/pr.md

@@ -0,0 +1,3 @@
+# Pull Requests
+
+In progress.