Creative Commons Launches Today
Luke Francl writes "On December 16, the Creative Commons is unveiling their commons licenses. Well, their website is up a little early Creative Commons provides an easy way for creators to give away some of their rights under copyright law without wading through hundreds of pages debating the merits of the GPL verus the OPL versus the FDL verus the public domain ad infinitum. By answering three simple questions, the Creative Commons web application selects an appropriate license for you. You can give it a try at the Choose a License page. They've also got a list of all the Creative Commons licenses." Peter Wayner has released his book Free For All under the license.
Anyone noticed that the Free For All book doesn't specify which Creative Commons license it's been released under?
Its pretty good idea. Easy yo use, and tells you why it chose that license as well as gives an easy to understand description of the license as well as the full detailed license text.
Again well thought out idea that will hopefully help many people use more open licenses now that they can easily find which one to use.
We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
Because, after all they don't want to impinge on /.'s territory.
reading through GNU and GNU FDL "license text" gives me a warm and fuzzy feeling :)
Consensus is good, but informed dictatorship is better
Comment removed based on user account deletion
It's interesting -- definitely a way to simplify the daunting task of picking a license. I recently began to roll my first SourceForge project and can tell you the license-selection step is very intimidating.
;)
Then again, I don't have the GPL stitched on my pillowcase like some of you.
-- jimmycarter
the mod says 'flamebait' but my brain says 'spot-on'. Linux nerds have singlehandedly turned the geek community, once thriving with creativity and individuality, into a sea of obnoxious RMS-gamahuching dweebs -- who think they're cool .
i liked it better before they came around.
Well, whats the purpose of having more then one open source liscense if they all are basically the same? Why not just take the best parts of them all and include them in the next revision of the most popular one?
"There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
Would the results of that page be called a
Legalize-O-Matic ?
Sledge-O-Matic, not just for spraying audiences anymore!!
All well and good, but what does the FSF think of all this? Their opinion matters rather more to me than some "Creative Commons" upstart.
I would also note that depending on the choices you make, you can easily end up with:
(i) a non-Open-Source compatible, non-DFSG-Free license, but one more akin to "source-available proprietary" -"Shared Source" or "Community Source" in Micro$oft/$un newspeak
or
(ii) a license that is Open Source, but not GPL compatible (e.g. recreates the old-style-BSD license, or prohibits commercial, non-proprietary use, which is permitted by the GPL).
This really muddies the waters further, not less, by blurring the distinction between Open and pseudo-open source.
Not really surprising given the O'Reilly involvement - they're known MS-apologists.
It's not about religion
Nor is it a matter of ethics.
It's not about love, caring, thoughtfulness, kindness, compassion, vision, hope, intellect, wisdom, or sharing.
It's about feeding my kids.
And I'm sorry, and I'm sure I'll get flamed for this for going against typical Slashdot Zealout creedo, but the license that someone uses for their drawings or computer code or music tracks doesn't mean jack in the long run.
So I'll continue to get paid for the hard work I do and I'll continue to raise my kids the way they should be, and give them whatever they need when they need it.
I'm a father for Christ's sake, not the Pope.
hmmm... I wanted the
'you can do anything you like with this so long as you don't vote for or support George W Bush.'
Looks like I'll have to keep the formula for philosophers stone to my self for a while.
thank God the internet isn't a human right.
Creative Commons provides an easy way for creators to give away some of their rights under copyright law without wading through hundreds of pages...
This stuff doesn't strike me as being particularly lawyerproof.
Here's hoping I'm wrong.
Is it fascism yet?
Although this seems like a fine idea in theory, I am having difficulty imagining many situations where people would use it, which would be useful to others.
It is not going to replace copyright for music or books (I realise these aren't mentioned, I'm just trying to think of some possible use - theirs are pretty crap and unlikely) for example - the industry wouldn't touch it for obvious reasons.
If it takes off at all, it would be for the benefit of amateurs only, but then, what's the point?
I'm not very good at making decisions... Or am I?
ok.
just let me figure out how to show my hand raised by using text.
They're similar in spirit, but the GPL is more specifically tailored to computer code.
feeding your kids to what?
the big nasty do down the road.
I don't believe some of you non religious, unethical, loveless non caring, thoughtless , horrible, evil, blinded, hopeless, stupid, unknowlageable , selfish people.
thank God the internet isn't a human right.
ShareAlike license -- the one you get if you click just the "sharealike" option when selecting licenses.
And if it is not, what was the need to create another license with the same conditions?
Unlike the GNU GPL, Creative Commons licenses are not be designed for software, but rather for other kinds of creative works: websites, scholarship, music, film, photography, literature, courseware, etc.
There is a pretty good FAQ too.
Avantslash - View Slashdot cleanly on your mobile phone.
The ShareAlike License looks like it requires that any modifications be distributed under the ShareAlike license (and no other). The GPL only requires that the key provisions of the GPL be followed. If you want to distribute your derivative work under a different (but compatible) license, that is acceptable under the GPL but not under the ShareAlike License. Without reading the fine print, that requirement may actually make the ShareAlike license incompatible with the GPL (as it puts additional restrictions).
.. your hand raises you !!!
You haven't been reading what people have been saying about this have you? There is nothing stopping them from using binary in XML. If they don't then great, yes it wouild be open, but if they do use binary you can forget it.
What we see depends on mainly what we look for. -- John Lubbock Now search for that bug slave!
So that it is GPL-incompatible, or so that people mistake Creative Commons licenses with the "no derivates", "requires attribution", or "no commercial use" clauses for real open-source.
Hint: Those three can make your project more like MS shared source or Sun community source than real open source.
MS would even be able to say "look, we're participating in the Creative Commons" while simultaneously NOT really being Open Source or Free Software AT ALL.
I wonder however, if people may shy away from this great resource simply because it lacks the exposure and "clout" of the GPL? That would truly be a unfortunate outcome.
Ñ'
That sounds like a nice idea at first sight.
But i think the trouble is that this selection system will ultimately invite people not to think of the differences between the licences.
Fine, it's nice to select a license quickly, but people won't be able to understand why choose this license instead of another one, or the issues related to each type of licences....
People will prefer this selection method instead of balancing pros & cons (i admit it can sometimes be a real pain if you release a lot of projects), thus losing track of the differences between all the licences...
Tsuyoikoto ha taisetsu da ne, dakedo namida mo hitsuyousa (Strength is an important thing, but tears too are necessary)
OK, so this web site gives licenses for the US, in english.
Are the licenses applicable outside the US?
If so, wouldn't it be nice to provide the license text in other languages (at least the main ones: French, Spanish, Chinese, Japanese, etc.)?
JB.
Is binary in XML up to spec? I've never heard of such a thing. They said they're gonna be 100% compliant with the XML specs.
Makes the Sun Community Source License seem simple.
Pathman, Free (as in GPL) 3D Pac Man
I agree. I don't know why this licence crap comes up again and again on the front page. Boring & irrelevant IMHO in the scheme of life.
Sun StarOffice and OpenOffice go one better: They store documents as Zipped XML ! All the advantages of MS Office 11, plus compression! Since Last Year!
Wow!
Clueless. Go learn to troll instead of flamebaiting.
AHKK. Please don't mod up this post. Every article has at least one post about OpenDK. This is a troll who is trying to attract people to his site/project.
Because of this, I don't see why they thought it necessary to create a new, almost identical license.
I'm a leaf on the wind. Watch how I soar.
MS is the FIRST Office suite vendor to store documents as XML
or really? besides, microsoft has the OPTION (read: not it's primary, default format)
openoffice has been xml for quite a while now, and I'm sure there are others as well.
oh yeah, why do you have me listed as a foe? hope I'm not raining on your parade.
sorry man, my bad.
Looking for Book Reviews? Check out Literary Escapism.
It doesn't matter. You can easily UUencode or base64 a properietary binary COM object (or anything else) into text form and shove it in a CDATA field.
I can't use this, I want to go big time and there's no checkbox for "Jealously guard your copyright by, bribing senators, buying laws, destroying civil liberties in your country, and harming the customers who support you,"
Religion is a gateway psychosis. -- Dave Foley
Still too much legalese for my liking. Just look at their Public Domain declaration. Give me a break.
I think no license is user-friendly if it can't be understood and bothered to be read by a 10-year old. Consider the fact that legally ANYONE SHOULD read and understand the license of every single piece of software they use and the usage agreement of every single website they visit that has one. In present time this is simply impossible.
This proliferation of licences will harm the adoption of Open Source / Free Software by commercial organizations. It's hard enough to persuade management that GPL'd software is safe to use, or to distinguish between LGPL and GPL. Now we have a dozen new licences which will need to be scrutinized by the legal department.
Is it just me, or was the world complicated enough without having another 8 different licenses to consider when you're publishing your work? I know the idea is that you forget that GPL, BSD and whatnot ever existed and rely exclusively on Creative Commons judgement about what should be in the license but it would have been nice to have been given a 'best fit' from the existing licenses in the wild. Also a quick run-down on the differences between the Creative Commons license and the best fit, and hints as to what they might mean in a courtroom or in corporate negotiations would be nice.
There's simply not enough information regarding the strengths and weaknesses of the given licenses, and how they compare to the incumbents, to make them compelling. And if they're not compelling then they're just another 8 licenses to try and pin the tail on when you're starting up a project.
One of the penalties for refusing to participate in politics is that you end up being governed by your inferiors - Plato
It's good to see that the Creative Commons people are encouraging authors to put works into the public domain, which is the simplest way to make something freely redistributable and the most liberal (as well as not having questions of how to interpret the wording in a particular licence).
Unfortunately, the Open Source Initiative refuse to certify public domain code as Open Source (they did in an earlier version of the Open Source definition, but not now, according to license-approval@opensource.org). So in a way this is another split between the Stallman / Lessig / FSF camp and the Eric Raymond / OSI camp, even though in theory they hold the same set of criteria for deciding what is free.
-- Ed Avis ed@membled.com
Abiword does it too
X(7): A program for managing terminal windows. See also screen(1).
That's the problem, the OpenSource world is all about everyone else. It almost doesn't matter how good your code is, if you aren't using a license I've heard of and understand then I'm not going to bother looking at/using your code.
Here's the simple answer:
In theory you can substitute public domain for the first option, but in reality this is very murky ... and you're probably better off just BSD/LGPL dual licensing.
Remeber you're trying to get technical people to use your product, we are coders, not lawyers.
ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
The GPL (and, I believe, the LGPL) requires you release the source code for any modified versions you distribute. ShareAlike does not.
Well, Its funny you mention that. I consider my self a master troll, and I'm actually thinking of starting a small school. Please post your thoughts on the matter.
In Soviet Russia, the software license chooses
unnh... a tunnel of light... and at the end, a Soviet Beowulf Cluster...
I really like the concept of the site. Picking a license is a very difficult part of releasing the source to a project, and the reason some of my personal projects are still closed source.
I would REALLY like to see something like this site, but slightly more involved, with a few more questions (with the description popup tips you can click on) where the end result is either a funky name like "Attribution-NoDerivs-NonCommercial License" or GPL or something like that if the answers you picked to the questions actually fit GPL. Having only the funky names for responses doesn't seem complete enough to me.
Morphing Software
The master immediately slapped the disciple upside his head.
"Master, why did you strike me?"
"We have no need for yet another free software license!"
The disciple was suddenly enlightened.
--
"Open source is good." - Steve Jobs
"Open source is evil." - Microsoft
And, knowing Microsoft, the binary blobs will probably be little-endian....
You know, the ones you've raised to believe that there is no such thing as good or evil, ethical behavior or savagery, production or theft, the power of the dollar or the power of the gun.
The best thing is that I can say is that I hope you inherit the world you're advocating.
Give your kids what they need? So your need trumps everything else? This sounds like pure Marxism: From each according to his ability, to each according to his need
Frankly, you shouldn't have bred.
I want to delete my account but Slashdot doesn't allow it.
Bush 1 others 4
Do you think XML is some magic pixie dust you can sprinkle on a format and make it all better, whereas binary formats are automatically complicated? XML is just another way of stating, it doesn't necessarily make formats any easier to reverse-engineer.
Wow!
Useless. Go slit your throat instead of wasting my air.
"On first glance -- brown hair, pale skin, and undergrad-style clothes -- Rich Baraniuk looks like an average guy. But look at his eyes, and you know you're in the presence of something rare. They're giant and brown and fairly glowing with the light of the millions of synapses firing at the same instant. "
Go Rich go, let those synapses fire away w/those big eyeballs while we all gag.
You can check it out by going to the home page http://www.ibiblio.org
You might find it interesting to see the licenses in action.
as soon as i saw the story, i went to the site and started on the merry path to licensing out some content (maybe some pictures or something)...
but the license i was most interested in, Attribution + Share Alike, seemed to present a recursion problem.
with software licenses this isn't such a big deal, because a big fat license and attribution file can be included (license.txt) and often is.
but with something like a picture, the attribution and/or copyright notice is not realistically going to be longer than a "normal" URL.
i send them a note about this, which i quote below. hopefully somebody has greater insight into this than i do, because to me it looks like you could end up doing a whole lotta work building your license.html pages on your website (mary in the example below) or you're more or less begging to be plagiarized.
the example:
i take a picture, you (joe) modify it, someone else (mary) modifies that, and it gets printed in a magazine. what's the credit? "foto by frost/joe/mary" or "foto by mary/joe/frost" or....?
this gets really complicated if, say, i provide a bland little picture and joe crops and enlarges it to make it interesting and then mary uses it in a collage that's really beautiful... wherein mary is really the primary author of her piece, and i am the author of the source of a component thereof. and what if mary has used fifty such pieces? soon there is more attribution than she can reasonably expect to print next to pictures of the collage (which she has, after all, been required to license)... do we then have an attribution link?
and in such a case, if all the original elements were licensed through creativecommons, would there be a way, on that website, to show all the attributions within one URL (with licenses)?
if i license something with "Attribution + Share Alike" that itself uses things licensed with "Attribution + Share Alike," i probably need to include those licenses' links and attributions within the creativecommons link to my page... at a very minimum.
This Like That - fun with words!
i allways figured that the GPL stated that any change to GPL licenced codehad to be released under GPL unless it for internal use only (as in not released to the open market). you can still charge money for your modefied code but you cant claim to be the creator of the original code, only the changes...
A lot of posters seem to be oblivious to the fact that people want to share things other than code. Things like art, literature and music. The GPL, BSD and other software licenses are a shoehorn fit at best and blatantly inappropriate in most cases when applied to these domains of intellectual property. Go read the GPL and see how many of the paragraphs deal exclusively with software terminology. Those licenses deal in terms of "source code", "machine code", etc. That's pretty easy to interpret for software, but what's "source code" in art? In music? Is sheet music the real source or should you be providing a fully instrumented MIDI file to work with as "source"? These new types of licenses are more appropriate for things that aren't software. This isn't a replacement for your precious GPL. It's, instead, an appropriate parallel for non-software instances.
The Glass is Too Big: My Take on Things
Please mod parent down. His comment doesn't deserve a +5. At best, it should be a +3.
:)
I have read the site, I have read the licenses, and they seem to me quite lawyerproof. They have been written by lawyers, after all.
Like many others, it seems this parent has just read the summary of the licenses, and not bothered to grok the legalese "source" code.
I fail to see how adding 12 new open source licenses to the pool makes things less complicated. It's surely just going to add to the confusion.
The dangerous part is that there is far more to those licenses than the brief questions, or the synopses would suggest. Anyone wanting to use them must make sure they read the full text and understand all of its implications.
Wouldn't you rather use a mature, tested and widely-known and understood license instead?
Yet another guy who hasn't bothered to read and understand what CC is about.
I am having difficulty imagining many situations where people would use it,
Anytime you have made some work, don't have a contract with a big professional distributor (which, believe it or not, is the majority of the cases) and don't have the skills to write a license yourself.
You know what the Net is supposed to be about, right? It is supposed to help exchange of information, ideas, works, etc. The CC licenses are here to help that.
Major corporations will continue to write their own licenses, of course.
It is not going to replace copyright for music or books
Obviously, you don't understand what copyright is.
If it takes off at all, it would be for the benefit of amateurs only, but then, what's the point?
And you got a +5 with such bullshit?
But i think the trouble is that this selection system will ultimately invite people not to think of the differences between the licences.
Oh yeah? How so? There's a page that summarizes very clearly the differences between the licenses. Besides, even the legalese is easy to read!
Here's yet another parent that doesn't belong to the +5 level.
from Creative Labs??
Then again, CL has not really been creative lately...
Re:Who will use this?
I will, for one, and many others already have.
Although this seems like a fine idea in theory, I am having difficulty imagining many situations where people would use it, which would be useful to others.
There is already a bunch of material licensed under their licenses, and numerous other efforts to achieve similar results under which a great deal of good music and prose is licensed. Clearly there are many others who are having little difficulty in finding these sorts of free licenses useful.
It is not going to replace copyright for music or books (I realise these aren't mentioned, I'm just trying to think of some possible use - theirs are pretty crap and unlikely) for example - the industry wouldn't touch it for obvious reasons.
It isn't "replacing copyright" (though drastic copyright reform eliminating the government monopoly entitlements it grants with a more balanced "sales tax as creator royalty" scheme would be highly desirable), it is creating a license that, similar to the BSD License, the FDL, and the GPL, will facilitate a growing commons of material all creative people can use and build upon.
Finally, who gives a fuck about the "industry" as such. Their purposes are already served, and have been so by a century of corrupt copyright legislation bought and paid for from our inexpensively purchased "representatives" in congress. The cultural squatters of New York, Nashville, and Hollywood, and the cartels they have formed, are the reason that the "vast cultural wasteland" of television and the lack of cultural depth in modern society have become so obvious, and such obvious truisms that they have become cliches.
These free licenses aren't intended to benefit the entrenched "industry" any more than the GPL is designed to Benefit the Sun Microsystems and Microsoft's of the world. It is intended to benefit ARTISTS and CREATIVE PEOPLE, not cultural squatters and an industry that has denigrated the art into a mere product of mass production, filtered down to the lowest common denominator.
If it takes off at all, it would be for the benefit of amateurs only, but then, what's the point?
First this is nonsense. One could have made the same inane (and in retrospect obviously incorrect) argument against the GPL, which has benefitted both amateurs (such as Linus Torvalds when he first began writing the Linux kernel) and professionals (such as IBM).
Likewise, the Creative Commons will empower amateurs (such as myself) and professionals. No, it won't empower Time Warner any more than the GPL empowers Microsoft, but it will empower Indy music and film makers (who are often professionals and not amateurs, though they often serve as a bridge in getting new and talented filmmakers noticed).
Second, every professional was at one time in their career an amateur. A great deal of amateur material is crap, but a great deal is also excellent. Having that material available as part of a commons, free to be distributed, improved upon, and incorporated into other, grander works is a very valuable thing to artists, to society, and to the health of our cultural heritage itself. No, it doesn't benefit Disney and Time-Warner, it benefits the tens of thousands of talented artists Disney, Time-Warner, and others of their ilk have traditionally trampled under their feet, and in addition it benefits the rest of us who enjoy and admire such works.
And that is very, very good thing, tripe and propoganda from the "industry" at its shills and astroturfers notwithstanding.
The Future of Human Evolution: Autonomy
I have rarely seen so many +5 comments that didn't deserve their rating.
Where did you read that this site gives licenses for the U.S.? The only text that is specifically dependant on the U.S. law is the Public Domain Dedication. No other text mentions the United States of America.
Of course, some might wonder what about other legal systems? Well, there's a FAQ!
Yes, it would be nice to have the licenses, more than translated, adapted to other countries and their legal systems. At least for France, it shouldn't be too hard; the GPL has been analyzed by French jurists, and they consider it is directly usable (once translated) in French courts. The CC licenses don't seem to outlandish to the GPL (yes, I have read them) so I think translating should be enough for France at least.
You feed your kids. What do I care what you do? I don't see anyone telling you that you have to use one of these licences.
I don't have kids and I can manage to both feed myself and my wife, cloth myself, keep a roof over my head and go on holiday twice a year. Thats with my day job. Then I come home and work on a large Open Source project, too. Are you saying that you're such a looser that you cant work and contribute to a charitable cause or Open Source project?
You suck. Looser.
To make matters worse, AT&T often wanted the BSD team to include features that would force all the BSD users to buy a newer, more expensive license from AT&T. In addition, license verification was never a quick or easy task. McKusick says, "We had a person whose fulltime job was to keep the AT&T licensing person happy." In the end, he concludes, "They paid us next to nothing and got a huge windfall."
HmmmmmmYou keep going until you die..."Me".
I read in alt.hackers.licenses that buried deep within the license code is a clause that activates on the 3rd Tuseday of every odd-numbered month that gives Creative Commons unlimited commercial rights to the work .. can anyone confirm this?
The text of this license is protected under the recursive public license.
It's refreshing to see people trying to make things simple for a change. The legal differences between different OS licenses are overwhelming at first.
Sure, as someone pointed out above, this may mean I may not have to investigate and think about the differences between existing licenses. Well, IMO, that would be a 'good thing'. I have other things to think about.
And imagine all those for who english is not their mother tongue. With this license, I would only have a few words to teach my francophone colleagues. Actually, come to think of it, I'm sure a lot of anglophones can't understand legalese either...
This would actually be my main critique of OS: so much of it is needlessly complicated.
Too many long licenses, short and/or inaccurate or no docs/installation notes, ideological camps all over the spectrum and so little plain speak.
Looking for blog software recently, I was unable to find something that I thought worked well that I could maintain (I guess I'll have to learn to use Perl). Sorting through all the different projects, I wished people would say "we started this slash port because we wanted something in our fave language"/"we think slash is a great idea, but has a poor architecture and would be easier to maintain written in an OO language".
For the most part, and on most OS projects, No such luck. Although this idea introduces even more licenses, it's still a step in the right direction: simplicity. Now, if we could make it that easy to find/compare OS software...
1) Are you virulently Open Source?
2) Do you want any large coporation to get their asses sued for using your code?
3) Are you hot?
Keep your packets off my GNU/Girlfriend!
a lot of picky criticisms here, most of which seem to miss the point in bizarrely obvious ways. it's not a new set of software licenses, it's not a position in the OSI/catfight, it's not even pretending to be a panacea or simplify anything that's happening already.
the varous open source software licenses have to deal with all the complexity of a medium where each product is compound, divisible, modifiable and copiable. that's why they're either very very short or very very long. For anything more restrictive than the MIT license's 'whatever, dude, but i made it', it gets complicated.
what cc are trying to do, like many others, is take the principles of the open source movement, and some of the lessons learned there, and apply them to the broader field of creative production. Unlike many others, they're trying to make it easy to use, without concealing the complexity of the subject, and I think they've pulled out exactly the right three questions to do that.
I get this kind of question all the time: i'm one part programmer and one part artist, most of my friends are wholly one or the other, and it's hard work trying to make sense of open source to writers, activists, people who just make things. The open part they tend to like, but the source part makes no sense at all. compile what?
Still, they eventually get this vague idea that someone else could take what they're doing, do something interesting with it and bring it back, and the light bulb goes off: their creative monologue will turn into a conversation, they'll gain ideas and confidence and get better at what they do. But how? And where to start? Go to GNU? I don't think so. Even opencontent.org gets all hair-shirt legal at you.
CC is friendly, supportive and prepared to put the money into lawyering things for the benefit of others. It would benefit from more historical and ideological context, a bit of cheering up and more clear recommendations to go with the questions, but I for one am grateful for a bit of potentially important work well done, even if I never use it because the GPL works fine for what I make.
Waiting...
I started using their license ideas on my web site a few weeks ago.
Pardon a small plug, but you can get my free web books (under a CC license) here.
-Mark
Ya, that's the ticket!
[ReidNews]
Interestingly, none of the possible combinations of choices on the Creative Commons page leads to an MIT, Apache, or BSD-style license, in which one allows use of the code for any purpose but disclaims liability. If you do not demand attribution, allow unrestricted commercial use, and allow derivative works to be created, the site attempts to steer you to the public domain. Are the authors doing this in an attempt to dissuade users from choosing this sort of license?
No, the GPL doesn't allow you to distribute your derivative works under any license other than the GPL. Even if you have a less restrictive license on some (your own) parts of the code, the entire derivative work can only be distributed under the terms of the GPL.
If your own parts of the code are useless separate from the derivative work, then you basically can't distribute them under any license besides the GPL. If they are useful on their own, you can consider your code a separate, original work, which combined with the GPLd work produces the derivative work.
If you create an original work, you are free to release it under any number of different, incompatible licenses. Unless of course the licenses are so overly broad that they state anything about other software that you can use, but I would tend to think such provisions to be unenforceable.
To put it more simply, lets say there is a GPL'd work A and your part of the work B is under a simplified BSD-style license (advertising and promotion clauses removed). What you get is:
A[GPL] + B[BSD] -> Derivative[GPL]
The existence of Derivative[GPL] doesn't hinder the separate existence of the works A[GPL] and B[BSD] under their respective licenses, unless B is tightly enough intergrated with A that they are unseperable.
IANAL, so this is just how I understand it, but I believe RMS would agree that this at least the correct interpretation of the GPL.
"One basic notion underlying Usenet is that it is a cooperative."
Having been on USENET for going on ten years, I disagree with this.
The basic notion underlying USENET is the flame.
-- Chuq Von Rospach
- this post brought to you by the Automated Last Post Generator...