Thank you for your advices and comments and your time.
Firstly:
If you feel that I am wrong and that this license is indeed a free software license I would encourage you to contact the Free Software Foundation and ask them to classify your license as such

1.) The license is based on open source license which you may find in several CPAN modules.
2.) We are fully aware of the confusion the way the license is formulated may cause and initiated a discussion concerning that 5-6 weeks ago as you may read here: The license discussion…is still opened.. I for one think that we may go back to GPL in version 2.0 with some sections being double or triple licensed.
Again the intention behind the license was NOT to stop anyone from further developing the code, but rather from abusing the original credits (an issue we have had in the past).
3.) The ajax popup you refer to is a test we make in version 2.0, and by the way it should work fine now on all Safari...or pre Safari browsers too. I have also fixed the cookie there now:
######################
sub bmsg{
######################
$query = new CGI;
$bm_cookie = $query->cookie(-name=>BROADCAST,
             -value=>$welcome_value,
             -expires=>"+1M",
             -httponly=>"1", 
             -secure=>"$secsid",
             -path=>"/");
print qq~Set-Cookie: $bm_cookie\n~;

print_topless();
$broadcastmsg = showhtml("$broadcast_msg");
print qq~<div style="color:#000000;font-size:12px;!important;">$broadc
+astmsg</div>~;
exit;
}

[download]

Thus, 1 month cookie instead of a session cookie, and overriding of original style sheet with "!important".
The irony is that you could not read this popup before (complete white on your browser)... but it is explaining that we are testing a new version.
4.) Comments: there are two sides to every coin, and I fully understand the "family thing" in PM. Its ok, but as one says there is no smoke without a fire (or something like this).
5.) Language: We have updated most of the language at 70-90%. We thought to provide these files as they are in hope that others will help in completing them.
6.) Last thing, some 4 years ago, some monks here were trying the script and forgot to delete the install file, I sent them a message about it, and last time I checked the script was still active on the server here (3 years ago), I don't remember where it was... just hope that they chmod it.

In reply to Re: (OT) Webapp and license, was Re^5: What's the best Perl CMS? by Anonymous Monk
in thread What's the best Perl CMS? by cosmicperl

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.