Re: Project Start: Section 1

Michael Lazzaro wrote:

>"Joseph F. Ryan" wrote:
>

<snip>

>>n another note, is there place (CVS) that can be set up
>>that this stuff can uploaded this stuff to? :)
>>    
>>
>
>Not yet.  We'll almost certainly just tack our stuff onto the current
>Parrot/Perl6 CVS tree, since that's the obvious place for it.
>

Well, the problem with that is  parrot/languages/perl6 tests are for the
parser and compiler, not the language; meaning that the compiler test cases
are to verify that the compiler is working correctly.  For instance, there
shouldn't be tests for variable attributes in the compiler test suite, when
that functionality isn't even close to being completed.

>But I
>note that CVS is pretty horrible at certain things -- it's a crappy way
>to coordinate on documents -- so I'm still thinking we want an online
>system of handling additions/comments/notations/edits, roughly similar
>to what I tested in the POOC with the bbs-thread-on-each-page.  Again,
>see http://cog.cognitivity.com/perl6/
>  
>

Hey, looks good to me.  

>A system like that is better set up for instant-visibility _proposed_
>edits, but the actual text is still committed by the moderator, so it's
>a well-proven way to coordinate efforts for large, granular projects
>like this one.  If we used CVS directly to patch/commit actual
>sub*sections, we'd run into the whole "battling edits" and patch/commit
>blackhole imposed by CVS systems.  It's bad enough with code, but for
>docs it can be infuriating.
>
>MikeL
>

So, an www system for documentation, and possibly CVS for unit tests?