- From: Mary Brady <mbrady@nist.gov>
- Date: Thu, 28 Jun 2001 14:09:17 -0400
- To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>, "Fred L. Drake, Jr." <fdrake@acm.org>
- Cc: <www-dom-ts@w3.org>
----- Original Message ----- From: "Fred L. Drake, Jr." <fdrake@acm.org> To: "Arnold, Curt" <Curt.Arnold@hyprotech.com> Cc: <www-dom-ts@w3.org> Sent: Thursday, June 28, 2001 1:39 PM Subject: RE: [General] domconftest now a project at SourceForge > > Arnold, Curt writes: > > I guess we should spend some time on what the CVS should look like since > > it is impossible to undo changes without leaving a trace. > > Not impossible, but difficult, tedious, and highly undesirable. ;) > > > domconftest > > tests > > java > > org > > w3c > > dom > > testing > > ecmascript > > adapters > > junit > > Where do you envison documentation would go? (Schema documentation, > test framework documentation, etc.) > Also, this seems somewhat Java-centric. Perhaps adapters/ should be > inside the java/ directory, and then other languages would have a > directory parallel to that? Where do you expect things like the > Python and ECMAScript components to go? I'd at least expect the > ECMAScript tests to be part of this repository since it plays an > important role in the W3C specifications for the DOM. > [mb] Absolutely! I agree that components for a particular binding should be closely linked, and of course, documentation needs a prominent home - somewhere close to the top. --Mary > > -Fred > > -- > Fred L. Drake, Jr. <fdrake at acm.org> > PythonLabs at Digital Creations > >
Received on Thursday, 28 June 2001 14:11:41 UTC