Re: Perl 6: Protecting Intellectual Property for Commercial Code

Hi James, On Mon, 23 Oct 2017 07:19:34 -0700 James Ellis Osborne III wrote: > Is compilation to bytecode still a todo feature? I managed to get a > solution supporting compilation, serial-based locking, & license expiration > delivered in Python last month for the nuclear

Re: Perl 6: Protecting Intellectual Property for Commercial Code

Frankly, if you're worried about this sort of thing, you have too much faith in "secret sauces", and not enough in understanding situations thoroughly. Code is trivial, implementation isn't. Back in the days of dBase II, I was a contractor for one ministry of the local government. They asked me

Re: who own my code?

On Mon, Oct 23, 2017 at 1:47 AM, Jan Ingvoldstad wrote: > 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

Re: who own my code?

I agree that this is really not the appropriate forum for this. Type a question like "if I write the same code for several clients, who owns it?" into a search engine, and you'll get a plethora of links. In this case, I would say the fairest thing is to write the sharable portion once on your own

Re: Perl 6: Protecting Intellectual Property for Commercial Code

Hi Mark, On Sun, 22 Oct 2017 22:37:31 + Mark Devine wrote: > 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