docs: retire questions file - questions via Redmine, discussion via Discourse
Founder ruling: all questions go through Redmine (notes on the relevant ticket, or umbrella #632), longer questions and durable decision discussion through Discourse (community.turnsys.com). Questions migrated to #639/#651 (netbird scope), #666 (SigNoz reopen), #834 (SBOM format); Discourse API key provisioning requested on #632.
This commit is contained in:
@@ -17,7 +17,9 @@
|
||||
> `reachableceo` is the human's personal account and is no longer used by
|
||||
> agents. Cloudron-side logins use the `vpentops` platform account.
|
||||
> Plans filed: SBOMs **#834**, GLPI software catalog **#835** (gated on
|
||||
> #801 write access). Open questions for the founder: questions-v1.md.
|
||||
> #801 write access). QUESTIONS go via Redmine notes on the relevant ticket
|
||||
> (never .md files); longer questions and durable decision records go to
|
||||
> Discourse (community.turnsys.com - API key provisioning requested on #632).
|
||||
|
||||
## Current State: STABLE (packaging phase, ongoing)
|
||||
|
||||
|
||||
@@ -1,23 +0,0 @@
|
||||
# Questions — TSYSDevStack-SupportStack-Cloudron
|
||||
|
||||
> Agent-authored questions for the founder. Answers inline, newest round at
|
||||
> the top; version up per round (questions-v2.md on the next round).
|
||||
|
||||
## Round 1 — 2026-09-06 (VpEngOps)
|
||||
|
||||
1. ~~**OAM chat access**~~ ANSWERED in ZCode 2026-09-06: "OAM chat" meant the
|
||||
OAM context here in ZCode — no Matrix credential needed. Identity source =
|
||||
vault item `creds/vpengops-vpentops`; commits now authored as VpEngOps.
|
||||
|
||||
2. **NetBird ruling scope** — #650 killed rathole ("netbird for all
|
||||
enterprise network access"). Do **Database-Gateway** (#639, landed:
|
||||
HTTPS DB-access proxy) and **Easy-Gate** (#651, landed: briefing-page
|
||||
gateway) fall inside that ruling, or are they distinct enough to keep?
|
||||
|
||||
3. **SigNoz reopen?** — with ClickHouse coming to the infra, SigNoz #666's
|
||||
storage blocker dissolves, but its OSS auth is still local-only (SSO is
|
||||
enterprise-gated = SSO-tax kill). Stay closed, or reopen under an
|
||||
explicit local-auth acceptance?
|
||||
|
||||
4. **SBOM format** — defaulting to CycloneDX JSON (syft). If the org
|
||||
standard is SPDX, or both formats are wanted, say so on #834.
|
||||
Reference in New Issue
Block a user