Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I do agree, forcing clearness from the beginning always pays.

If the business model does not allow for a full sell of the software (as suggested by someone, but it implies higher up-front costs for the buyer company) and doesn't fall in the Open Source "support" model, one can sell it on a time based license, making it clear in the contract and including also clear schedules for:

  • expected renewal of the license;
  • end of service if a new licence is not agreed in time (which should be a fair amount of time after the expiration of the first bullet).

In this case, I'd encapsulate some central functionality inside a XS module, together with the limiting code.

The OP should also consider how long all this should go on before they acquire the right to use the software without limitations. There are softwares (like a popular GSM planning tool I once used) that are basically "rented" for limited times, but this timed scheme could just be used to divide the price that makes *the OP* happy in chunks that make *the customer* happy.

Flavio
perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Don't fool yourself.

In reply to Re^2: Hiding source code (in a country with no laws) by polettix
in thread Hiding source code (in a country with no laws) by diego_de_lima

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others admiring the Monastery: (6)
As of 2024-03-28 19:54 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found