- From: Terje Bless <link@pobox.com>
- Date: Wed, 18 Feb 2004 22:18:40 +0100
- To: QA Dev <public-qa-dev@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ville Skyttä <ville.skytta@iki.fi> wrote: >CPAN distribution name: Currently the perl packages inside the script >are W3C::UserAgent and W3C::CheckLink::*, but I think W3C-LinkChecker >would be good so it is similar to W3C::Validator (which doesn't exist >yet :) and W3C::LogValidator. […] Agreed. W3C::LinkChecker is good. >CPAN distribution dir: I am fine with using my CPAN dir (account SCOP) >or something else. CPAN dir can change as needed (e.g. Perl itself follows the current Pumpking); using your dir makes sense since you're the one maintaining it. >CVS organization: a CPAN-like distribution layout would be good. Should >there be a new top-level directory on dev.w3.org, or a subdir under eg >perl/modules/W3C/LinkChecker/ for consistency with LogValidator? I'm loath to implement too deep directory structures, but in this case I think it makes sense to keep it under $CVSROOT/perl/modules/W3C/LinkChecker/. Not the least reason for which is that I foresee the modularized Markup Validator keeping its modules there while the Markup Validator itself (i.e. check, the config files, etc.) live on in the «validator» module; at least until the modularized code is stable, but possibly indefinitely. We'd best define a CVS module for «LinkChecker» though, so we don't force people to pull from seven subdirectories deep. - -- "I don't mind being thought of as a badguy, but it /really/ annoys me to be thought of as an *incompetent* badguy!" -- John Moreno -----BEGIN PGP SIGNATURE----- Version: PGP SDK 3.0.3 iQA/AwUBQDPWrqPyPrIkdfXsEQLqnACgyIVN4GJ9uUJQbnFyLXSoDxGcSdMAnRv+ GkNt11tIV6q3E3ex0nR6kZ2K =Uur6 -----END PGP SIGNATURE-----
Received on Wednesday, 18 February 2004 16:18:44 UTC