Porter roll call for Debian Stretch
-----BEGIN PGP SIGNED MESSAGE-----
Like last release, we are doing a roll call for porters of all release
architectures. If you are an active porter behind one of the [release
architectures] for the entire lifetime of Debian Stretch (est. end of
2020), please respond with a signed email containing the following
before Friday, the 9th of September:
* Which architectures are you committing to be an active porter for?
* Please describe recent relevant porter contributions.
* Are you running/using Debian testing or sid on said port(s)?
* Are you testing/patching d-i for the port(s)?
* If we were to enable -fPIE/-pie by default in GCC-6, should that change
also apply to this port? 
Feel free to use the following template as your reply:
I am an active porter for the following architectures and I intend
to continue this for the lifetime of the Stretchj release (est. end
For <ARCH>, I
- test (most|all) packages on this architecture
- run a Debian testing or unstable system on port that I use regularly
- fix toolchain issues
- triage arch-specific bugs
- fix arch-related bugs
- triage d-i bugs
- test d-i regularly
- fix d-i bugs/issues
- maintain buildds
- maintain/provide hardware for (or assist with) automated tests on ci.d.n,
- run other automated tests outside the Debian QA services (Please describe
<I am a DD|I am a DM|I am not a DD/DM>
I believe the port <is|is not> ready to have -fPIE/-pie enabled by default.
Niels, on behalf of the release team
 Enabling -fPIE/-fpie by default would harden debian systems against certain
attacks. See https://lintian.debian.org/tags/hardening-no-pie.html for
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----