07:27wlb: weston Merge request !1527 merged \o/ (Fix indentation of a few files https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1527)
07:27wlb: weston/main: Leandro Ribeiro * libweston: fix indentation of a few files https://gitlab.freedesktop.org/wayland/weston/commit/bcd76c372b42 libweston/ color-management.c color-properties.c id-number-allocator.c
07:39wlb: weston Issue #916 closed \o/ (Git tag 13.0.1 was moved https://gitlab.freedesktop.org/wayland/weston/-/issues/916)
09:27wlb: weston Merge request !1528 opened by Marius Vlad (mvlad) build: bump to version 13.0.2 for the point release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1528
10:37wlb: weston Merge request !1529 opened by Marius Vlad (mvlad) gitlab-ci.yml: Update CI_BUILD_REF_NAME https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1529 [CI]
11:09wlb: weston Merge request !1518 merged \o/ (A few enhancements to the toytoolkit event loop https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1518)
11:09wlb: weston/main: Leandro Ribeiro * clients: make main event loop more robust https://gitlab.freedesktop.org/wayland/weston/commit/2ac577731640 clients/window.c
11:27wlb: weston/13.0: Pekka Paalanen * CI: work around LeakSanitizer crashes with use_tls=0 https://gitlab.freedesktop.org/wayland/weston/commit/fc0419609e16 .gitlab-ci.yml .gitlab-ci/leak-sanitizer.supp tests/meson.build
11:27wlb: weston/13.0: Marius Vlad * build: bump to version 13.0.2 for the point release https://gitlab.freedesktop.org/wayland/weston/commit/86c636d8173f meson.build
11:27wlb: weston Merge request !1528 merged \o/ (build: bump to version 13.0.2 for the point release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1528)
11:43wlb: weston New tag: 13.0.2 https://gitlab.freedesktop.org/wayland/weston/tags/13.0.2
12:22wlb: weston Merge request !1530 opened by Marius Vlad (mvlad) build: bump to version 13.0.3 for the point release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1530
12:49wlb: weston Merge request !1530 merged \o/ (build: bump to version 13.0.3 for the point release https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1530)
12:49wlb: weston/13.0: Marius Vlad * build: bump to version 13.0.3 for the point release https://gitlab.freedesktop.org/wayland/weston/commit/8cb33a19163b meson.build
13:09wlb: weston New tag: 13.0.3 https://gitlab.freedesktop.org/wayland/weston/tags/13.0.3
13:11wlb: weston Issue #661 closed \o/ (10.0.93: documentation build fails with doxygen 1.9.5 https://gitlab.freedesktop.org/wayland/weston/-/issues/661)
13:12wlb: weston Issue #917 opened by Tomasz Kłoczko (kloczek) 13.0.2: documentation build fails https://gitlab.freedesktop.org/wayland/weston/-/issues/917
14:25wlb: wayland.freedesktop.org Merge request !81 opened by Marius Vlad (mvlad) release: Weston 13.0.2 and Weston 13.0.3 bug fix release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/81
14:28wlb: wayland.freedesktop.org Merge request !81 merged \o/ (release: Weston 13.0.2 and Weston 13.0.3 bug fix release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/-/merge_requests/81)
14:28wlb: wayland.freedesktop.org/main: Marius Vlad * release: Weston 13.0.2 and Weston 13.0.3 bug fix release https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/commit/59c8e8913a87 releases.html
14:41KarenTheDorf: What's the criteria for a protocol to be in 'staging' vs 'unstable'?
14:44zzag: unstable is obsolete
14:44zzag: new protocols should go to "staging"
14:52KarenTheDorf: Well that's simple. :D
15:01KarenTheDorf: I assume truely unstable stuff now lives out-of-tree, and staging is for things that are sufficently implemented cross-compositor or otherwise on-track to end up as stable?
15:09wlb: weston Issue #916 closed \o/ (Git tag 13.0.1 was moved https://gitlab.freedesktop.org/wayland/weston/-/issues/916)
15:16wlb: weston Issue #729 closed \o/ (Weston test suite is failing - EGL Surfaceless platform cannot be used https://gitlab.freedesktop.org/wayland/weston/-/issues/729)
18:44ids1024_: KarenTheDorf: I don't know if there's a set rule, but it seems generally protocols that are meant to be used by multiple compositors should be proposed to wayland-protocols. While out-of-tree protocols should generally be compositor-specific and prefixed with the compositor. The "truely unstable" version of the protocol is the one in a merge request to wayland-protcols that hasn't
18:44ids1024_: been merged yet.
18:47KarenTheDorf: Got it. xdg-decoration is 'unstable' but it seems widely supported by those DEs that wish to support it, so I should be fine to use it I guess. :crossed_fingers:
18:47ids1024_: Or in other words: if you want to propose a protocol to be implemented by multiple compositors, open an MR on wayland-protocols adding it to `staging`.
18:49ids1024_: Even if a new breaking version of xdg-decoration (xdg-decoration-unstable-v2) is released, generally compositors wouldn't stop supporting xdg-decoration-unstable-v1.
18:50KarenTheDorf: Oh I'm not brave enough yet for adding new protocols. (And kwin has stopped supporting kde-server-decoration, which is why I had a minor concern)
18:51KarenTheDorf: It's basically the same as xdg-decoration-v1 except for the interface names afaict
19:25daniels: yeah it’s fine to use that one
20:49zzag: KarenTheDorf: kwin still supports the kde protocol
20:50KarenTheDorf: *checks wayland-info* Huh! It does! I don't know why I thought it didn't!
20:51KarenTheDorf: But I've ported my library to xdg now so I have no use for this now-corrected misconception. :)
21:09emersion: KarenTheDorf: it's not the same, with xdg the compositor is in full control
21:37KarenTheDorf: emersion: Is it? I guess the comments suggest the server should honor the request? Regardless, I have my code set to just say "screw it, you're only getting fullscreen" if either 1) xdg-decoration isn't supported or 2) It is but the server insists on client anyway
21:41KarenTheDorf: One day I might implement libdecor
21:45kennylevinsen: KarenTheDorf: in xdg decoration, what the client specifies is just a preference. The server decides and is free to disregard the client preference, and may change its decision at will.
21:47KarenTheDorf: I thought that was how the kde one worked as well given the requests and events, but one of the comments does seem to imply it's not optional for the server to refuse. (I say that like there isn't one server that will ever implement it, kwin)