Commit ef2dd8ca authored by intrigeri's avatar intrigeri
Browse files

Merge remote-tracking branch 'origin/master'

parents e1a0fe35 7847bf59
......@@ -32,4 +32,3 @@ Feel free to add any relevant issue to this list.
* [[!gnome_gitlab seahorse-nautilus/issues/1 desc="seahorse-nautilus: non-ISO-C and non-deprecated-API warnings"]]
* [[!gnome_gitlab seahorse-nautilus/issues/4 desc="seahorse-nautilus: does not or only partially import keys"]]
* [[!gnome_gitlab seahorse/issues/22 desc="Seahorse: cannot Import Public SSH Keys"]]
* [[!gnome_gitlab gnome-settings-daemon/issues/210 desc="keyboard: Without settings or under GDM make sure to add the US layout"]]
......@@ -93,8 +93,6 @@ issue, which allows one to find duplicates later on if needed.
its solution as a feature)
- % Done: drop it (we don't use this field enough to provide any value)
- Estimated time → description
- Attachments: any issue/MR description or comment can have file
attachments
## Project management
......@@ -201,11 +199,6 @@ Relevant features — to be triaged as MUST/SHOULD/MAY:
like [[!tails_ticket 15878]] can be easily redirected.
* Preserve issue private/public status.
* Convert Textile to Markdown.
* Preserve watchers.
* Preserve issues relationships.
* Preserve other issues metadata.
* Does not require global GitLab administration token.
* Does not require SSH access to the GitLab machine.
## Tools
......
......@@ -11,13 +11,7 @@ enabled, without the user having to do _anything_ special about it.
Means: use the shim signed by Microsoft + GRUB2.
We don't support booting on a custom built kernel, so that should be
relatively easy. Except:
* The kernel won't allow loading an unsigned `aufs` module so we need
to migrate to `overlayfs` ([[!tails_ticket 8415]]).
* `overlayfs` does not allow stacking enough layers for our current
upgrade system, so we need to [[!tails_ticket 15281 desc="stack one
single SquashFS diff when upgrading"]].
relatively easy.
Resources
=========
......@@ -52,16 +46,5 @@ Resources
by Greg Kroah-Hartman
* Linux Foundation's
[Making UEFI Secure Boot Work With Open Platforms](http://linuxfoundation.org/publications/making-uefi-secure-boot-work-with-open-platforms)
Automated testing
=================
* The hard(est) part seems to be about how to enroll the signing keys
into the nvram file. One option is to use `EnrollDefaultKeys.efi`
from OVMF.
* [Automating Secure Boot Testing](https://www.youtube.com/watch?v=qtyRR-KbXYQ):
how Red Hat does CI for Secure Boot (FOSDEM 2018)
* <https://wiki.ubuntu.com/UEFI/SecureBoot/Testing>
* <https://en.opensuse.org/openSUSE:UEFI_Secure_boot_using_qemu-kvm>
* <https://fedoraproject.org/wiki/Using_UEFI_with_QEMU#Testing_Secureboot_in_a_VM>
* <https://github.com/puiterwijk/qemu-ovmf-secureboot>
......@@ -19,8 +19,8 @@ beginning of May.
- December 2018: spriver
- January 2019: emmapeel
- February 2019: intrigeri
- March 2019: TheNerdyAnarchist & emmapeel
- April 2019: sajolida
- March 2019: TheNerdyAnarchist
- April 2019:
- May 2019:
- June 2019:
- July 2019: u
......
......@@ -98,11 +98,13 @@ User experience
Hot topics on our help desk
===========================
XXX: Ask tails-bugs@boum.org to list hot topics for the last month.
1. there were several users reporting [[!tails_ticket 14754]]
1.
1. and there are still some people affected by [[!tails_ticket 10976]]
1.
1.
Infrastructure
==============
......
......@@ -20,7 +20,6 @@
* clone upstream git
git clone https://gitlab.gnome.org/GNOME/gnome-shell.git gnome-shell-git
git submodule update --init
* disable upstream VCS tag checking
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment