Bits from the DPL (February 2018)
-----BEGIN PGP SIGNED MESSAGE-----
Greetings from a bitterly cold & snowy London! However, a warm welcome
to the February 2018 edition of "Bits from the DPL".
Here's a brief outline of what I've been getting up to recently as your
* Re-appointed Kurt Roeckx as Project Secretary for another term.
Thank you, Kurt… 
* Had a call with the GitLab  Press team regarding the Alioth/Salsa
migration for an upcoming press release.
* Approved Debian's continued involvement with Google's Summer of Code
outreach programme. 
* Re-delegated the Debian System Administrators  delegation. This
represents the stepping down of Stephen Gran from the team ;
thank you for your careful and diligent work over the years, sgran.
* Attempted to connect various folks looking for keysigning  as
part of Debian Maintainer applications.
* Updated the DD certificate script  to support Debian Maintainers
 and "issued" a certificate to a Maintainer.
* Had some private discussions with Developers regarding the Debian
LTS project  as well as followed the recent conversation closely
on debian-devel , etc.
* Liased with SPI  to gain access to a Google component so that
DSA  could perform some administration.
* Informally delegated a Developer to begin investigatations into the
impact of the General Data Protection Regulation  on Debian.
[ 0] https://lists.debian.org/debian-devel-announce/2018/02/msg00002.html
[ 1] https://about.gitlab.com/
[ 2] https://wiki.debian.org/SummerOfCode2018
[ 3] https://wiki.debian.org/Teams/DSA
[ 4] https://lists.debian.org/debian-devel-announce/2018/02/msg00001.html
[ 5] https://wiki.debian.org/Keysigning/Coordination
[ 6] https://wiki.debian.org/DDCertificate
[ 7] https://wiki.debian.org/DebianMaintainer
[ 8] https://wiki.debian.org/LTS
[ 9] https://lists.debian.org/debian-devel
As well as responding to various follow-ups to previous requests, I:
* Had discussions around the status of a problematic Trusted
* Had a handful of conversations regarding why some contributors did
(or would) not submit funding requests.
* Gave "approval" for various Debian sub-projects applying for Mozilla
"MOSS" grants. 
* Fielded queries about merchandise printing.
* Answered some questions regarding the reimbursement procedure wiki
* Clarified some positions in the recent Debian Treasurer Team 
In terms of specific events, I addressed funding requests for (and
other administrative work around) a BSP in Tirana , the Hamburg
Mini-DebConf , SnowCamp 2018 , FOSS'ASIA 2018 , LibrePlanet
, FOSDEM 2018  and a Debian Women  meeting in Curitiba,
In addition to all of the above, I spent time on:
* Liasing with and advising the Anti Harrassment team  on a number
of specific issues, as well as evaluating potential additional team
* Addressing various poor behaviours of Developers.
* Moderating / contributing to the "/r/debian" subreddit .
* Looking into a potential trademark violation and/or scam.
* More work on Debian becoming a supported operating system on the
"Windows Subsystem for Linux"  platform. This has seen
significant progress throughout this month and we are almost
* Redirecting private support queries sent to the leader@ alias. Like
last month, I did not any requests in February to remove emails from
Don't forget Debian is willing to reimburse up to USD 100 for
travel/accommodation expenses to attend Bug Squashing Parties (BSPs)
. If there are no BSPs near to you 30], organise one!
Reimbursement requests should meet the following conditions:
* The requester agrees to communicate about their activities during
the event, such as posting to Planet Debian  The goal here
being to increase the visibility of such work.
* The requester must be a Debian contributor of some description or
have demonstrated an ability and committment to do that kind of
"Oh, one last thing..."
Lastly, in case you missed it:
* The DebConf 18 Call for Proposals (CfP) has been announced. 
* A Mini-DebConf in Hamburg in May has been announced. 
* Purism  now offers hardware discounts to Developers. 
See y'all next month…
: :' : Chris Lamb
`. `'` firstname.lastname@example.org / chris-lamb.co.uk
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----