Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Since the vroom seems to be asking for general categories rather than specific suggestions, I'd add the following:

1: Signal to Noise Ratio (I personally think we do pretty well here)
2: Section Relevance - Ability of the specific sections to adequately cover all possible (or desireable) topics.
3: Infrastructure (both structural and cultural) - is perlmonks prepared to deal with an influx of new users that it's success will bring? They must be assimilated...resistance is futile.
It might also be interesting to include something like "What is your favorite/least favorite thing about perlmonks? (Choose only one!)

On a side note, I think that one of the best things about perlmonks is the way that vroom runs the place...or doesn't at the situation dictates. This call for feedback is just another indication of that. While some similar sites have the feel of a monarchy (even if it's often a benevolent one), you really get the sense of community and of meritocracy here at perlmonks. The best ideas...and the best code... usually win out. In this, I think, the culture of perlmonks reflects the culture of Perl, but also the character of it's founders.

Thanks,
~monk d4vis
#!/usr/bin/fnord


In reply to (d4vis)RE: Upcoming survey to help me better the site by d4vis
in thread Upcoming survey to help me better the site by vroom

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (5)
As of 2024-03-28 10:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found