<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Verdana">Good advice from Larry and Dave, imho, tho ianal
either.<br>
<br>
What I know from US law: Any contract that involves transfer of
copyright requires *signed* documents saying so. Everything else can
pretty much go via email and whether the check clears. ;)<br>
<br>
The Graphic Artists' Guild advises that you retain copyright on any
custom work you do, and license it to the client -- in perpetuity even,
but retain the copyright. Make it clear you reserve the right to use
the work you do elsewhere, and how -- e.g., for promotional purposes
(like your portfolio). I always provide a link to the GPL regarding the
Drupal code, and make it clear to them that they will own it (which I
feel is a selling point of FOSS, as proprietary code they typically do
not get to own at all).<br>
<br>
And be clear that THIS IS NOT A WORK FOR HIRE. That can get into sticky
issues, at least in the US. The distinction between employee and
consultant can ride on that line.<br>
<br>
In the end, I go with the conventional wisdom: It depends on the
persons involved. If you can trust each other, the agreement can be
over a handshake. If you don't trust each other, then you could write a
contract the size of the phone book and you still won't be secure.<br>
<br>
Hope this helps! Best of luck with the project!<br>
<br>
Laura<br>
<br>
</font><br>
Fabio Varesano wrote:
<blockquote cite="mid43A4919C.6090407@varesano.net" type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everybody.
I'm going to start a drupal consulting project and I'm currently
writing an agreement between me and my client.
This is my first big drupal based consulting project.
I'm not really experienced on writing agreements becouse
I worked only as employeed on a web agency.
This is my first free-lace consulting agreement.
Every kind of advices or examples on this are really appreciated.
In particular: do you usally give some EULA (End User Licence Agreement)?
And if I want to share the developed modules or features
with the community (releasing as GPL) what do I have to do?
Thanks a lot
Cheers.
Fabio Varesano Italy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a>
iD8DBQFDpJGc0BeJLLhkg9ERArvKAKCYNGbSuFHnoIlGr1iONogBRp4QKgCfXQEz
vbwnvlF2+c3LvttHUNeucgo=
=kbx2
-----END PGP SIGNATURE-----
_______________________________________________
consulting mailing list
<a class="moz-txt-link-abbreviated" href="mailto:consulting@drupal.org">consulting@drupal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a>
</pre>
</blockquote>
</body>
</html>