Recognize that all the people in pmdev and gods are volunteers. I know personally I respond much better to requests, or "Wouldn't it be cool ifs" than things that sound like demands. That being said I don't personally have a lot of time or motivation to devote to such an endeavor at the moment, maybe someone else will step up to the plate.

Recognize that all the people in pmdev and gods are volunteers.

I do, and I respect their efforts to make things better. However, I do find it a bit odd that none of the people who have the power to implement replied (well, you did now (and thank you for that)).

I know personally I respond much better to requests, or "Wouldn't it be cool ifs" than things that sound like demands.

The title is provoking to draw attention to the issue. This is not a new problem, and there has been discussion about it before. When you strip Dumper() off the given code, you get a hash reference that I'm sure can be turned into something useful for the database. This doesn't fix the individual perlfunc =items or the ones from perlfaq, but there haven't been that much changes in those (afaik).

If my request sounds like a demand (which I can imagine with this title), please excuse me.

maybe someone else will step up to the plate.

I surely hope so! (And many others do too)

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

theorbtwo submitted a patch to the perlman display page which seems to address the problem.

Ex:) perlman:perlref

This approach can probably be applied to perlfunc-tions too.

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.

So what can be done?
... it could be a god-writeable everyone-readable wiki where a brief note could be added when decisions are made.

To wrap up this particular sub-thread: there is now the Tidings wiki (aka "What's New at PerlMonks" in your Information nodelet), updated by members of the Cabal as user-visible changes to the site are made.

We're building the house of the future together.

Gods don't/can't read all of the nodes that come out.

I think a node with a reputation of > 150 stands out on its own, but I'll add a petition anyway. Thank you.

Update The "make a petition" link just posts to Perl Monks Discussion, the very category this thread is in. The petition adding page does not state that. I assume you didn't know.

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

Wow, that's kind of strange. One would think that the post would go to sysadmin or something. Hmmmmm.... a mystery?