* Eric Cholet <[EMAIL PROTECTED]> [2004-02-10 18:51]: > There is of course another category of modules that I use, > larger systems such as a templating module, or a date module. > For those, I have found that hanging around mailing lists and > forums quickly point me to the better alternatives.
And that's exactly the process I think could be leveraged to build these comparative articles. I wasn't thinking of a single person writing an entire and exhaustive article on a subject. Exactly how it works would be a per-article issue; in some cases there might be one author who mostly maintains it themselves, or it could be someone taking "patches", or it might be a bunch of people writing mostly about the module they know best and addressing each other's points, or it might be maintained via a wiki.. I don't know. I don't think any single procedure is going to fit every domain here. This space intentionally left open. I'm just gunning for the simplest thing that could possibly work, here -- and we already have pretty much all the infrastructure for this suggestion in place. And if Perrin, Mark, and the others who have already written such articles on other occasions would make them available this way, we'd already have a sizable amount of tasks and popular modules covered. The selection isn't expected to be very large either. A single comparative article covers a broad spectrum enough that having just a dozen of them would probably account for 95% of the tasks people use CPAN modules for. I really think we don't need a whole lot to make this work well enough; we only need a small amount of an unfortunately extremely scarce resource -- people with interest and experience in a domain enough to be able and willing to write such articles, and (less effortsome) occasionally update them. And maybe one driven individual to organize the entire effort in the very beginning. -- Regards, Aristotle "If you can't laugh at yourself, you don't take life seriously enough."
