Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

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: Re:Spilling the beans (Score 1) 799

by tc (#21511467) Attached to: How to Deal With Stolen Code?
If he's a jerk, you don't want to work for him anyway. Best to find that out sooner rather than later.

Being sloppy with licensing is a good way to expose your company to legal risk, so you need to be straightforward with the facts to your management and get this cleared up. Talking to the lead in question is a good first step. Perhaps permission had been properly obtained, in which case it should be documented as such (e.g. in comments), otherwise the original author needs to be contacted. The lead needs to take responsibility here - that's why he's a lead.

Documenting where the code came from (assuming it's legit) is more than just good legal practice. It's also good engineering practice. If there are bugs in that area, a future maintainer can go back to that forum to report them, or look for solutions, for example.

A good lead should also know better than to play lawyer, but everyone has a bad day, and most people are basically decent and act in good faith. Start the conversation assuming that nobody had bad intentions and it should go fine.

According to the latest official figures, 43% of all statistics are totally worthless.