❦ 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
sponsors
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 of
❦ 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
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
versio
❦ 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 distribut
> 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
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 easil
7 matches
Mail list logo
