RCS (and probably CVS) are great for storing the version as well as the modification history. You can even have them added directly into your script (e.g. with $Id$ and $Log$ variables). The hardest part is making sure that people enter a short, concise description when checking the source back in after making changes. :) The other things (licensing, title, etc.) are static and can be entered one time, preferably from some sort of template. There is no real way to shorten it other than that - the license, copyright, title, and decription really need to come at the top of the script. I wouldn't think all of that would be needed for *every* script you write, but that's a management decision.

In reply to Re: nice styles for code headers by turnstep
in thread nice styles for code headers by markjugg

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.