Epic: package registry alpha (signed packages, CLI install, Studio Packages panel)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 5/100
Research direction
This is a multi-part epic covering a registry service, CLI install via turian brick, Studio Packages panel, and a design note tied to #197. Start by reading the existing turian brick command and the closed plugin/package epic #74 to understand current brick management. The work is design-heavy with no defined scope for a first change, so pick a specific sub-task and open a focused issue before coding. Done means the epic's acceptance criteria are met: a signed official package installs from Studio and CLI, and a tampered package is rejected.
Written by the indexing model from the issue text.
Description
Current State
turian brick manages installed bricks, and the plugin and package epic (#74) is closed. There is no package registry that Turian can query, and Studio has no panel to browse or install packages.
Tasks
- Registry service with signed packages and scoped tokens
- CLI install and update from the registry (
turian brick) - Official packages published and signed by the project
- Studio "Packages" panel reading the registry
- Design note: package overrides and replacement assets, and a compatibility contract for bricks across engine versions (#197)
- Free packages only in this epic; paid packages get their own epic later
Acceptance Criteria
- A user installs an official signed package from Studio and from the CLI, and a tampered package is rejected.
Related
#74, #197, brick extraction epic
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:build p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
c:build c:ui p:low size:L t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:assets c:build p:low size:S t:refactor
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
c:build c:engine p:medium size:M t:refactor
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
area-signalr
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dotnet/aspnetcore#69842 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 2 days
-
bug needs-triage
Difficulty 2/5 Under an hour Newbie friendliness 78/100
microsoft/microsoft-ui-reactor#1373 ·
Maintainers usually reply within 1 day
-
Client customer-reported KeyVault needs-team-attention question Service Attention
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Azure/azure-sdk-for-net#63861 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day