[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#931277: release-notes: document Wayland as default display server for GNOME in what's new



Paul Gevers wrote:
> I thinks we should document the switch of GNOME to Wayland as the
> default display server in the What's New section. Proposal attached.
> I've added d-a11y@l.d.o in X-D-CC, please keep them in the loop, because
> I think it is worth mentioning a recommendation to not use Wayland for
> people needing a11y technology. Did I phrase it right in the proposal?
> 
> Does this subject (a11y on Wayland) warrant a note in "Issues to be
> aware of for buster" chapter?

Probably the "apps-in-gnome-on-wayland" issues section should link
back to this whats-new section.

> +<section id="wayland-by-default-on-gnome">
> +  <!-- stretch to buster -->
> +  <title>GNOME defaults to Wayland</title>
> +  <para>
> +    Following the upstream code, GNOME in buster now uses the Wayland display
> +    server by default instead of the Xorg display server. The Wayland display
> +    server is more recent than Xorg, and therefor is designed to prevent some
> +    security issues present in Xorg.
> +  </para>

A bit repetitive, and we should probably say "modern", not "recent"
(for a start because that hints at the downside: its assumptions are
*too* modern for my video hardware).

       Following upstream, GNOME in buster defaults to using the Wayland
       display instead of Xorg. Wayland is a simpler and more modern
       design, which has advantages for security.

> +  <para>
> +    The Xorg display server is still installed by default and the default
> +    display manager still allows you to choose it as the display server for the
> +    next session, which may be needed if you want to use some applications (see
> +    <xref linkend="apps-in-gnome-on-wayland"/>).
> +  </para>
> +  <para>
> +    People requiring accessibility features of the display server, e.g. global
> +    keyboard shortcuts, are recommended to use Xorg instead of Wayland.
> +  </para>
> +</section>
> +
>  </section>
>  </chapter>

This all looks good to me, but I'm not sure how much of the detail
should go here and how much under "issues".
-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package


Reply to: