[WWdevel] Re: CVS alternative

[Sam Hathaway]

On Jan 10, 2005, at 4:13 PM, Michael Gage wrote:

>>
>>  Problems start in the non-tagged side, basically however we find 
>> them.  Once this thing is initialized, I guess we can start filling 
>> that up with lots of pg files.  When it gets tagged, then it is moved 
>> to the tagged-side, which will be organized to mirror the 
>> heirarchical topic structure of the database.
>>
>>  We may not be able to "polish" every problem, but as that is done, 
>> it simply gives an updated version of the problem on the tagged 
>> side.  The setup as described above basically gives up on the notion 
>> of systematically polishing problems.  If we want to keep that alive, 
>> we should have 3 basic sub-divisions (raw, tagged, and 
>> tagged-and-polished).  Actually, this 3-part version might be a good 
>> way to go.
>>
> I like the 3 part version.  Possibly even a 4th part for  problems 
> which can be used as models for future problems (exhibiting best 
> practices, etc. etc.)  This fourth part could be fairly small however, 
> and may not need to be a CVS.

Can anyone give me more details on how the repository of problem 
sources and the "database" will interact? Based on what little I know, 
it seems to me that the problem source should be part of the problem's 
database record.

By the way, has anyone thought about how problems will be packaged? 
Many problems consist of more than one file and it might be worth 
laying out a packaging format, so that a problem and all of its 
auxiliary files and metadata can be distributed as a single file.
-sam