That's fine, but be careful how you write those attachments, they are often written in such a way that they become additional restrictions and thus become non-open source. Also, I wouldn't reccomend using them as they are both removable by any third party that consumes your code (and thus are nearly useless) and they in essence make your project less compatible with other gplv3 projects.
On Thu, Dec 23, 2010 at 3:58 AM, LWC <[email protected]> wrote: > http://groups.google.com/group/google-code-hosting/browse_thread/thread/d90cbec5f86c88b7 > can't be bumped so I had to continue it here (which isn't too bad as > it started to get off-topic anyway). > > As of 2010, Google allows specifying custom licenses (as long as > they're OSI-approved). So can projects finally use GPLv3 with > exceptions without fearing you'd remove such projects? Keep strongly > in mind that exceptions are a closed list anyway. > > Exceptions are a huge benefit of GPLv3 and can be as trivial as "this > license is supplemented by Section 7's terms b) and c)". > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- Open Source Programs Manager, Google Inc. Google's Open Source and Developer programs can be found at http://code.google.com Personal Site and Weblog: http://dibona.com -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
