Repository for additional color and HDR related documentation (Re: [RFC PATCH v3 1/6] drm/doc: Color Management and HDR10 RFC)
ppaalanen at gmail.com
Thu Sep 30 13:04:30 UTC 2021
On Thu, 23 Sep 2021 10:43:54 +0300
Pekka Paalanen <ppaalanen at gmail.com> wrote:
> On Wed, 22 Sep 2021 11:28:37 -0400
> Harry Wentland <harry.wentland at amd.com> wrote:
> > On 2021-09-22 04:31, Pekka Paalanen wrote:
> > > On Tue, 21 Sep 2021 14:05:05 -0400
> > > Harry Wentland <harry.wentland at amd.com> wrote:
> > >
> > >> On 2021-09-21 09:31, Pekka Paalanen wrote:
> > >>> On Mon, 20 Sep 2021 20:14:50 -0400
> > >>> Harry Wentland <harry.wentland at amd.com> wrote:
> > >>>
> > ...
> > >
> > >> Did anybody start any CM doc patches in Weston or Wayland yet?
> > >
> > > There is the
> > > https://gitlab.freedesktop.org/swick/wayland-protocols/-/blob/color/unstable/color-management/color.rst
> > > we started a long time ago, and have not really touched it for a while.
> > > Since we last touched it, at least my understanding has developed
> > > somewhat.
> > >
> > > It is linked from the overview in
> > > https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14
> > > and if you want to propose changes, the way to do it is file a MR in
> > > https://gitlab.freedesktop.org/swick/wayland-protocols/-/merge_requests
> > > against the 'color' branch. Patches very much welcome, that doc does
> > > not need to limit itself to Wayland. :-)
> > >
> > Right, I've read all that a while back.
> > It might be a good place to consolidate most of the Linux CM/HDR discussion,
> > since gitlab is good with allowing discussions, we can track changes, and
> > it's more formatting and diagram friendly than text-only email.
> Fine by me, but the way things are right now, we'd be hijacking
> Sebastian's personal repository for these things. That's not ideal.
> We can't merge the protocol XML into wayland-protocols until it has the
> accepted implementations required by the governance rules, but I wonder
> if we could land color.rst ahead of time, then work on that in
> wayland-protocols upstream repo.
> It's hard to pick a good place for a cross-project document. Any other
> > > We also have issues tracked at
> > > https://gitlab.freedesktop.org/swick/wayland-protocols/-/issues?scope=all&utf8=%E2%9C%93&state=opened
we discussed things in
and we have a new home for the color related WIP documentation we can
use across Wayland, Mesa, DRM, and even X11 if people want to:
Yes, it's still someone's personal repository, but we avoid entangling
it with wayland-protocols which also means we can keep the full git
history. If this gets enough traction, the repository can be moved from
under my personal group to somewhere more communal, and if that is
still inside gitlab.fd.o then all merge requests and issues will move
The README notes that we will deal out merge permissions as well.
This is not meant to supersede the documentation of individual APIs,
but to host additional documentation that would be too verbose, too
big, or out of scope to host within respective API docs.
Feel free to join the effort or just to discuss.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the wayland-devel