feat: prepare for onboarding new members (#23)

* feat: add email field to contributors

* feat: rename meta to __meta

Author: ap-1

.env.example

@@ -1 +1,3 @@
+AUTHENTIK_API_URL="https://auth.scottylabs.org"
+AUTHENTIK_API_TOKEN="authentik-api-token"
 SLACK_TOKEN="governance-slack-token"

.github/workflows/visualize.yml

@@ -8,7 +8,7 @@ on:
       - "contributors/**"
       - "repos/**"
       - "teams/**"
-      - "meta/visualizer/**"
+      - "__meta/visualizer/**"
   workflow_dispatch:
 
 permissions:

.taplo.toml

@@ -17,19 +17,19 @@ column_width = 12
 include = ["contributors/*.toml"]
 
 [rule.schema]
-path = "./meta/schemas/contributor.schema.json"
+path = "./__meta/schemas/contributor.schema.json"
 enabled = true
 
 [[rule]]
 include = ["repos/*.toml"]
 
 [rule.schema]
-path = "./meta/schemas/repo.schema.json"
+path = "./__meta/schemas/repo.schema.json"
 enabled = true
 
 [[rule]]
 include = ["teams/*.toml"]
 
 [rule.schema]
-path = "./meta/schemas/team.schema.json"
+path = "./__meta/schemas/team.schema.json"
 enabled = true

Cargo.toml

@@ -1,6 +1,6 @@
 [workspace]
 resolver = "2"
-members = ["meta/validators/*", "meta/visualizer"]
+members = ["__meta/validators/*", "__meta/visualizer"]
 
 [workspace.package]
 license = "Apache-2.0"

README.md

@@ -2,26 +2,26 @@
 
 This repository defines the organizational structure, team membership, and project ownership for ScottyLabs' Tech Committee. It serves as the source of truth for our GitHub organization's governance model.
 
-In this document, 'ScottyLabs' will refer to the GitHub organization at https://github.com/ScottyLabs, and not the club itself.
+In this document, 'ScottyLabs' will refer to the GitHub organization at <https://github.com/ScottyLabs>, and not the club itself.
 
 ## Repository Structure
 
-```
+```py
 .
-├── contributors   # Individual contributor definitions
-├── docs           # Specific instructions for all three file types
-├── meta
+├── __meta
 │   ├── infra      # Terraform code for applying changes
 │   ├── schemas    # JSON schemas for validation
 │   ├── validators # Rust-based validation tools
 │   └── visualizer # Force graph for visualizing relationships
+├── contributors   # Individual contributor definitions
+├── docs           # Specific instructions for all three file types
 ├── repos          # Team definitions with members and repos
 └── teams          # Repository definitions with metadata
 ```
 
--   **Contributors** - Individuals who participate in ScottyLabs projects
--   **Teams** - Groups of contributors working on specific projects
--   **Repositories** - Code repositories owned by teams
+- **Contributors** - Individuals who participate in ScottyLabs projects
+- **Teams** - Groups of contributors working on specific projects
+- **Repositories** - Code repositories owned by teams
 
 Depending on what you are trying to register, follow the respective guide under `docs/`.
 
@@ -31,45 +31,47 @@ We enforce [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/
 
 This repository also includes several other checks to ensure integrity:
 
--   File names must match the content (the `name` field for repos and teams, the `github-username` field for contributors)
--   Cross-references must be valid (team members must exist as contributors, team repos must exist as repos)
--   GitHub users must exist
--   Slack member IDs and channel IDs must be valid
+- File names must match the content (the `name` field for repos and teams, the `github-username` field for contributors)
+- Cross-references must be valid (team members must exist as contributors, team repos must exist as repos)
+- GitHub users must exist
+- Slack member IDs and channel IDs must be valid
+
+## Development
 
-Validation runs automatically through GitHub Actions on PRs and pushes to main. However, you can also test validators locally:
+Validation runs automatically through GitHub Actions on PRs and pushes to main, so the following instructions will not be relevant to most people. If you are interested, you can also test validators locally:
 
 1. Make sure you are in the root of the repository.
 
 2. Install Rust with `rustup`, if you do not already have it installed:
 
-```sh
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-```
+    ```sh
+    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
+    ```
 
 3. Install `cargo-binstall` (enables use of `cargo binstall`):
 
-```sh
-cargo install cargo-binstall
-```
+    ```sh
+    cargo install cargo-binstall
+    ```
 
 4. Install Taplo:
 
-```sh
-cargo binstall taplo-cli
-```
+    ```sh
+    cargo binstall taplo-cli
+    ```
 
 5. Check TOML files for proper formatting and/or against the schemas:
 
-```sh
-taplo fmt --check # for formatting
-taplo check # against the schemas
-```
+    ```sh
+    taplo fmt --check # for formatting
+    taplo check # against the schemas
+    ```
 
 6. Run the other checks specified above:
 
-```sh
-cargo run --bin governance
-```
+    ```sh
+    cargo run --bin governance
+    ```
 
 ## License
 

meta/infra/.gitkeep renamed to __meta/infra/.gitkeep

@@ -19,7 +19,8 @@
         },
         "email": {
             "type": "string",
-            "format": "email"
+            "format": "email",
+            "pattern": "^[^@]+@andrew\\.cmu\\.edu$"
         }
     },
     "additionalProperties": false