# from Andy Lester
# on Tuesday 30 October 2007 07:39:
>> The trouble with ad-hoc is just that it tends
>> to *never* get formalized (i.e. never gets centrally documented,
>> becomes discoverable, appears in books, etc.)
>
>The trouble with planned soluttions is that it tends to *never* get
>implemented.
By ad-hoc, I was referring mostly to the distributed nature of the
META.yml living in the tarball regarding Aristotle's pondering of a
centralized system. It's about coordination schemes, formalization,
and discoverability -- not iterative development.
Note that the META.yml *fields* are primarily not ad-hoc. This is yet
another set of pros/cons/caveats in itself.
But, I'm also thinking about the scattered metadata in various
*.perl.org sites. I think the progress vector for making that metadata
more usefully organized and accessible probably involves META.yml in
some way.
--Eric
--
software: a hypothetical exercise which happens to compile.
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
|
