You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "David N. Welton" <da...@dedasys.com> on 2002/12/11 08:26:07 UTC
Explanation of STATUS file?
[ Please CC replies to me. ]
I only picked up on STATUS file usage recently, seeing them used in
some other projects. However, is this concept documented anywhere?
Might be something convenient to include in incubator.
Thankyou,
--
David N. Welton
Consulting: http://www.dedasys.com/
Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
Apache Tcl: http://tcl.apache.org/
Re: Explanation of STATUS file?
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David N. Welton wrote:
> [ Please CC replies to me. ]
>
> I only picked up on STATUS file usage recently, seeing them used in
> some other projects. However, is this concept documented anywhere?
> Might be something convenient to include in incubator.
I agree.
In the Avalon community it is helping a lot in getting a common
perception of what is happening, we should explain its role in our docs.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Explanation of STATUS file?
Posted by Ben Hyde <bh...@pobox.com>.
I think there are mess of random rituals, like the STATUS file, that
are useful but adopted with various degrees of enthusiasm in various
groups. It would be great to enumerate these and then let groups pick
and choose as they like.
Three example rituals or traditions -
Committers proof read each others commits.
To implement this one all the committers should strive to be
subscribed to the right cvs generated mail. Projects should
encourage 3rd parties to do the same. This highly focused
proofreading can create a-lot of quality at very low cost.
It is delightful to notice how different people notice very
different things about any given change.
Willful suppression of one's incredulity.
Project participants attempt to bite their tongue and let
experiments have a little headroom. It often very interesting
how long it takes an attempt to scratch an itch to transition
into a useful solution to the problem being addressed.
We don't do that! ... unless we ought to.
All the rules tend to be guidance and can be overridden if
that turns out to be a better tactic at the time. This one
is invoked only rarely, and then usually silently. If you
get into an argument that your in the "ought to" escape clause
then your probably not.
On Wednesday, December 11, 2002, at 02:26 AM, David N. Welton wrote:
>
> [ Please CC replies to me. ]
>
> I only picked up on STATUS file usage recently, seeing them used in
> some other projects. However, is this concept documented anywhere?
> Might be something convenient to include in incubator.
>
> Thankyou,
> --
> David N. Welton
> Consulting: http://www.dedasys.com/
> Personal: http://www.dedasys.com/davidw/
> Free Software: http://www.dedasys.com/freesoftware/
> Apache Tcl: http://tcl.apache.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>