Guillaume,

I never had to take a decision as you do. When I was working as a freelancer I wrote some code, but interestingly the company I did for is not selling the sole solution but ather a full service, so they owe the code, the client never sees it and wehen the client resigns from the service and support contract, ne will have nothing left. Actually, that gave me bad taste in my mouth.

But as others said before, regarding licenses consult a lawyer.

Regarding of what you could give back top the community, I'd think it would be rather usefull to get one or the other module you wrote for your app. It could be that there is one such thing whrer you'd say, that it would be no risk to your own business to publish that module to CPAN. But beware that the time you spend for supporting such a module and so on will take time, which you might need or at least better should invest into your business.

So, to make my point on it: DON'T do anything except your business now. It will take all your time and you'll have enough time later to give back something to the community.

Ok, I should have said that you help the community a lot as well by donating to perlmonks.org from your business profits. {grin}

Have a nice day
All decision is left to your taste

In reply to Re: To Open Or Not To Open by little
in thread To Open Or Not To Open by guillaume

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.