Bug#1008816: ITP: kwin-bismuth -- KDE Plasma extension for tiling windows
Blake Lee
Severity: wishlist
Owner: Blake Lee <bl...@volian.org>
X-Debbugs-Cc: debian...@lists.debian.org
* Package name : kwin-bismuth
Version : 3.0.0
Upstream Author : Mikhail Zolotukhin <ma...@gikari.com>
* URL : https://github.com/Bismuth-Forge/bismuth
* License : Expat, GPL-3+, CC-BY-4.0, LGPL-3.0+
Programming Lang: RypeScript, C++, QML
Description : KDE Plasma extension for tiling windows
Description: KDE Plasma extension for tiling windows
KDE Plasma add-on, that tiles your windows automatically
and lets you manage them via keyboard,
similarly to i3, Sway or dwm.
This package extends the kwin WM to allow for tiling windows.
I have used many different tiling scripts for kwin and in
my opinion this is by far the best one.
I plan on maintaining this on my GitLab, but I would have
no issue maintaining it with a team. I believe this is probably
an area for the KDE Extras Team.
I will need a sponsor to upload this package.
Didier Raboud
I have heard about Bismuth and would like to see it in Debian.
Le samedi, 2 avril 2022, 06.42:10 h CEST Blake Lee a écrit :
> * Package name : kwin-bismuth
> Version : 3.0.0
> no issue maintaining it with a team. I believe this is probably
> an area for the KDE Extras Team.
(Debian's Gitlab instance): https://salsa.debian.org/jgoerzen/bismuth
Would it make sense for you two to collaborate on this?
I agree it would make sense in KDE Extras, so (as I had the rights), just went
away and created a repo there:
https://salsa.debian.org/qt-kde-team/extras/kwin-bismuth
I've invited John and you to it; don't hesitate to ask if you have questions!
> I will need a sponsor to upload this package.
Didier Raboud
> As for the repo should I just mirror my current work from GitLab over to
> Salsa?
If that's working well for you, I'd say yes; having team-maintained packages
in a common location makes most things easier; including common CI test
scripts, team-at-large changes, etc.
Didier 'OdyX' Raboud
I found the repo; https://salsa.debian.org/qt-kde-team/extras/kwin-bismuth
One thing that struck me first is that the repository isn't in any of the standard git formats.
See https://dep-team.pages.debian.net/deps/dep14/ for a long description of the possibilities.
I can't remember what the Qt-KDE Extras practices is, so I checked; https://qt-kde-team.pages.debian.net/gitguidelines.html seems to be the latest recommendations.
Basically, I think it's reasonable to say that most Debian packages' repositories try to avoid mixing upstream and debian/* changes on the same branches. See https://wiki.debian.org/PackagingWithGit for some documentation on that area; specifically https://honk.sigxcpu.org/piki/projects/git-buildpackage/ git-buildpackage is pretty standard nowadays.
As for what I'm concerned, my ideal repository has an upstream/latest branch with upstream's own history, upstream/1.2.3 tags for releases, debian/latest for the changes (and initial addition) in debian/*, and debian/1.2.3-1 tags upon releases. Now, how to go there from where you are? I'd basically start a new repo from scratch, start from upstream's branch tip and reconstruct (in one commit, or more) the debian/latest branch.
Finally, another thing that will really help testing many Debian'isms before going to sid is the Salsa CI pipeline: https://salsa.debian.org/salsa-ci-team/pipeline/-/blob/master/README.md This will test many many things out-of-the-box, from the repository; so it'll also error-out early, and before reaching the Debian archive.
I'm aware this is a lot of links, and a lot of specific quirks to learn about Debian specificities. But getting them right upfront will make any and all later collaboration much easier and faster as the repository (and package) will look familiar to the rest of Debian. It's really worth going through the effort!
Best,
OdyX
2 août 2022 04:43 "Blake Lee" <bl...@volian.org> a écrit:
>
> I've moved over the repository into Salsa, updated it for the latest release `3.1.2`.
>
> I've built it on my Sid desktop with sbuild, lintian reports no errors, and it the software is
> working as expected.
>
> Let me know if you see anything you would change.
Patrick Franz
Am Dienstag, 2. August 2022, 13:34:24 CEST schrieb Didier 'OdyX' Raboud:
> Hello there,
[...]
> https://qt-kde-team.pages.debian.net/gitguidelines.html seems to be
> the latest recommendations.
with the master branch pointing to the unstable packaging.
If you want to go that route, I'd delete the repo just as Didier
suggested.
The quickest way to get help in such questions is ususally to ask on IRC
in #debian-qt-kde.
--
Med vänliga hälsningar
Patrick Franz
Didier 'OdyX' Raboud
Le dimanche, 25 septembre 2022, 04.45:58 h CEST Blake Lee a écrit :
> Apologies for it taking me so long to get to it.
No problem!
> I nuked the repo and is now a clean, one commit, repo with only the unstable
> debian files in the master branch.
Great, thanks! It was not a necessity to drop all past packaging work, but
doesn't hurt.
> I've also updated the files to build with the latest upstream release.
> Tested with sbuild that it builds successfully.
For _my_ standards, the package is still missing some thinks here and there,
which I have filed as issues on the Salsa project, under a common milestone:
https://salsa.debian.org/qt-kde-team/extras/kwin-bismuth/-/milestones/1#tab-issues
#3 can be discussed later, but the other are quite important before upload.
Comments from others welcome of course!
Best,
OdyX
Didier 'OdyX' Raboud
Le lundi, 17 octobre 2022, 04.17:59 h CEST Blake Lee a écrit :
> I hammered away basically everything but the CI. I'm not familiar enough
> with Debian's CI yet to just get it going. I'll have to research the link
> from the issue you posted when I have more time. luckily I am familiar with
> GitLab's CI in general so it shouldn't be difficult once I have a free
> block to try.
Actually, it was just a matter of configuring the repo with salsa-ci's file
(no code change), so I just went away and did that; the pipeline ran
successfully (minus the arm64 cross-build for an unrelated reason).
> I believe I got everything else the way it should be.
Yes. I commented and closed all issues on the repository (you could've done
this yourself, but no problem!).
The upload is on its way to the Debian NEW queue! Once it passes the review,
it'll be auto-built and passed on to unstable archive; but that can really
take some time, so be patient!
Best,
OdyX