A
recent case out of Idaho in the USA (Just Med Inc. v. Byce) wonderfully
demonstrates all the complexities that may arise when family relationships
intermingle with business and intellectual property law.
The
ugly facts are as follows:
Two
brothers-in-law had an idea to improve artificial larynx technology. After the usual experimentation they
obtained a patent for their improvement.
The
project was derailed by the death of one of the brother's wives, but was revived
a few years later.
A
corporation was formed with both brothers having a seat on the Board of
Directors together. Shares were split 1/3 for one brother and 2/3 for the other
and his wife.
Brother
1 and an employee (paid with stock) did most of the work on the technology. The
employee eventually left and Brother 2 became actively involved in the project,
reworking the source code. As with the
former employee, Brother 2 was compensated with stock. Brother 2 eventually quit his regular job to
work full-time on the software. During
the trial he stated that he had redone the software almost from scratch.
As
happens from time to time, Brother 2 eventually became disgruntled and
undertook a series of actions for which he was ultimately held
accountable. The first was to change
the copyright notice on the source code to show himself as the copyright owner
instead of the company. He also asked
Brother 1 for a cash salary, which Brother 1 agreed to. Brother 1 sent Brother 2 salary cheques for
a period of time but these were never cashed.
The
straw that broke the camel's back occurred in the spring of 2005 when the
company was negotiating a merger or buyout on very favourable terms. The night before Brother 1 was to
demonstrate the product to some of the interested parties, Brother 2 deleted
the most current (and bug-free) copy of the source code from the company's
computers. Needless to say, the
demonstration went poorly and the merger/buyout possibility evaporated.
The
company ultimately sued Brother 2 and Brother 2 raised, as a defence, the claim
that he was the sole author and owner of the computer software. He alleged that his relationship with the
company was that of an independent contractor as opposed to an employee.
This
distinction is important because software produced by employees in the course
of their employment is, in the absence of an agreement to the contrary,
property of the employer company. However, software developed by an independent contractor in the course
of their services is property of the independent contractor in the absence of
an agreement to the contrary.
The
Court ultimately concluded that Brother 2 was an employee of the company and
that the software belonged to the company and not Brother 2. The Court further held that Brother 2 was
liable for various other unsavoury actions (see above) and the end result was a
$41,000 judgment against him, not including punitive damages - which have yet
to be assessed.
The
motto of the story is this:
Document the relationships between individual programmers and an employer company - i.e., whether they are employees or independent contractors, and make sure that the agreement, whatever its form, contains provisions relating to ownership of intellectual property. The second general rule is that you should not go into business with your in-laws.
Recent Comments