So for sure you own all of the code *prior* to your modifications. As Liz has stated, unless you discuss things with the customer and *he chooses to relinquish his rights in writing*, then your modifications belong to him.
You can't hurt to start a discussion. That would be the best first step. On Tue, May 13, 2025 at 6:37 PM ToddAndMargo via perl6-users < perl6-us...@perl.org> wrote: > On 5/13/25 3:46 AM, Elizabeth Mattijsen wrote: > > I'd say, unless you made prior arrangements with the client specifically > stating that you own the copyright on the programming work you did, the > client owns the rights to the code. > > Oh it is specific to his installation. And the specific > code I wrote him, was a modification of my own code > that I indeed owned myself. > > And he had no idea I was coding or the specifics of > anything else I was doing. His instructions to me > were to get everything back working again, > as fast as possible. > > I conquered. It was actually a pretty fun task > too. I has a lot of separate pieces that all had > to get along with each other as a system. > > So I guess he also owns a lot of bash scripts too. > > If I were to reuse the code, I will have to > substantially modify it to someone else's needs. > > The major parts of the code I did not charge for > were having to come up with my own IO modules > to work around Raku's corked IO command to handle > UNC paths. That took me tons of time to figure > out what was wrong and how to cope with it. > > I though of writing my own API IO calls, but settled > on calling power shell from my modules as it > was faster. The programming part was suppose to take > less than eight hours and took me four days. It took > me a long time to figure out that Raku's IO calls > were trash when used with UNC paths. Things > just didn't work as expected and I was tearing > my hair out until I realized Raku was at fault. > > Don't suppose Raku is ever going to fix that. > You have to use UNC paths for network drives > when calling programs from the Windows Server > 2025 task scheduler. > > Thank you for the help, > -T > > >
