Bug#930557: i3-gaps RFS/ITP
❦ 3 October 2021 09:16 +02, Michael Stapelberg: > I will stress one more time that what we need here is not a one-time > sponsorship offer, but a multi-year commitment for maintaining the > i3-gaps package in Debian. Let's hear from antisocrates. I can offer a multi-year commitment for sponsorship and take over maintainance if needed. I can also maintain it myself. I suppose you would favor i3-gaps to conflict with i3-wm instead of trying to be co-installable (with or without alternatives as the difference is limited to a few binaries and I think this does not include i3-msg). -- Must I hold a candle to my shames? -- William Shakespeare, "The Merchant of Venice"
Bug#930557: i3-gaps RFS/ITP
Personally, I don’t want gaps to be built from src:i3-wm. It’s enough work to maintain one version of i3. That said, sur5r is doing all of the Debian work since I retired from Debian, so it’s ultimately up to him. I will stress one more time that what we need here is not a one-time sponsorship offer, but a multi-year commitment for maintaining the i3-gaps package in Debian. On Sun, 3 Oct 2021 at 08:57, Vincent Bernat wrote: > ❦ 3 October 2021 08:48 +02, Michael Stapelberg: > > > I still think it’d be better to spend time on merging gaps rather than > > packaging gaps, > > but it seems like nobody has the skill set and/or motivation. > > This is a very different skillset from packaging. > > > Is there someone who would continuously maintain i3-gaps in Debian? > > I wouldn’t want that package to diverge from upstream i3 in terms of > which > > version is available in Debian. > > Alternatively, src:i3-wm could build both i3-wm and i3-gaps. It adds > extra work on existing maintainers but maybe you and Jakob would be OK > with that? I can propose a patch for that if it helps. > -- > Use recursive procedures for recursively-defined data structures. > - The Elements of Programming Style (Kernighan & Plauger) > -- Best regards, Michael
Bug#930557: i3-gaps RFS/ITP
❦ 3 October 2021 08:48 +02, Michael Stapelberg: > I still think it’d be better to spend time on merging gaps rather than > packaging gaps, > but it seems like nobody has the skill set and/or motivation. This is a very different skillset from packaging. > Is there someone who would continuously maintain i3-gaps in Debian? > I wouldn’t want that package to diverge from upstream i3 in terms of which > version is available in Debian. Alternatively, src:i3-wm could build both i3-wm and i3-gaps. It adds extra work on existing maintainers but maybe you and Jakob would be OK with that? I can propose a patch for that if it helps. -- Use recursive procedures for recursively-defined data structures. - The Elements of Programming Style (Kernighan & Plauger)
Bug#930557: i3-gaps RFS/ITP
I still think it’d be better to spend time on merging gaps rather than packaging gaps, but it seems like nobody has the skill set and/or motivation. Is there someone who would continuously maintain i3-gaps in Debian? I wouldn’t want that package to diverge from upstream i3 in terms of which version is available in Debian. I’m asking in particular because people might switch from X11+i3 to Wayland+sway over the next few years. On Sun, 3 Oct 2021 at 08:35, Vincent Bernat wrote: > ❦ 17 June 2019 18:30 +02, Michael Stapelberg: > > > Ingo will outline what needs to be done to get i3-gaps into a mergable > > state, so that we can eventually bring these features to all i3 users. > > > > For the time being, our recommendation is to NOT add i3-gaps to Debian or > > any other Linux distribution. Instead, if you have time and motivation, > > please consider helping improve i3-gaps with the goal of a merge. > > It seems there is not much progress on this front. The issue on GitHub > does not show activity either. As other popular desktop distributions > (Fedora, openSuSE, Arch and Manjaro) are providing a i3-gaps package, > maybe an i3-gaps package in Debian could be reconsidered? > > I would gladly sponsor it if there is no strong opposition from i3 > maintainers. > -- > Write and test a big program in small pieces. > - The Elements of Programming Style (Kernighan & Plauger) > -- Best regards, Michael
Bug#930557: i3-gaps RFS/ITP
❦ 17 June 2019 18:30 +02, Michael Stapelberg: > Ingo will outline what needs to be done to get i3-gaps into a mergable > state, so that we can eventually bring these features to all i3 users. > > For the time being, our recommendation is to NOT add i3-gaps to Debian or > any other Linux distribution. Instead, if you have time and motivation, > please consider helping improve i3-gaps with the goal of a merge. It seems there is not much progress on this front. The issue on GitHub does not show activity either. As other popular desktop distributions (Fedora, openSuSE, Arch and Manjaro) are providing a i3-gaps package, maybe an i3-gaps package in Debian could be reconsidered? I would gladly sponsor it if there is no strong opposition from i3 maintainers. -- Write and test a big program in small pieces. - The Elements of Programming Style (Kernighan & Plauger)
Bug#930557: i3-gaps RFS/ITP
> 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 don’t think having it available temporarily is a good idea. It complicates the situation both for the package maintainers and for end users. -- Best regards, Michael
Bug#930557: i3-gaps RFS/ITP
Hey, thanks everyone for reaching out. The interest in making i3-gaps available to more people has prompted some discussion between Ingo (the maintainer of the i3-gaps fork, and an i3 core maintainer) and me. The key concern about the i3-gaps fork is code quality: the implementation cannot easily be merged into i3 as-is. One example is that you cannot enable gaps and display title bars at the same time. The intention behind publishing the fork was to make the feature available to people who can live with the lower code quality and restrictions, not to have a long-term sustainable fork. Ingo will outline what needs to be done to get i3-gaps into a mergable state, so that we can eventually bring these features to all i3 users. For the time being, our recommendation is to NOT add i3-gaps to Debian or any other Linux distribution. Instead, if you have time and motivation, please consider helping improve i3-gaps with the goal of a merge. Thank you, -- Best regards, Michael
