y.st./source/pages/en/a/licensing.xhtml

<?php
/**
 * <https://y.st./>
 * Copyright © 2017 Alex Yst <mailto:copyright@y.st>
 * 
 * This program 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.
 * 
 * This program 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 this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'Website component licensing',
	'subtitle' => 'The licenses that apply to this website and individual files',
	'copyright year' => '2017',
	'body' => <<<END
<p>
	As a whole, this website is offered to you under the terms of the $a[GNU] General Public License version Three.
	At your option, you may instead use any later version of this license, as published by the $a[FSF].
	I may not like the $a[FSF] because of their noxious attitude toward the freedoms needed with non-software, but their software license fits the needs of this website well.
	Additionally, individual files may be under additional and more permissive licenses.
	If the file is in a text-based format that allows comments (for example, $a[XHTML], $a[CSS], and JavaScript), the license information that applies to that file will be in the comments.
	$a[XHTML] files additionally have this information in the footer, though this would break $[CSS] and JavaScript files, so you&apos;ll just have to read the comments of those.
	Files with paths ending in &quot;.asc&quot; are released as-is.
	They&apos;re signature files and you may not have the private key that I used to sign my pages.
	If you edit my pages and wish the edited version to be signed, you&apos;ll need to sign with your own key as to not misrepresent me.
	That said, the signature files are still under the same license as the rest of the website, so if you wanted to use them for something, you&apos;d be able to, though I can&apos;t fathom what they&apos;d be useful for.
	The <a href="/a/canary.txt">canary</a> file also doesn&apos;t specify a license, but again, is covered by the $a[GNU] {$a['GPLv3+']} with no signing key provided.
	The non-text files of this website have typically been stored using file paths that reference both the license and the domain that the file originated from.
	There has been one exception to this, and that has been any image that is referenced in $a[XHTML] files using the <code>&lt;link/&gt;</code> tag (directly (in the case of the website icon) or indirectly (in the case of images used in $a[CSS])).
	As of <span title="{$entry(2017, 02, 01)}">2017-02-01</span>, this exception has been corrected.
	All non-text files are dual licensed under the $a[GNU] {$a['GPLv3+']} and a license specified in the path.
	The path format is as follows:
</p>
<blockquote>
	<p>
		/{tag}/{license}/{domain}/{image}
	</p>
</blockquote>
<p>
	{tag} is the $a[XHTML] tag used to reference the file, and is mainly for internal use.
	It won&apos;t apply to your use outside of this website.
	{license} is the abbreviation of the name of the license that applies in addition to the $a[GNU] {$a['GPLv3+']}.
	This will usually be either a {$a['CC BY']} or {$a['CC BY-SA']} license with a particular version number.
	{domain} will be the domain in which the image originated from.
	In cases where the image didn&apos;t originate from this domain, I&apos;ll usually include more complete attribution in the $a[XHTML] file that references the image.
	{image} can be anything that completes the path.
	It may contain one or several nested directories and will contain the file name including the file extension.
	This information, like {tag}, may not be meaningful for your purposes and can be thrown away.
</p>
<p>
	For your convenience as well as mine, a couple Git repositories exist that show this website&apos;s code in full:
</p>
<ul>
	<li>
		<a href="https://git.vola7ileiax4ueow.onion/y.st./y.st.">On Volatile Git</a>
	</li>
	<li>
		<a href="https://notabug.org./y.st./y.st.">On NotABug.org</a>
	</li>
</ul>
<p>
	As of late, these repositories have not been seeing daily updates.
	Be patient though, updates are made available about monthly.
</p>
END
);