Maintainer needed
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 10/100
Research direction
The issue names no files, tests, or entry points. Read the issue and surrounding repository context to determine whether ownership is available; done would require a confirmed maintainer for the package.
Written by the indexing model from the issue text.
Description
It's time for me to move on. As a random volunteer, I've felt little joy maintaining packages these past months. While I still like the technology and I still support Flatpak as a whole, I lack the motivation to actively contribute more then I've already done.
Perhaps somebody else will be able to take this role. For very important things, you can still tag me (@Eonfge) for the coming months.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 flathub/com.github.Flacon
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
flathub/com.github.Flacon#49 · 1 comment ·
All issues in flathub/com.github.Flacon
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
review-drift
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/hansei#14 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
rossoctl/lab-data-governance#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
rossoctl/serverless-harness#438 ·