How IP Law Helps FOSS Communities 98
dp619 writes "Fighting against software patents (New Zealand has banned them) tends to blind FOSS communities to aspects of IP law that actually serve them well. While certainly not perfect, patent, copyright, trademark, and trade secret law each has something to offer FOSS communities. Penn State law professor Clark Asay wrote a guest post for the Outercurve Foundation briefly describing some of the ways in IP law can help open source developers."
missing the point (Score:3, Insightful)
Open source isn't supposed to help developers. It's supposed to help USERS.
Re: (Score:2)
Buyer vs. Seller is a zero sum game.
Only if you assume that they're both douchebags. Assuming that, just because some people are douchebags, everyone's a douchebag, is not a nice way to live.
In any case, your analogy is flawed.
Re: (Score:2)
I give away stuff for free and still manage to live pretty well. So does FOSS.
Re: (Score:3)
Re: (Score:2)
Buyer vs. Seller is a zero sum game.
There isn't a voluntary trade without mutual benefit. Buyer vs. Seller is always positive sum.
Re:missing the point (Score:4, Insightful)
That is simply false. If it were true, economic exchanges would never occur.
In a zero sum game, the total cost of the participants gains and losses in utility--for one perhaps increasing and the other decreasing--add up to zero. One side may win, the other may lose, but both sides cannot win.
Let's say you've developed hydrophobia want to sell your used canoe on Craigslist. Let's say that I want to buy a canoe to go camping on an island in the middle of a lake. Your asking price is $300 and I think it's a good deal. I give you the $300; you give me the canoe. You're looking at this and saying, "Well, I'm less one canoe but I've gained $300 and he's less $300 but he's gained a canoe. So, it's break even." Or worse, you might be thinking, "Ha, that sucker. I had no use for that canoe so it was clearly worthless. But I can now by a sweet raincoat with my $300."
What you're missing here is a very basic economic reality: value is subjectively determined. Because of your hydrophobia, the canoe has no utility for you. You'd rather spend $300 on rain coats. So the exchange is a gain in utility for you. I, on the other hand, cannot make a paper boat out of three Benjamins and expect to get to my campsite. Money's use is that it can be exchange for something useful. I decide that I'll get more utility out of the canoe than $300 in the bank, so I buy it from you and from my perspective I've also gained in utility. It is, in other words, a win-win.
Where there is no force, compulsion, coercion, rent-seeking, or other machinations involved, free economic exchanges can always be win-win scenarios. People simply wouldn't trade, buy, or sell if they didn't value what they gained more than what they gave away.
Re: (Score:2)
Re: (Score:2, Insightful)
Not really. The "Users" in RMS's time WERE developers of some ability. Even when ERS took up the Open Source banner over Free Software, he was looking at it as a Developer.
People who are strictly users don't really care. This is how the UNIX vendors, Microsoft and Apple were able to dominate their respective fields for so long. It was only people who wanted to develop extensions of closed software that Open || Free vs closed became an issue.
Re: (Score:2)
"Not really. The "Users" in RMS's time WERE developers of some ability"
Open source would ENORMOUSLY benefit PC gaming. In fact the few games that were open sourced have all had amazing work done to them. Who cares if only a small subset of the gaming community/fans have the potential to fix/work on the code? That's true of anything requiring serious effort. I can only imagine where we'd be if it was required by law to open source all games. So many classic games would not have to have 'gangrene' code.
Re: (Score:2, Insightful)
Back in the days, computer users were technically proficient out of
The car: yup bolt its hood shut, thank you. (Score:2)
Thing is, though, as a tool, it should assist the user in helping them do what they want,
Yup. Do what the *end users want*.
The tool should *not work against them*.
Not do what *the makers decided to do*.
It should do what the end users want, even if the end user want to do something weird.
I should not be served a DCMA because I use a hammer as a paper weight instead of using it for nailing.
If I want to pry appart two pieces stuck together, I can use a screw driver. I won't be required to buy an extra "pro business deluxe" license to acquire a small chisel because screw drivers are only for screws
...Software patents: no sense (Score:2)
Also, software patents (and in general, patents on anything not physical, like "methods") make no sense at all.
Patents did make sense for industrial inventions.
It makes sense because physical objects take resources to create, they're expensive.
Idea are cheap: they are mostly free. It's the implementation that's challenging.
Back to the car method:
- If I'm the inventor of cars, I won't be able to create a prototype. I would need materials, I would need physical experimentation, etc. To invent cars, I would ne
Re: (Score:2)
People who are strictly users don't really know the difference.
That's what you should have said. Even the least caring users are directly affected by what's "under the hood" even if they never bother to open it. Your examples are not exactly convincing either:
Microsoft ... able to dominate
Mostly before Free Software gained momentum. Look what is happening to them now.
Apple ... able to dominate
They kind of stagnated until Jobs came back with a copy of Free BSD...
yeah , it's not like Android is Linux based (Score:2)
> smartphones and tablets which has nothing to do with free software.
Yeah, it's not like most smartphones run Linux or something. ;)
Microsoft wasn't late; they've been trying to do smartphones for at least ten years. Their system, Windows, just isn't any good for phones. Windows, as it's name implies, is designed for having many windows open doing different things, on hardware large enough to handle many concurrent applications. On a phone, you need to start with a small kernel with real-time capab
Re: (Score:2)
claiming NextSTEP is just a copy of free bsd is retarded
I did not call it "just a copy" but merely pointed out that it is based on open source, while you claimed to be an example of closed source success. Can we settle on "a copy with some bells and whistles attached"?
Re: (Score:2)
may have been some BSD code in there
There have beem "some", it is a fact. How much was it is arguable, but definitely much more than "may have been some".
FreeBSD didnt even exist yet!
FreeBSD did not exist, but free BSD did. You knew it, right? Here is an amusing article for you:
How Free Software Contributed to the Success of Steve Jobs and Apple [oreilly.com]
Re: (Score:2)
Yes and no. The idea of free software is that users and developers are ultimately the same. If you encounter a bug as a user or need some feature, you can fix it on your own, or, if you don't know how to do that, you may send the source to some grey-bearded friend who will patch it for you. That's the idea. It means that users are informed and encouraged to learn about the technology they use and hack and adjust it to their like, rather than being forced to use a weird blackbox with paid upgrades every few
Re: (Score:2)
It means that users are informed and encouraged to learn about the technology they use and hack and adjust it to their like, rather than being forced to use a weird blackbox with paid upgrades every few months.
That's a disingenuous comparison, in fact I can't think of any software at all for which I've done paid upgrades 'every few months' so what specifically are you referring to?
Even with open source applications like GIMP I would still rather use my copy of Photoshop CS2 than go to all the work to make GIMP a viable replacement. On the other hand Blender actually is in some real cases a viable replacements for its closed-source competitors. To win over users free software has to be better, not just cheaper and
Re: (Score:2)
It can help both. Most early open source (before the term was invented) was libraries intended for use by other programmers. The whole rational behind the GPL is to preserve the right of the user to modify the code, thus the user is also a programmer.
Re: (Score:2)
The whole rational behind the GPL is to preserve the right of the user to modify the code, thus the user is also a programmer.
But in the incredibly vast majority of cases the user is not - and doesn't want to be - a programmer.
Re: (Score:2)
I was talking about the rationale to create the GPL, that implies when it was first created and not the state that exists today. When the GPL was first created it was for software primarily intended for developers. Initially this evolved from the license first used with GNU Emacs, but then when formalized as a "license as subroutine" it was applied to other GNU programs which were primarily GCC and other Unix tools replacements.
Most of the clauses in the GPL are there precisely to allow the end user to mo
Re: (Score:2)
I was talking about the rationale to create the GPL, that implies when it was first created and not the state that exists today.
I understand, my point was that the reason users don't really care about open source is because most users aren't programmers and to a non-programmer user it really makes no difference, sure they could pay somebody to add features for them but the reality is that most of the time it's only businesses that do that. Open source needs to provide a tangible benefit to non-programmer users for them to care about it.
Re: (Score:2)
Says you.
I share my code because I want to help developers with the tools I work on, not because I have some altruistic, high-minded goals about helping users.
Different projects have different goals. The fact that people who would download my tools could be called "users" of them doesn't make them any less developers. To make broad, sweeping statements about who should benefit tries to pigeonhole the mind of the developers of open source projects, and that is a fool's game, because everyone has their
Re: (Score:3)
In Open Source, there is no clear boundary between developers and users. This is actually a benefit of open source, any user could be a developer.
New Zealand didn't ban software patents... (Score:4, Informative)
They basically just banned adding "on a computer", etc. to a patent automatically becoming a new patentable "invention".
Re:New Zealand didn't ban software patents... (Score:5, Informative)
*sigh* I am in New Zealand, and yes I have read and understood the legislation. For full disclosure I am also an Associate Member of the IITP, one of the groups who pushed hard to get this mess sorted out.
Most people skip the most important line which reads:
"A computer program is not a patentable invention." Section 15, part 3A: http://www.legislation.govt.nz/bill/government/2008/0235/latest/whole.html?search=sw_096be8ed8054d616_computer+program_25_se&p=1#DLM1419225 [legislation.govt.nz]
Now, is that unclear to anyone?
Re: (Score:1)
Section 15, part 3A:
I stand corrected.
Mod that link up.
Re: (Score:2)
It's a bit too early in the piece to see the legal ramifications at this stage, but I'll give you a brief outline of what would most likely happen in this environment:
"A system comprising a computer with a touch-sensing display, and a program running on that computer such that gesture A causes the computer to display blah blah blah" ; this is actually two separate things, one is the physical hardware which is a device capable of sensing touch. The program running on the device that performs other actions i
again with the version from five years ago? (Score:2)
You're linking to the 2008 version. GP accurately described the version that was actually passed.
The final version even included examples. It says that on one hand taking an old invention and implementing it in software doesn't make it new, on the other hand a new invention that happens to be built in C++ is a new invention. In other words, whether it's software, hardware, firmware, or dinnerware doesn't effect patentability.
Newness controls.
Re: (Score:3, Informative)
Here we have the legislative page: http://www.parliament.nz/en-nz/pb/legislation/bills/00DBHOH_BILL8651_1/patents-bill [parliament.nz]
Here we have the link to all related bill documents: http://www.legislation.govt.nz/bill/government/2008/0235/14.0/versions.aspx [legislation.govt.nz]
Additionally here we have a link to the "live" bill currently in force, this is the passed version, 235-2: http://www.legislation.govt.nz/bill/government/2008/0235/14.0/whole.html [legislation.govt.nz]
If you note Section 15, 3A, it still says the same. This is what is known as a trump l
Re: (Score:3, Informative)
Ahh, just spotted what you were referring to, it's a SOP. A supplementary order paper, and in this case it is the one that caused controversy and was not enacted into the final bill: http://www.legislation.govt.nz/sop/government/2013/0237/latest/whole.html#DLM5187401 [legislation.govt.nz] . I repeat, this SOP is not in force. Such papers are proposals for changes to the bill, you'll see this one is shown to be a proposal by it stating it is so.
So, please be a bit more careful, and link to your material next time :)
Re: (Score:2)
And that's the way it should be. Because let's say you invent a new radio modulation scheme that lets you approach Shannon's limit far closer than ever before even
Re: (Score:2)
Basically I'm not anti-patent, but software patents just strike me as completely wrong. Mostly because the overwhelming majority of them are crap, either overly broad idea obvious to anyone who has thought about the problem, or ideas that have been done previously by someone who didn't think to patent it (or couldn't afford the expense of patenting).
But overall patents still have a chance of succeeding at their original goal: provide a limited monopoly in exchange for disclosing your new invention. Note t
I wish I had mod points, thinking instead of KoolA (Score:2)
I wish I had mod points. You've thought things through and offered solutions, like shorter patent terms.
I wholeheartedly agree, a lot of bad patents, mostly overbroad ones or non-novel ones have been granted. That doesn't mean that a specific patent on a legitimately new invention shouldn't be issued just because the inventor built the invention on an SSD rather than discrete transistors. It means USPTO needs to stop issuing patents on things that aren't new, are obvious, or are too broad - all of which
Ain't that a surprise.. not.. (Score:5, Insightful)
Re:Ain't that a surprise.. not.. (Score:4, Insightful)
From sockpuppets, astroturfing to huge reports and fancy foundations
Re: (Score:2)
NZ banned software patents the same way they're banned in Europe i.e Not really.
Meantime we see patent lawsuits going to places like UK and Germany because they give judgements and injunctions even faster than rocket dockets like East Texas. See Motorola vs. Microsoft on H.264 patents on Windows 7 for example, or Apple vs. Samsung/HTC etc.
If those are not software patents then what are?
http://allthingsd.com/20120502/german-court-backs-motorolas-injunction-against-microsoft/ [allthingsd.com]
Re: (Score:3)
No - really - we did. Not sure if this is simply ignorance or wilful deception, but Software Patents are toast in New Zealand.
Now it may be true that you can still have embedded software which is part of a larger hardware system, but in terms of getting patents on software that runs on general purpose computers - they are most certainly not going to be granted.
Of course this does not invalidate existing patents, and we are yet to see any test cases that will better define the edge cases.
Re: (Score:1)
Re: (Score:2)
Oh I see, we get an Oracle shill to go with the Microsoft shill in the TFA.
Re: (Score:3, Interesting)
Outercurve's president seems to be the Apache Software Foundation's cofounder though.
Jim Jagielski, a co-founder of the Apache Software Foundation; a director of the Open Source Initiative; and currently a consulting software engineer for Linux giant Red Hat is now president of the Microsoft-sponsored, open-source friendly Outercurve Foundation's Board of Directors.
http://www.zdnet.com/microsoft-sponsored-outercurve-foundation-turns-to-apache-for-leadership-7000017596/ [zdnet.com]
Re: (Score:1)
... and receive according to their needs.
Why not receive proportional to what the give instead?
Re: (Score:2)
Re: (Score:3)
IP laws are despicable, costly to mankind, dangerous for research and harmful for the economy. I am still making business plans that rely on these bad rules of the game, just like I would include corruption in my plans if it was unavoidable in my country.
Yes, rethinking copyright laws would force us to rethink all the open source licences. We would
Re: (Score:2)
not a good sell (Score:4, Insightful)
Re: (Score:2)
Some efforts will be long term to lure skilled coders away to projects that dont have anti DRM clauses.
Some efforts will be short term to ensure politicians stay informed about trade deals and the role of Intellectual Property (IP).
Dubious advantages (Score:5, Insightful)
Imagine a mugger who claimed that he's a good mugger because he left you with enough money to catch the bus home. Should you be thankful that he didn't shoot you and that "all" you lost was a few hundred dollars, your credit card, and last year's iPhone?
What the blog claims as the advantages of IP laws, such as DMCA's safe harbor and the limts on copyright and patents, are problems that wouldn't exist if the laws didn't exist in the first place (if the mugger didn't mug you, you wouldn't feel the need to be thankful that he spared your life).
Re: (Score:2)
Still don't see patents helping (Score:3)
Re: (Score:2)
Trade secrets on the other hand? The secrets are in the source, which once opened are no longer secret. I can't find any far-fetched argument that supports trade secret law
Re:Still don't see patents helping (Score:5, Interesting)
That's how all of his points shake out. Every single one boiled down to... "Sure this law nearly turns thinking into crime, but there are some exceptions that you can work in". The FOSS philosophy requires no law to exist. For-profit software couldn't exist without legal protection. I'm not saying for-profit software is bad, but it certainly requires legal protection to sell something that requires almost no physical effort to reproduce.
The question we can't get any real public dialog on is "How much protection is the right amount to create the world we want to live in?"
Re: (Score:3)
A case can be made for all current 'intellectual property', but in essence it is all founded in a social contract. Its a deal we enter. Trademarks exist to protect good will and brand identity. There is a social benefit in knowing a certain product is made by a certain company because characteristics like quality can be inferred. Without trademarks any time some company got an edge with its name the name would be copied by competitors.
In copyright there is a social benefit in the support of the creative art
Re: (Score:2)
Patents also help when innovation is expensive. Consider drugs: a drug company will spend a whole lot of money on clinical trials and the like, and there's an excellent chance, for any given drug, that it's money down the drain. Patents on drugs allow companies to make enough money to support this. I haven't seen a better method to get an allocate this sort of research money. (This is a defense of the general idea; I'm not making any claim about specifics.)
Healthcare meds and equipment would be expe
Re: (Score:2)
Wish I had mod points. A clear, concise explanation of which side requires force of law, and a final sentence that raises the question of balance while allowing the reader to seek his own conclusion. The epitome of a thinking person's post. Thank you.
Re: (Score:3)
but it certainly requires legal protection to sell something that requires almost no physical effort to reproduce.
Not if you want support from the guys who wrote it. Which, incidentally, describes some of the arrangements I'm involved with regarding open source software, on both sides. Copyright has never been a factor.
try producing an OS with no effort (Score:2)
I contribute to several open source projects, and I'm the maintainer for some. So I "get" open source. Your idea of "requires no effort" irks me, though, because it leads to very incorrect conclusions.
FOSS works well when many people want the same software. Apache and Linux are examples - everyone needs an operating system and there are millions of web servers. If 0.1% of users contribute,
they can build and maintain good software together.
Where proprietary software works well is when there are a limited
Re: (Score:2)
The key phrase would be "...almost no physical effort to reproduce."
The problem is that the original production takes a great deal of effort, and has to be compensated for. While the freetards of the world think it's just about the cost of making a copy, that just isn't viable. Someone has to pay for the production in the first place.
Re: (Score:2)
If you want to maximize profit, then distribute the official release in as many markets as possible at once, which will reduce copying. It's already a good idea. Much of today's copyright infringement (why do people call it piracy? we have a term that actually describes it precisely) is due to region lockouts.
Re: (Score:2)
Someone has to pay for the production in the first place.
Maybe, maybe not. It's perfectly valid to be OK with living in a world where all IP is of volunteer quality. For most of the history of man, music was produced for free, although performances were often paid for. In the renaissance, there was a trend for wealthy people to finance IP, yet still make it public. On the other hand, you will get a more efficient market if people make music and software for money.
The problem with using words like "freetard" or "M$" is that all that does is point out that one
Re: (Score:2)
1) Copyright. The FOSS movement was created as a reaction against copyright being applied to software.
No, it was created as a reaction against software distributed without source. RMS couldn't fix his printer driver because it didn't come with source. And copyright is the only thing that allows copyleft licenses to require source distribution. Overall, I think copyright is a net benefit.
3) Trademarks. Same question as above. And the commercial branches of some FOSS projects have used trademarks to kill competing support/education.
Well, in response to "how many DCMA cease-and-desist notices have we seen" regarding trademarks, I think the answer is pretty clearly none. If you really meant, how many trademark lawsuits, I don't recall hearing of any. If
Re: (Score:2)
Misleading title (Score:2)
Re: (Score:2)
TFA doesn't say anything about laws that help FOSS, except for trademarks. Because they don't help. TFA only mentions a few cases where they don't hinder.
Trademarks don't help either. They harm. FOSS is less likely to be able to afford to go to court over a trademark.
There is just one place where copyright law aids FOSS, and that is in licensing. Without copyright law, the GPL could not function. Some argue that the GPL is necessary only because of copyright law, but I disagree. It still covers the case where you get binaries but not source. Without copyright you'd be free to redistribute, but you could not practically make changes because you still wouldn't
Re: (Score:2)