Skip to content

Commit 50e2989

Browse files
nirholasnirholas
committed
Initial commit
0 parents  commit 50e2989

1,086 files changed

Lines changed: 112935 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.dockerignore‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
output/
2+
*.iso
3+
.git/

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
name: Bug report
3+
about: Report a reproducible problem with PAI
4+
title: "[bug] "
5+
labels: ["bug", "triage"]
6+
assignees: []
7+
---
8+
9+
<!--
10+
Before filing, please read SUPPORT.md and CONTRIBUTING.md.
11+
NEVER attach or paste seed phrases, passphrases, wallet keys, or API tokens.
12+
Redact them from any logs or screenshots before uploading.
13+
-->
14+
15+
## What happened
16+
17+
<!-- Describe the bug in plain prose. -->
18+
19+
## What you expected to happen
20+
21+
<!-- What should have happened instead? -->
22+
23+
## Steps to reproduce
24+
25+
<!-- Minimal, numbered steps. The shorter and more deterministic, the faster we can help. -->
26+
27+
1.
28+
2.
29+
3.
30+
31+
## Environment
32+
33+
- **PAI version** (from `cat /etc/os-release`):
34+
- **Architecture**: <!-- AMD64 / ARM64 -->
35+
- **Hardware make/model**:
36+
- **RAM**:
37+
- **Boot mode**: <!-- UEFI / Legacy BIOS -->
38+
- **Persistence enabled**: <!-- yes / no -->
39+
- **Tor mode**: <!-- on / off -->
40+
41+
## Logs
42+
43+
Attach the following where relevant. **Redact any sensitive data first
44+
— never include seed phrases, passphrases, tokens, or private keys.**
45+
46+
- [ ] `journalctl -k` (kernel log)
47+
- [ ] `dmesg` output
48+
- [ ] Relevant application logs (specify which)
49+
- [ ] Boot log / screenshot of failure
50+
51+
<!-- Paste logs inside <details> blocks or attach as files. -->
52+
53+
## Screenshots
54+
55+
<!-- Optional. Drag & drop images here. Redact anything sensitive. -->
56+
57+
## Additional context
58+
59+
<!-- Anything else that might help: recent changes, related issues, hardware quirks. -->
60+
61+
## Pre-flight checklist
62+
63+
- [ ] I searched [existing issues](../issues?q=is%3Aissue) and found no duplicate
64+
- [ ] I read [SUPPORT.md](../blob/main/SUPPORT.md) and this is a bug, not a support question
65+
- [ ] I have redacted all secrets, seed phrases, passphrases, and tokens from logs and screenshots
66+
- [ ] I followed [CONTRIBUTING.md](../blob/main/CONTRIBUTING.md) guidance for filing reports

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
name: Bug Report
2+
description: Something isn't working as expected
3+
labels: ["bug"]
4+
body:
5+
- type: input
6+
id: title
7+
attributes:
8+
label: Summary
9+
placeholder: "Brief description of the bug"
10+
validations:
11+
required: true
12+
13+
- type: textarea
14+
id: steps
15+
attributes:
16+
label: Steps to Reproduce
17+
placeholder: |
18+
1. Boot PAI from USB
19+
2. ...
20+
validations:
21+
required: true
22+
23+
- type: textarea
24+
id: expected
25+
attributes:
26+
label: Expected Behavior
27+
validations:
28+
required: true
29+
30+
- type: textarea
31+
id: actual
32+
attributes:
33+
label: Actual Behavior
34+
validations:
35+
required: true
36+
37+
- type: input
38+
id: hardware
39+
attributes:
40+
label: Hardware
41+
placeholder: "e.g. ThinkPad X1 Carbon 2021, i7-1165G7"
42+
43+
- type: input
44+
id: version
45+
attributes:
46+
label: PAI Version
47+
placeholder: "e.g. v0.1.0 or dev/main"
48+
validations:
49+
required: true

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
name: Feature request
3+
about: Suggest a new capability or improvement for PAI
4+
title: "[feat] "
5+
labels: ["enhancement", "triage"]
6+
---
7+
8+
## Problem / motivation
9+
10+
What's missing or painful today? Describe the user problem, not the
11+
solution. Concrete examples of where you hit the limitation help a lot.
12+
13+
## Proposed solution
14+
15+
What should PAI do? Describe the *behavior* — what the user sees, what
16+
inputs and outputs look like — not the implementation.
17+
18+
## Alternatives considered
19+
20+
What other tools, workflows, or approaches did you look at? Why don't
21+
they fit your needs?
22+
23+
## Who benefits
24+
25+
Which user archetypes gain from this? (e.g. offline researchers, hobbyists
26+
on low-power hardware, privacy-conscious professionals, educators.)
27+
28+
## Fit with PAI's values
29+
30+
Please confirm this proposal is consistent with the project's principles:
31+
32+
- [ ] **Privacy-first** — does not require sending user data to third parties
33+
- [ ] **Offline-first** — works without a network connection, or degrades gracefully
34+
- [ ] **Minimalism** — adds capability proportional to its maintenance cost
35+
- [ ] **Reproducibility** — behavior is deterministic and inspectable
36+
37+
If any box is unchecked, explain the tradeoff below.
38+
39+
## Would you be willing to contribute this?
40+
41+
- [ ] Yes — I'd like to implement it
42+
- [ ] Maybe — with guidance or a co-maintainer
43+
- [ ] No — I'm only filing the request
44+
45+
## Additional context
46+
47+
Links, screenshots, references to prior art, or any other context that
48+
would help reviewers understand the request.

