Re: [WWdevel] Re: CVS alternative

[Sam H. <sh...@ma...>]

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

>>
>>  Problems start in the non-tagged side, basically however we find=20
>> them.=A0 Once this thing is initialized, I guess we can start filling=20=

>> that up with lots of pg files.=A0 When it gets tagged, then it is =
moved=20
>> to the tagged-side, which will be organized to mirror the=20
>> heirarchical topic structure of the database.
>>
>>  We may not be able to "polish" every problem, but as that is done,=20=

>> it simply gives an updated version of the problem on the tagged=20
>> side.=A0 The setup as described above basically gives up on the =
notion=20
>> of systematically polishing problems.=A0 If we want to keep that =
alive,=20
>> we should have 3 basic sub-divisions (raw, tagged, and=20
>> tagged-and-polished).=A0 Actually, this 3-part version might be a =
good=20
>> way to go.
>>
> I like the 3 part version.  Possibly even a 4th part for  problems=20
> which can be used as models for future problems (exhibiting best=20
> practices, etc. etc.)  This fourth part could be fairly small however,=20=

> and may not need to be a CVS.

Can anyone give me more details on how the repository of problem=20
sources and the "database" will interact? Based on what little I know,=20=

it seems to me that the problem source should be part of the problem's=20=

database record.

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