Re: status update

[Aaron Turner <aturner@linuxkb.org>]

On Mon, 15 Nov 1999, Jason Pincin wrote:

> OK - question for the group, and partial defense on my part.
> 
> Between commits by me, the site is usally broken horribly - because I am
> doing a lot of work with the object code, which the entire site is based
> on, and when I break something in the object code, usually everything is
> broken.

Maybe the the object code needs to be more modularized?  Maybe break up
functions.php3 into logical groups so you only source those modules you
need... and hence don't get killed when one funciton breaks another
unrelated one.

Basically, my idea about this was that people should be able to commit
their code after each coding session or two.  Maybe that's because my
coding style tends to add functionality a small bit at a time without
impacting other sections. Dunno enough about the object code to know if
this is possible or not.

Right now I wouldn't mind it being a broken every now and then if that
allowed you to commit more often.  When you make massive changes/updates
it just means that people have a lot more to learn and it's harder to
start using.

--
Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization  http://linuxkb.org/
Because world domination requires quality open documentation.