Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I would say "no logging", but how would we enforce it?

It's not practical to enforce it, so I say why bother? You can't control what people do with publicly available data on their PC, but you do have some say/rights in how they share that data with others. I think that's what we should focus on. Providing statistics from logged data is (in my opinion) perfectly OK.

No profanity directed at anyone

I think this could be summed up by saying "Be mature, no personal attacks against other people". Profanity directed at somebody is just an extension of name-calling. Severity of infraction is dependent upon severity of the attack. Profanity starts to move towards one extreme of that spectrum.

Don't use published code without citing it. -- Again, tough to enforce.

"Do not post copyrighted material without appropriate citation and/or permission from the author". You're right; this is largely an honor system thing, and you're also right in that many of us can spot Cookbook material pretty easily. It should be easy for us to then inform vroom or get the author to modify the node to include appropriate attribution. Aside from that, typical copyright stuff applies.

Aside from that, I agree complete with everything (well, almost everything ;) else!

David


In reply to Re: (Ovid) Re: Development of the Perl Monks Code of Conduct by Fastolfe
in thread Development of the Perl Monks Code of Conduct 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.