Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

Socrates Tzagiousis
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "i3-gaps"

* Package name    : i3-gaps
* Version         : 4.16.1-1
* Upstream Author : Ingo Bürk (Airblader)
* URL             : https://github.com/Airblader/i3
* License         : BSD-3-clause
* Section         : x11

It builds those binary packages:

   i3-gaps - Fork of i3-wm with extra features such as gaps

To access further information about this package, please visit the following URL:

   https://mentors.debian.net/package/i3-gaps

Alternatively, one can download the package with dget using this command:

   dget -x https://mentors.debian.net/debian/pool/main/i/i3-gaps/i3-gaps_4.16.1-1.dsc

More information about i3-gaps can be obtained from: 

https://github.com/Airblader/i3/blob/gaps/README.md Changes since the last upload: * Initial release (Closes: #909646) Regards, antisocrates
Reply | Threaded
Open this post in threaded view
|

Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

Dominik George-7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

On Mon, Jun 17, 2019 at 04:10:03AM +0300, antisocrates wrote:
> I am looking for a sponsor for my package "i3-gaps"

Thanks for your contribution! I looked into your package and have the
following remarks:

 * Did you talk to the i3-wm maintainer, Michael Stapelberg, about his
   opinion on this, and also about ways how to avoid the conflict
   between the packages and instead enable it to co-exist?

 * Your Recommends is a bit too "fat" IMHO. I would suggest keeping
   all that stuff aligned with the i3-wm package, and leave everything
   else to the i3 meta package. After upload, you can then ask the i3
   maintainer to include your i3-gaps package as alternative
   dependency in his i3 meta-package.

 * Please add a paragraph about what i3 is to your package
   description, not only the differences in i3-gaps.

 * Your d/copyright lists i3wm upstream as source rather than the fork,
   and also lists the original author as upstream contact. It should
   point to the GitHub source repo and list Ingo Bürk as upstream
   contact, While at it, please also look into whether Michael
   Stapelberg is the only copyright holder. At least Ingo's changes
   might be big enough to be separate copyrightable work. How did you
   verify the information you put into d/copyright?

 * I would prefer to have your packaging repository on
   salsa.debian.org.

 * Hmm, two almost exact copies of the same code in Debian in two
   conflicting packages? i3-gaps is a widely accepted fork I suppose,
   yes. What is Michael's opinion on that?

Please go through my remarks and comment each of them with what you
think about it, and whether you implemented it, will do so or
won't.

Cheers,
Nik
-----BEGIN PGP SIGNATURE-----

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl0HcsUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTylvB8D/0QzHlAilO3kt+nqsvRSQVxqZX1GUYcbvFRbCtxkoHuBAIOrcqPoK7v
JtRuDUbz+WkCtgf8o/qC22dytDHx9u4dTdidJu9htw5owJoFJB29ZpFPU9zRXRw+
kD+Fky3TsnvR4GxRIgrepOnQuvewvxBC37g+IteqELHHSG6YRN/JE0g1O5DZ2gV4
H8ngf1+P5jAASvEZmhfATfQdlyIQxiplTPd2P1vW/ux8nIYwpxBfIjfqeBw60PQB
Dfjmnw0woQEWq05oZCJjUDPpV6sHoJmwiu/tJgqw87T2+yoxPezPNOJARqpoc6C3
FOnVl8BTDmlpOOogsWzyAbLtzMrFREZiSet2HmbWUiapZb1drR1RrCUQzlc0oZy5
ohWhh4O/MdJtR1OYkp+654H6253jHltHULc1uWnyjrkNvsvTyQ0CPsj7Qac54Lj5
XMYtnGvDB3fiJ8zTZDoQR5CC2S+Raue+5d8Np6Dyepo3B2W3qaERKWeni8miCNxI
bBA1Hr83mN53KkUaZotFRipwjCtj8LWj4R4RvyB3KCu1p1dPdQAUvMYQepl9uXGp
xCBlWC1bLbZ40yzCBd2Oz2F5DX5vg2nxAEDxxajPWeGuY7YpS+iAmn9/C4p7Kj4/
d07OqHrwh0P8w3kqxlTkhjSIs8r+7PbN7mz/qR8LCvFhAAvLc6aLJw==
=rliv
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Bug#930633: RFS: i3-gaps/4.16.1-1 [ITP]

Dominik George-7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> Thanks for your contribution! I looked into your package and have the
> following remarks:

Oh, plus, also please fix the issues listed on your package's mentors page as
well, obiously ☺.

