A new node type would only be required if permissions were different. I don't see this as a "proliferation". You are proposing a similar "proliferation" of new "forum type" nodes which have /more/ fields than a nodetype and would require re-implementing the permissions structure that is already nicely captured in nodetypes.

I like the idea of not always having to add a new root node type for each "section". Granted, you were thinking mostly of new fora specifically for the sake of having different access permissions, where two extra nodetypes might be required for some sections.

But this is such a fundamental change, that I'd approach it in phases and look at implementing a forum as you've described without simultaneously taking on fundamental changes with permissions (which need to be done very carefully because they are too easy to get wrong -- as we've done several times not too long ago).

Anybody could work on this.

But you are the only one who was added to gods with a mandate to work on it (patch approval).

- tye        

In reply to Re^4: Create new [pmdev]-only section "Pmdev Discussion" (create new forum?) by tye
in thread Create new [pmdev]-only section "Pmdev Discussion" by jdporter

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.