Package request: Pixelorama
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- build-system
Research direction
Start by reviewing the repository's package requirements and the Pixelorama project at the linked homepage, including its release information. Identify the existing package template or build conventions that apply; done means a Pixelorama package can be built and installed according to the repository requirements.
Written by the indexing model from the issue text.
Description
Package name
pixelorama
Package homepage
https://github.com/Orama-Interactive/Pixelorama
Description
Pixelorama is a pixel art multitool; it is well-suited for artists, animators, and game-devs alike.
The Void Repo's pixel art software are either irregularly maintained or lack the feature-set standardized by software like Aseprite. Pixelorama might even exceed Aseprite in functionality: with non-destructive editing and 3d layers as an example. I'm not sure it meets the package requirements, but I must vouch for it's inclusion because of the reasons provided.
Does the requested package meet the package requirements?
Compiled
Is the requested package released?
Yes
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 2.8k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 325
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 void-linux/void-packages
-
bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
void-linux/void-packages#63249 · 3 comments ·
Maintainers usually reply within 1 day
-
xmlto: sources no longer available from upstreamPossibly taken @L1TerminalFault claimed this 4 days ago. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63237 ·
Maintainers usually reply within 1 day
-
AI 🤖 bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
void-linux/void-packages#63041 · 1 comment ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63016 ·
Maintainers usually reply within 1 day
-
nextcloud-client: VFS plugins installed where the client does not searchMay be free again A pull request for this issue was closed without being merged. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
void-linux/void-packages#62700 ·
Maintainers usually reply within 1 day
All issues in void-linux/void-packages
Similar issues
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ysb3996-blip/oops#51 ·
Maintainers usually reply within 1 day
-
luaebpf: the by-example page's intro names two outcomes of a lowering and omits the stop with the default verdictPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation severity: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
luainkernel/lunatik#2231 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dataiku/kiji-proxy#668 ·
Maintainers usually reply within 2 days
-
diagnostics good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Remove leftover Cloud66 custom_web process from ProcfilePossibly taken @ShahadatTest claimed this today. OpenDifficulty: Easy Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
rubyforgood/casa#7330 · 1 comment ·
Maintainers usually reply within 1 day