requesting Cairo Dock for Budgie ahead of Wayland
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
Please confirm there isn't an open request for this package
- I have searched through package addition requests
Homepage
Maintainer
- Would you like to be the maintainer for this package?
Why should this be included in the repository?
Plank will not be compatible with Wayland Budgie and Budgie will need a dock ahead of Wayland. Many of your Solus Budgie users including me are hesitant to install kde-based docks on their Budgie DE...that is if kde docks will be the only dock options going forward. Cairo is a non-KDE dock compatible with Wayland. Seems sensible to have that
Are we allowed to redistribute it?
Cairo-Dock/cairo-dock-core is licensed under the GNU General Public License v3.0
What kind of user will use this package, and how many users do you think will use this package?
The kind of user that will use this package are likely Budgie users that want a Budgie-integrated, non-kde, non-flatpak dock option when Budgie-Wayland arrives, as Plank will be unusable. Thanks for any consideration.
Link to source archive file
cairo-dock-core-3.6.1.tar.gz.asc at https://github.com/Cairo-Dock/cairo-dock-core/releases/tag/3.6.1
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing cairo-dock-core-3.6.1.tar.gz.asc and the package repository's package-addition process. Confirm the source, GPLv3 redistribution, and stated Budgie/Wayland use case; done means the package request has a clear resolution or a documented blocker.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100