‎.github/ISSUE_TEMPLATE/feature_request.yml‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: Feature Request
2+
description: Propose a new feature or improvement
3+
labels: ["enhancement"]
4+
body:
5+
- type: textarea
6+
id: problem
7+
attributes:
8+
label: Problem Statement
9+
placeholder: "What problem does this solve? Who is affected?"
10+
validations:
11+
required: true
12+
13+
- type: textarea
14+
id: solution
15+
attributes:
16+
label: Proposed Solution
17+
validations:
18+
required: true
19+
20+
- type: textarea
21+
id: alternatives
22+
attributes:
23+
label: Alternatives Considered
24+
placeholder: "Other approaches you've thought about"

‎.github/ISSUE_TEMPLATE/hardware_compat.yml‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
name: Hardware Compatibility Report
2+
description: Report whether PAI works on your hardware
3+
labels: ["hardware-compat"]
4+
body:
5+
- type: input
6+
id: machine
7+
attributes:
8+
label: Machine Make / Model
9+
placeholder: "e.g. Dell XPS 15 9500"
10+
validations:
11+
required: true
12+
13+
- type: input
14+
id: cpu
15+
attributes:
16+
label: CPU
17+
placeholder: "e.g. Intel Core i7-10750H"
18+
validations:
19+
required: true
20+
21+
- type: input
22+
id: wifi
23+
attributes:
24+
label: Wi-Fi Chipset
25+
placeholder: "e.g. Intel Wi-Fi 6 AX201 (run: lspci | grep -i wireless)"
26+
27+
- type: input
28+
id: gpu
29+
attributes:
30+
label: GPU
31+
placeholder: "e.g. NVIDIA GTX 1650 / Intel UHD 630"
32+
33+
- type: input
34+
id: version
35+
attributes:
36+
label: PAI Version
37+
placeholder: "e.g. v0.1.0"
38+
validations:
39+
required: true
40+
41+
- type: dropdown
42+
id: status
43+
attributes:
44+
label: Compatibility Status
45+
options:
46+
- "Works fully"
47+
- "Works with issues"
48+
- "Broken / does not boot"
49+
validations:
50+
required: true
51+
52+
- type: textarea
53+
id: notes
54+
attributes:
55+
label: Notes
56+
placeholder: "Anything that needed workarounds, partial issues, etc."

‎.github/ISSUE_TEMPLATE/question.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Question
3+
about: Ask a question — but check Discussions first
4+
title: "[q] "
5+
labels: ["question"]
6+
---
7+
8+
## Have you checked…
9+
10+
- [ ] The [FAQ](../../FAQ.md)
11+
- [ ] The [docs](../../docs/)
12+
- [ ] [GitHub Discussions](../../discussions)
13+
- [ ] Existing [issues](../../issues?q=is%3Aissue) (open and closed)
14+
15+
## Your question
16+
17+
Ask in plain prose. The more specific, the better the answer.
18+
19+
## What you've tried
20+
21+
A short list of things you already attempted or read. This helps us
22+
avoid repeating advice you've already seen.
23+
24+
-
25+
-
26+
27+
## Environment (if relevant)
28+
29+
- PAI version / commit:
30+
- Architecture (ARM64 / AMD64):
31+
- OS:
32+
33+
---
34+
35+
**For open-ended or long-running questions, please use
36+
[GitHub Discussions](../../discussions) instead of Issues.** Issues are
37+
reserved for actionable, bounded work items (bugs, features, concrete
38+
questions with a clear answer).

‎.github/ISSUE_TEMPLATE/security_vulnerability.md‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
name: Security vulnerability — STOP
3+
about: Do NOT report vulnerabilities here. Read this template first.
4+
title: "[DO NOT FILE] Security issue"
5+
labels: ["security", "do-not-file"]
6+
---
7+
8+
> **Stop. Do not submit this form.**
9+
>
10+
> Public security issues put PAI users at risk. Please report
11+
> vulnerabilities privately by following the instructions in
12+
> [SECURITY.md](../../SECURITY.md). If you have already started this
13+
> form, close it without submitting.
14+
15+
---
16+
17+
## Where to report
18+
19+
- **Email:** `contact@pai.direct` (see SECURITY.md for current address)
20+
- **PGP key:** fingerprint and key block are published in
21+
[SECURITY.md](../../SECURITY.md)
22+
- **GitHub private advisory:** use the
23+
[Security tab → "Report a vulnerability"](../../security/advisories/new)
24+
25+
## What to include
26+
27+
To help us triage quickly, please provide:
28+
29+
- Affected PAI version or commit
30+
- Architecture (ARM64 / AMD64) and environment
31+
- Clear reproduction steps or proof-of-concept
32+
- Impact assessment (what an attacker could do)
33+
- Suggested fix or mitigation, if you have one
34+
35+
## Expected response time
36+
37+
- **Acknowledgement:** within 3 business days
38+
- **Initial assessment:** within 7 business days
39+
- **Status updates:** at least every 14 days until resolution
40+
41+
## Coordinated-disclosure timeline
42+
43+
We follow a standard 90-day coordinated-disclosure window. We may
44+
request an extension for complex issues; we will not extend silently.
45+
Public disclosure happens jointly when a fix ships, or at the end of
46+
the window — whichever comes first.
47+
48+
## Hall of fame
49+
50+
Reporters who follow responsible disclosure are credited in
51+
[ACKNOWLEDGMENTS.md](../../ACKNOWLEDGMENTS.md) (opt-in). We do not run
52+
a paid bounty program at this time.
53+
54+
---
55+
56+
**Reminder:** close this tab without submitting. Use the private
57+
channels above instead.

0 commit comments

Comments
 (0)