Something I mentioned on GitHub, to clarify someone who was confused as to why their feature request was shot down (even with a patch attached).
The window management code of sway is basically closed to further enhancements. This has been an unspoken policy for a while now. We only merge bugfixes and otherwise we track i3 releases upstream.
Expanding sway into a giant kitchen sink is not my goal. We need to at some point become conservative with our changes, or else the runaway complexity will ruin the software. Eventually sway should be "done", in my opinion.
There is still room for improvement, but that is mainly limited to the domains in which i3 is not: the parts of sway (and wlroots) which replace the role of the Xorg server. To this end, we're building improvements around screen capture, VR support, and so on. We also continue to see lots of investment in wlroots, and I expect it will continue to mature for a long time.
Introducing shell access to builds.sr.ht VMs
DRM leasing: VR for Wayland
Replay the moon landing live (50 years latency) over the next several hours
weston 7.0 alpha has been released!
mako 1.4 is now available!
annotatesh will generate sr.ht annotations for you shell scripts:
Right now only builtins and POSIX utilities are supported, function references are planned.
I've been working on an automatically generated EDID library  based on kaitai . Still wondering whether it's a good idea.
Anyone knows about other generators for binary formats?
Announcing code annotations for SourceHut