All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

I'm kind of split between wanting it here on use perl, which is sort of an existing community hub, or on books.perl.org, because it deserves its own site. For various reasons which may become apparent later, I'm leaning towards the latter at the moment.

The good thing about doing it on use Perl is you already have the usersin the database with access etc. It's up to whoever wants to do it; if you want to do it on use.perl.org, I can help you do it. books.perl.org could redirect to use.perl.org etc. too. But if you have other plans, go for it.

Yep, I thought of that too. It'd be one less login for people to deal with, which is nice. OTOH, it might be a conflict if we wanted to give me admin access to the books stuff, but not the rest of use Perl (I don't know how fine-grained the access controls are).

Well _I_, of course, am a paragon of trustworthiness! But there are some shady characters like that Uri Guttman fellow who might be considered for admin duties related to book things as well. But you have to keep that guy on a _very_ tight leash!

(I'm joking, for those who aren't sure)

More seriously, I was thinking generally about whether we'd want to require a 100% overlap between having admin powers for book stuff and admin powers for use Perl in general. I, being a paranoid sort, tend to favor isolating systems.

For example, jobs.perl.org is only admin-able by a few designated people (me, Ask and Uri, for the curious) and that seems like a good default access level.

i resemble that remark. this thread made me actually get an account here. such work you are causing me!
anyhow, i got books.perl.org to do this kind of thing. first a comprehensive listing of all perl books (see my very old books page at: sysarch.com [sysarch.com]) with all the public info on the books. this sort of DB and layout is not something i think slashcode could do. then there is the reviews and ratings. do we want all entries to carry equal weight? then you get imdb wacko ratings. or do we give more weight thos

there are two main aspects to the books page, a basic db of all the books and a review/rating system. maybe i don't know slashcode but i don't think of it as a search front end.
as for why a mailing list is better that a web forum, i just can't answer that. it just is.:) you obviously have a biased view towards use.perl.:)
we already have a few interested people subscribed to that list so if autarch and anyone else wants to get involved, i suggest they subscribe there. the list will be ongoing even afte

maybe i don't know slashcode but i don't think of it as a search front end.

Slash is a general web application server. It can be anything you want it to be. pudge.net has a photo gallery and football picking. It is quite simple to add a search interface like that to Slash, you just write a simple plugin. Slash is actually very good at that kind of thing.

as for why a mailing list is better that a web forum, i just can't answer that. it just is.:) you obviously have a biased view towards use.perl.:)