[1765] in Kerberos_V5_Development
Re: krbdev vs krbcore
daemon@ATHENA.MIT.EDU (Theodore Ts'o)
Fri Sep 20 10:42:20 1996
Date: Fri, 20 Sep 1996 10:40:53 -0400
From: "Theodore Ts'o" <tytso@MIT.EDU>
To: hartmans@MIT.EDU
Cc: krbdev@MIT.EDU
In-Reply-To: <199609200622.CAA13388@tertius.mit.edu> (message from Sam Hartman on Fri, 20 Sep 1996 02:22:24 -0400)
Date: Fri, 20 Sep 1996 02:22:24 -0400
From: Sam Hartman <hartmans@MIT.EDU>
I assume the krbdev mailing list is semi-public, and while not
well-announced, may contain members who are not part of the MIT
Kerberos team. The krbcore group.list implies write access to the
source tree and is only for the Kerberos team. Both mailing lists
are archived to a public discuss meeting.
I assume that krbdev should be used for
announcements/discussion that do not have an implicit requirement for
privacy. However, things like release deadlines, security bugs, etc,
should be discussed on krbcore or through personal mail.
Sam,
Yes, that's how things have been working in practice; thanks for
explicitly documenting the current, existing practice.
The main difference from existing practice to how I want things
to be is that there's going to be a separate separate, private discuss
meeting to archive the krbcore mailing list.
- Ted
