telnet & ftp official status
Nicolas Williams
Nicolas.Williams at sun.com
Fri Oct 3 17:22:32 EDT 2008
On Wed, Oct 01, 2008 at 04:01:32PM -0400, Greg Hudson wrote:
> We discussed this process a bit yesterday. It's okay to informally
> discuss an API or feature change on the list before you've assembled the
> complete project proposal with detailed design and API documentation and
> so on. That way if it turns out we're not interested in a change, you
> haven't gone through the whole rigamarole for nothing.
>
> There downside is if the discussion peters out or rejects the proposal,
> there is no discoverable artifact left behind, only a thread in the
> mailing list archive which will quickly get lost. When I get a bit more
> settled, I will think about how best to record information about
> "non-projects" so that they can be referred to later, either using RT or
> the wiki.
This is an excellent point/idea.
Nico
--
More information about the krbdev
mailing list