- -nik
-----BEGIN PGP SIGNATURE-----

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl0Hc8wxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTyloqYEACPi2ZqDp5UT/W7u7sPTr8LimxDciPELohPI4qb0RHGTAT4qpkROeUZ
g02E981VpzGrnZ5ycAMxArZKYwGs5lidnsmiyA0ilQDkmeLoE864Rrj9BQUy7YpY
bZkk6nzx8iMOd3lURzj7jvIWrDWiVXaABGIrDZA4DbuDzze7T9E293Z24szvUCn6
VqJJ7CivDwcKYHXzwsAAfj5vsUT3CFa2UCy1ycbFUjCWMNVA2DUg1f+2OeoO7/cI
krnsnRltoTbqvJGHJh8UJwrDT/UVZ2x57s0hj7lRBQ2mzfOXLdqXRjaO/DWrQelZ
HyNHL8zf6PWlZnulHDIiPXZvEWeiT5xIzbHSWToL+uNtF+MzjGpSGvALkYtaAP3T
avy7WX5yjeKQ5VZD8fBVutYaRQSDaSQmspeESgHOF3AXjDQKth+R8+YmkZy2QmYq
zSS7B9F5Qc+3NtV7GbGo39+jQ6kGjNnmx+upryUfOl32TvirR0YG+2BjjC9TP6is
CAINW8xx+eV5kWShDhnwrTFbOQ4BFUA+DO9G1/dOkjuy2D1PxsQm8GuAYUTY6/tw
I2u/bHtWfnnEGvgfU6zTcWqoJygS4uQJp5koG5I9FosLkckE90/d2rS2i+V7zKkc
Jve5M22cP/mUTN6A2qAmmwuKP1dV+8KC8KxfrrG9r4SUCrdLhmluUQ==
=+Aqo
-----END PGP SIGNATURE-----

Reply | Threaded
Open this post in threaded view
|

Bug#930633: i3gaps

Socrates Tzagiousis
In reply to this post by Socrates Tzagiousis
A surprise, to be sure, but a welcome one.

Personally, seeing the popularity of vanilla i3 and by extension i3-gaps (which some people prefer aesthetically) in conjunction with the combined userbase of debian and all of its offspring, it became apparent i3-gaps should have been available sooner in debian.

If one was to graph the users the users of the debian-family of distributions and every other distribution family out there, it becomes clear that a lot of people might be missing something they are used to using elsewhere (most other big families of distributions have the fork available as can be seen here: https://repology.org/project/i3-gaps/versions).
And a lot of people have real trouble compiling this piece of software from source (mostly new linux users of the debian-derivatives).
Therefore since i use debian from time to time, when my gentoo box is occupied compiling for 12 hours straight, it occured to me i should package i3-gaps for debian and therefore all its derivatives to give people easy access.

Certainly, a merge is the superior solution and i am glad its actually being considered, but my understanding is that code refactoring/cleaning could take a considerable amount of time, and therefore the package should actually be available as a temporary solution for all those who want to use it, as it currently is everywhere else.

Again, i congratulate Michael and Ingo for their work.
Reply | Threaded
Open this post in threaded view
|

Bug#930633: i3gaps

Dominik George-7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Control: tags -1 = moreinfo
Control: noowner -1

Hi,

> Certainly, a merge is the superior solution and i am glad its actually
> being considered, but my understanding is that code refactoring/cleaning
> could take a considerable amount of time, and therefore the package should
> actually be available as a temporary solution for all those who want to use
> it, as it currently is everywhere else.

I am hereby refraining from sponsoring your upload:

 1. You did not respond to my remarks (yet)
 2. Both upstreams said the fork is of minor code quality
 3. Efforts are being made to fix that
 4. Debian stable is not for temporary solutions

You might find someone else to sponsor your upload, so I leave this
bug open. Please keep in mind that in the case that someone uploads
your package, you are responsible to keep it updated, and probably
manually fix all issues yourself if upstream decides to work on
vanilla i3 instead, and are also responsible for tidying up once the
fork is merged into i3 itself if that happens ☺.

Again, thanks for your contribution, though!

Cheers,
Nik
-----BEGIN PGP SIGNATURE-----

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl0IyLUxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTylilTD/4ubM8khtlVi9O2j0z0bOLAxJeCHpJnq5Xlw53nIxbWWd5zTeOpY9rH
XnQoC9lv5vRVt9Pvd8Y1G0jCy/LKDtboroQQ0VheCPmTXjdHghlhU17utDGjuNlM
MYhvSXd0RZgSCfmUy+kxTq7UJ8Z0GfqgAObAe8Xo/t2YjTBCe5gPP/x4yJMOi43S
GoxU/YJX/iD4p+3lZBzBfPHFnrs4gPGRsdn6YrI6+f7Y9OT/8rpYMyyWeceb8h1r
8uzYm+TZjN9hKq7yRAxySoeSNvO5iCDtnw3kpCdvH1pQlK/G9jFWM7OToyxxHpJM
ESR1CNhvPsj78Nf+HkN1wWN7p5kf4OhOo9BQR1WMqmJ2hsVCHtWCwhQcR7mROcP/
8ZOFUDnBTPY7GVMQYRxRXG3ix9F83hWeRNbcDyVOB8bFFZhRtUeuWbblxSZ13+9/
ElHEIl8hffr4lRfMd7PVO41WyN6qjUG1GqdFgbdb0VKm2djKI2741WYLhFFsS2Jz
KvjYO0qSHEa8HMS/P2jCz1Ai+xBjQST4SS/2nyZFPFmfUj5VJ+bJClXcwzP7neoA
DKGA5GYDzXK+msTdwhxfbDALZveDozTajcZ7kKitCtjLn7GW0I+ITtIWs1DgzjOf
RAfx22/U86kwd3SOi3aVuh4WrQzxVycgPW1523omPkad/07NBfRt6g==
=/4OK
-----END PGP SIGNATURE-----