@swick, @vitalyp, I think @hwentland might like to join in on the documentation from the KMS and hardware side, so I started thinking: https://email@example.com/msg367774.html
and had a discussion at #wayland: https://oftc.irclog.whitequark.org/wayland/2021-09-23
If we keep using @swick's personal fork of wayland-protocols, then it's both entangled with wayland-protocols and a personal repository. Having stuff in an unmerged non-main branch is also a bit awkward, and it is still going to be a long time until wayland/wayland-protocols!14 can land.
To me it seems like a new repository for the documentation would be best. We could give out push access to it much more easily since it would be isolated from anything else Sebastian might want to do with wayland-protocols.
There is a bit of resistance in making it an independent fd.o project straight, so we could start with a personal new repository. I could host it, or if @swick wants to? We'd set up the license, contributing instructions etc., copy in
color.rst (with history?) and delete it from MR 14.
I don't believe maintaining it in a different repository than the Wayland protocol extension would hurt. It's not a replacement for the protocol spec. The two can still be aligned and reference each other without needing intimate synchronization.
What do you think?