56
peaam
8y

"A client wants to buy 'the source', can we give him the source but not the code. We don't want him copying."

Comments
  • 5
    give the link and ownership to source, but no read and write rights
  • 2
    @achu where else has this been done?
  • 1
    @enchance don't know, but I call it 'fake sense of ownership'
  • 1
    Why do people even try?
  • 3
    Obfuscate the shit out of it, and only give compiled code (if applies, like bytecode or hex files)
  • 2
    @apex Doesn't compiled code not qualify as "the source?"
  • 4
    Tell them they can buy the company to get the source, or license it to them at an obscene cost along with very strict licensing restrictions. Buy never, ever, ever give away source code to clients.

    And before you even considering licensing, make sure you have stored a copy with an independent code repository so you can prove original authorship of things go bad
  • 1
    @AshMountDigger just curious here, why should you never give a client the source code? I don't have a job in the industry yet and I'm curious.
  • 3
    @joehop67 because at that point you no longer have control of your code, nor can you control very well what they do with that code. That's fine for open source, but if your goal is making money, it's a bad idea because you've lost control of your source of income. While the client may not have ill intentions, you can't trust that when your livelihood is on the line.
  • 0
    @enchance But he doesn't know 😋.

    PD: I'm a lot of days late, but I had to, hahaha
  • 0
    @achu did you just predict NFTs? damn...
Add Comment