Slashdot Mirror

← Back to Stories (view on slashdot.org)

Source Code Escrow

Posted by michael on from the my-precious dept.

Makarand writes "According to this article in The Economic Times (India) Software companies in India are embracing the trend where source code for the software being bought or sold is kept safe with an escrow agent with carefully drafted agreements. This allows the buyer to get hold of the source code in cases where software was licensed from a start-up which has now folded or a breach of contract regarding the maintenance services that were agreed upon can be proven. The source code is automatically released upon the occurrence of any of the events mentioned in the escrow agreement and the buyer will be able to study the source code and continue to provide support services for the software bought without relying on the employees of the software supplier."

2 of 182 comments (clear)

  1. nothing to see here..... move on by frovingslosh · · Score: 1, Redundant
    Nothing new here. And not a very viable concept. The company who insists the code be put in escro will get an assurance that something has been put in escro, but if the relationship has so little trust between parties that a third party needs to be brought in, then the developer may very well not put a full copy of everything in escro. If the company wanting the assurance doesn't find out until the developer no longer exists, they have little recourse. And if they find out before that, then the developer's worst fears are realized and justified.

    Unless an escro company is in the loop enough to do actual releases, then there will not be a viable system that confirms what is in escro is what the client needs.

    --
    I'm an American. I love this country and the freedoms that we used to have.
  2. The view that seems cynical is often the reality. by Futurepower(R) · · Score: 0, Redundant


    LOL.

    The view that seems cynical is often the reality. Quoting from the parent post, about how programming is often managed:

    "First a business manager makes the primary decision about which technology to use. Not only does the manager have no knowledge of the technologies, this decision often contradicts the advice if the technical advisors. Then a project manager cuts the work into pieces and assigns them to porgrammers. Again, the knowledge of what pieces ahould be grouped for one programmer is ignored. And the assignment starts with the manager's favorite programmer taking the interesting pieces, regardless of the programmer's skill level or suitability. Then the programmers do their thing, which usually involves getting high on caffeine and using the mystical energy to conduct the thoughts of higher powers into electronic form."