Documentation for “Zerocat Label Documentation”
Generated on: Sat, 18 Jun 2022 13:18:06 +0200
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
Within this project’s git repository, versions are tagged according to the following pattern:
<major>– The resulting product is a major change or upgrade.
<minor>– Additional functionality or new features are introduced.
<revision>– Bug fixes, minor changes, graphical stuff.
This version comes with a new documentation system, according to: Zerocat Project Template v0.0.12
The goal of Zerocat Label Documentation is to provide you with some general information about the label itself, in opposite to project specific infos.
All paths within this document are relative in respect to the original
location of this source file, which is located in the project’s
It is assumed that you are running a GNU/Linux-libre operating system.
Use git to clone the project’s sources:
git clone git://zerocat.org/zerocat/projects/doc
Change into the project’s documentation folder:
README.md to get started:
If you are on GNU Guix System, use make to create a dedicated profile, once. This allows you to match your environment to the one used by Zerocat, thus producing bit-identical results:
make -C ../guix pull
Create an empty environment with dedicated guix channel:
make -C ../guix environment
Create a shell with all prerequisites set up:
make -C ../guix shell
To leave the shell and the environment, later on, when you are done with this project, type:
To remove this project’s handy guix profile, type:
make -C ../guix clean
This will remove symlinks only. If you want to remove the profile from your system, run the GNU Guix Garbage Collector.
To list all available targets, type:
make -C ../guix help
If you are on another distro, check file ../guix/manifest.scm and install the listed packages with your package manager, manually. Adapt package names as required.
To build the documentation, type:
make -C ../doc
To get a full list of available targets, type:
make -C ../doc help
To clean-up, type:
make -C ../doc clean
Zerocat Label Documentation ships copyrighted work.
Zerocat Label Documentation is free software. It makes use of free software approved licenses only and should be freely distributable:
Authorship, copyright and license information may be provided in more detail on a per-folder and/or per-file basis. Check the sources.
Please report a bug if you find the distribution hindered.
See Zerocat Website for contact information.
Documentation source files are written in markdown syntax. They should carry their individual copyright and license notices right below the title giving headline, e.g.:
<Title-of-Document> =================== Copyright (C) <Year> <Name-of-Author> <Email-Address> Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". <Other-Headline> ---------------- ...content...
The generated documentation carries a license notice right at top on
its title page, with copyright statements generated from
Sections of the generated documentation are build from selected markdown source files, with their individual copyright and license notice stripped.
In order to enrich the generated documentation ...
*.mdmarkdown source files to
... and adapt ../doc/Makefile to produce nice output.
In case more tools are needed, don't forget to update ../guix/manifest.scm.
To make your image look nice within the documentation, select a landscape layout of 16:9 aspect ratio.
Use ImageMagick to prepare your image, e.g.:
If your image is big, reduce it to a maximal width of 2000 pixel:
mogrify -resize 2000x <image>
Please clean image files from metadata, before committing, i.e.:
mogrify -strip <image>
If you embed your image into a markdown documentation file, use this syntax:
![<path/to/image>] [<path/to/image>]: <path/to/image> "title message"
![<path/to/image>][my-image-shortcut] [my-image-shortcut]: <path/to/image> "title message"
These patterns will guarantee that
<img> tags will have their
title attributes properly set within the html output.
Please use this license header for code source files:
Zerocat Label Documentation --- General infos Copyright (C) <Year> <Name-of-Author> <Email-Address> This file is part of Zerocat Label Documentation. Zerocat Label Documentation is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. Zerocat Label Documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with Zerocat Label Documentation. If not, see <http://www.gnu.org/licenses/>.
If you intend to write shell scripts, use this skeleton to make them work for GNU Guix:
#!/bin/sh # Re-exec if we are not using Bash or are using Bash in POSIX mode. if [ -z "$BASH" ] || [ "$BASH" = "/bin/sh" ]; then bash=`command -v bash` if [ -z "$bash" ]; then echo "Couldn't find Bash, sorry!" exit 1 else exec "$bash" "$0" "$@" fi fi # We're using Bash now. set -o errexit set -o nounset set -o pipefail # Your code goes here ...
Update ../doc/NEWS.md and list your contributions.
You can use
git shortlog to get a starting point for your edit.
The domain names “www.zerocat.org” and “www.zerocat.de” are both pointing
to our server.
The server’s IP address is “188.8.131.52”.
Zerocat’s git repositories are hosted by user
git, and access control
is managed by a gatekeeper. A client can talk to the server’s
gatekeeper using SSH authentication, thus the generation of an
SSH keypair might be required.
Please make sure the following programs are available on your machine:
git– Distributed version control system
openssh– Client and server for the secure shell (ssh) protocol
Get yourself prepared by studying the output of:
You can generate a new pair of SSH keys by running:
$ ssh-keygen \ -t rsa \ -b 4096 \ -C "" \ -f ~/.ssh/my-zerocat-ssh-id
Adapt settings to your needs. This will create a pair of keys – a
secret and a public one, i.e.:
In case your public SSH key has been deposited on the server, you
might talk to the gatekeeper over
ssh and use the
info command to get
a full overview of repositories and of your current access permissions:
$ ssh -2 -4 \ -i ~/.ssh/my-zerocat-ssh-id \ -p 32323 \ email@example.com info
Note, as default, this would look up your
~/.ssh/id_rsa file for
authentication, but you specified an individual identity file with the
The gatekeeper offers some more commands, like:
help(lists all available commands)
desc(describes a specified repository)
$ ssh -2 -4 \ -i ~/.ssh/my-zerocat-ssh-id \ -p 32323 \ firstname.lastname@example.org desc zerocat/projects/chipflasher
Note the server’s SSH Daemon is listening to port 32323 only.
ssh client supports a configuration file named
where you can manually bundle the required credentials to make things
easier to deal with, e.g.:
~/.ssh/config -------------------------------------- host git-gatekeeper-zerocat user git hostname 184.108.40.206 port 32323 identityfile ~/.ssh/my-zerocat-ssh-id addressfamily inet serveraliveinterval 60 serveralivecountmax 10 PubkeyAcceptedKeyTypes +ssh-rsa
$ git clone ssh://git-gatekeeper-zerocat/zerocat/projects/<project-name>
This will download the repository and sets
origin to the same used
Now change into the newly created project folder and run
to see the project’s history.
Some repositories are publically accessible without authentication, i.e.:
Cloning can therefor be done using the git protocol:
$ git clone git://zerocat.org/zerocat/projects/chipflasher
These public projects are promoted on our website: www.zerocat.org/
Pro Git, Apress, 2nd edition, 2014
Git from the Bottom Up
The Thing About Git, explains
git add --patch
gitk example run-through: Use
gitk to understand
How to Write good Commit Messages
To ease collaboration, we would like to suggest the follwing settings
for your Git Configuration. You might place them in the
file of a project’s root folder, or – as an alternative – in your
global Git Configuration File
[user] name = <your name> email = <your email address> signingkey = <your PGP key ID> [commit] gpgsign = true [core] editor = nano [alias] # git log: # l: log, g: --graph --color, # c: --oneline, s: --pretty=short, f: --pretty=format, # a: --all lg = log --graph --color --decorate lga = log --graph --color --decorate --all lgc = log --graph --color --decorate --oneline lgca = log --graph --color --decorate --oneline --all lgs = log --graph --color --decorate --pretty=short lgsa = log --graph --color --decorate --pretty=short --all lgf = log --graph --color --decorate --pretty=format:'%C(auto) %h %d %G? %aN %s' lgfa = log --graph --color --decorate --pretty=format:'%C(auto) %h %d %G? %aN %s' --all # git diff: check = diff --check [push] default = simple
[alias] section now contains some aliases for
git log, and
git lgca should help you to get a quick overview of the
repository’s history. In case you need to verify authors, use
To see whether your changes would introduce misplaced white-space, run
git check as an alias of
git diff --check.
When using GPG-signed commits as suggested by
gpgsign = true in
[commit], please check your
~/.gnupg/gpg-agent.conf to have
a line available which specifies a pinentry program, i.e.:
Inspired by "Pro Git" book.
# get started with a repository git init git clone # show changes git diff git diff --cached # same as `--staged` git status git status -uno git status -s # commit changes git commit -am "<commit message>" # fast commit of *all* changes git add <file> git add --patch git commit -m "<commit message>" # fast commit of *staged* changes git commit --no-status git commit --uno # rename or delete files git mv git rm # work with branches git branch # list local branches, mark current one git branch <a-new-branch> # create a new local branch, but stay on current one git checkout -b <a-new-branch> # create *and* checkout a new local branch git stash # push away current changes which might hinder you to checkout elsewhere git stash pop # pop previously pushed changes # set up new-branch to track remote new-branch git checkout new-branch # delete branch upstream git push origin :my-obsolete-branch # delete local copies of already deleted upstream branches git fetch --prune # refers to all local copies of remotes # show history of commits git log git log --pretty=format:"%h %an %s" --graph git log --abbrev-commit --pretty=oneline --graph git log --abbrev-commit --pretty=medium git log -p -2 git log --follow <filename> # git configuration git config --list git config --add format.pretty oneline git remote -v git difftool --tool-help # show differences between commits/ branches/ tags/ etc. # in detail...: git diff <from> <to> git diff master documentation # in short...: git diff --stat <from> <to> git diff --stat <refspec> HEAD # you can omit 'HEAD'
Project Initiator and Maintainer ...
masteror asks contributors to do so
git branch my-new-branch ; git checkout my-new-branch git add new-file-in-branch ... git commit ... git push origin my-new-branch # Announce this via email git branch --set-upstream-to=origin/my-new-branch my-new-branch ... ... git push origin --delete my-new-branch # We are done with the branch, delete on server
git pull origin # Now new remote branches are visible git checkout my-new-branch # Sets up tracking branch (git branch -vv) ... ... git branch --delete my-new-branch # We are done with the branch, delete locally
git checkout master git merge my-new-branch
The (original) language is described here: https://daringfireball.net/projects/markdown/
Plenty of variants and extensions are around:
There a many different translators available.
This is a C/C++ implementation with an extensive test suite: https://github.com/jgm/cmark
To run it:
cmark in.md > out.html
To get something quickly up and running for openSUSE there is the "discount" package available:
It consists of a single lisp file
markdown-mode.el that needs to be
found in the Emacs load path. (Does not work with XEmacs.)
This is supposed to be as brief as possible. The goal is to capture a minimal subset of Markdown that is sufficent for our needs and is understood widely by various tools.
How to write markdown files, some guides:
Maintain a copyright and license notice right below title giving, first headline. Maintain copyright statements without leading spaces, but with two spaces inbetween and at the end in order to force a line break:
Copyright (C) <Year> <Name-of-Author> <Email-Address> ... GNU-FDL License Notice ...
We can take inspiration from others, for example
File ../images/ce-marking.png has been manually reproduced according to information given on: https://ec.europa.eu/growth/single-market/ce-marking_en
Version 1.3, 3 November 2008
Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
The "publisher" means any person or entity that distributes copies of the Document to the public.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.
"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A "Massive Multiauthor Collaboration" (or "MMC") contained in the site means any set of copyrightable works thus published on the MMC site.
"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.
"Incorporate" means to publish or republish a Document, in whole or in part, as part of another Document.
An MMC is "eligible for relicensing" if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Copyright (C) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with … Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.