Packaging: define a COPR-first distribution path
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
Research direction
The issue names no files, scripts or tests, so start by reading the README and any existing install instructions to see what packaging exists today. Settle the repo layout and release expectations with a maintainer before editing anything. Done means a maintainer-facing COPR doc and any agreed metadata changes, with the scope confirmed in the issue thread.
Written by the indexing model from the issue text.
Description
Document and prepare the COPR path as the first serious package distribution channel.
Scope:
- required repo structure assumptions
- build/release expectations
- docs for maintainers
- any metadata or packaging tweaks needed first
Goal:
Make COPR the first realistic packaged install route.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 5
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 graygarbage/HermesKey
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
graygarbage/HermesKey#21 ·
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
graygarbage/HermesKey#23 ·
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 48/100
graygarbage/HermesKey#24 ·
-
enhancement ux
Difficulty 4/5 3-5 days Newbie friendliness 25/100
graygarbage/HermesKey#16 ·
-
enhancement packaging
Difficulty 3/5 Half a day Newbie friendliness 40/100
graygarbage/HermesKey#15 · 1 comment ·
All issues in graygarbage/HermesKey
Similar issues
-
area:install bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-test-pipelines#307 ·
Maintainers usually reply within 2 days
-
Webcam overlay freezes during voxtype dictation while screen recording (pause_media pauses the overlay mpv)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
TYPO3BestPractices/tea#2409 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
msys2/MSYS2-packages#6825 ·
Maintainers usually reply within 1 day