Epic: extract bricks to their own repositories
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
Research direction
This is an epic that tracks several brick extractions, so there is no single file to start from. Read the linked issues #80, #78 and #77 first to see how the Gaya extraction and the CI boundary check are being handled. Pick one unclaimed child task, such as the OBJ importer in #303, and confirm its scope with a maintainer before starting. Done means that brick builds, tests and releases on its own, and CI fails when the engine references its code directly.
Written by the indexing model from the issue text.
Description
Current State
Bricks are the unit of optional engine functionality. Those with an independent release cadence should live in their own repositories, the way Gaya is being extracted (#80, #78) and the KTX2 and OAP libraries already were.
Tasks
- #303 OBJ importer
- KTX2 and OAP: consume the published packages (#31)
- #302 Localization
- #278 ASTC texture bake (editor brick)
- #254 Android brick, after .NET 11 GA
- #304 In-game UI brick
- For each: publish a package, consume it from Turian, enforce the boundary in CI (#77)
Acceptance Criteria
- Each extracted brick builds, tests and releases independently, and CI fails if the engine references its code directly.
Related
#80, #78, #77, #47
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 29m
- Merged PRs (30d)
- 38
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:high size:L t:feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
-
c:build c:editor p:medium size:XL t:feature
Difficulty 5/5 Over a week Newbie friendliness 5/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
Similar issues
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
[Bug]: Edit Bar buttons are not localizedPossibly taken @idumlupinar claimed this today. OpenStatus: New
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dnnsoftware/Dnn.Platform#7565 ·
Maintainers usually reply within 1 day
-
AzureBlobSnapshotStore.LoadAsync allocates the snapshot twice (growable MemoryStream + ToArray)Openenhancement
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
bug ui-only
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-cs#689 ·
Maintainers usually reply within 2 days