On Friday, October 11, 2002, at 01:10 AM, Simon Cozens wrote:
> [EMAIL PROTECTED] (Michael Lazzaro) writes: >> -- A way to submit fixes & new stuff. >> -- The ability to add (threaded) comments & questions, >> to encourage less important discussions off perl6-language. >> -- Problem/Solution ratings for recipes that everyone >> can help nudge. >> -- Acceptance ratings for recipes that (almost) nobody can nudge. >> -- An automatically generated PDF version. > > Why don't we ask ActiveState nicely, who already have most of this > infrastructure set up? If people feel that's a better way to go, that'd be fine too, (or we could put something on one of the other existing portals) but I'm looking for something a little different. I'm proposing something with a very focused scope. A "community" resource, yes, in the sense that the community will help build it, but one that's directed primarily at producing annotated reference material; a collection of Best Practice documents, with zero fluff. The community discourse that happens would be specifically tailored to producing those docs; other sites are better suited to evangelism, general discussion, etc., etc., and we should continue to support those vigorously. Since my company just happens to write corporate e-learning (online training) software based around a perl5 engine (wow, what a coincidence), we already have these features & more, but I wrote the POOC v0.1 as a quick proof-of-concept, so I didn't plug anything in. We also have access to people with substantial educational & corporate training experience who advise us on best-practice training approaches, which is _directly_ why I'm suggesting in an approach different from the other sites. Anyway, I don't want to jam this idea down people's throats, but I've been getting increasingly concerned that the documentation and community-building efforts have been falling far behind the design & implementation efforts, which is why I have been prodding some of the discussions lately. You can also see why my company wants to volunteer for this -- it'd be a great demo of something we can actually show people (as opposed to the usual proprietary/corporate stuff we do), and it would help a language that should be, as we all know, substantially more popular than it already is. (Don't even get me started on that last point...) MikeL
