Review of special packager access

Ben Cooksley bcooksley at kde.org
Fri Jul 8 12:49:38 UTC 2016


On Sat, Jul 9, 2016 at 12:41 AM, Philip Muskovac <yofel at gmx.net> wrote:
> Hi Ben,

Hi Philip,

>
> for Ubuntu I would be the relevant contact until someone says otherwise and
> we're very much still there ;)

Thanks, has been noted.

>
> While I'll look at the old keys soon, would it help you if we put a
> #Contact: at the top of the key list? Or do you have another place where
> that can be set?

In general it's up to individual distributions to manage the list of
keys as they see fit - as long as you know whose key is whose (and
they're all packagers for your distribution of course). The format I
mentioned is just one way of doing it.

>
> Philip Muskovac
> Kubuntu Developer

Cheers,
Ben

>
>
> Am 08.07.2016 um 13:39 schrieb Ben Cooksley:
>>
>> Hi all,
>>
>> My apologies if you're not a packager or someone associated with a
>> distribution - you can ignore this email. Packagers, please read on as
>> this contains important details.
>>
>> First: If you're a packager, please ensure you are subscribed to
>> kde-distro-packagers at kde.org, which is our usual list for
>> communicating with packagers. It would seem a number of you are
>> missing from there :)
>>
>> Prompted by a recent email I took a look at the list of accounts (one
>> per distribution) which are provided in order to facilitate early
>> access to packages - however for many i've no idea who would be the
>> relevant point of contact.
>>
>> I'd therefore like for someone from each distribution to please
>> confirm that their distro is still active and who can serve as a
>> general point of contact for that distribution. It would also be
>> appreciated if folks could check over their ~/.ssh/authorized keys
>> file and remove any outdated keys.
>>
>> If your distribution has completely lost access, please have someone
>> with an email address belonging to that distribution's domain email
>> sysadmin at kde.org to sort that out.
>>
>> KDE servers normally use a format something like this to clearly label
>> whose key(s) are whose, for those that might find it helpful.:
>>
>> ## Name <email.address at domain>
>> ssh-rsa....
>>
>> ## Next Name....
>>
>> The list of accounts, which should approximately correspond to
>> distributions, is as follows:
>>
>> - Active
>> - Aix
>> - Aosc
>> - Archlinux
>> - Arklinux
>> - Asplinux
>> - Bluewhite64
>> - Chakra
>> - Conectiva
>> - Crux
>> - Darwin
>> - Debian
>> - Exherbo
>> - Fedora
>> - FreeBSD
>> - Gentoo
>> - Kaos
>> - Mageia
>> - Magic
>> - Mandriva
>> - Meego
>> - NetBSD
>> - OpenBSD
>> - PCLinuxOS
>> - PLD
>> - Redhat
>> - Rpath
>> - Siduction
>> - Slackware
>> - Slamd64
>> - SUSE
>> - Tld
>> - Tru64
>> - Tukaani
>> - Turbo
>> - Ubuntu
>> - Uludag
>> - Uoirix
>> - Uomandriva
>> - Uosolaris
>> - Vine
>> - Yellow
>> - Yoper
>>
>> In two weeks time we'll go ahead and disable ones we don't get a response
>> from.
>>
>> Thanks,
>> Ben Cooksley
>> KDE Sysadmin
>
>


More information about the release-team mailing list