<br>The original question was "is anything we are doing patentable?" <br><br>I'm no lawyer -- thank God -- but beyond the source code there seems to be all kinds of things that can be patentable, such as design patents having to do with the interface and utility patents having to do with the way the site is used. <br>
<br>I don't know if building with open source software prohibits someone from seeking either type of patent, but neither patent would involve patenting the underlying code. <br><br>I agree telling the client to find a lawyer is the soundest advice.<br>
<br>Sam<br><br><br><br><div class="gmail_quote">On Fri, Dec 12, 2008 at 2:35 PM, Larry Garfield <span dir="ltr"><<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Jokes aside, the question of whether one can patent something under an open source license is still undecided by the courts. GPLv3, the Apache 2 license, and others include explicit language forbidding the enforcement of patents you hold on people using code you've released under those licenses because the threat of software patents has been made before, and software patents are, to be blunt, public enemy #1 for software development in general and open source development in particular. There's considerable debate as to whether software/business method patents can or should be issued in the first place, and open source developers are nearly universal in their opposition to them.<br>
<br>
Assuming you're in the US, the question becomes even harder. Given what our patent office has approved in recent years, I've no doubt that you could get them to give you a patent on something you do with Drupal if you have the right patent attorney word it vaguely enough, even if you didn't write it. That doesn't make it an appropriate use of the patent system, and given that Drupal is under the GPL and 99% of the code on whatever site you're building was written by someone else I would argue (speaking for myself here) that even trying to do so is unethical.<br>
<br>
It would probably also get you shunned by any open source project that heard of it, because "tainting" open source code with corporate patents is a very real and legitimate fear. People wouldn't be able to trust that you/your client aren't trying to work a patented method into Drupal, release it, then cry "ah ha, now I can force everyone who uses Drupal 7 to pay me $699 per install!"<br>
<br>
Also relevant is that Drupal is under GPLv2+, meaning that anything in Drupal core or in Drupal CVS could be released under GPLv3, which does have a patent protection clause. What happens if you release something under GPLv2 that has a patent restriction on it and that code is then legally incorporated into a GPLv3 codebase, I have no idea. The best approach is to avoid the patent and not find out.<br>
<br>
>From a strictly legal standpoint, only an actual lawyer can answer that question. From a business ethics standpoint, tell your client "no, what we're doing is open source, it's all shared." If you have a lawyer who recommends otherwise, you need to get yourself a new lawyer because that one 1) doesn't understand open source and 2) is behaving unethically. If your client insists on trying to find something to patent anyway, you get yourself a new client for the same reason.<br>
<font color="#888888"><br>
--Larry Garfield<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Fri, 12 Dec 2008 11:42:34 -0700, "Brett Evanson" <<a href="mailto:brettev@gmail.com">brettev@gmail.com</a>> wrote:<br>
> I'm working with a client that has asked me this question: "Is<br>
> anything we are doing patentable?".<br>
><br>
> What sort of things are patentable within open source development?<br>
> What sort of issues are there with specific licenses? Where do I even<br>
> go to start here?<br>
><br>
> Any help is much appreciated.<br>
><br>
> --<br>
> Brett Evanson<br>
> <a href="mailto:brettev@gmail.com">brettev@gmail.com</a><br>
> _______________________________________________<br>
> consulting mailing list<br>
> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
> <a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br>
_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br>