diff --git a/documentation/content/en/articles/freebsd-status-report-process/_index.po b/documentation/content/en/articles/freebsd-status-report-process/_index.po new file mode 100644 index 0000000000..9e38f12427 --- /dev/null +++ b/documentation/content/en/articles/freebsd-status-report-process/_index.po @@ -0,0 +1,863 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR The FreeBSD Project +# This file is distributed under the same license as the FreeBSD Documentation package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: FreeBSD Documentation VERSION\n" +"POT-Creation-Date: 2023-04-20 21:10-0300\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: YAML Front Matter: description +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:1 +#, no-wrap +msgid "Instructions for both writers and editors of status reports" +msgstr "" + +#. type: Title = +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:1 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:10 +#, no-wrap +msgid "FreeBSD Status Report Process" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:21 +msgid "'''" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:26 +msgid "" +"FreeBSD status reports are published quarterly and provide the general " +"public with a view of what is going on in the Project, and they are often " +"augmented by special reports from Developer Summits. As they are one of our " +"most visible forms of communication, they are very important." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:28 +msgid "" +"Throughout this document and in other places related to FreeBSD status " +"reports as well, the expression _status report_ is used both to indicate the " +"document published on a quarterly basis and the single entries that are in " +"it." +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:29 +#, no-wrap +msgid "Instructions for writers" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:33 +msgid "" +"This section provides some advice on writing status report entries from " +"mailto:theraven@FreeBSD.org[David Chisnall], experienced in technical " +"writing. Instructions on how to submit your entries are also given." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:36 +msgid "" +"_Do not worry if you are not a native English speaker. The " +"mailto:status@FreeBSD.org[status team] will check your entries for spelling " +"and grammar, and fix it for you._" +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:37 +#, no-wrap +msgid "Introduce Your Work" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:40 +msgid "_Do not assume that the person reading the report knows about your project._" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:44 +msgid "" +"The status reports have a wide distribution. They are often one of the top " +"news items on the FreeBSD web site and are one of the first things that " +"people will read if they want to know a bit about what FreeBSD is. Consider " +"this example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:47 +#, no-wrap +msgid "abc(4) support was added, including frobnicator compatibility.\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:53 +msgid "" +"Someone reading this, if they are familiar with UNIX man pages, will know " +"that `abc(4)` is some kind of device. But why should the reader care? What " +"kind of device is it? Compare with this version:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:57 +#, no-wrap +msgid "" +"A new driver, abc(4), was added to the tree, bringing support for\n" +"Yoyodyne's range of Frobnicator network interfaces.\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:61 +msgid "" +"Now the reader knows that abc is a network interface driver. Even if they " +"do not use any Yoyodyne products, you have communicated that FreeBSD's " +"support for network devices is improving." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:62 +#, no-wrap +msgid "Show the Importance of Your Work" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:65 +msgid "" +"_Status reports are not just about telling everyone that things were done, " +"they also need to explain why they were done._" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:73 +msgid "" +"Carry on with the previous example. Why is it interesting that we now " +"support Yoyodyne Frobnicator cards? Are they widespread? Are they used in a " +"specific popular device? Are they used in a particular niche where FreeBSD " +"has (or would like to have) a presence? Are they the fastest network cards " +"on the planet? Status reports often say things like this:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:76 +#, no-wrap +msgid "We imported Cyberdyne Systems T800 into the tree.\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:84 +msgid "" +"And then they stop. Maybe the reader is an avid Cyberdyne fan and knows " +"what exciting new features the T800 brings. This is unlikely. It is far " +"more likely that they have vaguely heard of whatever you have imported " +"(especially into the ports tree: remember that there are over 30,000 other " +"things there too...). List some of the new features, or bug fixes. Tell " +"them why it is a good thing that we have the new version." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:85 +#, no-wrap +msgid "Tell Us Something New" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:88 +msgid "_Do not recycle the same status report items._" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:94 +msgid "" +"Bear in mind that status reports are not just reports on the status of the " +"project, they are reports on the change of status of the project. If there " +"is an ongoing project, spend a couple of sentences introducing it, but then " +"spend the rest of the report talking about the new work. What progress has " +"been made since the last report? What is left to do? When is it likely to be " +"finished (or, if \"finished\" does not really apply, when is it likely to be " +"ready for wider use, for testing, for deployment in production, and so on)?" +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:95 +#, no-wrap +msgid "Sponsorship" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:98 +msgid "_Do not forget about your sponsors._" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:102 +msgid "" +"If you or your project has received sponsorship, a scholarship from somebody " +"or you have been already working as a contractor or an employee for a " +"company, please include it. Sponsors always certainly appreciate if you " +"thank them for their funding, but it is also beneficial for them to show " +"that they are actively supporting the Project this way. Last, but not " +"least, this helps FreeBSD to learn more about its important consumers." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:103 +#, no-wrap +msgid "Open Items" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:106 +msgid "_If help is needed, make this explicit!_" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:112 +msgid "" +"Is there any help needed with something? Are there tasks other people can " +"do? There are two ways in which you can use the open items part of the " +"status report: to solicit help, or to give a quick overview of the amount of " +"work left. If there are already enough people working on the project, or it " +"is in a state where adding more people would not speed it up, then the " +"latter is better. Give some big work items that are in progress, and maybe " +"indicate who is focussing on each one." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:114 +msgid "" +"List tasks, with enough detail that people know if they are likely to be " +"able to do them, and invite people to get in contact." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:115 +#, no-wrap +msgid "Submit your report" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:118 +msgid "The following methods are available to submit your reports:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:121 +msgid "" +"submit a link:https://reviews.freebsd.org/[Phabricator review] and add the " +"group _status_ to the reviewers list. You should put your reports in the " +"appropriate subdirectory of `doc/website/content/en/status/` (create it if " +"it is missing);" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:124 +msgid "" +"submit a pull request to the doc repository through " +"link:https://github.com/freebsd/freebsd-doc[its GitHub mirror] . You should " +"put your reports in the appropriate subdirectory of " +"`doc/website/content/en/status` (create it if it is missing);" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:126 +msgid "send an email to status-submissions@FreeBSD.org including your report." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:128 +msgid "" +"An link:https://www.FreeBSD.org/status/report-sample.adoc[AsciiDoc sample " +"report template] is available." +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:129 +#, no-wrap +msgid "Instructions for editors" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:132 +msgid "This section describes how the reviewing and publication process works." +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:138 +#, no-wrap +msgid "Status reports main webpage" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:140 +#, no-wrap +msgid "link:https://www.FreeBSD.org/status/[https://www.FreeBSD.org/status/]" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:141 +#, no-wrap +msgid "" +"Status reports archived GitHub repository (was used for reports from 2017Q4 " +"to 2022Q4):" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:143 +#, no-wrap +msgid "link:https://www.github.com/freebsd/freebsd-quarterly[https://github.com/freebsd/freebsd-quarterly]" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:144 +#, no-wrap +msgid "Main status team email address" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:146 +#, no-wrap +msgid "link:mailto:status@FreeBSD.org[status@FreeBSD.org]" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:147 +#, no-wrap +msgid "Email address for reports submission" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:149 +#, no-wrap +msgid "link:mailto:status-submissions@FreeBSD.org[status-submissions@FreeBSD.org]" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:150 +#, no-wrap +msgid "Mailing list for receiving calls for status reports" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:152 +#, no-wrap +msgid "link:https://lists.freebsd.org/subscription/freebsd-status-calls[freebsd-status-calls@FreeBSD.org]" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:153 +#, no-wrap +msgid "Phabricator status team main page" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:154 +#, no-wrap +msgid "link:https://reviews.freebsd.org/project/profile/88/[https://reviews.freebsd.org/project/88/]" +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:156 +#, no-wrap +msgid "Timeline" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:162 +msgid "" +"Reports are always accepted by the status team, but the main collection " +"process happens the last month of each quarter, hence in March, June, " +"September and December. Explicit calls for status reports will be sent in " +"those months. The months of January, April, July and October are dedicated " +"to putting together the reports submitted during the precedent quarter; this " +"can include waiting for late submissions. Status reports publication is " +"done during the same months as soon as the report are ready." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:165 +msgid "" +"All report submissions can have the deadline extended by " +"link:mailto:status-submissions@FreeBSD.org[emailing the status team] up " +"until the extended deadline, which is 8 days after the end of the quarter. " +"Entries from the " +"link:https://www.freebsd.org/administration/#t-portmgr[ports management " +"team] default to the extended headline, because of the overlap between " +"status reports and quarterly ports branches." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:169 +msgid "" +"Reviewing of submitted reports by people not part of the status team should " +"be essentially complete by mid-January/April/July/October (third-party " +"review slush). That is, barring typos or other light copyediting, the " +"status team should be able to start assembling the submissions soon after " +"the 15th. Note that this is not a complete freeze, and the status team may " +"still be able to accept reviews then." +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:172 +#, no-wrap +msgid "First quarter" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:172 +#, no-wrap +msgid "Second quarter" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:172 +#, no-wrap +msgid "Third quarter" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:174 +#, no-wrap +msgid "Fourth quarter" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:175 +#, no-wrap +msgid "First call for reports" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:176 +#, no-wrap +msgid "March 1st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:177 +#, no-wrap +msgid "June 1st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:178 +#, no-wrap +msgid "September 1st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:180 +#, no-wrap +msgid "December 1st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:181 +#, no-wrap +msgid "2 weeks left reminder" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:182 +#, no-wrap +msgid "March 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:183 +#, no-wrap +msgid "June 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:184 +#, no-wrap +msgid "September 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:186 +#, no-wrap +msgid "December 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:187 +#, no-wrap +msgid "Last reminder" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:188 +#, no-wrap +msgid "March 24th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:189 +#, no-wrap +msgid "June 24th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:190 +#, no-wrap +msgid "September 24th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:192 +#, no-wrap +msgid "December 24th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:193 +#, no-wrap +msgid "Standard deadline" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:194 +#, no-wrap +msgid "March 31st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:195 +#, no-wrap +msgid "June 30th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:196 +#, no-wrap +msgid "September 30th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:198 +#, no-wrap +msgid "December 31st" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:199 +#, no-wrap +msgid "Extended deadline" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:200 +#, no-wrap +msgid "April 8th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:201 +#, no-wrap +msgid "July 8th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:202 +#, no-wrap +msgid "October 8th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:204 +#, no-wrap +msgid "January 8th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:205 +#, no-wrap +msgid "Third-party review slush" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:206 +#, no-wrap +msgid "April 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:207 +#, no-wrap +msgid "July 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:208 +#, no-wrap +msgid "October 15th" +msgstr "" + +#. type: Table +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:209 +#, no-wrap +msgid "January 15th" +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:211 +#, no-wrap +msgid "Call for reports" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:214 +msgid "Calls for status reports are sent to the following recipients:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:216 +msgid "" +"the " +"link:https://lists.freebsd.org/subscription/freebsd-status-calls[freebsd-status-calls@FreeBSD.org " +"mailing list];" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:217 +msgid "" +"to all submitters of last status reports (they may have updates or further " +"improvements);" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:218 +msgid "and, depending on the season:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:219 +msgid "Various conference organizers:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:220 +msgid "link:mailto:secretary@asiabsdcon.org[AsiaBSDCon] in March (First Quarter);" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:221 +msgid "link:mailto:info@bsdcan.org[BSDCan] in May (Second Quarter);" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:222 +msgid "EuroBSDcon September - October (Third-Fourth Quarter)." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:223 +msgid "" +"EuroBSDcon as an organization is not interested in writing reports for " +"FreeBSD (at least it was not in October 2019: its reason is that the " +"conference is not FreeBSD specific), so reports about this event should be " +"asked of members of the FreeBSD community that attended it;" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:224 +msgid "" +"Google Summer of Code link:mailto:soc-students@FreeBSD.org[students] and " +"their link:mailto:soc-mentors@FreeBSD.org[mentors]." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:228 +msgid "" +"The easiest way to send calls for status reports is to use the " +"link:https://cgit.freebsd.org/doc/tree/tools/sendcalls/sendcalls[[.filename]#sendcalls# " +"perl script] in the [.filename]#tools/sendcalls# directory of the doc git " +"repository. The script automatically sends calls to all intended " +"recipients. It can also be used through a cron job, for example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:231 +#, no-wrap +msgid "" +"0 0 1,15,24 3,6,9,12 * cd ~/doc/tools/sendcalls && " +"git pull && ./sendcalls -s 'Lorenzo Salvadore'\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:237 +msgid "" +"If you are in charge of sending calls for status reports and you are indeed " +"using a cron job, please run it on freefall and sign it with your name so " +"that it is possible to infer who has configured the cronjob, in case " +"something goes wrong. Also please update the example above with your name, " +"as an additional safety measure." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:240 +msgid "" +"It may also be worth making a call for reports on the forums as " +"link:https://forums.freebsd.org/threads/call-for-freebsd-2014q4-october-december-status-reports.49812/[was " +"done in the past]." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:241 +#, no-wrap +msgid "Building the report" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:245 +msgid "" +"Submitted reports are reviewed and merged in the proper subdirectory of " +"[.filename]#doc/website/content/en/status/# as they come in. While the " +"reports are being updated, people outside the status team may also review " +"the individual entries and propose fixes." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:248 +msgid "" +"Usually the last step in the content review process is writing the " +"introduction in a file named [.filename]#intro.adoc#: a good introduction " +"can only be written once all the reports have been collected. If possible, " +"it is a good idea to ask different people to write the introduction to add " +"variety: different people will bring different viewpoints and help keep it " +"fresh." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:250 +msgid "" +"Once all the reports and the introduction are ready, the " +"[.filename]#_index.adoc# file needs to be created: this is the file in which " +"the reports are distributed into the various categories and sorted." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:251 +#, no-wrap +msgid "Publishing the report" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:254 +msgid "When all the files of the status report are ready, it is time to publish it." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:257 +msgid "" +"First [.filename]#doc/website/content/en/status/_index.adoc# is edited: the " +"next due date is updated and a link to the new report is added. The change " +"is then pushed on the repository and the status team checks that everythings " +"works as expected." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:259 +msgid "" +"Then the news entry for the main website page is added to " +"[.filename]#doc/website/data/en/news/news.toml#." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:261 +msgid "Here is a sample for the news entry:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:266 +#, no-wrap +msgid "" +"[[news]]\n" +"date = \"2021-01-16\"\n" +"title = \"October-December 2020 Status Report\"\n" +"description = \"The October " +"to December 2020 Status Report is now available with 42 entries.\"\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:269 +msgid "" +"Once the HTML version of the report has been built and is online, man:w3m[1] " +"is used to dump the website as plain-text, e.g:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:271 +#, no-wrap +msgid "" +"% w3m -cols 80 -dump https://www.FreeBSD.org/status/report-2021-01-2021-03/ " +"> /tmp/report-2021-01-2021-03.txt\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:274 +msgid "" +"man:w3m[1] has full proper unicode support. `-dump` simply outputs text " +"rendering of the HTML code that can then have a few elements snipped, while " +"`-cols` ensures that everything is wrapped to 80 columns." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:276 +msgid "" +"A link to the rendered report is added between the introduction and the " +"first entry." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:278 +msgid "" +"The report is finally ready to be sent, toggling disposition (the report " +"should be inlined), and ensuring it is encoded as UTF-8." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:280 +msgid "" +"Two emails are sent, both with subject in the format `FreeBSD Status Report " +"- Quarter `:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:282 +msgid "" +"one to " +"link:https://lists.freebsd.org/subscription/freebsd-announce[freebsd-announce@FreeBSD.org];" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:286 +msgid "" +"This one must be approved, so if you are in charge of sending this email, " +"ensure that someone does it (mail " +"link:mailto:postmaster@FreeBSD.org[postmaster] if it is taking long)." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/freebsd-status-report-process/_index.adoc:288 +msgid "" +"one to " +"link:https://lists.freebsd.org/subscription/freebsd-hackers[freebsd-hackers@FreeBSD.org], " +"which also has " +"link:https://lists.freebsd.org/subscription/freebsd-current[freebsd-current@FreeBSD.org] " +"and " +"link:https://lists.freebsd.org/subscription/freebsd-stable[freebsd-stable@FreeBSD.org] " +"in CC and `developers@FreeBSD.org` in BCC." +msgstr "" diff --git a/documentation/content/en/articles/license-guide/_index.po b/documentation/content/en/articles/license-guide/_index.po new file mode 100644 index 0000000000..5b2ef8b880 --- /dev/null +++ b/documentation/content/en/articles/license-guide/_index.po @@ -0,0 +1,766 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR The FreeBSD Project +# This file is distributed under the same license as the FreeBSD Documentation package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: FreeBSD Documentation VERSION\n" +"POT-Creation-Date: 2023-04-20 21:10-0300\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: YAML Front Matter: title +#: documentation/content/en/articles/license-guide/_index.adoc:1 +#, no-wrap +msgid "FreeBSD Licensing Policy" +msgstr "" + +#. type: Title = +#: documentation/content/en/articles/license-guide/_index.adoc:9 +#, no-wrap +msgid "FreeBSD License Policies" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:20 +msgid "'''" +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/license-guide/_index.adoc:26 +#, no-wrap +msgid "Preferred License for New Files" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:32 +msgid "" +"The rest of this section is intended to help you get started. As a rule, " +"when in doubt, ask. It is much easier to receive advice than to fix the " +"source tree. The FreeBSD Project makes use of both explicit licenses (where " +"the verbatim text of the license is reproduced in each file) and detached " +"licenses (where a tag in the file specifies the license, as described in " +"this document)." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:34 +msgid "The FreeBSD Project uses this text as the preferred license:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:42 +#: documentation/content/en/articles/license-guide/_index.adoc:138 +#, no-wrap +msgid "" +"/*-\n" +" * Copyright (c) [year] [your name]\n" +" *\n" +" * SPDX-License-Identifier: BSD-2-Clause\n" +" */\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:48 +msgid "" +"The FreeBSD project does not allow using the \"advertising clause\" in new " +"code. Due to the large number of contributors to the FreeBSD project, " +"complying with this clause for many commercial vendors has become " +"difficult. If you have code in the tree with the advertising clause, please " +"consider switching to a license without it. New contributions to FreeBSD " +"should use the BSD-2-Clause license." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:54 +msgid "" +"The FreeBSD project discourages completely new licenses and variations on " +"the standard licenses. New licenses require the approval of {core-email} to " +"reside in the main repository. In the past, non-standard licenses have " +"generated more problems than standard ones. Poor drafting of non-standard " +"licenses often causes more unintended consequences, so they are unlikely to " +"be approved by {core-email}. The FreeBSD project is standardizing on the " +"BSD-2-Clause license, as published by SPDX." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:60 +msgid "" +"In addition, project policy requires that code licensed under some non-BSD " +"licenses must be placed in specific sections of the repository. For some " +"licenses, compilation must be conditional or disabled by default. For " +"example, code in the static part of the GENERIC kernel must be licensed " +"under the BSD or substantially similar licenses. GPL, APSL, CDDL, etc, " +"licensed software must not be compiled into the static GENERIC kernel. Code " +"with these licenses may be used in pre-compiled modules, however." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:64 +msgid "" +"Developers are reminded that, in open source, getting \"open\" correct is " +"just as important as getting \"source\" correct. Improper handling of " +"intellectual property has serious consequences. Any questions or concerns " +"should immediately be brought to the attention of {core-email}." +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/license-guide/_index.adoc:66 +#, no-wrap +msgid "Software License Policy" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:72 +msgid "" +"The following sections outline the project's Software License Policies in " +"detail. For the most part we expect developers to read, understand and " +"utilize the sections above this one in order to apply appropriate licenses " +"to their contributions. The rest of this document details the philosophical " +"background to the policies as well as the policies in great detail. As " +"always, if the text below is confusing or you need help with applying these " +"policies, please reach out to {core-email}." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:73 +#, no-wrap +msgid "Guiding Principles" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:78 +msgid "" +"The FreeBSD Project aims to produce a complete, BSD-licensed operating " +"system allowing consumers of the system to produce derivative products " +"without constraint or further license obligations. We invite and greatly " +"appreciate the contribution of both changes and additions under the " +"two-clause BSD license, and encourage the adoption of this license by other " +"open source projects. Use of the BSD license is key to encouraging the " +"adoption of advanced operating system technology, and on many notable " +"occasions has been pivotal to widespread use of new technology." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:80 +msgid "" +"We accept however that compelling reasons exist to allow " +"differently-licensed software to be included in the FreeBSD source tree." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:83 +msgid "" +"We require software licensed under some non-BSD licenses to be carefully " +"isolated in the source tree so that it cannot contaminate BSD-only " +"components. Such cautious management encourages licensing clarity and " +"facilitates the production of BSD-only derivative products." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:87 +msgid "" +"Unless a special exception is made, no existing BSD-licensed components may " +"be replaced with more restrictively licensed software. We encourage FreeBSD " +"and third party developers to seek the relicensing, dual-licensing, or " +"reimplementing of critical components under the BSD license instead. Such " +"would ease their more integral adoption into the FreeBSD operating system." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:88 +#, no-wrap +msgid "Policy" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:92 +msgid "" +"The import of new software licensed under any licenses other than the BSD " +"license and BSD-Like Licenses (as defined below) requires the prior approval " +"of the FreeBSD Core Team. Requests for import must include:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:94 +msgid "" +"A list of features or bug fixes that the new version or patches contain, " +"along with evidence that our users need those features. PRs or references " +"to mailing list discussions are ideal forms of evidence." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:96 +msgid "" +"This process should be used for all software imports, not just those that " +"require Core Team review. The mere existence of a new version does not " +"justify an import of software to source or ports." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:98 +msgid "" +"A list of FreeBSD branches that may be affected. Expansions of scope " +"require a new request to and approval from the FreeBSD Core Team." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:101 +msgid "" +"The Apache License 2.0 is acceptable for use in some cases. The Core Team " +"must approve the import of new Apache License licensed components or the " +"change of license of existing components to the Apache License." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:102 +#: documentation/content/en/articles/license-guide/_index.adoc:107 +#: documentation/content/en/articles/license-guide/_index.adoc:112 +msgid "This license is approved for the following components:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:103 +msgid "LLVM toolchain and (with LLVM Exceptions) runtime components." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:106 +msgid "" +"The BSD+Patent License is acceptable for use in some cases. The Core Team " +"must approve the import of new BSD+Patent License licensed components or the " +"change of license of existing components to the BSD+Patent License." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:108 +msgid "EDK2 derived code related to UEFI functionality" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:111 +msgid "" +"The Common Development and Distribution License (CDDL) is acceptable for use " +"in some cases. The Core Team must approve the import of new CDDL licensed " +"components or the change of license of existing components to the CDDL." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:113 +msgid "DTrace" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:114 +msgid "ZFS filesystem, including kernel support and userland utilities" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:120 +msgid "" +"Historically, the phrase 'All Rights Reserved.' was included in all " +"copyright notices. All the BSD releases had it, in order to comply with the " +"https://en.wikipedia.org/wiki/Buenos_Aires_Convention[Buenos Aires " +"Convention of 1910] in the Americas. With the ratification of the " +"https://en.wikipedia.org/wiki/Berne_Convention[Berne Convention] in 2000 by " +"Nicaragua, the Buenos Aires Convention -- and the phrase -- became " +"obsolete. As such, the FreeBSD project recommends that new code omit the " +"phrase and encourages existing copyright holders to remove it. In 2018, the " +"project updated its templates to remove it." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:123 +msgid "" +"Initially, many items in the FreeBSD tree were marked with " +"BSD-2-Clause-FreeBSD. However, SPDX has obsoleted the license as a variant; " +"and the SPDX text of the obsolete tag differs enough from the standard " +"FreeBSD license that it shouldn't be used. A review of its current use is " +"ongoing." +msgstr "" + +#. type: Title ==== +#: documentation/content/en/articles/license-guide/_index.adoc:124 +#, no-wrap +msgid "Acceptable licenses" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:128 +msgid "" +"The following licenses are considered to be acceptable BSD-Like Licenses for " +"the purpose of this Policy. Deviations or the use of any other license must " +"be approved by the FreeBSD Core Team:" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:130 +msgid "The 2 clause version of the BSD license" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:140 +msgid "The 3 clause version of the BSD license" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:148 +#, no-wrap +msgid "" +"/*-\n" +" * Copyright (c) [year] [your name]\n" +" *\n" +" * SPDX-License-Identifier: BSD-3-Clause\n" +" */\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:150 +msgid "The ISC License" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:158 +#, no-wrap +msgid "" +"/*-\n" +" * Copyright (c) [year] [copyright holder]\n" +" *\n" +" * SPDX-License-Identifier: ISC\n" +" */\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:160 +msgid "The MIT License" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:168 +#, no-wrap +msgid "" +"/*-\n" +" * Copyright (c) [year] [copyright holders]\n" +" *\n" +" * SPDX-License-Identifier: MIT\n" +" */\n" +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/license-guide/_index.adoc:169 +#, no-wrap +msgid "Software Collection License" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:174 +msgid "" +"The FreeBSD Project licenses its compilation of software as described in " +"[.filename]#COPYRIGHT# under the BSD-2-Clause license. This license does " +"not supersede the license of individual files, which is described below. " +"Files that do not have an explicit license are licensed under the " +"BSD-2-Clause license." +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/license-guide/_index.adoc:175 +#, no-wrap +msgid "License File Location" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:187 +msgid "" +"To comply with the https://reuse.software/[REUSE Software] standard as much " +"as possible, all license files will be stored in the [.filename]#LICENSES/# " +"directory of the repository. There are three subdirectories under this top " +"level directory. The [.filename]#LICENSES/text/# subdirectory contains, in " +"detached form, the text of all the licenses that are allowed in the FreeBSD " +"software collection. These files are stored using the " +"SPDX-License-Identifier name followed by .txt. The " +"[.filename]#LICENSES/exceptions/# subdirectory has the text of all " +"exceptions that are allowed in detached form in the FreeBSD software " +"collection. These files are stored using the exception identifier name " +"followed by .txt. The [.filename]#LICENSES/other/# contains, in detached " +"form, the license files references in SPDX-License-Identifier expressions, " +"but aren't otherwise allowed as detached licenses. All such files must " +"appear at least once in the FreeBSD software collection, and should be " +"removed when the last file that references them is removed. Licenses that " +"have no adequate SPDX matching license must be in " +"[.filename]#LICENSES/other/# and have a filename that starts with " +"LicenseRef- followed by a unique idstring. No such files have currently " +"been identified, but if they are, a full list will appear here." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:191 +msgid "" +"The FreeBSD Project currently does not make use of the `DEP5` files " +"described in the `REUSE Software` standard. The FreeBSD Project has not " +"marked all the files in the tree yet in accordance with this standard, as " +"described later in this document. The FreeBSD Project has not yet included " +"these files in its repositories since this policy is still evolving." +msgstr "" + +#. type: Title == +#: documentation/content/en/articles/license-guide/_index.adoc:193 +#, no-wrap +msgid "Individual Files License" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:197 +msgid "" +"Each individual file in the FreeBSD software collection has its own " +"copyright and license. How they are marked varies and is described in this " +"section." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:201 +msgid "" +"A copyright notice identifies who claims the legal copyright to a file. " +"These are provided on a best effort basis by the project. Because " +"copyrights may be legally transferred, the current copyright holder may " +"differ from what is listed in the file." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:210 +msgid "" +"A license is a legal document between the contributor and the users of the " +"software granting permission to use the copyrighted portions of the " +"software, subject to certain terms and conditions set forth in the license. " +"Licenses can be expressed in one of two ways in the FreeBSD software " +"collection. Licenses can be explicit in a file. When a license grant is " +"explicit in the file, that file may be used, copied, and modified in " +"accordance with that license. Licenses can also be expressed indirectly, " +"where the text of the license is elsewhere. The project uses the Software " +"Package Data Exchange (SPDX) license identifiers for this purpose, as " +"described in the following subsections. SPDX license identifiers are " +"managed by the SPDX Workgroup at the Linux Foundation, and have been agreed " +"on by partners throughout the industry, tool vendors, and legal teams. For " +"further information see https://spdx.org/ and the following sections for how " +"the FreeBSD Project uses them." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:213 +msgid "" +"Entities that contribute fixes and enhancements to the software collection " +"without an explicit license agree to license those changes under the terms " +"that apply to the modified file(s). Project policy, in line with industry " +"practice, only includes a copyright notice from significant contributors to " +"the files in the collection." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:215 +msgid "There are four types of files in the FreeBSD software collection" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:216 +msgid "Files that have only an explicit copyright notice and license." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:217 +msgid "" +"Files that have both an explicit copyright notice and license, and a " +"SPDX-License-Identifier tag." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:218 +msgid "" +"Files that have only a copyright notice and an SPDX-License-Identifier tag, " +"but no explicit license" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:219 +msgid "Files that lack any copyright or license at all" +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:220 +#, no-wrap +msgid "Only Copyright and License" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:224 +msgid "" +"Many files in the FreeBSD software collection have both a copyright notice " +"and an explicit license contained in the file. In these cases, the license " +"contained in the file governs." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:225 +#, no-wrap +msgid "Copyright and License with SPDX-License-Identifier expression" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:231 +msgid "" +"Some files in the FreeBSD software collection contain a copyright statement, " +"an SPDX-License-Identifier tag and an explicit license. The explicit " +"license takes precedence over the SPDX-License-Identifier tag. The " +"SPDX-License-Identifier tag is the project's best effort attempt to " +"characterize the license, but is only informative for automated tools. See " +"<> for how to interpret the " +"expression." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:232 +#, no-wrap +msgid "Only Copyright and SPDX-License-Identifier expression." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:238 +msgid "" +"Some files in the tree contain detached licenses. These files contain only " +"a copyright notice and an SPDX-License-Identifier expression, but no " +"explicit license. See <> " +"for how to interpret the expression. Note: the expressions allowed for " +"detached licenses by the project are a subset of the expressions used " +"informationally or that are defined by the standard." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:240 +msgid "" +"The license for files containing only the SPDX-License-Identifier should be " +"construed to be" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:243 +msgid "" +"Start the license with the copyright notice from the file. Include all the " +"copyright holders." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:246 +msgid "" +"For each sub-expression, copy the license text from " +"[.filename]#LICENSE/text/`id`.txt#. When exceptions are present, append " +"them from [.filename]#src/share/license/exceptions/`id`.txt#. " +"SPDX-License-Identifier expressions should be construed as described in the " +"SPDX standard." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:249 +msgid "" +"Where `id` is the SPDX short license identifier from the `Identifier` column " +"of https://spdx.org/licenses/[SPDX Identifiers] or " +"https://spdx.org/licenses/exceptions-index.html[license exception]. If " +"there is no file in [.filename]#LICENSE/#, then that license or exception " +"cannot be specified as a detached license under this section." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:251 +msgid "" +"When reading the license text that is detached from a file, a number of " +"considerations must be taken to make the detached license make sense." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:254 +msgid "" +"Any reference to a copyright notice shall refer to the copyright notice " +"constructed from the licensed file, not from any copyright notice in the " +"license text file itself. Many SPDX files have sample copyright notices " +"that are understood to be examples only." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:256 +msgid "" +"When names of entities are referred to in the license text, they shall be " +"construed to apply to the list of all copyright holders listed in the " +"copyright notices of the licensed file. For example, the BSD-4-clause " +"license contains the phrase \"This product includes software developed by " +"the organization\". The phrase 'the organization' should be replaced by the " +"copyright holders." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:258 +msgid "" +"When the SPDX offers variations of the license, it is understood the license " +"in the [.filename]#LICENSE/# file represents the exact version of the " +"license selected. The SPDX standard exists to match families of licenses " +"and these variations help match similar licenses that the SPDX organization " +"believes to be legally identical." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:262 +msgid "" +"For licenses that have slight variations in text, the SPDX has guidelines to " +"match them. These guidelines are not relevant here. Contributors wishing " +"to license under a variant of a SPDX license not contained verbatim in " +"[.filename]#LICENSE/# cannot use the detached option and must specify the " +"license explicitly." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:263 +#, no-wrap +msgid "Files without Copyright or any License Marking" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:268 +msgid "" +"Some files cannot have suitable comments added to them. In such cases, a " +"license may be found in [.filename]#file.ext.license#. For example, a file " +"named [.filename]#foo.jpg# may have a license in " +"[.filename]#foo.jpg.license#, following the REUSE Software conventions." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:271 +msgid "" +"Files created by the project that lack a copyright notice are understood to " +"fall under the blanket copyright and licensing in [.filename]#COPYRIGHT#. " +"Either the file is a mere recitation of facts, not protectable by Copyright " +"Law, or the content is so trivial as to not warrant the overhead of an " +"explicit license." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:274 +msgid "" +"Files that lack marking and have more than a trivial amount of copyrightable " +"material, or whose author believes them to be improperly marked, should be " +"brought to the attention of the FreeBSD core team. It is the strong policy " +"of the FreeBSD Project to comply with all appropriate licenses." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:276 +msgid "" +"In the future, all such files will be marked explicitly, or follow the REUSE " +"Software [.filename]#.license# convention." +msgstr "" + +#. type: Title === +#: documentation/content/en/articles/license-guide/_index.adoc:278 +#, no-wrap +msgid "SPDX-License-Identifier Expressions" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:285 +msgid "" +"An 'SPDX License expression' is used in two contexts in the FreeBSD software " +"collection. First, its full form is used for files that have explicit " +"license statements contained within the file as well as a summarizing " +"SPDX-License-Identifier expression. In this context, the full power of " +"these expressions may be used. Second, in a restricted form described " +"above, it is used to denote the actual license for a given file. In the " +"second context, only a subset of this expression is allowed by the project." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:289 +msgid "" +"An `SPDX License sub-expression` is either an SPDX short form license " +"identifier from the https://spdx.org/licenses/[SPDX License List], or the " +"combination of two SPDX short form license identifiers separated by \"WITH\" " +"when a https://spdx.org/licenses/exceptions-index.html[license exception] " +"applies. When multiple licenses apply, an expression consists of keywords " +"\"AND\", \"OR\" separating sub-expressions and surrounded by \"(\", \")\" . " +"The " +"https://spdx.github.io/spdx-spec/appendix-IV-SPDX-license-expressions/[full " +"specification of expressions] spells out all the details and takes " +"precedence when it conflicts with the simplified treatment of this section." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:297 +msgid "" +"Some license identifiers, like [L]GPL, have the option to use only that " +"version, or any later version. SPDX defines the suffix `-or-later` to mean " +"that version of the license or a later version. It defines `-only` to mean " +"only that specific version of the file. There is an old convention to have " +"no suffix (which means what the new '-only' suffix means, but which people " +"confuse for `-or-later`). In addition, affixing a `+` suffix was meant to " +"mean `-or-later`. New files in FreeBSD should not use these two " +"conventions. Old files that use this convention should be converted as " +"appropriate." +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:302 +#, no-wrap +msgid "" +" // SPDX-License-Identifier: GPL-2.0-only\n" +" // SPDX-License-Identifier: LGPL-2.1-or-later\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:306 +msgid "" +"`WITH` should be used when a license modifier is needed. In the FreeBSD " +"project, a number of files from LLVM have an exception to the Apache 2.0 " +"license:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:310 +#, no-wrap +msgid " // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:314 +msgid "" +"https://spdx.org/licenses/exceptions-index.html[Exception tags] are managed " +"by SPDX. License exceptions can only be applied to certain licenses, as " +"specified in the exception." +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:317 +msgid "" +"`OR` should be used if the file has a choice of license and one license is " +"selected. For example, some dtsi files are available under dual licenses:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:321 +#, no-wrap +msgid " // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/articles/license-guide/_index.adoc:325 +msgid "" +"`AND` should be used if the file has multiple licenses whose terms all apply " +"to use the file. For example, if code has been incorporated by several " +"projects, each with their own license:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/articles/license-guide/_index.adoc:329 +#, no-wrap +msgid " // SPDX-License-Identifier: BSD-2-Clause AND MIT\n" +msgstr "" diff --git a/documentation/content/en/books/handbook/wayland/_index.po b/documentation/content/en/books/handbook/wayland/_index.po new file mode 100644 index 0000000000..d81dd4cc7f --- /dev/null +++ b/documentation/content/en/books/handbook/wayland/_index.po @@ -0,0 +1,1200 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR The FreeBSD Project +# This file is distributed under the same license as the FreeBSD Documentation package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: FreeBSD Documentation VERSION\n" +"POT-Creation-Date: 2023-04-20 21:09-0300\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"Language: \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. type: YAML Front Matter: description +#: documentation/content/en/books/handbook/wayland/_index.adoc:1 +#, no-wrap +msgid "" +"This chapter describes how to install and configure Wayland and compositors " +"on FreeBSD, which provides a graphical user environment" +msgstr "" + +#. type: YAML Front Matter: part +#: documentation/content/en/books/handbook/wayland/_index.adoc:1 +#, no-wrap +msgid "Part I. Getting Started" +msgstr "" + +#. type: YAML Front Matter: title +#: documentation/content/en/books/handbook/wayland/_index.adoc:1 +#, no-wrap +msgid "Chapter 6. Wayland" +msgstr "" + +#. type: Title = +#: documentation/content/en/books/handbook/wayland/_index.adoc:14 +#, no-wrap +msgid "Wayland on FreeBSD" +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:52 +#, no-wrap +msgid "Wayland Synopsis" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:57 +msgid "" +"Wayland is a new display server, but it differs from Xorg in several " +"important ways. First, Wayland is only a protocol that acts as an " +"intermediary between clients using a different mechanism which removes the " +"dependency on an X server. Xorg includes both the X11 protocol, used to run " +"remote displays and the X server will accept connections and display " +"windows. Under Wayland, the compositor or window manager provides the " +"display server instead of a traditional X server." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:60 +msgid "" +"Since Wayland is not an X server, traditional X screen connections will need " +"to utilize other methods such as VNC or RDP for remote desktop management. " +"Second, Wayland can manage composite communications between clients and a " +"compositor as a separate entity which does not need to support the X " +"protocols." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:64 +msgid "" +"Wayland is relatively new, and not all software has been updated to run " +"natively without `Xwayland` support. Because Wayland does not provide the X " +"server, and expects compositors to provide that support, X11 window managers " +"that do not yet support Wayland will require that `Xwayland` is not started " +"with the `-rootless` parameter. The `-rootless` parameter, when removed, " +"will restore X11 window manager support." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:69 +msgid "" +"The current NVidia driver should work with most wl-roots compositors, but it " +"may be a little unstable and not support all features at this time. " +"Volunteers to help work on the NVidia DRM are requested." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:73 +msgid "" +"Currently, a lot of software will function with minimal issues on Wayland, " +"including Firefox. And a few desktops are also available, such as the " +"Compiz Fusion replacement, known as Wayfire, and the i3 window manager " +"replacement, Sway." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:80 +msgid "" +"As of May, 2021, plasma5-kwin does support Wayland on FreeBSD. To use " +"Plasma under Wayland, use the `startplasma-wayland` parameter to " +"`ck-launch-session` and tie in dbus with: `ck-launch-session " +"dbus-run-session startplasma-wayland` to get it working." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:86 +msgid "" +"For compositors, a kernel supporting the man:evdev[4] driver must exist to " +"utilize the keybinding functionality. This is built into the " +"[.filename]#GENERIC# kernel by default; however, if it has been customized " +"and man:evdev[4] support was stripped out, the man:evdev[4] module will need " +"to be loaded. In addition, users of `Wayland` will need to be members of " +"the `video` group. To quickly make this change, use the `pw` command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:90 +#, no-wrap +msgid "pw groupmod video -m user\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:95 +msgid "" +"Installing Wayland is simple; there is not a great deal of configuration for " +"the protocol itself. Most of the composition will depend on the chosen " +"compositor. By installing `seatd` now, a step is skipped as part of the " +"compositor installation and configuration as `seatd` is needed to provide " +"non-root access to certain devices." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:98 +msgid "" +"All of the compositors described here should work with " +"package:graphics/drm-kmod[] open source drivers; however, the NVidia " +"graphics cards may have issues when using the proprietary drivers. Begin by " +"installing the following packages:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:102 +#, no-wrap +msgid "# pkg install wayland seatd\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:107 +msgid "" +"Once the protocol and supporting packages have been installed, a compositor " +"must create the user interface. Several compositors will be covered in the " +"following sections. All compositors using Wayland will need a runtime " +"directory defined in the environment, which can be achieved with the " +"following command in the bourne shell:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:111 +#, no-wrap +msgid "% export XDG_RUNTIME_DIR=/var/run/user/`id -u`\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:116 +msgid "" +"It is important to note that most compositors will search the " +"XDG_RUNTIME_DIR directory for the configuration files. In the examples " +"included here, a parameter will be used to specify a configuration file in " +"[.filename]#~/.config# to keep temporary files and configuration files " +"separate. It is recommended that an alias be configured for each compositor " +"to load the designated configuration file." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:124 +msgid "" +"It has been reported that ZFS users may experience issues with some Wayland " +"clients because they need access to `posix_fallocate()` in the runtime " +"directory. While the author could not reproduce this issue on their ZFS " +"system, a recommended workaround is not to use ZFS for the runtime directory " +"and instead use `tmpfs` for the [.filename]#/var/run# directory. In this " +"case, the `tmpfs` file system is used for [.filename]#/var/run# and mounted " +"through the command `mount -t tmpfs tmpfs /var/run` command and then make " +"this change persist across reboots through [.filename]#/etc/fstab#. The " +"XDG_RUNTIME_DIR environment variable could be configured to use " +"[.filename]#/var/run/user/$UID# and avoid potential pitfalls with ZFS. " +"Consider that scenario when reviewing the configuration examples in the " +"following sections." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:129 +msgid "" +"The seatd daemon helps manage access to shared system devices for non-root " +"users in compositors; this includes graphics cards. For traditional X11 " +"managers, `seatd` is not needed, such as both Plasma and GNOME, but for the " +"Wayland compositors discussed here, it will need enabled on the system and " +"be running before starting a compositor environment. To enable and start " +"the `seatd` daemon now, and on system initialization:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:134 +#, no-wrap +msgid "" +"# sysrc seatd_enable=”YES”\n" +"# service seatd start\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:138 +msgid "" +"Afterward, a compositor, which is similar to an X11 desktop, will need to be " +"installed for the GUI environment. Three are discussed here, including " +"basic configuration options, setting up a screen lock, and recommendations " +"for more information." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:140 +#, no-wrap +msgid "The Wayfire Compositor" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:145 +msgid "" +"Wayfire is a compositor that aims to be lightweight and customizable. " +"Several features are available, and it brings back several elements from the " +"previously released Compiz Fusion desktop. All of the parts look beautiful " +"on modern hardware. To get Wayfire up and running, begin by installing the " +"required packages:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:149 +#, no-wrap +msgid "" +"# pkg install wayfire wf-shell alacritty swaylock-effects swayidle wlogout " +"kanshi mako wlsunset\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:155 +msgid "" +"The `alacritty` package provides a terminal emulator. Still, it is not " +"completely required as other terminal emulators such as `kitty`, and XFCE-4 " +"`Terminal` have been tested and verified to work under the Wayfire " +"compositor. Wayfire configuration is relatively simple; it uses a file that " +"should be reviewed for any customizations. To begin, copy the example file " +"over to the runtime environment configuration directory and then edit the " +"file:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:160 +#, no-wrap +msgid "" +"% mkdir ~/.config/wayfire\n" +"% cp /usr/local/share/examples/wayfire/wayfire.ini ~/.config/wayfire\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:165 +msgid "" +"The defaults for most users should be fine. Within the configuration file, " +"items like the famous `cube` are pre-configured, and there are instructions " +"to help with the available settings. A few primary settings of note " +"include:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:173 +#, no-wrap +msgid "" +"[output]\n" +"mode = 1920x1080@60000\n" +"position = 0,0\n" +"transform = normal\n" +"scale = 1.000000\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:181 +msgid "" +"In this example, from the configuration file, the screen's output should be " +"the listed mode at the listed hertz. For example, the mode should be set to " +"`widthxheight@refresh_rate`. The position places the output at a specific " +"pixel location specified. The default should be fine for most users. " +"Finally, transform sets a background transform, and scale will scale the " +"output to the specified scale factor. The defaults for these options are " +"generally acceptable; for more information, see the documentation." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:185 +msgid "" +"As mentioned, Wayland is new, and not all applications work with the " +"protocol yet. At this time, `sddm` does not appear to support starting and " +"managing compositors in Wayland. The `swaylock` utility has been used " +"instead in these examples. The configuration file contains options to run " +"`swayidle` and `swaylock` for idle and locking of the screen." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:187 +msgid "" +"This option to define the action to take when the system is idle is listed " +"as:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:191 +#, no-wrap +msgid "idle = swaylock\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:194 +msgid "And the lock timeout is configured using the following lines:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:201 +#, no-wrap +msgid "" +"[idle]\n" +"toggle = KEY_Z\n" +"screensaver_timeout = 300\n" +"dpms_timeout = 600\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:204 +msgid "" +"The first option will lock the screen after 300 seconds, and after another " +"300, the screen will shut off through the `dpms_timeout` option." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:212 +msgid "" +"One final thing to note is the key. Most of the configuration " +"mentions this key, and it is the traditional `Windows` key on the keyboard. " +"Most keyboards have this super key available; however, it should be remapped " +"within this configuration file if it is not available. For example, to lock " +"the screen, press and hold the super key, the kbd:[shift] key, and press the " +"kbd:[escape] key. nless the mappings have changed, this will execute the " +"swaylock application. The default configuration for `swaylock` will show a " +"grey screen; however, the application is highly customizable and well " +"documented. In addition, since the swaylock-effects is the version that was " +"installed, there are several options available such as the blur effect, " +"which can be seen using the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:216 +#, no-wrap +msgid "% swaylock --effect-blur 7x5\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:222 +msgid "" +"There is also the `--clock` parameter which will display a clock with the " +"date and time on the lock screen. When package:x11/swaylock-effects[] was " +"installed, a default [.filename]#pam.d# configuration was included. It " +"provides the default options that should be fine for most users. More " +"advanced options are available; see the PAM documentation for more " +"information." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:225 +msgid "" +"At this point, it is time to test Wayfire and see if it can start up on the " +"system. Just type the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:229 +#, no-wrap +msgid "% wayfire -c ~/.config/wayfire/wayfire.ini\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:236 +msgid "" +"The compositor should now start and display a background image along with a " +"menu bar at the top of the screen. Wayfire will attempt to list installed " +"compatible applications for the desktop and present them in this drop-down " +"menu; for example, if the XFCE-4 file manager is installed, it will show up " +"in this drop-down menu. If a specific application is compatible and " +"valuable enough for a keyboard shortcut, it may be mapped to a keyboard " +"sequence using the [.filename]#wayfire.ini# configuration file. Wayfire " +"also has a configuration tool named Wayfire Config Manager. It is located " +"in the drop-down menu bar but may also be started through a terminal by " +"issuing the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:240 +#, no-wrap +msgid "% wcm\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:244 +msgid "" +"Various Wayfire configuration options, including the composite special " +"effects, maybe enabled, disabled, or configured through this application. " +"In addition, for a more user-friendly experience, a background manager, " +"panel, and docking application may be enabled in the configuration file:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:250 +#, no-wrap +msgid "" +"panel = wf-panel\n" +"dock = wf-dock\n" +"background = wf-background\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:256 +msgid "" +"Changes made through `wcm` will overwrite custom changes in the " +"[.filename]#wayfire.ini# configuration file. The [.filename]#wayfire.ini# " +"file is highly recommended to be backed up so any essential changes may be " +"restored." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:259 +msgid "" +"Finally, the default launcher listed in the [.filename]#wayfire.ini# is " +"package:x11/wf-shell[] which may be replaced with other panels if desired by " +"the user." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:261 +#, no-wrap +msgid "The Hikari Compositor" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:271 +msgid "" +"The Hikari compositor uses several concepts centered around productivity, " +"such as sheets, workspaces, and more. In that way, it resembles a tiling " +"window manager. Breaking this down, the compositor starts with a single " +"workspace, which is similar to virtual desktops. Hikari uses a single " +"workspace or virtual desktop for user interaction. The workspace is made up " +"of several views, which are the working windows in the compositor grouped as " +"either sheets or groups. Both sheets and groups are made up of a collection " +"of views; again, the windows that are grouped together. When switching " +"between sheets or groups, the active sheet or group will become known " +"collectively as the workspace. The manual page will break this down into " +"more information on the functions of each but for this document, just " +"consider a single workspace utilizing a single sheet. Hikari installation " +"will comprise of a single package, package:x11-wm/hikari[], and a terminal " +"emulator `alacritty`:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:275 +#, no-wrap +msgid "# pkg install hikari alacritty\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:280 +msgid "" +"Other shells, such as `kitty` or the Plasma `Terminal`, will function under " +"Wayland. Users should experiment with their favorite terminal editor to " +"validate compatibility." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:285 +msgid "" +"Hikari uses a configuration file, [.filename]#hikari.conf#, which could " +"either be placed in the XDG_RUNTIME_DIR or specified on startup using the " +"`-c` parameter. An autostart configuration file is not required but may " +"make the migration to this compositor a little easier. Beginning the " +"configuration is to create the Hikari configuration directory and copy over " +"the configuration file for editing:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:290 +#, no-wrap +msgid "" +"% mkdir ~/.config/hikari\n" +"% cp /usr/local/etc/hikari/hikari.conf ~/.config/hikari\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:296 +msgid "" +"The configuration is broken out into various stanzas such as ui, outputs, " +"layouts, and more. For most users, the defaults will function fine; " +"however, some important changes should be made. For example, the $TERMINAL " +"variable is normally not set within the user's environment. Changing this " +"variable or altering the [.filename]#hikari.conf# file to read:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:300 +#, no-wrap +msgid "terminal = \"/usr/local/bin/alacritty\"\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:308 +msgid "" +"Will launch the `alacritty` terminal using the bound key press. While going " +"through the configuration file, it should be noted that the capital letters " +"are used to map keys out for the user. For example, the kbd:[L] key for " +"starting the terminal kbd:[L+Return] is actually the previously discussed " +"super key or Windows logo key. Therefore, holding the kbd:[L/super/Windows] " +"key and pressing kbd:[Enter] will open the specified terminal emulator with " +"the default configuration. Mapping other keys to applications require an " +"action definition to be created. For this, the action item should be listed " +"in the actions stanza, for example:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:315 +#, no-wrap +msgid "" +"actions {\n" +" terminal = \"/usr/local/bin/alacritty\"\n" +" browser = \"/usr/local/bin/firefox\"\n" +"}\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:318 +msgid "" +"Then an action may be mapped under the keyboard stanza, which is defined " +"within the bindings stanza:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:327 +#, no-wrap +msgid "" +"bindings {\n" +" keyboard {\n" +"SNIP\n" +" \"L+Return\" = action-terminal\n" +" \"L+b\" = action-browser\n" +"SNIP\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:333 +msgid "" +"After Hikari is restarted, holding the Windows logo button and pressing the " +"kbd:[b] key on the keyboard will start the web browser. The compositor does " +"not have a menu bar, and it is recommended the user set up, at minimal, a " +"terminal emulator before migration. The manual page contains a great deal " +"of documentation it should be read before performing a full migration. " +"Another positive aspect about Hikari is that, while migrating to the " +"compositor, Hikari can be started in the Plasma and GNOME desktop " +"environments, allowing for a test-drive before completely migrating." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:340 +msgid "" +"Locking the screen in Hikari is easy because a default [.filename]#pam.d# " +"configuration file and unlock utility are bundled with the package. The key " +"binding for locking the screen is kbd:[L] (Windows logo key)+ kbd:[Shift] + " +"kbd:[Backspace]. It should be noted that all views not marked public will " +"be hidden. These views will never accept input when locked but beware of " +"sensitive information being visible. For some users, it may be easier to " +"migrate to a different screen locking utility such as swaylock-effects, " +"discussed in this section. To start Hikari, use the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:344 +#, no-wrap +msgid "% hikari -c ~/.config/hikari/hikari.conf\n" +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:347 +#, no-wrap +msgid "The Sway Compositor" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:353 +msgid "" +"The Sway compositor is a tiling compositor that attempts to replace the i3 " +"windows manager. It should work with the user's current i3 configuration; " +"however, new features may require some additional setup. In the forthcoming " +"examples, a fresh installation without migrating any i3 configuration will " +"be assumed. To install Sway and valuable components, issue the following " +"command as the root user:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:357 +#, no-wrap +msgid "# pkg install sway swayidle swaylock-effects alacritty dmenu-wayland dmenu\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:360 +msgid "" +"For a basic configuration file, issue the following commands and then edit " +"the configuration file after it is copied:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:365 +#, no-wrap +msgid "" +"% mkdir ~/.config/sway\n" +"% cp /usr/local/etc/sway/config ~/.config/sway\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:369 +msgid "" +"The base configuration file has many defaults, which will be fine for most " +"users. Several important changes should be made like the following:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:385 +#, no-wrap +msgid "" +"# Logo key. Use Mod1 for Alt.\n" +"input * xkb_rules evdev\n" +"set $mod Mod4\n" +"# Your preferred terminal emulator\n" +"set $term alacritty\n" +"set $lock swaylock -f -c 000000\n" +"output \"My Workstation\" mode 1366x786@60Hz position 1366 0\n" +"output * bg ~/wallpapers/mywallpaper.png stretch\n" +"### Idle configuration\n" +"exec swayidle -w \\\n" +" timeout 300 'swaylock -f -c 000000' \\\n" +" timeout 600 'swaymsg \"output * dpms off\"' resume 'swaymsg " +"\"output * dpms on\"' \\\n" +" before-sleep 'swaylock -f -c 000000'\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:395 +msgid "" +"In the previous example, the `xkb` rules for man:evdev[4] events are loaded, " +"and the $mod key is set to the Windows logo key for the key bindings. Next, " +"the terminal emulator was set to be `alacritty`, and a screen lock command " +"was defined; more on this later. The output keyword, the mode, the " +"position, a background wallpaper, and Sway is also told to stretch this " +"wallpaper to fill out the screen. Finally, `swaylock` is set to daemonize " +"and lock the screen after a timeout of 300 seconds, placing the screen or " +"monitor into sleep mode after 600 seconds. The locked background color of " +"000000, which is black, is also defined here. Using swaylock-effects, a " +"clock may also be displayed with the `--clock` parameter. See the manual " +"page for more options. The man:sway-output[5] manual page should also be " +"reviewed; it includes a great deal of information on customing the output " +"options available." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:403 +msgid "" +"While in Sway, to bring up a menu of applications, hold the Windows logo key " +"(mod) and press the kbd:[d] key. The menu may be navigated using the arrow " +"keys on the keyboard. There is also a method to manipulate the layout of " +"the bar and add a tray; read the man:sway-bar[5] manual page for more " +"information. The default configuration adds a date and time to the upper " +"right-hand corner. See the `Bar` stanza in the configuration file for an " +"example. By default, the configuration does not include locking the screen " +"outside of the example above, enabling a lockout timer. Creating a lock key " +"binding requires the following line to the `Key bindings` section:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:408 +#, no-wrap +msgid "" +"# Lock the screen manually\n" +"bindsym $mod+Shift+Return exec $lock\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:414 +msgid "" +"Now the screen may be locked using the combination of holding the Windows " +"logo key, pressing and holding shift, and finally pressing return. When " +"Sway is installed, whether from a package or the FreeBSD Ports Collection, a " +"default file for [.filename]#pam.d# was installed. The default " +"configuration should be acceptable for most users, but more advanced options " +"are available. Read through the PAM documentation for more information." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:420 +msgid "" +"Finally, to exit Sway and return to the shell, hold the Windows logo key, " +"the shift key, and press the kbd:[e] key. A prompt will be displayed with " +"an option to exit Sway. During migration, Sway can be started through a " +"terminal emulator on an X11 desktop such as Plasma. This makes testing " +"different changes and key bindings a little easier prior to fully migrating " +"to this compositor. To start Sway, issue the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:424 +#, no-wrap +msgid "% sway -c ~/.config/sway/config\n" +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:427 +#, no-wrap +msgid "Using Xwayland" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:431 +msgid "" +"When installing Wayland, the `Xwayland` binary should have been installed " +"unless Wayland was built without X11 support. If the " +"[.filename]#/usr/local/bin/Xwayland# file does not exist, install it using " +"the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:435 +#, no-wrap +msgid "# pkg install xwayland-devel\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:441 +msgid "" +"The development version of Xwayland is recommended and was most likely " +"installed with the Wayland package. Each compositor has a method of " +"enabling or disabling this feature." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:445 +msgid "" +"Once `Xwayland` has been installed, configure it within the chosen " +"compositor. For Wayfire, the following line is required in the " +"[.filename]#wayfire.ini# file:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:449 +#, no-wrap +msgid "xwayland = true\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:453 +msgid "" +"For the Sway compositor, `Xwayland` should be enabled by default. Even so, " +"it is recommened to manually add a configuration line in the " +"[.filename]#~/.config/sway/config# like the following:" +msgstr "" + +#. type: delimited block . 5 +#: documentation/content/en/books/handbook/wayland/_index.adoc:457 +#, no-wrap +msgid "xwayland enable\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:462 +msgid "" +"Finally, for Hikari, no changes are needed. Support for `Xwayland` is build " +"in by default. To disable that support, rebuild the package from the ports " +"collection and disable Xwayland support at that time." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:466 +msgid "" +"After these changes are made, start the compositor at the command line and " +"execute a terminal from the key bindings. Within this terminal, issue the " +"`env` command and search for the `DISPLAY` variables. If the compositor was " +"able to properly start the Xwayland X server, these environment variables " +"should look similar to the following:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:470 +#: documentation/content/en/books/handbook/wayland/_index.adoc:500 +#, no-wrap +msgid "% env | grep DISPLAY\n" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:476 +#, no-wrap +msgid "" +"WAYLAND_DISPLAY=wayland-1\n" +"DISPLAY=:0\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:482 +msgid "" +"In this output, there is a default Wayland display and a display set for the " +"Xwayland server. Another method to verify that `Xwayland` is functioning " +"properly is to use install and test the small package:[x11/eyes] and check " +"the output. If the `xeyes` application starts and the eyes follow the mouse " +"pointer, Xwayland is functioning properly. If an error such as the " +"following is displayed, something happened during the `Xwayland` " +"intitialization and it may need reinstalled:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:486 +#, no-wrap +msgid "Error: Cannot open display wayland-0\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:492 +msgid "" +"A security feature of Wayland is that, without running an X server, there is " +"not another network listener. Once `Xwayland` is enabled, this security " +"feature is no longer applicable to the system." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:496 +msgid "" +"For some compositors, such as Wayfire, `Xwayland` may not start properly. " +"As such, `env` will show the following information for the `DISPLAY` " +"environment variables:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:506 +#, no-wrap +msgid "" +"DISPLAY=wayland-1\n" +"WAYLAND_DISPLAY=wayland-1\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:511 +msgid "" +"Even though `Xwayfire` was installed and configured, X11 applications will " +"not start giving a display issue. To work around this, verify that there is " +"already an instance of `Xwayland` using a UNIX socket through these two " +"methods. First, check the output from `sockstat` and search for X11-unix:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:515 +#, no-wrap +msgid "% sockstat | grep x11\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:518 +msgid "There should be something similar to the following information:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:526 +#, no-wrap +msgid "" +"trhodes Xwayland 2734 8 stream /tmp/.X11-unix/X0\n" +"trhodes Xwayland 2734 9 stream /tmp/.X11-unix/X0\n" +"trhodes Xwayland 2734 10 stream /tmp/.X11-unix/X0\n" +"trhodes Xwayland 2734 27 stream /tmp/.X11-unix/X0_\n" +"trhodes Xwayland 2734 28 stream /tmp/.X11-unix/X0\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:530 +msgid "" +"This suggests the existence of an X11 socket. This can be further verified " +"by attempting to execute `Xwayland` manually within a terminal emulator " +"running under the compositor:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:534 +#, no-wrap +msgid "% Xwayland\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:537 +msgid "" +"If an X11 socket is already available, the following error should be " +"presented to the user:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:546 +#, no-wrap +msgid "" +"(EE)\n" +"Fatal server error:\n" +"(EE) Server is already active for display 0\n" +"\tIf this server is no longer running, remove /tmp/.X0-lock\n" +"\tand start again.\n" +"(EE)\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:550 +msgid "" +"Since there is an active X display available using display zero, the " +"environment variable was just set improperly, to fix this, change the " +"`DISPLAY` environment variable to `:0` and attempt to execute the " +"application again. The following example uses package:mail/claws-mail[] as " +"the application which needs the `Xwayland` service:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:554 +#, no-wrap +msgid "export DISPLAY=:0\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:557 +msgid "" +"After this change, the package:mail/claws-mail[] application should now " +"start using `Xwayland` and function as expected." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:559 +#, no-wrap +msgid "Remote Desktop Using VNC" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:565 +msgid "" +"Earlier in this document it was noted that Wayland does not provide the same " +"X server style access as Xorg provides. Instead, users are free to pick and " +"choose a remote desktop protocol such as RDP or VNC. The FreeBSD Ports " +"collection includes the `wayvnc`, which will support wlroots based " +"compositors such as the ones discussed here. This application may be " +"installed using:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:569 +#, no-wrap +msgid "# pkg install wayvnc\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:573 +msgid "" +"Unlike some other packages, `wayvnc` does not come with a configuration " +"file. Thankfully, the manual page documents the important options and they " +"may be extrapolated into a simple configuration file:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:582 +#, no-wrap +msgid "" +"address=0.0.0.0\n" +"enable_auth=true\n" +"username=username\n" +"password=password\n" +"private_key_file=/path/to/key.pem\n" +"certificate_file=/path/to/cert.pem\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:588 +msgid "" +"The key files will need to be generated, and it is highly recommended they " +"be used for increased security of the connection. When invoked, wayvnc will " +"search for the configuration file in [.filename]#~/.config/wayvnc/config#. " +"This could be overwritten using the `-C configuration_file` option when " +"starting the server. Thus, to start the `wayvnc` server, issue the " +"following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:592 +#, no-wrap +msgid "% wayvnc -C ~/.config/wayvnc/config\n" +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:599 +msgid "" +"At the time of this writing, there is no rc.d script to start `wayvnc` on " +"system initialization. If that functionality is desired, a local startup " +"file will need to be created. This is probably a feature request for the " +"port maintainer." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:602 +#, no-wrap +msgid "Wayland Login Manager" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:606 +msgid "" +"While several login managers exist and are slowly migrating to Wayland, one " +"option is the package:x11/ly[] text user interface (TUI) manager. Needing " +"minimal configuration, `ly` will start Sway, Wayfire, and others by " +"presenting a login window on system initialization. To install `ly`, issue " +"the following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:610 +#, no-wrap +msgid "# pkg install ly\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:613 +msgid "" +"There will be some configuration hints presented, the import steps are to " +"add the following lines to [.filename]#/etc/gettytab#:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:619 +#, no-wrap +msgid "" +"Ly:\\\n" +" :lo=/usr/local/bin/ly:\\\n" +" :al=root:\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:622 +msgid "" +"And then modify the ttyv1 line in [.filename]#/etc/ttys# to match the " +"following line:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:626 +#, no-wrap +msgid "ttyv1 \"/usr/libexec/getty Ly\" xterm onifexists secure\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:631 +msgid "" +"After a system reboot, a login should appear. To configure specific " +"settings, such as language and edit " +"[.filename]#/usr/local/etc/ly/config.ini#. At minimal, this file should " +"have the designated tty that was previously specified in " +"[.filename]#/etc/ttys#." +msgstr "" + +#. type: delimited block = 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:635 +msgid "" +"If setting ttyv0 up as the login terminal, it may be required to press the " +"kbd:[alt] and kbd:[F1] keys to properly see the login window." +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:638 +msgid "" +"When the login window appears, using the left and right arrows will swap " +"through different, supported, window managers." +msgstr "" + +#. type: Title == +#: documentation/content/en/books/handbook/wayland/_index.adoc:640 +#, no-wrap +msgid "Useful Utilities" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:646 +msgid "" +"One useful Wayland utility which all compositors can make use of is the " +"waybar. While Wayfire does come with a launch menu, an easy-to-use and fast " +"taskbar is a good accessory for any compositor or desktop manager. A " +"Wayland compatible taskbar that is fast and easy to configure is waybar. To " +"install the package and a supporting audio control utility, issue the " +"following command:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:650 +#, no-wrap +msgid "# pkg install pavucontrol waybar\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:653 +msgid "" +"To create the configuration directory and copy over a default configuration " +"file, execute the following commands:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:658 +#, no-wrap +msgid "" +"% mkdir ~/.config/waybar\n" +"% cp /usr/local/etc/xdg/waybar/config ~/.config/waybar\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:662 +msgid "" +"The `lavalauncher` utility provides a launch bar for various applications. " +"There is no example configuration file provided with the package, so the " +"following actions must be taken:" +msgstr "" + +#. type: delimited block - 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:666 +#, no-wrap +msgid "mkdir ~/.config/lavalauncher\n" +msgstr "" + +#. type: Plain text +#: documentation/content/en/books/handbook/wayland/_index.adoc:669 +msgid "" +"An example configuration file that only includes Firefox, and is placed on " +"the right, is below:" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:675 +#, no-wrap +msgid "" +"global-settings {\n" +"\twatch-config-file = true;\n" +"}\n" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:680 +#, no-wrap +msgid "" +"bar {\n" +"\toutput = eDP-1;\n" +"\tposition = bottom;\n" +"\tbackground-colour = \"#202020\";\n" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:683 +#, no-wrap +msgid "" +"\t# Condition for the default configuration set.\n" +"\tcondition-resolution = wider-than-high;\n" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:687 +#, no-wrap +msgid "" +"\tconfig {\n" +"\t\tposition = right;\n" +"\t}\n" +msgstr "" + +#. type: delimited block . 4 +#: documentation/content/en/books/handbook/wayland/_index.adoc:696 +#, no-wrap +msgid "" +"\tbutton {\n" +"\t\timage-path = " +"/usr/local/lib/firefox/browser/chrome/icons/default/default48.png;\n" +"\t\tcommand[mouse-left] = /usr/local/bin/firefox;\n" +"\t}\n" +"\tbutton {\n" +"\t image-path = /usr/local/share/pixmaps/thunderbird.png;\n" +"\t command[mouse-left] = /usr/local/bin/thunderbird;\n" +"}\n" +msgstr ""