Some people owe me doc updates...

[Gerald Carter]

On Thu, 2 May 2002, Green, Paul wrote:

> Suggestion: in the future turn down code changes w/o accompanying
> documentation changes.  Yes, it is a tough stance, and yes, you might
> lose a few nice features, or a few coders.  But I think it more likely
> that people will accept the new situation and rise to the challenge.  
> Samba is a critical product these days and having such a requirement
> would simply recognize that fact.  In actuality, I think the actual
> policy would be to simply defer the commit until the author supplies the
> documentation changes.

I like the idea, but I think its our own that did it this time :-)

> Over on the perl5-porters list, where I've been working for ~6 months,
> we have a pretty good record of getting code changes, docu changes, and
> test case additions or changes all at the same time.  Not perfect, but
> pretty good.
> 
> Of course, maybe you are doing this already, and because I've been away
> for a while I didn't notice. If that's the case, ignore this.

Good advice :-)

There's a lot of parameters in HEAD that need documenting right now.
I think some people want to get busy (or others might want
to help out).







cheers, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN 0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--