![]() We made it a condition that porting gaps into i3 would have to resolve these issues. ![]() It caused a few issues and had some drawbacks. ![]() However, the original gaps patch was focused on being small and easy to maintain. Clearly the fork was popular, and as someone else pointed out here as well, the Wayland "port" of i3, sway, added gaps from the beginning on with great success. Whilst originally gaps were considered an "anti feature" for i3, years ago we already decided that we'd accept adding gaps into i3. From there it became popular and I took on the maintainership, eventually contributing to i3 itself and finally becoming a maintainer there as well. I took on i3-gaps by taking an existing patch and rebasing it to the latest i3 HEAD. ![]() The story of this merge is not only several years long, but a true success story in OSS in my eyes. I'm the maintainer of i3-gaps and also a maintainer for i3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |