23

Someone I know asked me for a favour. They made an agreement with a software firm for some custom software for basically inventory on a web interface, generic DB+webserver. They need me to do updates to it as a favour.

It's handoff time. The guys are giving him some trouble. I let them know if I need to do maintainence and whatnot, I need the source code. The guys are saying no. I recommended we use a licence that basically says "Buyer can modify the software and source code, but not distrobute it. Creator can distrobute the software and whatever they want".

I've looked around, and I saw recommendations for :

  • source code escrow
  • internal-use license
  • Modified Source Code License
  • custom Restricted Source Code License
  • internal modification only licence

anyone have recommendations of specific licences?

you are viewing a single comment's thread
view the rest of the comments
[-] litchralee@sh.itjust.works 5 points 6 days ago* (last edited 6 days ago)

I'm not sure I'm understanding the situation. You (Skullgrid; SG) were asked by an acquaintance (ACQ) to help work on a software package that ACQ would deliver to a software firm (SWF). So far, these are the relations that I see:

  • SG is doing a favor for ACQ
  • ACQ has a contract with SWF

Now at the "handoff time", which I presume is when SWF accepts the software as complete and delivered, SWF is complaining about how the software package will be maintained.

If I understand all of that correctly, why does SWF's complaints involve you? You do not have a relationship to SWF. And SWF (correctly) will not let a third-party have source-code access to software that SWF paid for, unless you (SG) are working as a contractor under ACQ.

The real question is how ACQ is handling these concerns: ACQ should demand that SWF negotiate a maintenance contract, one which allows ACQ to use any contractor of their choice (which could include SG).

The idea that SG -- someone with no relationship to SWF -- can use a software license to keep source-code access in order to do future maintenance, that idea is likely dead-on-arrival: SWF owns the software upon delivery, in full. Unless the contractual agreement between SWF and ACQ allows for ACQ to retain a license, ACQ cannot then extend a personal license to SG.

A maintenance contract, however, would grant such a license to ACQ. And if such contract allows for subcontractors to access the source code, then formalizing SG as an unpaid contractor would be a way forward.

[-] Skullgrid@lemmy.world 4 points 6 days ago* (last edited 6 days ago)

It's actually ACQ that's complaining about the maintainence. They want the project to be finished, and if they need some minor changes, for me to get involved. Probably due to the cost of monthly payments (speculation).

A maintenance contract, however, would grant such a license to ACQ. And if such contract allows for subcontractors to access the source code, then formalizing SG as an unpaid contractor would be a way forward.

Do you know where I can find an example of this kind of licence?

EDIT : Basically, ACQ wants changes after delivery date, and I need source code to make the changes and deploy them to wherever. We need a licence that says "ACQ and SG will use the source code only to make changes for their system/deploy and not sell it, SWF keeps all their rights and do whatever they want with the code"

EDIT2 : I went for a slightly modified Polyform internal use licence, what do you think? https://polyformproject.org/licenses/internal-use/1.0.0

[-] ulterno@programming.dev 3 points 5 days ago

There's ambiguity in the above conversation.

  1. The original post tells me that SWF has made the software and is giving it to ACQ; ACQ is asking SG for modification.

  2. @litchralee@sh.itjust.works seems to understand it this way: ACQ has made the software and is giving it to SWF and wants SG to do further modifications.

  3. The comment that I am replying to, won't make @litchralee@sh.itjust.works (who is assuming [2.]) realise [1.].

[-] Skullgrid@lemmy.world 2 points 5 days ago
  1. is wrong. 1) is correct.
[-] litchralee@sh.itjust.works 0 points 5 days ago

Intriguing. Upon rereading, that is also a plausible interpretation. But I think the issue still stands, but in reverse: if the software is produced by SWF, is licensed to ACQ for use (but not modification), then there will be a need for ACQ (not SG) to negotiate a source-code license with SWF.

If OP's question is now about what sort of license terms would be workable, that's entirely up to SWF. They would be within their rights to not even answer the phone, once they've completed their delivery per whatever contract they have worth ACQ.

[-] Skullgrid@lemmy.world 2 points 5 days ago

is licensed to ACQ for use (but not modification), then there will be a need for ACQ (not SG) to negotiate a source-code license with SWF.

yes, the negociation is being done by ACQ. I am giving assistance explaining to ACQ how what they want can be achieved. I am not certain on the specifics on which licence to recommend, so I am coming to the wise people of this community to see what they might know that I am missing. As in "here's a licence I used/saw that could help"

load more comments (10 replies)
load more comments (10 replies)
this post was submitted on 31 May 2026
23 points (96.0% liked)

Programming

27160 readers
702 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS