[1936] in Kerberos_V5_Development
Re: confidential support
daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Nov 11 13:16:26 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: gnats-admin@rt-11.mit.edu, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 11 Nov 1996 13:16:10 -0500
In-Reply-To: "Barry Jaspan"'s message of Mon, 11 Nov 1996 12:28:32 -0500
>>>>> ""Barry" == "Barry Jaspan" <bjaspan@MIT.EDU> writes:
"Barry> Could you explain this a little more thoroughly? Your
"Barry> email went completely over my head. :-)
Sorry; it was targeted at people who had the unfortunate
experience of dealing with the internals of Gnats. I'm not quite sure
why I Cc:'d it to krbdev other than to create a perminant record.
Since I talked to tlyu, I have a better idea of how it will
work for end users of Gnats, and I can try to explain.
* Two mailing lists have been created: krb5-prs-internal and
krb5-prs-public.
* The krb5-prs-public list will receive all PRs with confidential set
to know or PRs that are improperly formatted and that get tossed into
pending.
* krb5-prs-internal gets all PRs.
* This obseletes krb5-bugs-redist because krb5-bugs-redist contains
the wrong set of people for either list but cannot be renamed until
after the migration happens.
* krb5-prs-public will get krb5-bugs-redist minus people on krbcore.
* krb5-prs-internal will get people on krbcore who are on
krb5-bugs-redist. It will be open to krbcore, additional people on
the krbcore discuss ACL not on krbcore, and other people Ted thinks it
should be open to.
* I don't have sufficient consensus to actually install this code;
it's just sitting on a branch in a CVS repository. I have talked to
Tom and convinced him of the rationality of the plan.
--Sam
