Re: who own my code?

[Jan Ingvoldstad]

On Sun, Oct 22, 2017 at 10:32 PM, Brandon Allbery  wrote:
> This is still best discussed elsewhere... isn't there a stackexchange for
> this kind of stuff?

Ah, Stack Exchange, the quality site where the _first_ answer is the
most significant.

Anything else is better than asking people to go there for help.


-- 
Jan

Perl 6: Protecting Intellectual Property for Commercial Code

[Mark Devine]

Perl 6 Users,

[[ Bouncing off Re: who own my code? ]]

This is the first of several possible spin-off questions, but here goes…

Perl 6 has its public ecosystem, which will drive growth and adoption.  Then 
there’s the commercial side, which would also drive the language from another 
important angle.  I believe in a balance of public sharing and private 
enterprise.

I am interested in packaging some of my long-term Perl 6 
projects/scripts/apps/frameworks into some kind of relocatable object form 
(binary) that cannot be easily altered or trivially reverse engineered.  Put 
another way, I sometimes would prefer not to sell source code to my customers, 
but rather some form of compiled package that can’t easily be diddled by a 
SysAdmin.  If I create code for a particular commercial domain over years, then 
I want to get compensated for it and not have it be diluted with copy-cats one 
week after I release it.  Certainly some of the generic libraries that I create 
in the future can be modularized for the Perl 6 ecosystem and I’ll push those 
eventually, but the really specialized domain-specific code that fills a 
commercial void & that I will commit years to maintaining, I’d like to offer a 
commercial license, key-protect, sell subscriptions, etc.

Again, I’m very interested in contributing to the ecosystem when possible.  I 
still need to grow past baby/teenager Perl 6, and I’ll get there soon.  But 
after creating something targeted only for customer purchase/subscription, what 
tools are available in the Perl 6 toolbox?  I saw something for the Java 
back-end (to .jar), but not much else.

Is there a Perl 6 roadmap that might mention compiling Perl 6 modules/scripts 
into something atomic, binary, & relocatable?  Or preferably the capability to 
compile only specific Perl 6 modules, requiring an existing Perl 6 on the 
target host?

Thanks,

Mark

From: Brandon Allbery [mailto:allber...@gmail.com]
Sent: Sunday, October 22, 2017 16:33
To: vijayvithal jahagirdar 
Cc: ToddAndMargo ; perl6-users 
Subject: Re: who own my code?

This is still best discussed elsewhere... isn't there a stackexchange for this 
kind of stuff?

On Sun, Oct 22, 2017 at 4:24 PM, vijayvithal jahagirdar 
mailto:jahagirdar...@gmail.com>> wrote:
Now If I implement this for one customer does the code becomes his IP and I 
cannot implement it for another?

Default is owned by who you are working for. If you want something else, you 
can negotiate it; you want to be clear about it, and for something relatively 
low level like this it should not be a problem in practice. That said, the part 
that requires this is also likely the least portable part: unless they're all 
using the same framework, it's the glue to their site framework that is (a) 
more difficult (b) more likely to be different between sites.

--
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com 
 ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

Re: who own my code?

[Brandon Allbery]

This is still best discussed elsewhere... isn't there a stackexchange for
this kind of stuff?

On Sun, Oct 22, 2017 at 4:24 PM, vijayvithal jahagirdar <
jahagirdar...@gmail.com> wrote:

> Now If I implement this for one customer does the code becomes his IP and
> I cannot implement it for another?
>

Default is owned by who you are working for. If you want something else,
you can negotiate it; you want to be clear about it, and for something
relatively low level like this it should not be a problem in practice. That
said, the part that requires this is also likely the least portable part:
unless they're all using the same framework, it's the glue to their site
framework that is (a) more difficult (b) more likely to be different
between sites.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

Re: who own my code?

[vijayvithal jahagirdar]

I had a similar dilemma, Recently multiple customers asked for the same
feature, say add "login with google" in their old CGI.pm based website.

Now If I implement this for one customer does the code becomes his IP and I
cannot implement it for another?

Should I retype the same hundred lines for each customer or can I
encapsulate the code in a library and reuse the library across customers?

Even if I decide to retype it for all customers, The first implementation
would take longer as I was also understanding the technology at the same
time and subsequent implementation would be faster. So the first client is
effectively subsidizing the subsequent clients

Regards
Vijay

On Sun, Oct 22, 2017 at 12:35 AM, Brandon Allbery 
wrote:

> On Sat, Oct 21, 2017 at 5:56 AM, ToddAndMargo 
> wrote:
>
>> On Sat, Oct 21, 2017 at 12:57 AM, ToddAndMargo >>> > wrote:
 On 10/21/2017 12:40 AM, ToddAndMargo wrote:

 If I write a program for a customer who pays my labor to
 write it, who own the program?  Me or the customer?


 I am a private contractor.  What they payed me for fixing a/the
 problem.  They don't care how.  I was wondering if they owned
 any of the code I wrote to fix the problem.  The customer did
 not specifically ask me to write anything.


>> On 10/21/2017 01:07 AM, Brent Laabs wrote:
>>
>>> This depends on the contract you signed with the customer, and laws in
>>> your local jurisdiction.  As such, it's probably a question more
>>> appropriate to ask a lawyer than this list.
>>>
>>>
>> There is no contract involved.  The customer wants a problem fixed.
>> He does not want to know how.  And he is not commissioning me for
>> any software.  Just a fix.
>>
>
> My working assumption in this case is that for fixing/patching existing
> software, any code is subject to the original copyright and ownership;
> because I am working as an agent for the customer, new stuff is owned by
> the customer unless specified otherwise.
>
> BUT.
>
> If this situation comes up, you need to be talking to the *customer* about
> it. It doesn't necessarily need to be a formal contract, but the final
> decision should be in writing and you and the customer should both have
> signed copies of it in case questions come up in the future.
>
> --
> brandon s allbery kf8nh   sine nomine
> associates
> allber...@gmail.com
> ballb...@sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad
> http://sinenomine.net
>



-- 
https://www.facebook.com/vijayvithal.jahagirdar
https://twitter.com/jahagirdar_vs
http://democracies-janitor.blogspot.in/