diff --git a/content/architecture/apis-and-services.md b/content/architecture/apis-and-services.md
index 2ea0b1fbfd343f3d05a324e67d90241bfb691e80..7890dce27a4adf389852b854510c005de1c999e4 100644
--- a/content/architecture/apis-and-services.md
+++ b/content/architecture/apis-and-services.md
@@ -227,8 +227,8 @@ Full package list in TSV format, categorized under different repository componen
- [gdk-pixbuf](https://developer.gnome.org/gdk-pixbuf/2.36/): Image manipulation
- [pixman](http://www.pixman.org/): Low-level graphics
-- [Pango](https://developer.gnome.org/pango/stable/): High-level font rendering
-- [Mesa](http://mesa3d.org/sourcedocs.html): Low-level graphics
+- [Pango](https://pango.gnome.org/): High-level font rendering
+- [Mesa](https://docs.mesa3d.org/): Low-level graphics
- [harfbuzz](https://www.freedesktop.org/wiki/Software/HarfBuzz/): Low-level font rendering
- [freetype](https://www.freetype.org/freetype2/docs/documentation.html): Low-level font rendering
- [JSON GLib](https://developer.gnome.org/json-glib/1.2/): (De)serialization of JSON
diff --git a/content/architecture/bundle-spec.md b/content/architecture/bundle-spec.md
index 197721eccb8d1169aa8255938d6c3af72c294600..1cc4dd7245517ea4e7de668470c74eaed7a78d6c 100644
--- a/content/architecture/bundle-spec.md
+++ b/content/architecture/bundle-spec.md
@@ -13,7 +13,7 @@ date = "2016-09-05"
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
-[RFC 2119](https://tools.ietf.org/html/rfc2119).
+[RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119).
This specification uses [semantic versioning]. After version 1.0.0 is
finalized, the major version number (first component) will be incremented
@@ -1225,7 +1225,7 @@ backwards compatibility, and is considered deprecated.
[IETF Media Types]: https://www.iana.org/assignments/media-types/media-types.xhtml
[IETF URI schemes]: https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml
[localestring]: https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#localized-keys
-[Portable Network Graphics]: https://tools.ietf.org/html/rfc2083
+[Portable Network Graphics]: https://datatracker.ietf.org/doc/html/rfc2083
[DBusActivatable]: https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#dbus
[org.gtk.Application]: https://wiki.gnome.org/Projects/GLib/GApplication/DBusAPI
[Reverse domain name notation]: https://en.wikipedia.org/wiki/Reverse_domain_name_notation
diff --git a/content/architecture/image-build-infrastructure.md b/content/architecture/image-build-infrastructure.md
index 1ae86b62b8bacc3dd52b713966faac0c44bc284d..55b15a2d2a5860f3981aa9fc3a7162e49af20d23 100644
--- a/content/architecture/image-build-infrastructure.md
+++ b/content/architecture/image-build-infrastructure.md
@@ -297,8 +297,8 @@ Jenkins master:
* workflow-support
* ws-cleanup
-To retrieve the list, access the [script console](https://jenkins.apertis.org/script)
-and enter the following Groovy script:
+To retrieve the list, access the script console and enter the following Groovy
+script:
```
Jenkins.instance.pluginManager.plugins.toList()
diff --git a/content/architecture/sysroots-and-devroots.md b/content/architecture/sysroots-and-devroots.md
index de9ba44e909b56e6f5d1cf20683476f15a5e4713..f8fbf2812567651831a3cf310747e79cafc9f204 100644
--- a/content/architecture/sysroots-and-devroots.md
+++ b/content/architecture/sysroots-and-devroots.md
@@ -57,9 +57,9 @@ the target release is recommended.
Sysroots are available from the Apertis release artifact repository
as `sysroot*.tar.gz` tarballs under the `$release/$architecture/sysroot/` folder,
for instance
-[`sysroot-apertis-v2019pre-arm64-v2019pre.0.tar.gz`](https://images.apertis.org/release/v2019pre/v2019pre.0/arm64/sysroot/sysroot-apertis-v2019pre-arm64-v2019pre.0.tar.gz)
+[`sysroot-apertis-v2021-amd64-v2021.0.tar.gz`](https://images.apertis.org/release/v2021/v2021.0/amd64/sysroot/sysroot-apertis-v2021-amd64-v2021.0.tar.gz)
under
-[`v2019pre.0/arm64`](https://images.apertis.org/release/v2019pre/v2019pre.0/arm64/sysroot/).
+[`v2021.0/arm64`](https://images.apertis.org/release/v2021/v2021.0/amd64/sysroot/).
# Devroot
@@ -95,11 +95,11 @@ architectures.
Devroots are available from the Apertis release artifact repository
as the `ospack*.tar.gz` tarballs under the `$release/$architecture/devroot/` folder,
for instance
-[`ospack_v2019pre-arm64-devroot_v2019pre.0.tar.gz`](https://images.apertis.org/release/v2019pre/v2019pre.0/arm64/devroot/ospack_v2019pre-arm64-devroot_v2019pre.0.tar.gz)
+[`ospack_v2021-amd64-devroot_v2021.0.tar.gz`](https://images.apertis.org/release/v2021/v2021.0/amd64/devroot/ospack_v2021-amd64-devroot_v2021.0.tar.gz)
under
-[`v2019pre.0/arm64`](https://images.apertis.org/release/v2019pre/v2019pre.0/arm64/devroot/).
+[`v2021.0/arm64`](https://images.apertis.org/release/v2021/v2021.0/amd64/devroot/).
-As of `v2019pre`, the Apertis SDK images come with the `armhf` devroot pre-installed.
+As of `v2019`, the Apertis SDK images come with the `armhf` devroot pre-installed.
# A comparison
diff --git a/content/architecture/web-engine.md b/content/architecture/web-engine.md
index 342235a909c7ccf619c7995e8fc20a9f5b2d3749..0e77082c7a24e93b0612f148785d96bdd101ded0 100644
--- a/content/architecture/web-engine.md
+++ b/content/architecture/web-engine.md
@@ -100,6 +100,6 @@ That ensures the APIs will feel native to the JavaScript environment,
and will significantly reduce the attack surface presented to pages,
compared to a solution that makes all native libraries available.
-[Web]: https://live.gnome.org/Design/Web
+[Web]: https://wiki.gnome.org/Apps/Web
[Epiphany]: https://live.gnome.org/Epiphany
diff --git a/content/concepts/application-bundle-metadata.md b/content/concepts/application-bundle-metadata.md
index 84d1c029f6b218b93b133a71dd1154001be33045..5dcf76bc5ad6b6223501788f0b80ee5b38dd1235 100644
--- a/content/concepts/application-bundle-metadata.md
+++ b/content/concepts/application-bundle-metadata.md
@@ -586,6 +586,6 @@ requester's AppArmor label (part of the AppArmor context).
[Platform]: {{< ref "glossary.md#platform" >}}
[Security concept design]: {{< ref "security.md" >}}
[Snappy]: http://snapcraft.io/
-[Snappy metadata]: https://developer.ubuntu.com/en/snappy/guides/meta/
+[Snappy metadata]: https://snapcraft.io/docs/snapcraft-top-level-metadata
[System extension]: {{< ref "applications.md#system-extensions" >}}
[X-Vendor]: https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#extending
diff --git a/content/concepts/applications.md b/content/concepts/applications.md
index 8c99591826b1a67572f2f8b86d798bce462d46fe..86ae00ea2f9b105c651da919f165e01c469cfe82 100644
--- a/content/concepts/applications.md
+++ b/content/concepts/applications.md
@@ -1336,16 +1336,15 @@ last system upgrade.
This document references the following external sources of information:
- - XDG Base Directory Specification:
- [*http://standards.freedesktop.org/basedir-spec-latest.html*](http://standards.freedesktop.org/basedir-spec-latest.html)
+ - [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/)
- - Apertis System Updates and Rollback design
+ - Apertis [System Updates and Rollback]({{< ref "system-updates-and-rollback.md" >}}) design
- - Apertis Multiuser design
+ - Apertis [Multiuser]({{< ref "multiuser.md" >}}) design
- - Apertis Supported API design
+ - Apertis [Supported API]({{< ref "supported-api.md" >}}) design
- - Apertis Preferences and Persistence design
+ - Apertis [Preferences and Persistence]({{< ref "preferences-and-persistence.md" >}}) design
- Eastlake 3rd, D. and A. Panitz, "Reserved Top Level DNS Names", BCP
32, RFC 2606, DOI 10.17487/RFC2606, June 1999
@@ -1371,13 +1370,13 @@ This document references the following external sources of information:
[XDG Base Directory Specification]: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
-[LUKS]: https://code.google.com/p/cryptsetup/
+[LUKS]: https://gitlab.com/cryptsetup/cryptsetup
[tar's checkpoint]: http://www.gnu.org/software/tar/manual/html_section/checkpoints.html
[libosso]: http://maemo.org/api_refs/5.0/5.0-final/libosso/group__Statesave.html
-[memory.usage_in_bytes]: http://www.kernel.org/doc/Documentation/cgroups/memory.txt
+[memory.usage_in_bytes]: https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt
[GMemoryMonitor]: https://gitlab.gnome.org/GNOME/glib/merge_requests/1005
diff --git a/content/concepts/conditional_access.md b/content/concepts/conditional_access.md
index f7259333864c669ecbfff89a461d0a08eb1dcd54..602075e82bd294cbbcd8cac7a2491d316e387920 100644
--- a/content/concepts/conditional_access.md
+++ b/content/concepts/conditional_access.md
@@ -1606,7 +1606,7 @@ We recommend representing a downloaded app-bundle as follows:
**Unresolved:** In the current design we are encrypting the access
tokens, which has the effect of ["binding" the signature to the
-encryption](http://world.std.com/~dtd/sign_encrypt/sign_encrypt7.html).
+encryption](https://theworld.com/~dtd/sign_encrypt/sign_encrypt7.html).
Are we gaining any desired security properties from doing so, or would
it be sufficient to send an encrypted session key along with a signed
but unencrypted access token? Does an attacker gain anything from the
diff --git a/content/concepts/connectivity.md b/content/concepts/connectivity.md
index 3dfed314f94cf231940d87e9073cf73ae149f5ff..74a66493bc4f29e0f7ae4ca76b2130f4660d31cc 100644
--- a/content/concepts/connectivity.md
+++ b/content/concepts/connectivity.md
@@ -327,7 +327,7 @@ which protocol they want for a given conversation.
Existing open-source connection managers support messaging through
Jabber, GTalk, Facebook, Live Messenger, and more. Audio and video calls
-are also supported over Jabber, GTalk and SIP. See the [Telepathy wiki]
+are also supported over Jabber, GTalk and SIP. See the [Telepathy site]
for more details. Before deciding on shipping any of these,
however, it's important to verify whether any legal issues may arise,
mainly related to trademarks.
@@ -451,7 +451,7 @@ access point that other devices can connect to. This is done by turning
on tethering mode on WiFi or Bluetooth.
> See the tethering properties at the bottom of
-> <http://git.kernel.org/?p=network/connman/connman.git;a=blob;f=doc/technology-api.txt;h=851d5ea629975c9c82d86c7863aaab2997485c34;hb=HEAD>
+> <https://git.kernel.org/pub/scm/network/connman/connman.git/tree/doc/technology-api.txt?id=HEAD>
As is the case with other features, this needs proper UI to be created to let the user turn the
tethering on as well as specify the desired SSID and pass-phrase for
@@ -685,7 +685,7 @@ Note that HostIP is essentially useless for mobile use cases, since
it tries to use the IP address as an indication of the location, but
that is not very accurate in general and for mobile specifically
-> A somewhat outdated list: <http://www.freedesktop.org/wiki/Software/GeoClue/Providers>
+> A somewhat outdated list: <https://gitlab.freedesktop.org/geoclue/geoclue/-/wikis/home>
Those could be useful to provide
location information with coarse accuracy for applications such as the
@@ -758,13 +758,13 @@ gupnp library. For more information about this please see the Media
Management design document (sometimes referred to as Media/Indexing
design).
-[ConnMan]: http://ConnMan.net/
+[ConnMan]: https://git.kernel.org/pub/scm/network/connman/connman.git/
[oFono]: http://oFono.org/
-[BlueZ]: http://bluez.org/
+[BlueZ]: http://www.bluez.org/
-[connman-networking]: http://git.kernel.org/?p=network/connman/connman.git;a=blob;f=doc/session-api.txt;h=e19c6bfe0b6e6fc379cfa3632ac21f338610717d;hb=HEAD)
+[connman-networking]: https://git.kernel.org/pub/scm/network/connman/connman.git/tree/doc/session-api.txt?id=HEAD
[NET_RAW capability]: http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=net/core/sock.c;h=b374899aecb6ea3a8590ae9ccdbb3e60225561d4;hb=HEAD#l470
@@ -776,9 +776,9 @@ design).
[N9 devices]: http://techprolonged.com/index.php/2011/11/12/nokia-n9-a-complete-walk-through-meego-harmattan-software-and-user-interface-experience/#contacts-calling
-[Telepathy wiki]: http://telepathy.freedesktop.org/wiki/Protocols%20Support
+[Telepathy site]: https://telepathy.freedesktop.org/components/
-[ipheth]: http://giagio.com/wiki/moin.cgi/iPhoneEthernetDriver
+[ipheth]: https://github.com/torvalds/linux/blob/master/drivers/net/usb/ipheth.c
[bluez-profiles]: http://www.bluez.org/profiles/
@@ -790,7 +790,7 @@ design).
[gypsy]: http://gypsy.freedesktop.org/
-[USB implementers forum]: http://www.usb.org/developers/devclass_docs/MTP_1.0.zip
+[USB implementers forum]: https://usb.org/sites/default/files/MTPv1_1.zip
[libmtp]: http://libmtp.sourceforge.net/
diff --git a/content/concepts/contacts.md b/content/concepts/contacts.md
index 3a0cd61eb361f007ecec0964f4fa89e6abfb861c..4da3aafcffc7ff0470674d31cab0f7fd921d0811 100644
--- a/content/concepts/contacts.md
+++ b/content/concepts/contacts.md
@@ -606,7 +606,7 @@ from.
[SyncML]: http://en.wikipedia.org/wiki/SyncML
-[Folks]: http://telepathy.freedesktop.org/wiki/Folks
+[Folks]: https://wiki.gnome.org/action/show/Projects/Folks
[folks-need-merge]: https://bugzilla.gnome.org/show_bug.cgi?id=646808
@@ -626,4 +626,4 @@ from.
[BlueZ]: http://www.bluez.org/
-[Zeitgeist]: http://zeitgeist-project.com/
+[Zeitgeist]: https://zeitgeist.freedesktop.org/
diff --git a/content/concepts/egress_filtering.md b/content/concepts/egress_filtering.md
index 52419f0587d8abdd7e0982c73b3fcc90093c7bb0..83bdce797751bdff82a16524334ceb6fdbb80fda 100644
--- a/content/concepts/egress_filtering.md
+++ b/content/concepts/egress_filtering.md
@@ -468,7 +468,7 @@ One mechanism that might be proposed is to require that the platform is
able to perform [deep packet
inspection](https://en.wikipedia.org/wiki/Deep_packet_inspection) on all
network traffic; this is essentially a [web application
-firewall](https://www.owasp.org/index.php/Web_Application_Firewall),
+firewall](https://owasp.org/www-community/Web_Application_Firewall),
which is a specialized form of [application-level
gateway](https://en.wikipedia.org/wiki/Application-level_gateway).
However, we do not believe this to be particularly useful here.
@@ -539,11 +539,11 @@ techniques, neither of which appears to be desirable.
- A man-in-the-middle is one of the attacks that HTTPS is designed
to prevent, which means that recent/future HTTPS techniques such
as [certificate
- pinning](https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning)
+ pinning](https://owasp.org/www-community/controls/Certificate_and_Public_Key_Pinning)
will tend to include measures that should defeat it.
- Terminating the TLS connection at the proxy can also lead to
[new
- vulnerabilities](https://www.owasp.org/index.php/Certificate_and_Public_Key_Pinning#When_Do_You_Whitelist.3F)
+ vulnerabilities](https://owasp.org/www-community/controls/Certificate_and_Public_Key_Pinning#When_Do_You_Whitelist.3F)
for the application.
- The same single-point-of-failure reasoning as above applies.
- All the problems with deep packet inspection, noted above, still
@@ -679,7 +679,7 @@ However, it is not clear from the public documentation whether iOS apps
are able to bypass ATS by using lower-level system calls such as
`socket()`; if they are, then a compromised application could still send
unencrypted HTTP requests. [Xamarin
-documentation](https://developer.xamarin.com/guides/ios/platform_features/introduction_to_ios9/ats/)
+documentation](https://docs.microsoft.com/en-gb/xamarin/ios/platform/introduction-to-ios9/#app-transport-security)
describes the C\# APIs `HttpWebRequest` and `WebServices` as unaffected
by ATS, which suggests that lower-level system calls do indeed bypass
ATS. This matches the ATS-like mechanism that we recommend above.
@@ -818,7 +818,7 @@ However, it is not clear from the public documentation whether iOS apps
are able to bypass ATS by using lower-level system calls such as
`socket()`; if they are, then a compromised application could still send
unencrypted HTTP requests. [Xamarin
-documentation](https://developer.xamarin.com/guides/ios/platform_features/introduction_to_ios9/ats/)
+documentation](https://docs.microsoft.com/en-gb/xamarin/ios/platform/introduction-to-ios9/#app-transport-security)
describes the C\# APIs `HttpWebRequest` and `WebServices` as unaffected
by ATS, which suggests that lower-level system calls do indeed bypass
ATS. This matches what we recommend
diff --git a/content/concepts/geolocation-and-navigation.md b/content/concepts/geolocation-and-navigation.md
index 9153e6b52e2a7fb067bb8e8a08637fc0d4bf5870..58721bfbbe19fa8487d34eed3b8d59d729475b2a 100644
--- a/content/concepts/geolocation-and-navigation.md
+++ b/content/concepts/geolocation-and-navigation.md
@@ -1532,7 +1532,7 @@ interface org.apertis.NavigationGuidance1.Progress {
Additional properties may be added in future.
> Syntax is a pseudo-IDL and types are as defined in the D-Bus
-> specification, <http://dbus.freedesktop.org/doc/dbus-specification.html\type-system>
+> specification, <http://dbus.freedesktop.org/doc/dbus-specification.html#type-system>
### Navigation route guidance turn-by-turn API
@@ -1570,7 +1570,7 @@ interface org.apertis.NavigationGuidance1.TurnByTurn {
```
> Syntax is a pseudo-IDL and types are as defined in the D-Bus
-> specification, <http://dbus.freedesktop.org/doc/dbus-specification.html\type-system>
+> specification, <http://dbus.freedesktop.org/doc/dbus-specification.html#type-system>
The design of the turn-by-turn API is based heavily on the
freedesktop.org [Notifications specification],
@@ -2591,7 +2591,7 @@ string, followed by it split up into its un-encoded components.
[YOURS]: http://wiki.openstreetmap.org/wiki/YOURS
-[IVI Navigation project]: http://projects.genivi.org/ivi-navigation/documentation
+[IVI Navigation project]: https://at.projects.genivi.org/wiki/display/NAV/IVI+Navigation+Home
[Google Maps geocoding API]: https://developers.google.com/maps/documentation/geocoding/intro
@@ -2599,7 +2599,7 @@ string, followed by it split up into its un-encoded components.
[Google Maps Roads API]: https://developers.google.com/maps/documentation/roads/intro
-[Google Maps Geolocation API]: https://developers.google.com/maps/documentation/geolocation/intr
+[Google Maps Geolocation API]: https://developers.google.com/maps/documentation/geolocation/intro
[geoclue-accuracy-bounds]: http://www.freedesktop.org/software/geoclue/docs/gdbus-org.freedesktop.GeoClue2.Location.html#gdbus-property-org-freedesktop-GeoClue2-Location.Accuracy
@@ -2619,7 +2619,7 @@ string, followed by it split up into its un-encoded components.
[Nominatim server]: http://wiki.openstreetmap.org/wiki/Nominatim
-[geocode_forward_new_for_params]: https://developer.gnome.org/geocode-glib/stable/GeocodeForward.htmlgeocode-forward-new-for-params
+[geocode_forward_new_for_params]: https://developer.gnome.org/geocode-glib/stable/GeocodeForward.html#geocode-forward-new-for-params
[Photon]: http://photon.komoot.de/
diff --git a/content/concepts/global-search.md b/content/concepts/global-search.md
index 932fb1cbfae03b4771081487f6cd04c7522f8f17..971ebe2864de1a184eb5c284bfe75f4e56020ac9 100644
--- a/content/concepts/global-search.md
+++ b/content/concepts/global-search.md
@@ -920,9 +920,9 @@ document, new software components will need to be created:
- Preference management for the search system.
-[Zeitgeist]: http://zeitgeist-project.com/
+[Zeitgeist]: https://zeitgeist.freedesktop.org/
-[Evolution-data-server]: http://www.go-evolution.org/EDS_Architecture
+[Evolution-data-server]: https://wiki.gnome.org/Apps/Evolution/EDS_Architecture
[Folks]: https://live.gnome.org/Folks
@@ -932,4 +932,4 @@ document, new software components will need to be created:
[Lucene++]: https://github.com/luceneplusplus/LucenePlusPlus
-[Unity lenses]: http://developer.ubuntu.com/resources/technologies/lenses-and-scopes/
+[Unity lenses]: https://wiki.ubuntu.com/Unity/Lenses/Guidelines
diff --git a/content/concepts/gnupg-replacement.md b/content/concepts/gnupg-replacement.md
index a959c42152eca70168a5c751eb7caf69e9b4c82d..81ef6d19d45c367c42922bbd60f0d6a6df9ec221 100755
--- a/content/concepts/gnupg-replacement.md
+++ b/content/concepts/gnupg-replacement.md
@@ -252,9 +252,9 @@ Started in 2017.
It currently able to verify RSA, SHA1, SHA256 and SHA512 signatures.
-Version | # commits | # contributors | CI | gpgv replacement | C API
-:-----: | --------: | -------------: | :-: | :--------------: | -----
-[0.3.0](https://crates.io/crates/gpgrv/0.3.0) | 109 | 2 | no | yes | NA
+Version | # commits | # contributors | CI | gpgv replacement | C API
+:-----: | --------: | -------------: | :-: | :--------------: | -----
+[0.3.0](https://crates.io/crates/gpgrv) | 109 | 2 | no | yes | NA
Used by:
- APT
diff --git a/content/concepts/inter-domain-communication.md b/content/concepts/inter-domain-communication.md
index ed4b576fa76acfd3f0ee3436dae0e52a2a7f5f02..be8083660d621548c3a1b5704ac67b4ccf9106d7 100644
--- a/content/concepts/inter-domain-communication.md
+++ b/content/concepts/inter-domain-communication.md
@@ -3749,7 +3749,7 @@ to transfer frames are recommended on single board setups (virtualised or contai
[gnutls-cert]: http://www.gnutls.org/manual/html_node/Certification.html
-[openssl-cert]: https://www.openssl.org/docs/fipsvalidation.html
+[openssl-cert]: https://www.openssl.org/docs/fips.html
[rhel-cert]: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Security_Guide/sect-Security_Guide-Federal_Standards_And_Regulations-Federal_Information_Processing_Standard.html
@@ -3757,7 +3757,7 @@ to transfer frames are recommended on single board setups (virtualised or contai
[AES-GCM]: https://en.wikipedia.org/wiki/Advanced_Encryption_Standard
-[cryptopp-eval]: https://groups.google.com/forum/msg/cryptopp-users/5x-vu0KwFRk/CO8UIzwgiKYJ
+[cryptopp-eval]: https://en.wikipedia.org/wiki/AES_instruction_set#Performance
[EXT_image_dma_buf_import]: https://www.khronos.org/registry/egl/extensions/EXT/EGL_EXT_image_dma_buf_import.txt
diff --git a/content/concepts/internationalization.md b/content/concepts/internationalization.md
index 43f7287fec9129f381d24efb8d0d9ee494801789..ec0ef1fed132fd2b5e13b24319712c71851b9778 100644
--- a/content/concepts/internationalization.md
+++ b/content/concepts/internationalization.md
@@ -10,6 +10,9 @@ aliases = [
]
outputs = [ "html", "pdf-in",]
date = "2016-05-28"
+
+status = "Requires Update"
+statusDescription = "Services and availability of Transifex under certain terms may have changed and needs re-evaluating."
+++
This design explains how the Apertis platform will be made localizable
@@ -345,7 +348,7 @@ fair amount of experience.
Transifex is newer and was created to accommodate better than Pootle to
the actual workflows of most projects today. Its UI is richer in
features that facilitate translation and, more importantly, has good
-commercial support (by [Indifex]). It provides as well an API that
+commercial support (by Indifex). It provides as well an API that
can be used to integrate it with other systems. See [Transifex]( {{< ref "#transifex" >}} ) for more
details.
@@ -381,7 +384,8 @@ and [translation][transifex-translation].
##### Deployment options
Transifex is available as a hosted web service in
-[*http://www.transifex.net*](http://www.transifex.net/) and there are
+[*http://www.transifex.com*](http://www.transifex.com/) and there are
+
several [pricing options][transifex-plans] depending on the project size, features
and level of technical support desired.
@@ -389,9 +393,9 @@ The FOSS part of Transifex is available as Transifex Community Edition
and can be freely downloaded and installed in any machine with a
minimally modern and complete Python installation. This version lacks
some of the features that are available in
-[*http://transifex.net*](http://transifex.net/) and in the Enterprise
+[*http://transifex.com*](http://transifex.com/) and in the Enterprise
Edition. The installation manual for the community edition is in
-[*http://help.transifex.net/server/install.html*](http://help.transifex.net/server/install.html).
+`http://help.transifex.net/server/install.html`.
The hosted and the enterprise editions support these features in
addition of what the community edition supports:
@@ -414,7 +418,7 @@ English or other natural language.
Finally, Indifex provides commercial support for the enterprise edition
of Transifex, which can either be self-hosted or provided as SaaS. Their
portfolio includes assistance with deployment, consultancy services on
-workflow and customization, and a broad package of [technical support][transifex-support].
+workflow and customization, and a broad package of technical support.
##### Maintenance
@@ -728,7 +732,7 @@ This graph illustrates their work-flow:
-[open-translation-tools]: http://en.flossmanuals.net/open-translation-tools/
+[open-translation-tools]: http://archive.flossmanuals.net/open-translation-tools/
[IBUS]: http://en.wikipedia.org/wiki/Intelligent_Input_Bus
@@ -738,7 +742,7 @@ This graph illustrates their work-flow:
[GtkIMContext]: http://developer.gnome.org/gtk/unstable/GtkIMContext.html#GtkIMContext.description
-[StEntry]: http://developer.gnome.org/st/3.3/StEntry.html
+[StEntry]: https://developer.gnome.org/st/stable/StEntry.html
[st-im-text]: http://git.gnome.org/browse/gnome-shell/tree/src/st/st-im-text.c
@@ -754,33 +758,29 @@ This graph illustrates their work-flow:
[msgmerge]: http://www.gnu.org/savannah-checkouts/gnu/gettext/manual/html_node/msgmerge-Invocation.html
-[Pootle]: http://translate.sourceforge.net/wiki/pootle/index
+[Pootle]: http://pootle.translatehouse.org/?id=pootle/index
-[Transifex]: https://www.transifex.net/
+[Transifex]: https://www.transifex.com/
[Rosetta]: https://translations.launchpad.net/
-[Indifex]: http://www.indifex.com/
-
-[csv2po]: http://translate.sourceforge.net/wiki/toolkit/csv2po
-
-[transifex-management]: http://help.transifex.net/intro/projects.html
+[csv2po]: http://docs.translatehouse.org/projects/translate-toolkit/en/latest/commands/csv2po.html?id=toolkit/csv2po
-[transifex-translation]: http://help.transifex.net/intro/translating.html
+[transifex-management]: https://www.transifex.com/features/team-management/
-[transifex-plans]: https://www.transifex.net/plans/
+[transifex-plans]: https://www.transifex.com/pricing/
-[transifex-support]: https://www.transifex.net/tour/products/transifexee/
+[transifex-translation]: https://www.transifex.com/features/translation-tools/
-[transifex-translation-tm]: http://help.transifex.net/intro/translating.html#user-tm
+[transifex-translation-tm]: https://www.transifex.com/features/translation-tools/
-[transifex-memory]: http://help.transifex.net/intro/projects.html#setting-up-translation-memory
+[transifex-memory]: https://docs.transifex.com/translation-memory/sharing-tm
-[transifex-prepopulate]: http://help.transifex.net/intro/projects.html#prepopulate-translations-with-100-matches-on-tm
+[transifex-prepopulate]: https://docs.transifex.com/translation-memory/enabling-autofill/
-[transifex-glossary]: http://help.transifex.net/intro/translating.html#glossary
+[transifex-glossary]: https://docs.transifex.com/glossary/glossary
-[transifex-push]: http://help.transifex.net/features/client/index.html#push
+[transifex-push]: https://docs.transifex.com/client/push
[Fontconfig]: http://fontconfig.org/
@@ -790,7 +790,7 @@ This graph illustrates their work-flow:
[ubuntu-language-ja]: http://packages.ubuntu.com/hardy/language-support-ja
-[qt-language-switching]: http://developer.qt.nokia.com/faq/answer/how_can_i_dynamically_switch_between_languages_in_my_application_using_e.g_
+[qt-language-switching]: https://wiki.qt.io/How_to_create_a_multi_language_application
[gnome-translation-contribute]: https://live.gnome.org/TranslationProject/ContributeTranslations
diff --git a/content/concepts/media-management.md b/content/concepts/media-management.md
index f2e5d1f843f731f2de62d0ff448ae9817ad02c02..7413e3272586ac310ba5b599b447ba60f79b6dd3 100644
--- a/content/concepts/media-management.md
+++ b/content/concepts/media-management.md
@@ -1879,7 +1879,7 @@ tutorial "*Monitor filesystem activity with [inotify]*".
[WAL]: http://www.sqlite.org/draft/wal.html
-[Tracker-formats]: https://live.gnome.org/Tracker/SupportedFormats
+[Tracker-formats]: https://wiki.gnome.org/Projects/Tracker/SupportedFormats
[Tracker Extract-docs]: http://developer.gnome.org/libtracker-extract/0.12/libtracker-extract-How-to-use-libtracker-extract.html
@@ -1899,7 +1899,7 @@ tutorial "*Monitor filesystem activity with [inotify]*".
[REST]: http://en.wikipedia.org/wiki/Representational_state_transfer
-[librest]: https://live.gnome.org/Librest
+[librest]: https://wiki.gnome.org/Projects/Librest
[libsoup]: http://developer.gnome.org/libsoup/
diff --git a/content/concepts/multimedia.md b/content/concepts/multimedia.md
index 6a6a15e24b0d9a66eb9f31bd459f82d380a2490b..713515409ffec0d156ba7ae8aa7fa37bfbaf9e6a 100644
--- a/content/concepts/multimedia.md
+++ b/content/concepts/multimedia.md
@@ -12,7 +12,7 @@ outputs = [ "html", "pdf-in",]
date = "2016-05-28"
status = "Requires Update"
-statusDescription = "Requires update to reflect changes incorporated into Apertis and wider range of hardware now supported."
+statusDescription = "Requires update to reflect changes incorporated into Apertis and wider range of hardware now supported. "
+++
This document covers the various requirements for multimedia handling in
@@ -471,21 +471,21 @@ communicates with the Traffic control daemon in the manner described.
Furthermore some a testcase will be provided to emulate changing network
conditions.
-[CSS]: http://www.dvdcca.org/css.aspx
+[CSS]: http://www.dvdcca.org/css
[GStreamer]: http://gstreamer.freedesktop.org/
-[ed-pres]: http://video.linux.com/videos/gstreamer-10-no-longer-compromise-flexibility-for-performance
+[ed-pres]: https://events.static.linuxfound.org/images/stories/pdf/lf_elc12_hervey.pdf
[wim-pres]: http://gstconf.ubicast.tv/videos/keynote-gstreamer10/
-[GstBaseVideoDecoder]: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-bad-libs/html/gst-plugins-bad-libs-GstBaseVideoDecoder.html
+[GstBaseVideoDecoder]: https://www.freedesktop.org/software/gstreamer-sdk/data/docs/latest/gst-plugins-bad-libs-0.10/gst-plugins-bad-libs-GstBaseVideoDecoder.html
-[GstBaseVideoEncoder]: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-bad-libs/html/gst-plugins-bad-libs-GstBaseVideoEncoder.html
+[GstBaseVideoEncoder]: https://www.freedesktop.org/software/gstreamer-sdk/data/docs/latest/gst-plugins-bad-libs-0.10/gst-plugins-bad-libs-GstBaseVideoEncoder.html
[ClutterGstPlayer]: http://developer.gnome.org/clutter-gst/stable/ClutterGstPlayer.html
-[playbin2]: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/gst-plugins-base-plugins-playbin2.html
+[playbin2]: https://www.freedesktop.org/software/gstreamer-sdk/data/docs/2012.5/gst-plugins-base-plugins-0.10/gst-plugins-base-plugins-playbin2.html
[queue2]: http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-plugins/html/gstreamer-plugins-queue2.html
@@ -493,8 +493,8 @@ conditions.
[Plymouth]: http://www.freedesktop.org/wiki/Software/Plymouth
-[brey-blog]: http://brej.org/blog/?cat
+[brey-blog]: http://brej.org/blog/?p=158
[gentrans]: http://gentrans.sourceforge.net/docs/head/manual/html/howto.html#sect-introduction
-[Fluendo DVD Player]: http://www.fluendo.com/shop/product/fluendo-dvd-player/
+[Fluendo DVD Player]: https://fluendo.com/en/products/multimedia/oneplay-dvd-player/
diff --git a/content/concepts/preferences-and-persistence.md b/content/concepts/preferences-and-persistence.md
index 84428620df01576c4ff8a7771f6da7dbaa222dd5..d7b637e22f688c28ac765ab28ca1967cd073f20c 100644
--- a/content/concepts/preferences-and-persistence.md
+++ b/content/concepts/preferences-and-persistence.md
@@ -442,7 +442,7 @@ On a GNOME or KDE desktop, all user secrets, passwords and credentials
are stored using the [Secret Service] API. In GNOME, this API is
implemented by GNOME Keyring; in KDE, by KWallet.
-The [API][Secret Service API] allows storage of byte array ‘secrets’ (such as
+The API allows storage of byte array ‘secrets’ (such as
passwords), along with non-secret attributes used to look them up, in an
encrypted storage file which must be unlocked by the user before it can
be accessed by applications. Unlocking it may be automatic if the user
@@ -858,8 +858,8 @@ In its current state (May 2015, detailed in [GNOME Linux desktop]( {{< ref "#gn
support the necessary fine-grained access controls for multiple
components accessing the preferences. However, a design is being
implemented upstream to proxy access to dconf through a separate service
-which imposes access controls based on AppArmor ([mostly implemented as
-of January 2016][appservice]).
+which imposes access controls based on AppArmor (mostly implemented as
+of January 2016).
On the assumption that this work can be completed and integrated into
Apertis on an appropriate timescale (see [Summary of recommendations]( {{< ref "#summary-of-recommendations" >}} )),
@@ -1801,9 +1801,7 @@ As discussed in the above sections, we recommend:
[XDG-base-dir-spec]: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
-[Secret Service]: http://standards.freedesktop.org/secret-service/
-
-[Secret Service API]: http://standards.freedesktop.org/secret-service/pt02.html
+[Secret Service]: https://specifications.freedesktop.org/secret-service/latest/index.html
[Android-shared-pref]: http://developer.android.com/guide/topics/data/data-storage.html#pref
@@ -1847,8 +1845,6 @@ As discussed in the above sections, we recommend:
[D-Bus-secret-service]: http://standards.freedesktop.org/secret-service/
-[appservice]: https://git.collabora.com/cgit/user/xclaesse/appservice.git
-
[GSettings-schema]: https://git.gnome.org/browse/glib/tree/gio/gschema.dtd
[GVariant type]: https://developer.gnome.org/glib/stable/glib-GVariantType.html#id-1.6.18.6.9
diff --git a/content/concepts/robustness.md b/content/concepts/robustness.md
index 44f79d3b691542e022e548d09934980ff77965e2..6e54e19999de0e67d54d226ac0e3a33391bb93ea 100644
--- a/content/concepts/robustness.md
+++ b/content/concepts/robustness.md
@@ -333,9 +333,8 @@ well as reliability of the MMC card.
The storage erase block size [can be read][get-flash-erase-size] from /proc/mtd or from
U-Boot but the flash storage can report something different than
-the real numbers. Some sizes are available on the [Linaro wiki][linaro-sizes].
-Linaro-image-tools is [now able][linaro-alignment] to generate images with a correct
-alignment.
+the real numbers. Linaro-image-tools is now able to generate images with a
+correct alignment.
#### Testing
@@ -777,17 +776,13 @@ the filesystem is
[dconf]: https://live.gnome.org/dconf
-[GKeyFile]: https://developer.gnome.org/glib/2.37/glib-Key-value-file-parser.html
+[GKeyFile]: https://developer.gnome.org/glib/stable/glib-Key-value-file-parser.html
[kernel-ext4]: http://kernel.org/doc/Documentation/filesystems/ext4.txt
[btrfs-mount-options]: https://btrfs.wiki.kernel.org/index.php/Mount_options
-[get-flash-erase-size]: http://processors.wiki.ti.com/index.php/Get_the_Flash_Erase_Block_Size
-
-[linaro-sizes]: https://wiki.linaro.org/WorkingGroups/KernelArchived/Projects/FlashCardSurvey
-
-[linaro-alignment]: https://bugs.launchpad.net/linaro-image-tools/bug/626907
+[get-flash-erase-size]: https://bootlin.com/blog/managing-flash-storage-with-linux/
[GNOME-housekeeping]: http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/housekeeping/gsd-disk-space.c#n693
@@ -801,7 +796,7 @@ the filesystem is
[sched_setscheduler (2)]: http://www.kernel.org/doc/man-pages/online/pages/man2/sched_setscheduler.2.html
-[cpuacct]: http://www.kernel.org/doc/Documentation/cgroups/cpuacct.txt
+[cpuacct]: https://www.kernel.org/doc/Documentation/cgroup-v1/cpuacct.txt
[ioprio_set]: http://www.kernel.org/doc/man-pages/online/pages/man2/ioprio_set.2.html
@@ -825,4 +820,4 @@ the filesystem is
[Btrfs]: https://btrfs.wiki.kernel.org/
-[Force Unit Access]: http://en.wikipedia.org/wiki/SCSI_Write_Commands#Write_.2810.29
+[Force Unit Access]: https://en.wikipedia.org/wiki/Disk_buffer#Force_Unit_Access_(FUA)
diff --git a/content/concepts/security.md b/content/concepts/security.md
index a3399a340c77bdc63ab8bda2b156ebd586fd486d..548da1aa72e6e8d83ad3a48dfff94058cb3f7270 100644
--- a/content/concepts/security.md
+++ b/content/concepts/security.md
@@ -398,7 +398,7 @@ topic).
> See, for instance, how the A2DP service verifies the caller has the
> required permission:
-> <https://github.com/android/platform_frameworks_base/blob/master/core/java/android/server/BluetoothA2dpService.java#L257>
+> <https://android.googlesource.com/platform/frameworks/base/+/22f7dfd23490a3de2f21ff96949ba47003aac8f8/core/java/android/server/BluetoothA2dpService.java#251>
No effort is made specifically towards thwarting applications
misbehaving and causing a Denial of Service on system services or the
@@ -427,8 +427,8 @@ also kills applications when under memory pressure.
It also uses a simple *API privilege level* framework as the base of its
security and reliability architecture. Applications running with the
-*Normal* API privilege level need to specify which *[API privilege
-groups][bada-privileged-api]* it needs to be able to access in their manifest file.
+*Normal* API privilege level need to specify which *API privilege
+groups* it needs to be able to access in their manifest file.
Some APIs are restricted under the *System* API level and can be used
only by Samsung or its authorized partners. It's not possible to say
@@ -821,7 +821,7 @@ average duration.
SMACK's performance characteristics should be similar to that of
SELinux, given their similar approach to the problem. SMACK has been
-tested for a [TV embedded scenario][smack-embedded-tv] which has shown performance
+tested for a TV embedded scenario which has shown performance
degradation from 0% all the way to 30% on a worst-case scenario of
deleting a 0-length file. Degradation varied greatly depending on the
benchmark used.
@@ -2080,9 +2080,7 @@ from iterating on an implementation.
[Android-responsiveness]: http://developer.android.com/guide/practices/design/responsiveness.html
-[bada-privileged-api]: http://developer.bada.com/help/index.jsp?topic=/com.osp.documentation.help/html/bada_overview/using_privileged_api.htm
-
-[iOS-sec]: http://images.apple.com/ipad/business/docs/iOS_Security_May12.pdf
+[iOS-sec]: https://github.com/V3RL4223N3/Programming/blob/master/iOS/iOS_Security_May12.pdf
[iOS-sandbox]: http://www.usefulsecurity.com/2007/11/apple-sandboxes-part-1/
@@ -2110,8 +2108,6 @@ from iterating on an implementation.
[SELinux-perf-impact]: http://blog.larsstrand.no/2007/11/rhel5-selinux-benchmark.html
-[smack-embedded-tv]: http://www.embeddedalley.com/pdfs/Smack_for_DigitalTV.pdf
-
[cgroup-v1]: https://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt
[cgroup-v2]: https://www.kernel.org/doc/Documentation/cgroup-v2.txt
diff --git a/content/concepts/sensors-and-actuators.md b/content/concepts/sensors-and-actuators.md
index 1d5cfc1db32899f78be458da245a4a4088ab4251..e432c4ca8bf8f0c4212a3c122e8aca4d223c4c6c 100644
--- a/content/concepts/sensors-and-actuators.md
+++ b/content/concepts/sensors-and-actuators.md
@@ -656,15 +656,10 @@ bus and various clients, including this Web API Vehicle and any native
apps. Unfortunately, the Vehicle Interface API seems to be unspecified
as of August 2015, at least in publicly released GENIVI documents.
-> <http://git.projects.genivi.org/?p=web-api-vehicle.git;a=blob_plain;f=doc/WebAPIforVehicleDataRI.pdf;hb=HEAD>
-> Section 2.2.3
-
The Web API Vehicle has the same features and scope as the W3C API, but
its implementation is clumsier, relying a lot more on seemingly
unstructured magic strings for accessing vehicle properties.
-> <http://git.projects.genivi.org/?p=web-api-vehicle.git;a=blob_plain;f=doc/WebAPIforVehicleData.pdf;hb=HEAD>
-
It was last publicly modified in May 2013, and might not be under
development any more. Furthermore, a lot of the wiki links in the
specification link to private and inaccessible data on
@@ -767,7 +762,7 @@ produced by the [Car Connectivity Consortium] rather than a device
manufacturer like Apple or Google.
The specifications for MirrorLink are proprietary and only available to
-registered developers. In [their brochure][mirrorlink-brochure] (page 2), it is stated that
+registered developers. In a brochure (now unavailable for download), it is stated that
support for allowing apps access to sensor data is planned for the
future (as of 2014).
@@ -828,8 +823,8 @@ vehicle-specific plugin.
### AllJoyn
The [AllJoyn Framework] is an internet of things (IoT) framework
-produced under the Linux Foundation banner and the [AllSeen
-Alliance]. (Note that IoT frameworks are explicitly out of scope
+produced under the Linux Foundation banner and the [Open Connectivity
+Foundation]. (Note that IoT frameworks are explicitly out of scope
for this design; this section is for background information only. See
[Bluetooth wrist watch and the Internet of Things]( {{< ref "#bluetooth-wrist-watch-and-the-internet-of-things" >}} )) It allows devices to discover and communicate with each
other. It is freely available (open source) and has components which run
@@ -2082,9 +2077,7 @@ enum Availability {
[W3C Automotive and Web Platform]: https://www.w3.org/community/autowebplatform/
-[W3C Automotive and Web Platform]: http://projects.genivi.org/web-api-vehicle/home
-
-[Web API Vehicle]: http://git.projects.genivi.org/?p=web-api-vehicle.git;a=blob_plain;f=doc/WebAPIforVehicleData.pdf;hb=HEAD
+[Web API Vehicle]: https://at.projects.genivi.org/wiki/display/PROJ/Web+API+Vehicle
[W3C Vehicle Information API Specification]: https://www.w3.org/TR/vehicle-information-api
@@ -2112,8 +2105,6 @@ enum Availability {
[Car Connectivity Consortium]: http://carconnectivity.org/
-[mirrorlink-brochure]: http://carconnectivity.org/public/files/files/MirrorLink_2pgBrochure_0.pdf
-
[Windows in the Car]: http://www.techradar.com/news/car-tech/microsoft-sets-its-sights-on-apple-carplay-with-windows-in-the-car-concept-1240245
[Android's Sensor API]: http://developer.android.com/guide/topics/sensors/index.html
@@ -2128,9 +2119,9 @@ enum Availability {
[broker-API]: https://github.com/otcshare/automotive-message-broker/blob/master/docs/amb.in.fidl
-[AllJoyn Framework]: https://allseenalliance.org/framework
+[AllJoyn Framework]: https://openconnectivity.org/technology/reference-implementation/alljoyn/
-[Allseen Alliance]: https://allseenalliance.org/
+[Open Connectivity Foundation]: https://openconnectivity.org/
[Availability interface]: http://www.w3.org/2014/automotive/vehicle_spec.html#data-availability
diff --git a/content/concepts/supported-api.md b/content/concepts/supported-api.md
index 417009f4ec3543975aa6aadeca111ff98f84e413..545185357432632dbe9373976f1bb789e6e251e6 100644
--- a/content/concepts/supported-api.md
+++ b/content/concepts/supported-api.md
@@ -466,7 +466,7 @@ As discussed in section 3.5.1, [The GTK upgrade and a Clutter API break]( {{< r
there are ways to deal with ABI/API breakage in these libraries. Keeping
both versions installed for a while is one of them. In the short term
there will be at least one set of API changes that will have a big
-impact on the Apertis project: [Clutter 2.0]. That new version of
+impact on the Apertis project: Clutter 2.0. That new version of
clutter is one of the steps in preparation for a future merge of GTK+
and Clutter.
@@ -671,5 +671,3 @@ also tools that should be used where
[Android-api-removals]: http://developer.android.com/sdk/api_diff/14/changes/alldiffs_index_removals.html
[iOS-api-changes]: https://developer.apple.com/library/ios/#releasenotes/General/iOS50APIDiff/index.html
-
-[Clutter 2.0]: http://wiki.clutter-project.org/wiki/ClutterChanges:2.0
diff --git a/content/concepts/system-updates-and-rollback.md b/content/concepts/system-updates-and-rollback.md
index 0f261802362c695a5eecc38aa4bf80babc83c2ae..f1f210243b11a3151b7287351a6f8c429f647155 100644
--- a/content/concepts/system-updates-and-rollback.md
+++ b/content/concepts/system-updates-and-rollback.md
@@ -321,7 +321,7 @@ provides a good balance between complexity and robustness.
The conceptual model behind OSTree repositories is very similar to the one used
by `git`, to the point that the [introduction in the OSTree
-manual](https://ostree.readthedocs.io/en/latest/manual/introduction/) refers
+manual](https://ostree.readthedocs.io/en/stable/manual/introduction/) refers
to it as "git for operating system binaries".
Albeit they take different tradeoffs to address different use-cases they
@@ -1201,7 +1201,7 @@ The ChromeOS auto-update system:
[OSTree]: http://ostree.readthedocs.io
-[OSTree atomic upgrades]: https://ostree.readthedocs.io/en/latest/manual/atomic-upgrades/#atomic-upgrades
+[OSTree atomic upgrades]: https://ostree.readthedocs.io/en/stable/manual/atomic-upgrades
[GPT]: http://en.wikipedia.org/wiki/GUID_Partition_Table
diff --git a/content/concepts/text-to-speech.md b/content/concepts/text-to-speech.md
index 61f49b1ae72ff9f0b3116a0fa3781fc5d2cf9796..bdf938588390c6db0fac071bfe328c7da879c90d 100644
--- a/content/concepts/text-to-speech.md
+++ b/content/concepts/text-to-speech.md
@@ -530,12 +530,10 @@ which are available already.
#### Festival
- Sounds less robotic than espeak, but still quite robotic (example
- here:
- [http://tts.speech.cs.cmu.edu:8083/](http://tts.speech.cs.cmu.edu:8083/))
+ [here](https://www.cstr.ed.ac.uk/projects/festival/onlinedemo.html))
- A bit slower
- Already packaged for Ubuntu
- - Supports 3 languages (English, Spanish and
- Welsh)
+ - Supports 3 languages (English, Spanish and Welsh)
- [http://www.cstr.ed.ac.uk/projects/festival/](http://www.cstr.ed.ac.uk/projects/festival/)
#### pico
@@ -570,7 +568,7 @@ which are available already.
- Non-FOSS
- Has been used previously in
eCore
- - [http://www.nuance.com/for-business/text-to-speech/vocalizer/index.htm#demo](http://www.nuance.com/for-business/text-to-speech/vocalizer/index.htm#demo)
+ - [Demo](https://www.nuance.com/omni-channel-customer-engagement/voice-and-ivr/text-to-speech.html#!)
## Approach
diff --git a/content/concepts/wayland_evaluation.md b/content/concepts/wayland_evaluation.md
index 10b63b8bc578bed79ca6c94df764ecca8c625c62..973037cb852983e061a70266eb78f267023d3304 100644
--- a/content/concepts/wayland_evaluation.md
+++ b/content/concepts/wayland_evaluation.md
@@ -470,7 +470,7 @@ between the processes; performance overhead and programming complexity
of IPC communications) as described in the sections above.
Both Mutter and Weston support the [xdg-shell Wayland
-protocol](http://cgit.freedesktop.org/wayland/weston/tree/protocol/xdg-shell.xml)
+protocol](https://cgit.freedesktop.org/wayland/wayland-protocols/tree/stable/xdg-shell/xdg-shell.xml)
for implementing management of client windows (such as minimisation,
fullscreening and maximisation). Wayland IVI introduces its own shell
protocol instead:
diff --git a/content/concepts/web-portal-caching.md b/content/concepts/web-portal-caching.md
index f0efaf0b57939476a1b3833fe1bdd94d1f7fce47..4beab4285997f34779cd9c97ce63a96680eca1f6 100644
--- a/content/concepts/web-portal-caching.md
+++ b/content/concepts/web-portal-caching.md
@@ -108,10 +108,10 @@ which may be the reason why the specification is still in the current status.
WebKit currently has several caches:
* a non-persistent, in-memory cache of rendered pages
which is set to 2 pages if the total RAM is bigger or equal to 512MB
-* a non-persistent, in-memory [decoded/parsed object cache](https://trac.webkit.org/browser/trunk/Source/WebKit2/Shared/CacheModel.cpp#L83),
+* a non-persistent, in-memory [decoded/parsed object cache](https://trac.webkit.org/browser/webkit/releases/WebKitGTK/webkit-2.0/Source/WebKit2/Shared/CacheModel.cpp#L83),
set to 128MB if the total RAM is bigger or equal to 2GB
and progressively lowered as the amount of total RAM decreases
-* a persistent, on-disk [resources cache](https://trac.webkit.org/browser/trunk/Source/WebKit2/Shared/CacheModel.cpp#L158)
+* a persistent, on-disk [resources cache](https://trac.webkit.org/browser/webkit/releases/WebKitGTK/webkit-2.0/Source/WebKit2/Shared/CacheModel.cpp#L158)
of 500MB if there are more than 16GB free on the disk,
progressively scaling down to 50MB if less than 1GB is available.
@@ -224,6 +224,6 @@ when the connection to the Internet is available.
[Indexed Database API]: https://www.w3.org/TR/IndexedDB/
[RFC7234]: https://tools.ietf.org/html/rfc7234
[Offline Web applications]: https://html.spec.whatwg.org/multipage/browsers.html#offline
-[Decoded/parsed object cache]: https://trac.webkit.org/browser/trunk/Source/WebKit2/Shared/CacheModel.cpp#L83
-[Resources cache]: https://trac.webkit.org/browser/trunk/Source/WebKit2/Shared/CacheModel.cpp#L158
+[Decoded/parsed object cache]: https://trac.webkit.org/browser/webkit/releases/WebKitGTK/webkit-2.0/Source/WebKit2/Shared/CacheModel.cpp#L83
+[Resources cache]: https://trac.webkit.org/browser/webkit/releases/WebKitGTK/webkit-2.0/Source/WebKit2/Shared/CacheModel.cpp#L158
[Service Workers]: https://www.w3.org/TR/service-workers/
diff --git a/content/guides/boot_optimisation.md b/content/guides/boot_optimisation.md
index c07315b337aa5963d33b2e1d3fc86fb32a17e587..6ccb576ad4cfb9654eaa5671cb2fb1d0ff9d738a 100644
--- a/content/guides/boot_optimisation.md
+++ b/content/guides/boot_optimisation.md
@@ -44,7 +44,7 @@ There are two tools provided by systemd that are useful to profile and optimise
system's startup time,
[systemd-analyze](http://www.freedesktop.org/software/systemd/man/systemd-analyze.html)
and
-[systemd-bootchart](http://www.freedesktop.org/software/systemd/man/systemd-bootchart.html).
+[systemd-bootchart](https://manpages.debian.org/testing/systemd-bootchart/systemd-bootchart.1.en.html).
## systemd-analyze
@@ -164,7 +164,7 @@ optimise it.
There are different options that can be passed to bootchart to tune its
execution. These can also be set on `/etc/systemd/bootchart.conf`. Refer
to the
-[systemd-bootchart manpage](http://www.freedesktop.org/software/systemd/man/systemd-bootchart.html)
+[systemd-bootchart manpage](https://manpages.debian.org/testing/systemd-bootchart/systemd-bootchart.1.en.html)
for information about the different options.
`systemd-bootchart` is provided in the `development` Apertis repository.
diff --git a/content/guides/buildingpatchingandmaintainingtheapertiskernel.md b/content/guides/buildingpatchingandmaintainingtheapertiskernel.md
index d51d8acee1e49461348cb13f680882e61d77839f..9518fe200e0966c9576a85149fadc94eb8737e8e 100644
--- a/content/guides/buildingpatchingandmaintainingtheapertiskernel.md
+++ b/content/guides/buildingpatchingandmaintainingtheapertiskernel.md
@@ -211,10 +211,10 @@ Now that we have a binary kernel, we can boot the board. Assuming the
config is setup correctly (you'll need the relevant network and other
drivers built in to the kernel, along with NFS root support) you can
boot with a pre-built NFS root. The Apertis provides rootfs for various
-architectures, for example the x86_64 (amd64) Apertis v2019.0rc3 nfs
+architectures, for example the x86_64 (amd64) Apertis v2021.0 nfs
root can be found here:
-<https://images.apertis.org/release/v2019/v2019.0rc3/amd64/nfs/>
+<https://images.apertis.org/release/v2021/v2021.0/amd64/nfs/>
# Packaging
@@ -476,10 +476,8 @@ The built kernel packages will be available in `~/build`.
## Installing package and testing
-To test we are going to boot the [Apertis 2019
-Minimal](https://images.apertis.org/release/v2019/v2019.0rc4/amd64/minimal/apertis_v2019-minimal-amd64-uefi_v2019.0rc4.img.gz)
-image on the Minnowboard. Download the image and write to an SD Card
-using bmaptool:
+To test we are going to boot the a minimal image on the Minnowboard. Download
+the image and write to an SD Card using bmaptool:
$ wget https://images.apertis.org/release/v2019/v2019.0rc4/amd64/minimal/apertis_v2019-minimal-amd64-uefi_v2019.0rc4.img.bmap
--2019-09-26 18:14:45-- https://images.apertis.org/release/v2019/v2019.0rc4/amd64/minimal/apertis_v2019-minimal-amd64-uefi_v2019.0rc4.img.bmap
diff --git a/content/guides/connectivity-documentation.md b/content/guides/connectivity-documentation.md
index c41f4e6457d5914886686aebd32dcbd7f2bd01a5..b134cb4abe6aa184d628ba90ec26c64a67bbb1f2 100644
--- a/content/guides/connectivity-documentation.md
+++ b/content/guides/connectivity-documentation.md
@@ -444,7 +444,7 @@ as a [Individual].
The Telepathy backend also serves as a good example. As the EDS backend,
it is well-implemented and documented.
-[oFono community]: https://ofono.org/community
+[oFono community]: https://01.org/ofono
[telepathy-dbus]: http://telepathy.freedesktop.org/spec/
diff --git a/content/guides/development_process.md b/content/guides/development_process.md
index f5c8961c6c86d2910254dbf790551b3a4a1cc5c5..21391681c9b9c182068032da4a6ba11388ebfdb3 100644
--- a/content/guides/development_process.md
+++ b/content/guides/development_process.md
@@ -62,7 +62,7 @@ Clone the forked repository
[merge request on GitLab](https://docs.gitlab.com/ce/user/project/merge_requests/).
* If changes are not ready and some (strongly encouraged) early feedback is
required, the merge request should be
- [marked as Work In Progress (WIP)](https://docs.gitlab.com/ce/user/project/merge_requests/work_in_progress_merge_requests.html).
+ [marked as Work In Progress (WIP)](https://docs.gitlab.com/ce/user/project/merge_requests/drafts.html#mark-merge-requests-as-drafts).
## Review
@@ -105,7 +105,7 @@ Clone the forked repository
* If changes are needed, a force-push with the changes is required to the
submitted branch to update the commits that are part of the merge request
(always remember to
- [use `--force-with-lease`](https://developer.atlassian.com/blog/2015/04/force-with-lease/)
+ [use `--force-with-lease`](https://blog.developer.atlassian.com/force-with-lease/)
instead of `--force`).
* Questions, request to clarify and any other kind of discussion should be
handled via comments on the merge request.
diff --git a/content/guides/howtobuildyourownkernel.md b/content/guides/howtobuildyourownkernel.md
index ac326c4609b70e05f456bda57691f5fd4ae2cf76..43b7a8648cd152ce33b148ee8377432ce778d5a3 100644
--- a/content/guides/howtobuildyourownkernel.md
+++ b/content/guides/howtobuildyourownkernel.md
@@ -366,10 +366,8 @@ The built kernel packages will be available in `~/build`.
# Installing and testing
-To test we are going to boot the [Apertis 18.03
-Minimal](https://images.apertis.org/release/18.03/18.03.0/amd64/minimal/apertis_18.03-minimal-amd64-uefi_18.03.0.img.gz)
-image on the Minnowboard. Download the image and write to an SD Card
-using bmaptool:
+To test we are going to boot an Apertis APT-based minimal image on the
+Minnowboard. Download the image and write to an SD Card using bmaptool:
$ wget https://images.apertis.org/release/18.03/18.03.0/amd64/minimal/apertis_18.03-minimal-amd64-uefi_18.03.0.img.gz
--2018-06-20 09:01:20-- https://images.apertis.org/release/18.03/18.03.0/amd64/minimal/apertis_18.03-minimal-amd64-uefi_18.03.0.img.gz
diff --git a/content/guides/howtodevelopondevices.md b/content/guides/howtodevelopondevices.md
index 3200679afe17e9509aaed574ab134dd81cee8ad9..e72b457cffb79446b8374fe3f9facdd6ee55b151 100644
--- a/content/guides/howtodevelopondevices.md
+++ b/content/guides/howtodevelopondevices.md
@@ -14,13 +14,10 @@ reference Apertis images.
# Which image to choose
-The APT-based images like
-[`apertis_18.09-minimal-amd64-uefi_18.09.0.img.gz`](https://images.apertis.org/release/18.09/18.09.0/amd64/minimal/apertis_18.09-minimal-amd64-uefi_18.09.0.img.gz)
-and
-[`apertis_18.09-target-amd64-uefi_18.09.0.img.gz`](https://images.apertis.org/release/18.09/18.09.0/amd64/target/apertis_18.09-target-amd64-uefi_18.09.0.img.gz)
-are the ones providing all the flexibility needed for development,
-letting developers install and remove packages, and otherwise customize
-the rootfs.
+The APT-based [minimal]({{< ref "images.md#minimal" >}}) and [target]({{< ref
+"images.md#target" >}}) images are the ones providing all the
+flexibility needed for development, letting developers install and remove
+packages, and otherwise customize the rootfs.
The OSTree-based images are tailored as a reference for product
deployments: their constraints make installing and removing packages
diff --git a/content/guides/sdk-network-development.md b/content/guides/sdk-network-development.md
index c399150a80d7bc51c3882cd201300fc6a337ce25..565dffb118dca52a54db251da4e9bc4ff24f29b6 100644
--- a/content/guides/sdk-network-development.md
+++ b/content/guides/sdk-network-development.md
@@ -74,7 +74,7 @@ To minimise any influence from the VM host and isolate the network connection be
virtual network interface to the VM, the other the USB network adapter. At
the beginning of each line we get a few characters showing the status of the
device, here `*AO` and `*AR` as detailed in the
- [connman documentation](https://01.org/connman/documentation):
+ [connman documentation](https://web.archive.org/web/20200218110018/https://01.org/connman/documentation):
> The symbols in the output above are: '*' favorite (saved) network, 'A'
> autoconnectable, 'O' online and 'R' ready. If no letter is shown in the O/R
diff --git a/content/guides/version_control.md b/content/guides/version_control.md
index aba9e16bb8516c23e887e0c6a5a1099785b3a327..6e93c4db67c70370a292fa46e9fe18748afb4184 100644
--- a/content/guides/version_control.md
+++ b/content/guides/version_control.md
@@ -13,7 +13,7 @@ aliases = [
Git is used for version control for all Apertis projects. This page assumes
good working knowledge of git; some introductory material is available
[here](https://www.atlassian.com/git/tutorials/), and a
-[git cheatsheet is here](https://training.github.com/kit/downloads/github-git-cheat-sheet.pdf).
+[git cheatsheet is here](https://education.github.com/git-cheat-sheet-education.pdf).
# Summary
@@ -98,7 +98,7 @@ The following principles give the reasoning for all the advice above:
- Each commit should take the repository from one working state to another,
otherwise
- [bisection](http://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git#Binary-Search)
+ [bisection](https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git#Binary-Search)
is impossible.
- Each commit should be individually revertable. If it later turns out that the
commit was a bad idea, `git revert [commit ID]` should take the repository
@@ -238,10 +238,10 @@ Merges should be carried out via the gitlab UI as a merge request to enable easy
# External links
-- [Pro Git](http://git-scm.com/book/en/v2), a comprehensive guide
+- [Pro Git](https://git-scm.com/book/en/v2), a comprehensive guide
- [Git best practices](https://sethrobertson.github.io/GitBestPractices/)
- [Git FAQ](https://help.github.com/categories/using-git/)
- [Atlassian git tutorial](https://www.atlassian.com/git/tutorials/)
-- [Official git tutorial](http://git-scm.com/docs/gittutorial)
+- [Official git tutorial](https://git-scm.com/docs/gittutorial)
- [Interactive git tutorial](https://try.github.io/)
- [git-tower tutorial](http://www.git-tower.com/learn/)
diff --git a/content/guides/webkit2_customizablewidget.md b/content/guides/webkit2_customizablewidget.md
index 091412feb99d91ea2400faebf6be402b361fa2d6..797f3992fe845095fbfdc1c0333483eae1e70016 100644
--- a/content/guides/webkit2_customizablewidget.md
+++ b/content/guides/webkit2_customizablewidget.md
@@ -22,7 +22,7 @@ Here are some information and tips which help you write rules in gtk.css. When
defining style rules, you can use a class name for some widgets as its
selector. For instance, it is possible to use '.button' instead of 'GtkButton'.
Please refer to
-[gtk-contained.css](https://github.com/GNOME/gtk/blob/master/gtk/theme/Adwaita/gtk-contained.css).
+[gtk-contained.css](https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/gtk/theme/Adwaita/gtk-contained.css).
You can learn how Adwaita theme is defined and which class name is available.
## Button
diff --git a/content/guides/xml_parsing.md b/content/guides/xml_parsing.md
index 621168800aaa0d073379e1bd89542c69250a5e41..34de867c5063dbe28b69069490b1da65ed1b026e 100644
--- a/content/guides/xml_parsing.md
+++ b/content/guides/xml_parsing.md
@@ -77,6 +77,6 @@ validate the relevant XML files.
## External links
- [XML website](http://www.xml.com/)
- - [XML Schema tutorial](http://www.w3schools.com/schema/)
+ - [XML Schema tutorial](https://www.w3schools.com/xml/schema_intro.asp)
- [libxml2 website](http://xmlsoft.org/)
- [libxml2 documentation](http://xmlsoft.org/html/libxml-lib.html)
diff --git a/content/policies/hardware_enablement.md b/content/policies/hardware_enablement.md
index 86c6b0938e73dcd33eb7d56aad9bafcc007ecbdd..bb009568baceb935ca63d7e45f5eabbfba5a73d3 100644
--- a/content/policies/hardware_enablement.md
+++ b/content/policies/hardware_enablement.md
@@ -101,7 +101,7 @@ should be exposed via the standard Video for Linux 2 APIs (V4L2). To
ensure efficient sharing of the captured frames with other hardware
components (e.g. for displaying), the driver should support exporting
the frame via dma buffers
-[1](https://www.kernel.org/doc/html/latest/media/uapi/v4l/vidioc-expbuf.html).
+[1](https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/vidioc-expbuf.html).
#### Bluetooth
@@ -146,7 +146,7 @@ at the two extremes there are:
For the former category the standard Linux Video for Linux 2 (V4L2)
decoder interface should be exposed
-[3](https://www.kernel.org/doc/html/latest/media/uapi/v4l/dev-mem2mem.html) which is
+[3](https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/dev-mem2mem.html) which is
directly supported by GStreamer.
The latter category typically needs more support on the user space side,
diff --git a/content/qa/_index.md b/content/qa/_index.md
index 9ae8d9d274c9e0c4371a733b4fdba22bb8ec9050..ff0ee185dae091730423b8dec4927672b627f15d 100644
--- a/content/qa/_index.md
+++ b/content/qa/_index.md
@@ -39,12 +39,6 @@ Tools used for QA tasks and infrastructure.
- [lqa](https://gitlab.collabora.com/collabora/lqa): It submits the
automated tests jobs to LAVA. It also offers a LAVA API that can be
used by other scripts.
- - [phab-handler](https://git.collabora.com/cgit/singularity/tools/phab-handler.git/):
- It updates the Phabricator tasks status by the B\&I infrastructure.
- - [phab-tasks](https://git.collabora.com/cgit/singularity/tools/phab-tasks.git):
- Tool that helps checking Phabricator tasks status. It is mainly used
- to check for new bugs during the weekly testing rounds and helps to
- generate the email report.
- [lwr](https://gitlab.collabora.com/collabora/lwr): The LAVA weekly
round tool is used to fetch the automated tests results and generate
the wiki report page for the weekly testing round.
diff --git a/content/reference_hardware/arm32.md b/content/reference_hardware/arm32.md
index ace2ff73de5da8a14b90c4efa06598e4d9bfd7dc..a47b1baf17aedf6ce1dc362518caf927251ba329 100644
--- a/content/reference_hardware/arm32.md
+++ b/content/reference_hardware/arm32.md
@@ -16,15 +16,14 @@ If you currently don't have access to any supported hardware, the `amd64`
images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
-| Reference | Hardware | Comments |
-| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
-| ARM reference device | i.MX6 Sabrelite | [Setup guide]( {{< ref "/reference_hardware/imx6q_sabrelite_setup.md" >}} ) |
-| Power source | [The 5V+ power source unit](http://www.digikey.com/product-search/en?WT.z_header=search_go&lang=en&site=us&keywords=993-1019-ND&x=14&y=17) that should come with the i.MX6 Sabrelite | |
-| SD card | Full-sized SD card (or microSD in full-size adapter), 16GB or larger | Speed class C10/U1 or better recommended |
-| Recommended: 100 Mbit network switch or hub | Use a network connection that *does not* support gigabit | Workaround for [reliability issues with this particular hardware when using gigabit](https://community.nxp.com/thread/381119) |
-| Recommended: LVDS panel touchscreen | [HannStar HSD100PXN1-A00-C11](https://www.mouser.com/ProductDetail/Boundary-Devices/NIT6X_101HANNSTAR/?qs=%2Fha2pyFaduhICqiA62NC348xLf7lkR37nWVKEUqzpogToe6HSSy1X%2FAMJ8uCmShD) | |
-| Recommended: LVDS panel cable | [Cable for LVDS panel](http://boundarydevices.com/products/lvds-cable-for-freescale-10-1-hannstar/) | |
-| Recommended: USB to serial adapter | [USB\<-\>serial adapter cable](http://www.amazon.com/TRENDnet-RS-232-Serial-Converter-TU-S9/dp/B0007T27H8/ref=sr_1_1?s=electronics&ie=UTF8&qid=1396528293&sr=1-1&keywords=usb+to+serial+adapter) | To look at the console |
-| Recommended: USB keyboard | USB keyboard | |
-| Optional: Attached camera | [OV5640-based 5MP MIPI attached camera module](http://boundarydevices.com/products/nit6x_5mp_mipi/) | |
-| | | |
+| Reference | Hardware | Comments |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
+| ARM reference device | i.MX6 Sabrelite | [Setup guide]( {{< ref "/reference_hardware/imx6q_sabrelite_setup.md" >}} ) |
+| Power source | The 5V+ power source unit that should come with the i.MX6 Sabrelite | |
+| SD card | Full-sized SD card (or microSD in full-size adapter), 16GB or larger | Speed class C10/U1 or better recommended |
+| Recommended: 100 Mbit network switch or hub | Use a network connection that *does not* support gigabit | Workaround for [reliability issues with this particular hardware when using gigabit](https://community.nxp.com/thread/381119) |
+| Recommended: LVDS panel touchscreen | [HannStar HSD100PXN1-A00-C11](https://eu.mouser.com/ProductDetail/Boundary-Devices/NIT6X_101HANNSTAR/?qs=%2Fha2pyFaduhICqiA62NC348xLf7lkR37nWVKEUqzpogToe6HSSy1X%2FAMJ8uCmShD) | |
+| Recommended: LVDS panel cable | Cable for LVDS panel | |
+| Recommended: USB to serial adapter | [USB\<-\>serial adapter cable](https://www.amazon.com/TRENDnet-Converter-Installation-Universal-TU-S9/dp/B0007T27H8) | To look at the console |
+| Recommended: USB keyboard | USB keyboard | |
+| Optional: Attached camera | [OV5640-based 5MP MIPI attached camera module](https://boundarydevices.com/product/ov5640_camera_imx8m/) | |
diff --git a/content/reference_hardware/arm64.md b/content/reference_hardware/arm64.md
index af908143894fe9e24e41871a973c4dbe5a94e813..52113a005431cf72111d79db0e30f415344fafd9 100644
--- a/content/reference_hardware/arm64.md
+++ b/content/reference_hardware/arm64.md
@@ -12,7 +12,7 @@ SoCs are the main target.
The recommend reference boards for these images are the R-Car Starter Kit
boards, however the Salvator-x boards are also supported. For more information
about Renesas R-Car starter kit please see the
-[Renesas product page](https://www.renesas.com/en-us/solutions/automotive/adas/solution-kits/r-car-starter-kit.html).
+[Renesas product page](https://www.renesas.com/us/en/products/automotive-products/automotive-system-chips-socs/r-car-h3-m3-starter-kit).
The following [optional extras]( {{< ref "/reference_hardware/extras.md" >}} )
may be of interest.
diff --git a/content/reference_hardware/extras.md b/content/reference_hardware/extras.md
index 9c06d142e60f235cb0ff1f5b5557b4286cb021e7..82c8327430ec1a75aab78cddf6501c6dcdf9bcfb 100644
--- a/content/reference_hardware/extras.md
+++ b/content/reference_hardware/extras.md
@@ -8,15 +8,15 @@ title = "Optional Extra Reference Hardware"
The following optional extras are those used for testing in combination with
the reference hardware platforms.
-| Reference | Hardware | Comments |
-| -------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Bluetooth dongle | [Bluetooth PTS Radio Module](http://www.gvinedesigns.com/shopping/bluetooth/product_detail.cfm?pid=141) | Only needed for Bluetooth testing and development. |
-| Reference phone \#1 | iPhone 6 | Only needed for Bluetooth testing and development. |
-| Reference phone \#2 | Android Phone | Only needed for Bluetooth testing and development. Please use any Android phone with Bluetooth v4.0 and Android OS version 9 |
-| Reference router | [D-link N300 router](http://www.dlink.com/us/en/home-solutions/connect/routers/dir-615-wireless-n-300-router) | Only needed for ConnMan testing and development. |
-| Reference 3G modem | [Huawei E3372 3G modem](http://consumer.huawei.com/en/mobile-broadband/dongles/tech-specs/e3372.htm) | Only needed for 3G connectivity testing and development. |
-| SDK Multi-touch device | [Apple Magic Trackpad](http://store.apple.com/us/product/MC380LL/A/magic-trackpad) | Only needed for multi-touch development. |
-| Reference Webcam | [Logitech HD Pro Webcam C910](http://www.logitech.com/en-in/product/6816) | Only needed for development related with camera features. |
-| Alternative Bluetooth dongle | [Asus USB-BT211 Mini Bluetooth Dongle](http://www.amazon.co.uk/gp/product/B0033CA2XM) | Only needed for development related to BlueTooth. |
-| Wireless dongle | [Asus USB-N10 - 150Mbps Wireless Lan USB Adapter](http://www.amazon.co.uk/gp/product/B002VGQQAE) | Only needed for development related to Wireless. |
+| Reference | Hardware | Comments |
+| ---------------------------- | ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| Bluetooth dongle | [Bluetooth PTS Radio Module](https://store.bluetooth.com/) | Only needed for Bluetooth testing and development. |
+| Reference phone \#1 | iPhone 6 | Only needed for Bluetooth testing and development. |
+| Reference phone \#2 | Android Phone | Only needed for Bluetooth testing and development. Please use any Android phone with Bluetooth v4.0 and Android OS version 9 |
+| Reference router | [D-link N300 router](https://eu.dlink.com/uk/en/products/dir-615-wireless-n-300-router) | Only needed for ConnMan testing and development. |
+| Reference 3G modem | [Huawei E3372 3G modem](https://consumer.huawei.com/en/routers/e3372/specs/) | Only needed for 3G connectivity testing and development. |
+| SDK Multi-touch device | [Apple Magic Trackpad](http://store.apple.com/us/product/MC380LL/A/magic-trackpad) | Only needed for multi-touch development. |
+| Reference Webcam | [Logitech HD Pro Webcam C910](http://www.logitech.com/en-in/product/6816) | Only needed for development related with camera features. |
+| Alternative Bluetooth dongle | [Asus USB-BT211 Mini Bluetooth Dongle](http://www.amazon.co.uk/gp/product/B0033CA2XM) | Only needed for development related to BlueTooth. |
+| Wireless dongle | [Asus USB-N10 - 150Mbps Wireless Lan USB Adapter](http://www.amazon.co.uk/gp/product/B002VGQQAE) | Only needed for development related to Wireless. |
diff --git a/content/release/15.03/releasenotes.md b/content/release/15.03/releasenotes.md
index 459d65edb57817f2aed3dfbdfbeaa5eea0679c97..57b6118916cf45d15d0d1bf2575dc1934ed46015 100644
--- a/content/release/15.03/releasenotes.md
+++ b/content/release/15.03/releasenotes.md
@@ -194,7 +194,7 @@ The list of available test cases, including those can be found
LAVA service packages are available in the SAC tools repository. To be
able to install it, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation)
+[instructions]()
### Mailing List
diff --git a/content/release/15.06/releasenotes.md b/content/release/15.06/releasenotes.md
index b12a9e8f2aa97600b63ed8574a8c88ff6c3c3bd1..332cdcef3d0ae1b2d2f115ad4f826e1d7c11ad6c 100644
--- a/content/release/15.06/releasenotes.md
+++ b/content/release/15.06/releasenotes.md
@@ -269,7 +269,7 @@ The list of available test cases, including those can be found
LAVA service packages are available in the Apertis tools repository. To
be able to install it, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation)
+[instructions]()
### Mailing List
diff --git a/content/release/15.09/releasenotes.md b/content/release/15.09/releasenotes.md
index 0037aabd1ac01fb6eda31f76aa9e33c2ea6ddf01..6108b9e019d6ac14a66b5fa1cb1d059d5fb68303 100644
--- a/content/release/15.09/releasenotes.md
+++ b/content/release/15.09/releasenotes.md
@@ -358,7 +358,7 @@ The list of available test cases, including those can be found
LAVA service packages are available in the Apertis tools repository. To
be able to install it, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation)
+[instructions]()
## Known issues
diff --git a/content/release/15.12/releasenotes.md b/content/release/15.12/releasenotes.md
index 1a33e9df7682865326799d3df74efe334e6f5c3a..7835e13f75de562433d5c33cef76c11f7a6e02bf 100644
--- a/content/release/15.12/releasenotes.md
+++ b/content/release/15.12/releasenotes.md
@@ -223,7 +223,7 @@ the subset of settings which its AppArmor profile allows it to read and
write. This change is transparent to applications which already use the
GSettings API. A new `GSettingsBackend` has been implemented to deal
with all the details. Current work-in-progress code is available at
-<https://git.collabora.com/cgit/user/xclaesse/appservice.git>
+`https://git.collabora.com/cgit/user/xclaesse/appservice.git`
## Text to Speech design
@@ -493,7 +493,7 @@ The list of available test cases, including those can be found
LAVA service packages are available in the Apertis tools repository. To
be able to install it, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation)
+[instructions]()
## Known issues
diff --git a/content/release/16.03/releasenotes.md b/content/release/16.03/releasenotes.md
index aa0def0b9a4e0e8f03bfafe8c31fb013583429a1..7409ee6023e024ac7ddd601c5dbd4c8485374b14 100644
--- a/content/release/16.03/releasenotes.md
+++ b/content/release/16.03/releasenotes.md
@@ -402,7 +402,7 @@ The list of available test cases, can be found
LAVA service packages are available in the Apertis tools repository. To
be able to install it, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation).
+[instructions]().
## Known issues
diff --git a/content/release/16.06/releasenotes.md b/content/release/16.06/releasenotes.md
index fbec13f4d12fb7e72502f78422f25f0eb23b3f82..4a1ca6f1406fe42963c461de8430317ddbedcc09 100644
--- a/content/release/16.06/releasenotes.md
+++ b/content/release/16.06/releasenotes.md
@@ -331,7 +331,7 @@ found [here]( {{< ref "/qa/test_cases" >}} ).
LAVA service packages are available in the Apertis tools repository. To
install, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation).
+[instructions]().
## Known issues
diff --git a/content/release/16.09/releasenotes.md b/content/release/16.09/releasenotes.md
index c04d2c5ced85f860ddaa9d84a274e3e045c6bde8..3cabbc3b4fa34dc41beb593786c0490348c52d47 100644
--- a/content/release/16.09/releasenotes.md
+++ b/content/release/16.09/releasenotes.md
@@ -219,7 +219,7 @@ found [here]( {{< ref "/qa/test_cases" >}} ).
LAVA service packages are available in the Apertis tools repository. To
install, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation).
+[instructions]().
## Known issues
diff --git a/content/release/16.12/releasenotes.md b/content/release/16.12/releasenotes.md
index 4b24b7ef0f7456d802aa3eb4ff041ec07cd49572..5e4433fb9a5b55381f8fb6b97eba9d4f9fd10758 100644
--- a/content/release/16.12/releasenotes.md
+++ b/content/release/16.12/releasenotes.md
@@ -360,7 +360,7 @@ found [here]( {{< ref "/qa/test_cases" >}} ).
LAVA service packages are available in the Apertis tools repository. To
install, please follow
-[instructions](https://lava.collabora.co.uk/static/docs/installing_on_debian.html#debian-installation).
+[instructions]().
## Known issues
diff --git a/content/release/18.03/releasenotes.md b/content/release/18.03/releasenotes.md
index be5038e65dc9a0a26849ff318e829bbce07dd271..a8705af9186cf0258e4f41906b2c50e53c243d33 100644
--- a/content/release/18.03/releasenotes.md
+++ b/content/release/18.03/releasenotes.md
@@ -167,7 +167,7 @@ and all Apertis tests jobs have been ported to use this new job format
LAVA server has been upgraded to version **2018.2** dropping support for
V1 jobs and completing the V2 migration:
-<https://lava.collabora.co.uk/static/docs/v2/>
+<https://lava.collabora.co.uk/static/docs/v2/index.html>
## Known issues