governance: record Linas Board and AeroSim membership
Build and publish Corp v1 Board portal / build (pull_request) Successful in 33s
Build and publish Corp v1 Board portal / build (pull_request) Successful in 33s
This commit is contained in:
@@ -13,5 +13,6 @@ sidebar_position: 1
|
||||
| [Panther Skeleton](/members/panther-skeleton/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
|
||||
| [MartynasP](/members/martynasp/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
|
||||
| [Eduard](/members/eduard/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
|
||||
| [Linas](/members/linas/) | Active | Board member; AeroSim member | AeroSim Team | 1 |
|
||||
|
||||
Only governance-relevant professional information belongs here. Do not store secrets, credentials, private contact details, or unnecessary personal data.
|
||||
|
||||
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Linas"
|
||||
description: "Identify Linas's Corp v1 Board and AeroSim project responsibilities and verified access state."
|
||||
sidebar_position: 6
|
||||
---
|
||||
|
||||
# Linas
|
||||
|
||||
| Field | Value |
|
||||
|---|---|
|
||||
| Full name | Linas Ramanauskas |
|
||||
| Discord | `<@1483820991720329227>` — `linas_02251` / Linas |
|
||||
| Governance roles | Corp v1 Board member; AeroSim human team member |
|
||||
| Team | [AeroSim Team](/teams/aerosim/) |
|
||||
| Active projects | [AeroSim](/projects/aerosim/) |
|
||||
| Gitea | `linas` (user ID `21`) — verified in both AeroSim organization teams; account reports `active=false` |
|
||||
|
||||
On 2026-08-17, effective `VIEW_CHANNEL`, `SEND_MESSAGES`, and `READ_MESSAGE_HISTORY` access was verified in `corp-v1-board` and all six AeroSim channels. Existing effective permissions were sufficient, so no Discord permission mutation was made.
|
||||
|
||||
The unambiguous Gitea identity `linas` belongs to `aerosim-maintainers` (team ID `23`) and `aerosim-skill-maintainers` (team ID `24`). Those teams cover both required project repositories and all thirteen adopted skill repositories. Access assignment is complete, but Gitea login activation remains pending because the account reports `active=false`.
|
||||
Reference in New Issue
Block a user