- Apr 26, 2021
-
-
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>
-
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>
-
- Apr 23, 2021
-
-
Ritesh Raj Sarraf authored
It has been dropped in the packaging-tools repository Signed-off-by:
Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
-
Ritesh Raj Sarraf authored
Signed-off-by:
Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
-
- Apr 22, 2021
-
-
Ritesh Raj Sarraf authored
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>
-
Martyn Welch authored
Fix double "the" in the OP-TEE document. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
- Apr 19, 2021
-
-
Provide some updates to clarify issues raised by the document review. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
- Apr 16, 2021
-
-
Frederic Danis authored
Starting with Apertis v2022dev2, `Flatpak` is also able to use `Ed25519` cryptography. Signed-off-by:
Frédéric Danis <frederic.danis@collabora.com>
-
- Apr 15, 2021
-
-
Emanuele Aina authored
The document was written before all communication applications moved to closed silos, back when XMPP was commonly used. The tradeoffs in the document no longer apply and the strategy should be revised. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Apr 14, 2021
-
-
Elvstam Cantner Andreas authored
Change 'journactl' -> 'journalctl' Signed-off-by:
Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>
-
Sjoerd Simons authored
-
Sjoerd Simons authored
-
This document tries to outline at a quite high level the types of devices and scenarious Apertis tends to support to give potential users a starting point for considering apertis. For each sections tables are provides with references to more detailed documentation section to drill into further technical depth.
-
Elvstam Cantner Andreas authored
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>
-
- Apr 13, 2021
-
-
Elvstam Cantner Andreas authored
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)
-
Elvstam Cantner Andreas authored
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>
-
Signed-off-by:
Samir Jasarevic <samir.jasarevic@se.bosch.com>
-
Elvstam Cantner Andreas authored
Signed-off-by:
Samir Jasarevic <samir.jasarevic@se.bosch.com>
-
MAC-DAC-example.png figure added to the AppArmor guideline. Signed-of-by:
<samir.jasarevic@se.bosch.com> Introduction to file access in AppArmor. An example of MAC and DAC file access permissions is shown. Signed-off-by:
<samir.jasarevic@se.bosch.com> Apply 4 suggestion(s) to 1 file(s) Apply 1 suggestion(s) to 1 file(s) Apply 1 suggestion(s) to 1 file(s) Apply 2 suggestion(s) to 1 file(s) Updated file access based on the review comments. Signed-off-by:
<samir.jasarevic@se.bosch.com> Update file access with 4 spaces for code Signed-off-by:
<samir.jasarevic@se.bosch.com>
-
The current guideline on AppArmor covers basic overview and breifly mentions development steps needed. This commit extends the AppArmor guideline with more in-depth development steps and examples for how to developt AppArmor profiles. Sections included: Profile Introduction - Profile Modes - System Logs Profile Development - Manually Write The Profile - Tool Aided Profile Development Signed-off-by:
Andreas Elvstam Cantner <andreas.elvstam@se.bosch.com>
-
Signed-of-by:
<samir.jasarevic@se.bosch.com>
-
- Apr 09, 2021
-
-
Frederic Danis authored
Signed-off-by:
Frédéric Danis <frederic.danis@collabora.com>
-
Ariel D'Alessandro authored
Signed-off-by:
Ariel D'Alessandro <ariel.dalessandro@collabora.com>
-
- Apr 08, 2021
-
-
Since when using OSTree folder /home is writable and preserved across updates clarify this to avoid misunderstandings and to be consistent with the rest of the document. Signed-off-by:
Walter Lozano <walter.lozano@collabora.com>
-
In order to clarify that the principles describe in preferences and persistence also apply to Flatpak add a small reference to it. Signed-off-by:
Walter Lozano <walter.lozano@collabora.com>
-
Remove a line that was repeated by mistake in system updates and rollback. Signed-off-by:
Walter Lozano <walter.lozano@collabora.com>
-
Apertis now has open registration on it's GitLab instance. Update the documentation to reflect this. Correct some spelling mistakes and grammatical issues noticed when reading documents. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
Peter Senna Tschudin authored
Signed-off-by:
Peter Senna Tschudin <peter.senna@collabora.com>
-
Added the guide how to create Apertis tests for LAVA. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Apr 05, 2021
-
-
We are updating the privacy policy and terms of use as part of opening up GitLab. Add these to the website and provide a page covering the need for the change and providing links to the new and old documents. Add a banner to the home page highlighting this change. We will need to give 30 days notice before fully affecting the change as it's stated we will do that in the existing privacy policy. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
- Mar 29, 2021
-
-
Emanuele Aina authored
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
The release flow and product lines document has been moved from designs to policies, however we have some links to this document in places that are really not possible to change. Add an alias to forward from the old address. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
We have added a status page to the project. This should be added to the navigation bar to make it more visible. Rather than adding more entries that will make the bar cluttered, remove the link to the community page as this only points to the mailing list at the moment and highlighting that doesn't seem to be resulting in people signing up. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
The status page has now been implemented for Apertis, mark the document as such. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
Now we have an implemented a status page, add details about this to the infrastructure monitoring document. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
- Mar 28, 2021
-
-
Debian upstream version tag should start with debian/ instead of apertis/. Fix this. Signed-off-by:
Ariel D'Alessandro <ariel.dalessandro@collabora.com>
-
- Mar 25, 2021
-
-
Martyn Welch authored
Version 4.0 of the CC BY-SA license was written in a way that didn't require to be ported to different legal jurisidictions, thus it is correctly known as the "Creative Commons Attribution-ShareAlike 4.0 International License" not the "Creative Commons Attribution-ShareAlike 4.0 Unported License". Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
Martyn Welch authored
As stated on the "Applying Licensing" page: https://www.apertis.org/policies/license-applying/ Apertis code, including build scripts, helpers and recipes, is primarily licensed under the Mozilla Public License Version 2.0. Images (such as icons) and documentation in Apertis are licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license. The website is (pretty much) entirely documentation, so should be licensed as CC BY-SA 4.0, however the repository has mistakenly been given an MIT license. Correct this by adding the correct license text. Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-