A scan of external links has shown numerous places where external links are
broken, fix them.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

A scan of "external" links are showing numerous places where links point to
supposedly Apertis provided content which is now gone. Fix these or remove
links.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

The v2019 release has reached the end of its support period. It also marks the
point at which we are now fully into the current Apertis release cadence, with
a development, stable and old stable release being supported.

Remove the pointer to the "old old stable" from the main page, the data from
the releases file and the reference to the supported version of Virtual Box.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

It is frequently important for device manufacturers to harden the devices that
they produce, in order to ensure that their devices continue to comply with
required regulations and protect against compromise by malicious third parties.

Provide documentation highlighting techniques that can be used to harden an
Apertis based device.

Update dictionary to include words and acronyms wrongly picked up as spelling
mistakes.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Current SDK images requests to manually setup the Virtual Machine in
VirtualBox, as we're only provinding the disk image (.vdi file).

Support to generate a VirtualBox Appliance image (.ova file) that works
out of the box has been recently added to `apertis-image-recipes`.

Starting Apertis release version `v2022`, SDK images will be uploaded in
OVA format. Let's document that and still keep the previous `.vdi` disk
image setup for old versions reference.

Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

Signed-off-by: Tino Lippold <Tino.Lippold@de.bosch.com>

It seems that quite a few people have added links to the packaging guide,
add in an alias to make sure we catch these when they've not been updated.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We are now beginning to use "+apertisX" rather than "coX" for Apertis changes.
Tweak the description of versioning to use this new string.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

There is a very kernel specific workflow in the component guide, move this to
the kernel specific document where it makes more sense.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

The workflows in component guide target Apertis maintainers more than
developers, it is also out-of-date in some places. Update this guide and make
it more relevant to non-maintainers in the process.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: mtt2hi <thomas.mittelstaedt@de.bosch.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

The information about the workflows and repository structure is all
jumbled up. Rename and sort the documentation into high-level
information, workflows and repository layout.

Shift more detailed documentation found in this document into more suitable
locations, rewording/adapting as required.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

There are two sections that indirectly point to the packaging guide.
Remove these as they don't really add anything.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

The packages have been moved from repository based subdirectories under
`pkg/` to `pkg/` its self. Update the URLs used on the website to reflect
this.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

The remaining documents in designs are completely obsolete. Remove these
designs to avoid confusion. The designs folder is part of the legacy
layout so remove it completely now that there's no documents. Fix any
broken links.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Martyn Welch authored 3 years ago and Martyn Welch committed 3 years ago

The connectivity document is more of a guide on how to implement support
than a concept. Add status to page as it is out of date, but move to
guides as this is the "right" place for it.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

We have added the new Terms of Use and Privacy Policy to the website and
in-line with the existing policies we state we will give 30 days notice of
change.

Note: These changes will switch to the new policies and should not be
merged until the 6th May 2021.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Emanuele Aina authored 3 years ago and Martyn Welch committed 3 years ago

The Apertis packaging toolchain and pipelines have switched from the
`coX` packaging version suffix to `apertisX` to better distinguish the
work of the Apertis team from more Collabora-specific packages.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 3 years ago and Martyn Welch committed 3 years ago

The Apertis packaging toolchain and pipelines have switched from the
`coX` packaging version suffix to `apertisX` to better distinguish the
work of the Apertis team from more Collabora-specific packages.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Emanuele Aina authored 3 years ago and Martyn Welch committed 3 years ago

The Apertis packaging toolchain and pipelines have switched from the
`coX` packaging version suffix to `apertisX` to better distinguish the
work of the Apertis team from more Collabora-specific packages.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Martyn Welch authored 3 years ago and Emanuele Aina committed 3 years ago

Removing default code highlighting requires us to explicitly mark code we
wish to be highlighted. Tweak howtobuildyourownkernel.md to act as a show
case of how to do this.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Signed-off-by: Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>

This commit enables the generation and display of the ToC on all pages
where it's relevant due to the content size.

More pages could have been included but left aside due to inconsistent
use of heading levels leading to rendering/visual glitches.

The pages' content has not been modified, except for the "Terms of use"
page which included a manually-generated ToC.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Arnaud Ferraris authored 3 years ago and Martyn Welch committed 3 years ago

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Arnaud Ferraris authored 3 years ago and Martyn Welch committed 3 years ago

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Arnaud Ferraris authored 3 years ago and Martyn Welch committed 3 years ago

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Extended "Apertis integration testing with LAVA" guide with additional
details.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>
Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

Arnaud Ferraris authored 3 years ago and Peter Senna Tschudin committed 3 years ago

The "Publishing a single application" section introduces the use of
.flatpakrepo files, which are detailed in the subsequent "Publishing a
repository" section. Moving the latter section before the former
therefore makes more sense.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

Arnaud Ferraris authored 3 years ago and Peter Senna Tschudin committed 3 years ago

As requested, this commit adds more detailed explanations and
step-by-step commands for creating and installing signed flatpak
applications.

Signed-off-by: Arnaud Ferraris <arnaud.ferraris@collabora.com>

It has been dropped in the packaging-tools repository

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

One exception case, that of maintaining a package from an independent
upstream source tarball, was documented separately.

This was causing confusion to us all as this content wasn't reflected on
the master page, i.e. Apertis Packaging Guide

This patch just moves the content to the right location

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Change 'journactl' -> 'journalctl'

Signed-off-by: Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>

Update and re-shuffle the existing parts of the apparmor.md guide
to merge the old guide with the new guide:
 - Update summary with new ref links.
 - Reused a few sections but rephrased and updated references.
 - Removed a few, no longer needed, sections.
 - Fix minor formatting

Signed-off-by: Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>

Rewrite introduction to reflect the newly updated guide on AppArmor and
profile development. Briefly mention that DAC and capabilities are not
considered in the guide but considered prerequisites.

Signed-off-by: Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>

Apply 2 suggestion(s) to 1 file(s)

Summary of content:
 - Introduction to mount rules in AppArmor
 - Short explanation of correlation between CAP_SYS_ADMIN and mount
 - 2 examples for profiles that allow mount operations.

Signed-off-by: Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>

Jasarevic Samir authored 4 years ago and Elvstam Cantner Andreas committed 3 years ago

Signed-off-by: Samir Jasarevic <samir.jasarevic@se.bosch.com>

Signed-off-by: Samir Jasarevic <samir.jasarevic@se.bosch.com>