Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl community hive mind book recommendations 15 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • books.perl.org (Score:2, Informative)

    by delegatrix (506) on 2002.01.07 11:15 (#2789) Homepage
    At the Apprenticeship Hour at YAPC::NA last year, Uri Guttman asked for help in developing books.perl.org for this sort of purpose.
    • Ah, yes,

      I do recall that.

      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.

      -dave
      • 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).
          • I'd have no problem giving you admin access.
            • 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 isol
              • There is some support in Slash for ACLs, but I've never used it. If necessary, it could be used, and if it needs some work, I could make it work. So no worries. :)
              • 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
                • this sort of DB and layout is not something i think slashcode could do.

                  Yes, but that is a reflection of your limited knowledge, not of Slash. :-) Slash is completely flexible in such matters.

                  there is also a very quiet companion email list for this which might be a better forum than use.perl

                  Why?

                  • 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. :)

    • What about using something PODish for inline book reviews in the online journals? =bookreview Core Perl This book ruined my recent Jamaican vacation. I couldn't but it down ... yada yada =cut You could always parse and export to books.perl.org if/when put into production. Spearhead the semantic web with simplistic inline comments. WOOHOO!
      • (cursed submit button)

        What about using something PODish for inline book reviews in the online journals?

        =bookreview Core Perl This book ruined my recent Jamaican vacation. I couldn't but it down ... yada yada

        =cut

        You could always parse and export to books.perl.org if/when put into production. Spearhead the semantic web with simplistic inline comments. WOOHOO!
        • Well, it would require a fairly complex bit of POD (title, edition, author(s), publisher, categories, rating, etc).

          And people'd screw it up (or forget about it) on a regular basis. With a nice simple set of web forms it'd be easy to add info.
          • I'm not talking about creating the whole application with one tag. Just the text of the review.

            There's something terrific about not having to interrupt your blog train of thought, log in to a separate application, look up all those attributes you mentioned, then type in your book review. Instead, use a tag to mark off your review, and either Slash outputs the necessary RSS-like file for bot consumption, or a web harvester comes along, parses your blog and dumps the text into some web-accessible ra
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.