Recently there have been several posts concerning the deployment of perl on an Enterprise scale while conforming to the strict methodologies imposed by rigid audit controls. Primarily they were spawned by edwardo's post.

This is an area I've been given a year by my employer to grapple with and propose solutions for. I'm re-wrapping edwardo's post in an effort to find out:

  1. Who has done what.
  2. What other's feel would be ideal.
  3. Gather consensus on what would be required,
  4. Find others in a similar situation that might be interested in a collaborative effort to find the best path to resolution to bring perl into larger scale development enviornments.

If anyone would like to make comments via email please email me at jeff.bulley@midata.com

coreolyn Duct tape devotee.


In reply to Perl In The Enterprise by coreolyn

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.