I moved on to D35099.

Since a few people requested this be put it a single chapter, I created D35099. There are no content changes with this change, it just moves the current version to a single chapter. Then, I would like to work with everyone who has made comments here and make sure they are addressed. Thank you for your patience with me, my free time is not as abundant as we would like.

Sorry - I am always so busy, then I tell myself to look at this and never do because something always comes up in life. Anyway, how about I submit a new review where the section is migrated to a new chapter? Then we can continue improving and adding to a chapter instead of a section. I should have free time this weekend. Thanks! And sorry I go missing all the time! :(

In D32436#792520, @bcr wrote:

In general. There were some changes proposed which would still need to go into a new patch.
But I'm thinking if they are not too critical, then we should think about getting a Wayland chapter into the handbook in the first place and the do the fixes in a followup commit. That would not stall this initiative (having the info in a public place) and also enable others to contribute their own work.

In D32436#791966, @pauamma_gundo.com wrote:

In D32436#791757, @bcr wrote:

Any update on this?

Are you and I waiting for each other to do something, or are you asking someone else?

In D32436#791757, @bcr wrote:

Any update on this?

Any update on this? Would love to show the world that FreeBSD supports Wayland to the degree that is described here.
We can then add stuff later once we already have a basic handbook chapter.

Done with the first round. For the second one, if you don't use https://wiki.freebsd.org/Phabricator#Create_a_Revision_via_command_line_.28if_using_git.29 but prefer https://wiki.freebsd.org/Phabricator#Create_a_Revision_via_Web_Interface, can you make sure to use -U999999? That way, reviewers should be able to suggest changes directly instead of through a long seriess of s/foo/bar/.

One thing this is sorely lacking is accessibility options. The three areas that need a mention are:

• sticky keys: for some people (eg, those with motor disabilities affecting fine motor control, arthritis, or other joint problems including various forms of joint pain) holding the Windows, pressing and holding shift, and finally pressing return isn't an option.
• screenreader support.
• voice control for people unable to type at all.

Pausing now, will look at the Sway section later.

Shamelessly using your mention of the wrong review ID in your commit message (D32463 instead of D32436), which left this open, to suggest my own edits, since I'm in docs but not a committer. Since I don't know Wayland, I'm only looking at language and clarity, not correctness.

Good news! Got GDM working!

Fix another consolekit path.

Using the Update diff option this time, sorry about that. I made some rewording changes based on feedback, such as rewording and moving the NVidia driver note, and removing the ck-launch-session as recommended. It should now properly work when sway is started. Another user reached out to me and said they wanted to add to the sway section but they will enhance it through a PR later.

Fix a path variable (sorry it still doesn't work :-( ).

Fix a small Makefile error. Sorry if GDM still doesn't work.

Bugzilla report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261540

+1 on uploading the diff to Phabricator properly (e.g., Update Diff button in Web UI). The attached diff(s) are easy to miss.

Maybe "update diff" instead of attaching? I'm somewhat confused whether what I see in Phabricator is the same as in the newest attached diff.

I'm attaching a new patch that adds ly configuration and various clean up as discussed in this change. I didn't want to work tonight and this was more fun, hopefully I can put this in the handbook and if there are additional changes, people can just kick it around as changes are needed and Wayland becomes more utilized. :)

Just a few comments noted - I got a patch commited into ports so ly will function properly, I want to migrate some comments here and ly into a new patch. I'll to get that done this week or next week. Some comments not responded too so I can spend time migrating the suggestions properly before just marking them as "done." Thanks!

Tom, I see no problem with getting this in before the release, as the documentation distribution set is no longer included on the installer.

In D32436#732395, @evgeniy_khramtsov.org wrote:

I almost forgot, this was not added in the newest revision: just starting seatd is not enough, a user is required to be a member of "video" group.

In D32436#732379, @lwhsu wrote:

One thing I would suggest is considering breaking the long lines into one sentence per line, as asciidoc recommended:
https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line

I almost forgot, this was not added in the newest revision: just starting seatd is not enough, a user is required to be a member of "video" group.

One thing I would suggest is considering breaking the long lines into one sentence per line, as asciidoc recommended:
https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line

Thanks for improving this diff. I'm not good at reviews, so please wait
for someone else to approve, but I added some nitpicks:

Updated diff (after pasting it in a follow up of course - duh).

Thanks for documenting Wayland on FreeBSD. I added some notes to places that may need change. Not sure about Plasma or nvidia parts, I neither use Plasma nor own and nvidia GPU.

Small suggestions.