Several thoughts:
  1. I don't think that cutting and pasting code is too difficult for even making small changes. Each node (container, superdoc, etc) or opcode is a fairly small piece of code and is pretty easy to manage as far as updating.
  2. As far as the name, I believe that vroom and several other monks have been using the term developers to describe the would-be group.
  3. Finally, if no one will be able to edit the actual source or view the MySQL database, then I see no reason why there should be only a select group that can view the source. Why not make it so that all people can submit there own changes? or post their updated code in Perl Monks Discussion for comments/suggestions?

Zenon Zabinski | zdog | zdog7@hotmail.com

In reply to (zdog) Re: Perl Monk Hackers by zdog
in thread Perl Monk Hackers by srawls

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.