Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Now that this has had time to rattle around in my brain, I think the best choices are 1) to have janitors make minor fixes where appropriate (consideration is probably the best way to submit requests for such). If more extensive "improvements" are warranted, then 2) someone needs to make those improvements and when they finish them, they just need to post the new version like anybody else would (and include a link to the original) and the pedagogues will change the link in Tutorials to point to the new version.

In the unlikely event of a group of more than 1 person effectively taking on joint, on-going responsibility for extensive changes to some tutorial(s) (seems very unlikely), we can consider a wiki-like tutorial. No need to burn that bridge until we get to it.

As for what is appropriate for janitors to do to Tutorials, my first stab at a guiding principle is to respect the authorship. That is, objectively technical corrections should be inbounds and nothing else. And if the correction can't be adequately described in the small "consideration" text field, than a reply is probably a better first step.

- tye        

In reply to Re^5: Page not found issue while accessing a link from perl monk's tutorial (ownership) by tye
in thread Page not found issue while accessing a link from perl monk's tutorial by jesuashok

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others imbibing at the Monastery: (4)
    As of 2018-07-21 08:11 GMT
    Find Nodes?
      Voting Booth?
      It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

      Results (445 votes). Check out past polls.