Bug 174339
| Summary: | Change public PGP code on ctm mailing lists | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | Stephen Montgomery-Smith <stephen> |
| Component: | Books & Articles | Assignee: | postmaster |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Stephen Montgomery-Smith
2012-12-10 19:50:01 UTC
Responsible Changed From-To: freebsd-doc->postmaster over to appropriate entity On Thu, Dec 20, 2012 at 08:59:41AM -0500, Eitan Adler wrote: > On 20 December 2012 08:06, David Wolfskill <david@catwhisker.org> wrote: > > On Thu, Dec 20, 2012 at 06:37:10AM +0000, eadler@FreeBSD.org wrote: > >> Synopsis: Change public PGP code on ctm mailing lists > >> > >> Responsible-Changed-From-To: freebsd-doc->postmaster > >> Responsible-Changed-By: eadler > >> Responsible-Changed-When: Thu Dec 20 06:36:54 UTC 2012 > >> Responsible-Changed-Why: > >> over to appropriate entity > >> > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=174339 > > > > Huh??!? > > > > postmaster (per se) does not have a commit bit. > > > > When (e.g.) postmaster creates a new mailing list, we submit a doc PR to > > get the Handbook updated. > > > > What, exactly, would you have postmaster do in this case? > > My understanding is that he wants the list description updated: e.g., > http://lists.freebsd.org/mailman/listinfo/ctm-cvs-cur > .... Oh. Right. Sorry; that wasn't my impression when I had discussed the process with him, and I hadn't actually read the PR.... :-( I screwed up. :-( OK; I've updated the list descriptions. In the process, I found that some lists' descriptions lacked the key, so I augmented the following with the key (and introductory text): * ctm-src-6 * ctm-src-6-fast * ctm-src-8 * ctm-src-8-fast * ctm-src-9 * ctm-src-9-fast That said, it is not clear to me that placing the key in each list's description is ideal. I suspect that it might be better-placed in the Handbook, (as security-officer.key is, in doc/share/pgpkeys), perhaps as "ctm-moderator.key" (merely as an example). It could then be committed -- possibly by the CTM moderator -- and recorded in a single place under version control and accessible in the Handbook (vs. duplicated (accurately, we hope!) for each new CTM list that gets created, and updated with no audit trail whatsoever). Peace, david (current hat: part of postmaster@freebsd.org) -- David H. Wolfskill david@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. Hi Stephen, Is there anything left we (postmaster@) can do here? Florian State Changed From-To: open->patched This should be fixed, waiting for confirmation. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/05/2013 05:19 AM, Florian Smeets wrote: > Hi Stephen, > > Is there anything left we (postmaster@) can do here? > > Florian > Thank you. Nothing more to do until the end of February, when I will be closing down some of the ctm mailing lists. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ6D92AAoJEC3xK9GaktgHFZYIALj/AeheqdD5038Ub28MuFIP 9fLRgYNcGFbHT2V37gjMK0LEWtf1U65dsTmW+QD0BmlkOYjy4RYr3y+KJlvwbKNA XOMAtiJHH9TK1zvtq8uzh+dpBd3e97UAvKlBzIGIP1P6Nk+XuFVnQOreGDHQABr6 h+6VF2UPPC8tZcrGex7y8UvNzNOYNk5cSvqliZ6H7wjPVvrM0HD4AYixSt4x4pfC vzVxdyhdg7TMJn1pUt6vGa5CoJILykCWM9xKuVghcragATneR6Ic/7wD9YNhzhxE nWNFs3ZgWQmHdJ3bTh+lxEa+VikctAEELESr+hd5FDA0ph5nZpjUHAVEflDW+UE= =TuJb -----END PGP SIGNATURE----- State Changed From-To: patched->closed Resolved. |