Creating the software is a piece of cake compared to training people to use it, maintaining it and extending it for new/modified uses over its lifetime.

So are you saying that the source code itself is a side issue, i.e. I benefit by putting code in the sunshine for anyone's review, and organizations that plan to compete with the software don't care about access to the source code since they'll start from scratch anyway? Will they really? I suppose that organizations that plan to compete will have their own challenge if their "non-open source" stuff is not far spiffier.

With regard to the resellers I hope to sign up, I guess ultimately they don't care where the code comes from as long as it works and as long as it catalyzes the additional sales/services opportunities that will be part of their offerings. For them do I cast open source as "reliability insurance?"

Should I maintain the trappings of traditional software packages of installation keys for demo versions and serial number keys for production versions? Obviously the wrapper enforcing the key can be deleted but that would violate the license agreement, wouldn't it? :-)

Does 'open source' code present far different issues for maintenance? What about proliferating versions?

In reply to open source, training/maintenance by ff
in thread software collectives vs. price of organizational license by ff

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.