* [gentoo-project] GLEP 63 - was Call for agenda items - Council meeting 2014-03-11
@ 2014-03-04 15:02 99% Rich Freeman
0 siblings, 0 replies; 1+ results
From: Rich Freeman @ 2014-03-04 15:02 UTC (permalink / raw
To: gentoo-project
On Tue, Mar 4, 2014 at 9:52 AM, Anthony G. Basile
<basile@opensource.dyc.edu> wrote:
>
> One week until the council meeting. Just to make sure I'm not missing any
> issues and we don't have a last minute rush, here's the agenda so far:
>
> http://dev.gentoo.org/~blueness/council/council_agenda_20140311.txt
Moving discussion to a separate thread (if my MUA isn't broken)...
It looks like we actually want to approve the GLEP, but I think it is
still a bit weak on documentation.
The only instructions for creating keys reference two outside sources
that aren't actually aligned with the policy as far as I can tell.
From http://ekaia.org/blog/2009/05/10/creating-new-gpgkey/ :
Key is valid for? (0) 0
Key does not expire at all
(does not comply with 5-year max)
https://wiki.debian.org/Keysigning does not mention half the stuff on
our list, like control over digests/etc.
Certainly an exhaustive set of instructions on using gpg is too much,
but can we at least get:
1. A list of steps that can be followed to generate a key that is
useful and compliant with the policy.
2. A command that can be supplied with a key ID and tell you if the
key complies or not.
Right now we just have a bunch of pointers to various websites and a
set of guidelines, and devs are basically expected to figure it out.
I think the result of this is going to be a lot of back-and-forth
trying to get everybody to fix their keys, with new issues cropping up
all the time.
Rich
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2014-03-04 15:02 99% [gentoo-project] GLEP 63 - was Call for agenda items - Council meeting 2014-03-11 Rich Freeman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox