Something appears to have been done: a quick look at the documentation shows a note that it is out dated, along with a link to perldoc.com.

On one hand I would like to see more responses from gods on issues like this. It is rather frustrating that there isn't a great deal of communication about future plans and the direction of site development. For example, it was roughly three weeks after the site switched to CSS that I learned there were plans to eventually fix things for those of us whose CSS implementations are linked to JavaScript.

On the other hand, I don't think three days is a long time. The News section was offline without comment for something like six months--that's a long time. Also, there are plenty of pressing concerns, and I wouldn't be surprised if documentation ranks pretty low compared to issues like server overloading. Don't forget there are also a lot of suggestions made and it would probably be a full-time job to respond to them. Making demands probably won't increase responsiveness. Update: I hadn't read vroom's post before writing this. Just refer to the points he made for a summary of what I wanted to say with this paragraph.

So what can be done? I would like to see a member of gods post a (weekly?) status report just to give the rest of us a general rundown of developments. They could take turns, or it could be a god-writeable everyone-readable wiki where a brief note could be added when decisions are made. These ideas, however, do require members of gods to make communication a priority.

Any individual who wants to hear about site changes would probably do better to hang out on IRC and listen to the discussions. An enterprising person might post summaries of these discussions (with permission, of course), which would solve the lack of communication without putting any more pressure on the developers. No doubt there's a good deal of xp in it as well.

In reply to (kudra: increasing communication) Re: gods? pmdev?(Re: I want site documentation updates and I want them now.) by kudra
in thread I want site documentation updates and I want them now. by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.