OpenLaw to Support Open Source Community
From ralphclark: I recently contacted Wendy Seltzer at OpenLaw to ask if they could assist the open source community in its struggle with the forces of evil (the MPAA and the DMCA and UCITA). After a brief dialogue she finally wrote back:
" I have been thinking more about this project and the tools we'll need for it, since I haven't gotten a negative response, indeed several positive ones, from people at the Berkman Center.
I think it's probably best to start low-maintenance, with a mailing list and a Web page, then to add components such as Web-based discussion and a collection of links and documents.
If you have suggestions for links to the key documents/Web pages, that would be a great help."
I think this is our clarion call: I've seen plenty of good quality debate on these issues here on Slashdot, and the most unsupportable viewpoints have been flamed to death by now so I'm sure there are lots of people reading this who have something valuable to contribute. You should e-mail your (sensible) suggestions to Open Law Feedback and she'll pick them up from there. One suggestion: When you mail, write your idea below in comments - than people can avoid duplication of effort.
The word of the day is "pro bono". Lawyers have been doing voluntary community service for a long, long time. The eyes of many lawyers probably will make "bugs" shallow.
However.
As far as law is concerned, the eyes of a million SlashBots are worth about, oh, golly . . . I don't think they make numbers that small. How's this: That and a dollar will get you a 50-cent cup of coffee. Just barely.
I can see it now: "IT"5 ALL ABOU7 THE SEC0ND AM3NDM3N7!"
God help whoever as to wade through the email on this one.
"Christianity neither is, nor ever was a part of the common law." --
Now this is a good idea.
It's obvious that the Open-Source (free-software) community is under attack from those who don't understand it and would like to kill it. This is probably the best way for us to meet this challenge - leveraging the one thing that makes us different (and arguably nimbler and better) than our closed-source nemeses.
Not all of us are lawyers, and that's OK. When it comes to technical issues, you have the techies to make the cases, and the lawyers to put them into formats that the courts will accept and that could possibly win.
I don't think I'm exaggerating when I say that this marks a turning point for free software. Maybe now we can mount competent defenses/offenses against the large corporations who would stifle/censor us.
Kudos.
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
So, who's interested? :)
The only attorney that I know of who is helping pro-bono is working on the DVD lawsuits.
We want to file our own patents and then license them for blanket use by free software. We need attorneys for that. Sometimes we want to go to court to fight things like the DVD lawsuit or patents that are being enforced against free software. That's more than just consulting, but it would be great if we could get some more pro-bono help with that, too. That one pro-bono attorney, and the staff attorney at EFF who is working on DVD, are pretty overwhelmed and could use some help.
Someday, we might have to be the agressor, too. Enforcing our licenses, or attacking something like the DVD Copy Control Consortium in the courts. I'm not expecting all of this to be pro-bono. We need more money to do this than we have so far.
Thanks
Bruce
Bruce Perens.
This is all fine and good. I've joined EFF, I've joined the ACLU, and I put my considerable moral support behind all of this...
But what else do you suggest?
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
IANAL, but my dad is, and that's essentially how he explained it to me. I'd appreciate any corrections/clarifications.
This isn't easy to explain, but think what would happen if it became public knowledge that there was a group of lawyers working for free for "just" cases. They'd be innundated... both with requests and with people upset they didn't make the cut. Unlike code where the product is already there - a legal forum would help push a case from start to finish. It's the "something for nothing" crowd I'm worried about here..
The second, and less important, problem I see is that unless there is a clear set of guidelines / criterion for what such a forum would - and would not do or allow is laid out, it's doomed from the start. The reason is simply that there is no focus, hence work is duplicated, petty arguements break out over what the Right Thing is (or direction), and things just never get done.
Lastly, it would take a helluva lot of lawyers to do this... and, uhh.. in our country.. they're pretty busy already.
That's not open source. That's an open API. There's still an elite cabal of people (lawyers) who are the only ones (in most cases) that put the stuff together and submit it. In order to do most things, one must go through a lawyer.
This gives us access a little more to the internals. Things must go through the kernel API now, instead of the userspace API. It's the difference between a libc call and a system call.
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
No, I agree with his ideals, actually. But there's a such thing as tact. And there's a such things as compromise. Free software wouldn't be where it is now if it weren't for ESR. It'd still be a fringe movement. ESR knows how to talk to the people who have the money. And in spite of RMS's ideals, it's the money that gets the wheels moving.
RMS has done a lot, but he is ultimately not the reason it is going mainstream. One of them, yes. THE? No.
For the record, I do admire ESR standing up for his beliefs and stuff. I don't knock that. I wish I were half that idealistic. But... life, at least for me, isn't that way...
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
This is a decent idea, but I'm not too sure how it would actually pan out. Lawyers are a finicky bunch, but that's not their fault - law is very finicky.
Starting small, with sites such as this, is probably the best idea.
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
But in this case... the documentation actually determines how well the code runs.
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
Consider how the GPL uses copyright against itself. I'm thinking of the same sort of strategy, although not as elegant as RMS did with GPL.
Thanks
Bruce
Bruce Perens.
Is it that the lawyers in a case are going to post the briefs-in-progress and invite public comment? This is NOT the same as open source. The "open" part is the same, but law is not source code.
Source code is, to a first approximation, either correct or not. If someone wants to work on a routine in a program, it can usually be modularized, parcelled out, and tested to some degree of reliabily. Critically, it's typically OBVIOUS if it's completely wrong.
A judge isn't a compiler. No-one really knows if a legal argument is going to work or not. It's like the world's worst debugging session, there's almost no way to retest the results.
It sounds like a good idea, but there's a lot that's very unclear in practice.
It's obvious that the Open-Source (free-software) community is under attack from those who don't understand it and would like to kill it. This is probably the best way for us to meet this challenge - leveraging the one thing that makes us different (and arguably nimbler and better) than our closed-source nemeses.
Oh please. The open-source model is not under attack from people who don't understand it. It's not like Sony, Microsoft, and Paramount are all gathered around a table going, "That damn OSS. We don't know what it is, but it's high-time it stopped!" While I'm not sure what you mean by open-source, I'll go over both possible explanations (since you're ambiguous about it). Free software has actually been given out by Microsoft (remember Internet Explorer? Netmeeting? Messenger?) and Microsoft recognizes and even links to many sites that promote Windows freeware. I think companies like Apple and Microsoft that deal in decidedly pay-for software recognize the value of free software in promoting their operating system and would never want the practice to stop. As for open-source software, Apple has supported it. IBM has supported it. The DVD consortium is not against it. The NSA is not against it. Wal-Mart is not against it. There's not a coordinated attack against open-source software and to say it is so is to not understand the nature of the legal battles that involve potential OS/free software concepts.
I don't think the law idea is necessarily a bad one. I do think trying to characterize it as a champion of OS/free software is. I will also point out that the open-source community model is a software model and does not always translate into other professions. Law is practiced by registered lawyers for a reason, because there are many intricacies to law that need to be studied to be understood (IANAL). While a community of free lawyers may be a great idea, considering the incredible time-commitment it takes to become a lawyer and the decidedly puny return on pro bono services, I don't see it as a profession you're going to get the world's best and brightest in. Lawyers do not have the mentality of programmers.
And while we're on the topic of open-source models, I use open-source software and I support it, too, but I do not live an open-source life. I do not give people permission to reproduce and change my ideas. I do not give a community the group right to tinker with my car. I do not want an open-source model managing my electric utilities or my sewage or my education. I think open-source ideas have their place, and I think they rightly belong in information services, like programming, writing, and support, but I don't necessarily think they extend into everything.
Sometimes, I don't like computers to cross into real life, and the paranoid comments that prompted this reply highlight a fear of mine that that is exactly what's happening.
I've been corresponding with Wendy Seltzer since the initial suggestion that we do this in the original proposal thread. Thanks to sholton for pointing us to openlaw and to ralphclark for efforts to bring this about.
I've also been in touch with Robin Gross from the EFF, who has indicated that she would like to participate in the forum. I hope that we can create a high quality combination of legal and technical input.
This step is just the start, I hope. I would like to encourage people to participate in this. I think it would be a good goal to file an 'amicus' brief to each of the DVD cases that is written using open source methods that represents the views of the open source community.
I couldn't help but notice that you used those terms interchangeably. Free Software is _not_ the same thing as freeware! To paraphrase RMS, free software means free as in you can do whatever you want with it, not free as in beer. Just thought I'd clear that up...
--
WARNING!
Just because something is illegal does not make it immoral. Nor is the reverse true.
We would like them to be equivalent, but differences of opinion over morality will prevent that.
Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
And then there is the primary. You think the person with the most votes wins, right? Wrong! Delegates from each state can throw the popular vote any way they choose. For example, let's say you voted for John McCain in the New Hampshire primary, and indeed McCain won New Hampshire. But the good ol' boys in the Republican convention may be in a George W. Bush mood, which is more than likely. They may very well say, "New Hampshire casts all of its votes to Bush." The delegates can do that!
Okay, so now your guy won the primaries and is in the general election. Hey, he or she wins! Nope, not quite. There's a little known group called the "electoral college" that can do whatever they want, and _legally_. Just as with the delegates in the primary, they can decide the people are off their collective rocker and then elect THE OTHER GUY!
Okay, well what about laws. Did you think that the president makes the laws? Nope. He or she can do nothing but veto a law, providing less than 2/3rds of the congress voted for it. Laws are passed by the congress, a relatively small group of people.
So, you want UCITA to be rejected? Where can you go and vote against it? NOWHERE. You have to vote for someone to get into congress first, and then maybe they'll vote against it. But good luck there. It could take 6 years to get a new person into office. By then UCITA could be law.
"But, can't I vote on a ballot for or against a law?" NOT FOR FEDERAL LAWS! This can only be done for _some_ state laws. First you need to get it on the ballot: not an easy task. Then, even if it passes, the state legislature can nullify it the next day. This happened in my state, where the legislature passed a seatbelt law. The _people_ said no and voted to remove it via ballot. Well, I guess we didn't know what we wanted, at least according to the legislature, because right after the _people_ shot the law down, the legislature VOTED IT RIGHT BACK IN AGAIN!
It's frustrating, because the only way a person can support or oppose a law is to vote for a representative that feels the same way. BUT THE REPRESENTATIVE MAY VOTE AGAINST YOUR IDEALS ON EVERY OTHER ISSUE.
Much of the way the U.S. government works is due the difficulties in communication and travel when the U.S. was established in the 18th century. It would be pretty pathetic trying to get everyone in the country to mail in a vote on every issue when the letter could take a few weeks to get across the country. It was therefore considered more pragmatic to have representatives at every step in the process.
The communications or information age should change all this, however. The speed at which people can now educate themselves and share ideas cannot be compared to the way things were in great grandpa's days.
I hope that computers will put an end to the delegate and electoral college system, and even the representative system. And I hope people can be trusted with the responsibility of direct democracy. But that's another issue.
Jeff
This sort of thing has cropped up before. And it has always been due to human error.
--
This sort of thing has cropped up before. And it has always been due to human error.
HAL9000
Ah, but software companies are claiming more than copyright protection. They're claiming that through the device of the shrink wrap license, you have entered into a contract with them where you agree not to reverse engineer the software.
The other way such a body could help is by giving advice about things to do *before* litigation starts. They could teach the free software community how to protect itself, how to avoid blunders which make litigation more likely.
Perhaps somebody could put together a legal howto. How to keep your copyright enforceable. How to react to threatening letters. And if it comes to it, how to defend yourself in court. Sure, reading a howto is no substitute for years of legal training, but it's better than nothing.
perl -e 'fork||print for split//,"hahahaha"'
I agree that law is not strictly like source code, but the picture isn't quite as bleak as you paint it.
There is one market that openlaw forums could address quite well: those silly cdroms of do-it-yourself legal briefs that you buy and fill in the blanks and use. While it's true that it's impossible to foresee how new judges will react to new arguments in new proceedings, some things have been filed and refiled to death and it's silly to pay a lawyer to reinvent the wheel with them.
And you overstate the dissimilarity between source code and law in another fashion: like with new judges in new situations, established source code can break in new environments and hardware configurations. Just as the user will make a bug report and tell the author that the code doesn't always work in a given situation, so will the would-be lawyer when his argument falls on its face. And while code is more reproduceable than is law, any coder will also be quick to tell you that bugs often seem to appear and disappear with the phase of the moon.
With that said, I have to smirk at what coding would look like if it functioned in the same way that law does in one respect: all those disclaimers about how "I am not a lawyer". Can you imagine what source code would look like if it were sprinkled with comments asserting "This may look like code, and if you try to compile it it might actually work, but I am not a programmer and this is not code."? Feel free to insert a wisecrack about Microsoft here.
"If one is really a superior person, the fact is likely to leak out without too much assistance" -- John Andrew Holmes
> Apple makes a profit.
It has been known not to for several years in a row. Of course Red Hat makes consistent losses right now, but Apple probably did this at the start, too.
perl -e 'fork||print for split//,"hahahaha"'
I don't know anything at all about the DMCA, but if that is the case, it will assuredly be struck down by the Supreme Court. The right to reverse engineer is as important to Capitalism as free speech and thought, IMNSHO. I'm not very worried.
Nope, it would be:
17'5 411 480u7 7#3 53c0nD 4m3ndM3n7...
-or perhaps-
17'5 411 480u7 7#3 53c0|\|D 4|V|3|\|dIVI3I\I7...
Or something even more ridiculous...
That's not even worth 2 cents... Sorry.
There's a level of inefficiency built into the system specifically to avoid straight-up vote over issues, and specifically to avoid democracy. Think for a second about what you are suggesting. Consider what votes you'd get for the following issues:
- What is the official American OS? (Windows/Mac/Linux/Be)
- How much taxes should people pay? (twice as much as now/same as now/nobody should pay any taxes)
- Should Microsoft be allowed to innovate and help consumers by standardizing the world on its products? (Yes, they have that right/No, they should not be allowed to help consumers if it hurts Sun)
Beginning to get the picture? Direct democracy is basically an open invitation to pure Politics As Spin, and it is very likely that you'd be the first against the wall, you slashdot reader hacker criminal type youThe problem is, it's well accepted that larger factions _will_ stomp all over smaller factions given the slightest opportunity. That's the way it's always been, and certainly watching the tech industry does _not_ suggest that this tendency has changed with the increase in technology we've seen.
The question you need to ask is, exactly how do you keep all littler factions from being taken out and shot? That's basically what happens as soon as you start attempting to use pure democracy. For instance, in pure democracy applied to the computer industry, this very website is grossly undeserving of any support or 'mindshare'. It isn't about windows- it wastes huge amounts of resources, periodically slashdots other sites and eats bandwidth and offers _nothing_ to support Windows, which clearly has the numbers. Now, if Windows users mostly _want_ Slashdot that would be a different story, but under direct democracy there is no room for the concept of 'Loyal Opposition' much less underground or radical factions. It's a powerful homogenizing force that only begins to really kick in when people sense that they have the power to use this 'direct democracy'.
It's not merely the 'Bread And Circuses' problem, it is worse because you get factions seemingly 'competing' in much the same way that the largely unregulated computer industry has been 'competing': playing dirty as hell, and winner-take-all. If you think having the RIAA and MPAA around treading on your rights is a problem, imagine what happens when The People get to vote on these issues! These associations have media resources that would blow your mind, and sure as 'hacker' is spun to sound like a terrorist, you'll get the issues presented in such a way that Orwell would drill through his grave, and The People will cheerfully vote to have to taken out and shot if you reverse engineer software programs. Hell, I could see _programming_ _itself_ made illegal for the unlicensed, given the right spin- such as these DOS attacks, or some credit-card-oriented spin.
You don't know how lucky you are to live in a system where any particular faction is basically tied up in red tape. If you want to see what direct democracy looks like, look at Microsoft in the tech industry, and imagine them without the DoJ or any government. The trouble is you can't expect people to take an interest in everything: at least the representatives can be expected to read 4000 page bills and the like, as that is their job. You cannot expect the general public to read 4000 page bills before voting on them, so the vote becomes pure armwrestling over how things are phrased and spun. That's not really democracy because people are being fooled...
How do you keep the other side from following all of your discussions? Do you really want the lawyer on the other side to know exactly what arguments you'll make in court?
I think this is a great idea, but I'm wondering about this aspect. How do you keep your best arguments a secret? Or do you just hope that they're so good, it doesn't matter WHO knows them?
----
You have to make an effort but Linux can be pretty much as secure as OpenBSD. It's just usually shipped in a wide-open state.
If you can't figure out how to mail me, don't.
For linux tips: http://www.linuxtipsblog.com
The other is not so obvious, but even more important: the source distributed with OpenBSD has undergone an extensive (years long) line by line security audit. Bugs that were fixed in OpenBSD two years ago and posted to various advisories lists are still turning up in Linux (and Free/NetBSD, and even proprietary Unix variants) to this day.
In addition, even given that a Linux distribution which has been audited to the degree that OpenBSD has (btw, there isn't one) is shipped in a secure-by-default (which I don't know of either...) state, this does not imply security. Security is a process which transcends a particular software installation (as the thousands of dumpster-diving and social engineering tales make clear).
There is a tradeoff, however, between security and usability. Most Linux newbies (or anything else newbies for that matter) don't want to be told that they have to reconfigure 10 security settings to easily reset the permissions on their sound card. People run X as root. People, for some reason, like to run anonymous ftp servers. And so on. The distro that strikes a balance between ease of use and default security will go a long way towards widespread adoption.
"Cause there's 40 different shades of black, so many fortresses and ways to attack, so why you complainin'?"
I don't want to discourage or anything, but since court decisions are already open and capable of being modified by anyone with (a certain standard) education and experience, the law is already essentially open source. It's just that it takes a lot longer than a single case to fix -- a single court case is the equivalent of a single edit-compile-test-debug cycle, and nobody ever wrote a program with only one of those ;-).
This digital millenium copyright act garbage really needs a good jury nullification, though. Now THAT would be quick.
Anyhow, I don't think a whole lot of unskilled but enthusiastic eyes are going to find anything worthwhile.
-Billy
But anyone can become a lawyer if they invest in the training and meet the standard. Or more importantly, anyone can run for office -- our system was designed so that the common man had a chance at office, even though this isn't always the case -- and if they get elected, they can make laws.
Think of law as open source via a smaller bazaar than usual; more like the FreeBSD team than the Linux developers. There's a tighter grip on who can make a CVS commit (write and enact legislation) and who can submit patches (judge's precedents), but anyone has access to the law and, provided they go through the proper voting, running for office or law training, change it...
Three Step Plan:
1. Take over the world.
2. Get a lot of cookies.
3. Eat the cookies.
I was wondering is there is an exact say formal method of reverse engineering that works for hardware and such. I am really quite curious if I am to be more fully informed about the process. I would have thought it was just guess test and repeat however I may more than likely be wrong in this account.
Sometimes for some things there is no other way to do something then use reverse engineering. Most old and unattended cobol applications needed a little RE before their true nature was discovered.
I hope this works I have been getting a great many network reed errors or something (may be a little conspiracy)
Slashdot social engineering at it's finest
My thinking on the matter is colored by a lot of reading on Watergate: representatives were placed in pretty intolerable positions at that time. Some represented deeply conservative constituencies which doggedly supported Nixon- yet gradually the representatives began to realise that Nixon had lied to them, lied to the people, committed crimes, and as impeachment grew closer and closer, they all ended up turning against Nixon, because they owed their constituencies not just their obedience, but their judgement. It was a tough call, causing many of them great anguish- they like you took representation seriously. But the bottom line was this: they knew that their own constituents had been lied to and misled, and they couldn't wait around for 'em to figure that out. They had to act based on the truth.
If it was a pure democracy, it is possible that Watergate could have ended in an expertly 'spun' poll or vote (The Nixon people spent millions in astroturf campaigns through fake organizations, even buying a fullpage Times advertisement under a false name) resulting in a criminal President who engaged in wiretapping, surveillance, and conspiracy to burglary and obstruction of justice... staying in office and continuing to do it. That's not OK.
By the same token, though it's hard to argue that politicians should be trusted, _somebody_ has to get the job of learning up on this stuff and deciding things. When you read history it might surprise you, sometimes, how our pols can sometimes rise above all the corruption and politicking and do what we'd want them to do- even eloquently, movingly.
Campaign reform, yes. Tie the hands of corporate pork barrel special interests, yes. Replace the pols with one big vote- no thank you. For all their faults the pols do that job better than one big vote ever could.
Movie publishers gave me authority to descramble a movie on DVD for the sole purpose of viewing the movie at home. Some of them may explicitly state that I'm allowed to use authorized player only; others may not. It's enough to find ONE DVD that does not explicitly restricts my choice of player to argue that I have the authority to build and use (with this particular movie) my own player, and I can share its design with others. It will not be a "circumvention" as defined by DMCA.
OTOH suppose a game like Quake comes along with encrypted copyrighted non-distributable (hi NP guy) maps, and the license explicitly states that you can use these maps within context of this game only. Then decrypting a map would be an act of "circumvention" as defined, as there are no non-infringing uses for that.
No "moderate this down" this time.
--
Industrial space for lease in Flatlandia.
Well the judge who granted the MPAA injunction doesn't think so.
Ummm, AFAIK the MPAA injunction has nothing to do with shrinkwrap licenses. The claims made in that case were intellectual property ones, mainly that DeCSS is a threat to MPAA members' right to protection of intellectual property.
--
Intellectual property, on the other hand, is rahter fuzzy and slippery. People may agree on some basic concepts, but very soon there will start appearing exceptions and side issues and ramifications that weren't thought out. It's very hard to get from basic principles to details in intellectual property law for two reasons:
1) Intellectual property isn't so well correlated to physical possession. You may buy a book, the book is yours, but the content is mine, etc.
2) Intellectual property can be duplicated. If I own a tract of land, I can't copy it, if I own a book I can.
Therefore, I think we need some differentiation between material and intellectual property in the law. It's easy to say they are exactly the same in principle, just say "pirating software is exactly like stealing", but saying it doesn't make it true. At least, not in the practical sense.
Unenforceable laws should be avoided, because they create a general disrespect for the law. It's like the alcohol prohibition that some countries tried in the early 20th century. Those laws had only one effect: they created a widespread corruption among the police officers and a lot of admiration and tolerance for gangsters among the general public. The intellectual property laws as they stand now, will only create a cracker worship mentality among the people.
From the /. moderator guidelines: If you can't be deep, be funny
For code, code readings are great. More code readings are better. This is, in part, because code either works or it doesn't, is fast or it isn't. This isn't always true, but it is more true than it isn't. To the extent this is true, the leverage of a community of open source contributors interested in a project is better, not worse.
For law, code readings are silly. It is not true of the law that an argument either works or it doesn't, or that more code readings can be used to find "the best argument." Indeed, to the contrary, Brooks law may ultimately overtake a legal project, and squeeze it to death: too many cooks . . .
A brief is usually subjected to rigid page limitations, and must be delivered up subject to a rigid (and usually short-fuse) time deadline. This is not the stuff for which large numbers of hobbyist contributors can be useful. Where legal research must be complete, it must be COMPREHENSIVE, and where it needn't be complete, it needn't be deep at all.
More important, the twenty pages of a legal brief must persuade. Advocacy is quite different from merely "getting it right." There is never room in twenty pages to give a complete and comprehensive analysis of everything relevant -- but twenty pages is the space in which you must give ALL the analysis of everything important. You must pick your BEST shots, focus on your BEST issues, and present them in their BEST light. Then, one must find the theme, the overall single "gist" of the argument, and weave those arguments therein, so that the judge or judges reading the brief are drawn in and buy into the rest of the story.
This is the kind of stuff for which one mind works better than two, at least after the brainstorming. Sure, it is helpful to have a few more eyes passing over a work to help cite-check and proofread the brief. Sure, it is helpful to have many people providing access to the obscure "home-run" cases when you can find them, if they can find them. But ultimately, someone needs to sift through these myriad claims of genius "finds," to determine their merits and relative weight.
In law, it is the FOCUS and HONING of an argument, not merely a comprehensive analysis, that wins the day. In my view, the Brooks law communications may well quickly defeat the possibility that a brief can be improved by an open law analysis.
At the end of the day, debugging a brief is not a big deal. Cite-checking twenty pages of brief's cases isn't that hard. Fifty people doing it doesn't make it much better.
The economies of scale that make open source work just don't seem to fit into the world of legal research and briefing. I agree with Seth and others who manifest skepticism that OpenLaw is simply an attempt to leverage the hype and panache, without the real and meaningful benefits, of open source.
This is not to say that legal volunteerism is unimportant. To the contrary, it is essential. Better pro bono publico work may well be improved by a network of (a moderate number of) well-wired attorneys working together in smaller bits, but with a central cathedral focus. (It is also a wonderful opportunity to make pro bono work fun!) If this is openlaw, I'm all for it. But it still is just law in a cathedral, albeit with wires, and not in the bazaar.
My point is that computer geeks are rarely lawyers. I Am, as they say, Not a Lawyer. Nor are you, I'm willing to bet.
The answer to most legal questions is "ask a lawyer", not "ask Slashdot". Would you hire a programmer to write code? Hell, I wouldn't even hire most Slashdotters to write code -- and they know more about that than they do about the law.
"Christianity neither is, nor ever was a part of the common law." --
--
Industrial space for lease in Flatlandia.
It is possible that I may have misread/overread what was written there and misunderstood your response, but I don't see how your remarks are in any way responsive to mine, or to the subject matter of the article.
Perhaps you misread the article? The OpenLaw project is about a methodology for developing legal arguments in ongoing cases, and has nothing (except in the most indirect sense) to do with lawmaking or participatory democracy.
I'm not sure their discussion mechanism actually works; I don't see any items other than the ones the OpenLaw staff posted, and at one point I got the message Warning: Uninitialized variable or array index or property (phorum-collapse-general) in home/httpd/html/msdoj/discuss/read.php3 on line 271. So they need to do some debugging.