Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Be honest, and you won't have a problem. (Score 3, Insightful) 447

by Templar (#31380572) Attached to: Why Paying For Code Doesn't Mean You Own It

It depends upon your local laws and your contract. In the U.S., the default laws tend to vary by state. The last time I checked with my attorney, he told me that here in NY, all work is considered to be work-for-hire unless specified in writing. This means that the source code is automatically the property of the client, unless I get a contract stating otherwise. Which I do sometimes, but not that often.

Things get stickier if you use other people's libraries or even open source software within your project.

I've found that it's easiest to avoid problems if you simply discuss it with your client beforehand, and be as transparent as possible in your methods and expectations.

When the weight of the paperwork equals the weight of the plane, the plane will fly. -- Donald Douglas

Working...