Software teams: how the code got made

Teams that build for clients may find some code belongs to those clients. Ownership is worked through during scoping, and whether any client code can go in depends on your agreements and your counsel.

Customer names often show up in tickets, chat threads and logs. In the copy, people and companies are replaced with placeholders and account details are removed. You can also exclude any repository, tool or period.

A team can look first at its issue tracker and review history, because those show how decisions are made and defended. Source repositories can join later for each product, or stay out for good. Anything covered by a client agreement gets its own review before scope is considered.

However the scope starts, the copy is made the same way. License Your Data works only from what you approve, swaps names and identifiers for placeholders, and shows you a sample before anything goes out. Your originals stay in your systems the whole time.