Red Hat Asks for UCITA Reversal
OSS advocate writes "According to this NewsForge article, Red Hat has engaged the services of Carol Kunze (ucitaonline.com) to try to convince the National Conference of Commissioners on Uniform State Laws to take UCITA back. There's a list of email addresses in case you want to send the commish a letter yourself." Red Hat's letter is a good start.
Thank you Redhat for not only helping yourself, but the open source community as a whole.
As an established business, your views will hopefully make it more difficult for the commissioners to justify such laws.
Gee, I'm so glad that in a time of falling tax revenues for so many states, counties and municipalities, that en masse they're going to staple themselves to the mast of the good ship S.S. Licensing Schemes. Full Steam Ahead. Say, what's that sinking feeling?
"There is a thin line between ignorance and arrogance, and only I have managed to erase that line." - Dr. Science
...ok. Time for bed.
A programmer is a machine for converting coffee into code.
How about reversing DMCA, shortening the span of software patents, reversing copyright lengthening, passing laws about *not* passing laws to enhance the *life* of businesses?
"Ten years from now, they could do it in a few seconds." -- The Racketeer of the Hellfire Club, 1993, Phrack 42
Dear Senators,
I am not an electronics engineer (as per having a paper degree), however I
do engineer electronics that could be said to be equal to someone who has
such a degree. I am an inventor, a musician, a digital creator, an
electronics tinker'r whatever you would like to call it, the name really
doesn't matter as much as the intent. I take thoughts and create material
objects, it doesn't take a degree to do what I am saying. I would also
remind you I am a vetran of the United States Air Force as well as I am
currently a voter (libertarian.) Without creative folks such as myself
and others like Henry Ford, Thomas Jefferson, you wouldn't even have
electricity, lights, computers, and cars.
Statements like the following by the MPAA, "in order to help plug the hole,
watermark detectors would be required in all devices that perform analog to
digital conversions." are not very carefully thought out statements, they
worry me, as to exactly what is going on in my government and here is why.
At least four years ago, I was heavilly into building electronics, I was
engineering a device that converted from analog to digital and from digital
back to analog again. (It was basically a digital audio delay.) I started
with parts from old electronics that people had thrown out on the street. I
have spent many hours desoldering chips, and parts from electronics which
were discarded in this fashion.
I have a full personal library of technical manuals (several different
years) from Motorola, Texas Instruments, Analog Devices, Supertech, Zillog,
Intel, mosteck, National Semiconductor and MANY OTHERS. Basically I can
look up part numbers from nearly any chip and figure out how it works and
what I can use it for.
Durring the course of events I decided one day I wanted to build a digital
delay for my guitar. There were many D2A A2D chips to choose from, flash
converters, etc the list is endless. I won't bore you. To make a long
story short I decided to go with parts from Analog Devices for my A2D/D2A.
I ended up buying some parts from Analog Devices specifically part ADJ569JN,
and I used some memory that I had laying around from all the parts that I
collected. I had to build a counter circuit to make the ram work in each
memory segment for each sample. A fully blown electronics engineer I am
not however such an engineer can easilly verify what I say to be true. So,
basically the MPAA want's someone like me to add a watermark detector to
my digital audio delay. Well first off I do not care about digital
watermarking, that is not my problem, that was not part of my design, and
to be forced to learn how to engineer this into my design is...well insane.
And anyone who passes or suggests such laws is also...insane. So, before
you quickly dismiss me off as some wacko, I would suggest that those who
push such bills and legislation are the true wackos. Where I would rather
be more concerned about removing digital noise from the output (all digital
circuits have noise) and figuring out creative methods of how to modulate
the clock circuit for different sound effects, they *MPAA* would have me
spend my time working on how to put their watermark detector into my
circuit. Frankly with the lack of information (I had to buy books from
overseas to explain how to do digital to analog and analog to digital) that
is available in the United States I would warn those who would decide to
pass such legislation that a.) unless your ready to nuke our economy b.)
ready to make the purchase of electronics illegal. c.) have the brightest
engineers leave the United States d.) anger the public e.) ruin music
f.) ruin creativity by the future youth who take electronics classes in
schools g.) probably ruin your own political career then do not pass such
insane legislation. It is _not_ your place to make such decisions in my
opinion since you are _not_ qualified.
If your so smart to pass such legislation, answer me this. How many memory
segments will I need to use from my 8x8 ram to incorporate digital
watermarking into my Digital Audio Delay Device? Which pins does it need
to be connected to on the AD7569JN? What CHIP (which has the digital
watermarking in it) do I have to buy? How much does it cost? Who is the
maker of said chip? What is the part number on the chip? Is it compatable
with my circuit? Does this chip have any digital noise associated with it
which will bleed into my device? If so how do I supress such digital
noise? If your not ready to answer these questions, then your not ready to
pass this legislation.
I know that most senators and lawyers are not electronics (digital and analog)
experts so what qualifies them to pass law on a technology they do not fully
understand? Furthermore it comes to my attention that other bills like
the SSSCA which have had their name changed over and over, are insane,
poorly thought through, placing the burdon on the wrong folks to solve the
problem.
It also seems to me there are already laws against piracy, so no further
laws are needed. Another thing that upsets me is how these bills slip
through without even consulting the public, or letting someone like me
vote, in many cases government websites are broken and feedback forms
do not work, other times phones are busy, and nobody is around to answer
them, and some political candidates have NO EMAIL ADDRESS! this is
unacceptable. Forcing me to physically stand face to face in order to
get my point across is bad. Forcing me to make political contributions
for legislation is also bad.
Although I am no longer designing electronics at this current point in time
I may want to again. And I know that others like myself in the future will
become interested in Transmitters, Receivers, Digital and Analog
electronics, what in effect you are doing is pushing a new electronics
law (A very stupid law) into the natural laws of electronics. Especially
the young should be encouraged to get into electronics design early on in
their lives. It keeps them out of trouble and away from drugs and alchohol.
Another thing that frankly angers me is by passing the CBDTPA act you are
condemning me for using Linux, which is an operating system that does what
I want. You would be making the personal computer into some bastardised
piece of equipment that plays mickey mouse videos, when I do not even want
that on my computer at all. I use my computer to write code. In some
cases the code can do the exact same thing my earlier discussion on the
AD7569JN does. I do not want my resources being used by the media.
I want my resources being used for what I purchased them for. And that
is development. CBDTPA stifles development. It sacrifices the IT sector,
at the expense of the MPAA.
I do not pretend to have the money that the MPAA has. However is is
unfair to destroy education about electronics and dumb down america.
Which is, despite all, the BEST COUNTRY IN THE WORLD!
I may not live long enough to get back into electronics design again, but
PLEASE DONT ruin the future because of a damned mouse.
Thank you for reading my comments.
If, like me, you've never heard of UCITA and are looking to form your own opinion, a summary is available here:
http://www.ucitaonline.com/slhpwiu.html
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
No need to mod this up...
TO: NCCUSL Commissioners
FROM: Carol Kunze
RE: Discussion of UCITA on July 29, 2002 at NCCUSL Annual Conference
* * * *
I write to you on behalf of Red Hat, Inc., a software services company which also distributes the open source operating system Linux.
We are making what we appreciate is an extraordinary request - THAT YOU REVERSE THE 1999 DECISION TO ADOPT UCITA.
UCITA was written for the proprietary (commercial, for profit) software industry. It does not reflect the practices of the open source community, nor the expectations of parties to an open source transaction.
Open source software is primarily written by communities of users, often
through non-profit organizations. Open source software can be freely copied, freely modified and the source code is freely available to enable users to do so. All copies can be freely redistributed.
This means that everyone is free to service, adapt, fix bugs and write compatible software. The developer has no monopoly on servicing the product.
Because open source software can be freely distributed, the distributor may have no contractual relationship, or indeed even know many of the authors of the code which it is distributing.
UCITA is written for transactions involving a single license, where an agreement is concluded, where the distributor has a direct or indirect contractual relationship with the developer, and where there are profits to support warranties. Many open source software transactions do not conform to this model in any respect.
The open source community has created its own set of practices and norms that differ widely from the commercial rules that UCITA adopts as the standard. UCITA does not reflect the open source community's development model, its distribution model, its license terms, nor its general expectations.
UCITA may bring certainty to software licensing law, but only for proprietary software distributors. NCCUSL should not adopt a law with default terms which, if applied to an open source transaction, would convert it into a proprietary transaction against the will of the user and the distributor.
NCCUSL should not adopt a law which threatens the existence of an important and growing alternative in the software market. By adopting proprietary practices as the norm, UCITA attempts to force open source to conform to a model based on profits and warranties.
This would destroy open source.
It is not for NCCUSL to decide which form of software development and distribution to legally validate. NCCUSL SHOULD EITHER LEGISLATE A SOFTWARE LAW WHICH REFLECTS BOTH PROPRIETARY AND OPEN SOURCE PRACTICES, OR IT SHOULD REFRAIN FROM LEGISLATING.
Red Hat respectfully requests that you vote to reverse the previous adoption of UCITA.
Sincerely,
Carol A. Kunze, Esq.
901 Cape Cod Ct
Napa, CA 94558
707.966.5211
fax 707.371.1807
ckunze@ix.netcom.com
Linux really seams to need a large lobby group that plays golf with the legislators like the comercial software industry has. Linux has a large and vocal group but a group without funds to lobby (put money in politicians pockets). There should be another way to reach to politicians but today money seems to be their primary goal in life tightly followed by power. One possible way would be to try and get the larger companies using linux (AOL, RH, SuSe, IBM etc) together into a group that looks after the interest of open source. I have a strong feeling that all the little companies combined into one entity can make a difference. Other industries have common groups that tends to thier lobbying need so it shouldnt be impossible for open source to have one either. I know there are groups out ther already but im talking about a group of companies, not individuals. Individuals are lucky if they can make even a blipp on the radar whereas if IBM and a group of other companies combined would make the radar look like a christmas tree.
HTTP/1.1 400
For those of you who (like me) have a limited knowledge about the UCITA, Infoworld as an excellent summary of what it is and the problems with it.
What it essentially seems to do is make EULA's legally binding and allows them to be undisclosed until after the sale is made. It doesn't seem so much anti-open source as it pro-commercial software.
The future isn't what it used to be.
NCCUSL Commissioner Email Addresses
Alaska
art@dillonfindley.com
Deborah_Behr@law.state.ak.us
lsjkj@aol.com
wgc@customcpu.com
Alabama
RepGaines@aol.com
rmccurle@law.ua.edu
tjones@law.ua.edu
bruce@hwnn.com
Arkansas
jpender@pmppa.com
larry@arkleg.state.ar.us
david@nixonlaw.com
pcarroll@roselawfirm.com
jdeacon@barrettdeacon.com
Arizona
henderson@nt.law.arizona.edu
l.lemon@azbar.org
tberg@fclaw.com
California
bion.gregory@ccusl.ca.gov
darlinghallrae@compuserve.com
elihu2000@aol.com
wburke@shearman.com
senator.sher@sen.ca.gov
nsterling@clrc.ca.gov
Pamela_Chin@parsons.com
Ronald.phillips@pepperdine.edu
williamsrc@aol.com
Colorado
charley.pike@state.co.us
russgeor@sni.net
lw2demuth@worldnet.att.net
tomg@grimshawharring.com
bkreplep@aol.com
Connecticut
bhawkins@goodwin.com
david.biklen@po.state.ct.us
john.langbein@yale.edu
pavetti@aol.com
lmorgan@rjmlawct.com
WBreetz@law.uconn.edu
District of Columbia
bkass@kass-skalet.com
cbrookinshudson@dccouncil.washington.dc.us
zeldonj@dcsc.gov
efdyke@venable.com
jamescmckay@yahoo.com
Delaware
mhoughton@mnat.com
ann.c.stilson@law.widener.edu
robinsonr@ce.net
Florida
lstagg@akerman.com
ecutl@carltonfields.com
ehrhardt@law.fsu.edu
hkittles@hklaw.com
jessen.linda@leg.state.fl.us
jmorse@law.fsu.edu
Georgia
mwmacy@aol.com
rwellman@arches.uga.edu
rgm@hbss.net
Hawaii
ekent@hawaii.edu
jachanin@hotmail.com
toyofuku@pixi.com
hiaglegis@yahoo.com
lewart@goodsill.com
takayama@capitol.hawaii.gov
Iowa
cdmahon@aol.com
Sheldon-kurtz@uiowa.edu
david.walker@drake.edu
Idaho
dghiger@stoel.com
pckm@marshallbatt.com
Illinois
ctabb@law.uiuc.edu
hjs@arnstein.com
mbgetty@aol.com
r-picker@uchicago.edu
richwards@legis.state.il.us
tryder@gtec.com
tjmccrackenjr@ameritech.net
jeremiah@hopsut.com
harry_leinenweber@ilnd.uscourts.gov
diane_ford@gov.state.il.us
Indiana
GBepko@iupui.edu
S40@ai.org
mts@starkey-law.com
hpatchel@iupui.edu
Kansas
elpom@networksplus.net
mroneal@southwind.net
zzconc@washburn.edu
temert@terraworld.net
hite@hitefanning.com
Kentucky
dcetrulo@email.msn.com
scawood@mmlk.com
johngillig@lrc.state.ky.us
john.spangler@lrc.state.ky.us
wswilborn@aol.com
Louisiana
guillotj@legis.state.la.us
henry.gabriel@sstar.com
wdh3770@aol.com
Massachusetts
smithee@bingham.com
stephen_chow@pscboston.com
Maryland
kingwebnet@aol.com
Maine
Bcoggeshall@PierceAtwood.com
rrobinson@rkmlegal.com
marsulu4@aol.com
Michigan
arichner@house.state.mi.us
ggulliver@lsb.state.mi.us
jjwhite@umich.edu
rwebster@clarkhill.com
sencdingell@senate.state.mi.us
Minnesota
HARRYMW@msn.com
robertstein@staff.abanet.org
mndavies@aol.com
harriet.lansing@courts.state.mn.us
hhaynsworth@wmitchell.edu
michele.timmons@revisor.leg.state.mn.us
Robert.Tennessen@gpmlaw.com
Missouri
jfarnold@lashlybaer.com
englishda@missouri.edu
mferry@gatewaylegal.org
fryp@missouri.edu
heinszt@missouri.edu
henningw@missouri.edu
Mississippi
tbeck@mail.lbo.state.ms.us
ncarlton@ltindall.com
navyjag@aol.com
iq.attys@usa.net
pwatson@mail.house.state.ms.us
hooper@olemiss.edu
smdavis@olemiss.edu
Montana
eck@selway.umt.edu
gpetesch@state.mt.us
Jcnelson@state.mt.us
jmazurek@state.mt.us
North Carolina
mbenfield@compuvision.net
flewis@mail.jus.state.nc.us
rbillings@law.wfu.edu
snichols@mail.jus.state.nc.us
wnj@coa.state.nc.us
russell.walker@ncisd.nc.us
North Dakota
oanderson@ou.edu
dhogue@ndak.net
jburingr@state.nd.us
mike.unhjem@bcbsnd.com
wstenehjem@aol.com
lklemin@state.nd.us
Nebraska
abeam@ce8.uscourts.gov
hsperlman@unl.edu
mgmlawnp@nponline.net
jpepperl@unicam.state.ne.us
ruth@nol.org
New Jersey
jdonegan@prsmo.com
New Mexico
ciscolaw@hotmail.com
desiderior@law.unm.edu
jpburton@rodey.com
pplarragoite@hotmail.com
paula.tackett@state.nm.us
mlo1@7cities.net
Nevada
fdaykin@lcb.state.nv.us
erdoes@lcb.state.nv.us
mjames@sen.state.nv.us
wasserman@lcb.state.nv.us
New York
jvigdor@boylanbrown.com
rlong@cglawllp.com
rsmith@dpw.com
SSternLaw@aol.com
normlg510@aol.com
Ohio
AttyBoris@aol.com
lee_mccorkle@wendys.com
rogers.23@osu.edu
sfisher@arterhadden.com
w-evans@onu.edu
Oklahoma
duchessb@swbell.net
lwhinery@ou.edu
Oregon
Gregory.A.Chaimov@state.or.us
jwillis@schwabe.com
mwalters@wrcdlaw.com
Pennsylvania
creitz@law.upenn.edu
jsheehan@state.pa.us
stuckey@state.pa.us
haf3@psu.edu
poulin@law.villanova.edu
Rhode Island
cmassouda@rilin.state.ri.us
judge_William_Hillman@mab.uscourts.gov
South Dakota
glebrun@lynnjackson.com
Law@DemJen.com
scott@jhmmj.com
dgregers@wfss.com
Tennessee
ctrost@wallerlaw.com
ellen.tewes@legislature.state.tn.us
rclark@armstrongallen.com
Texas
htindall@tindallfoster.com
leonard.reese@tlc.state.tx.us
rsatterwhite@stubbemanlawfirm.com
mmpc@texoma.com
p.guillot@airmail.net
marianne_auld@baylor.edu
Utah
RMartineau@SCMLAW.com
Virginia
emiller@leg.state.va.us
pamela_sargent@vawd.uscourts.gov
ccring@ober.com
jfrench@leg.state.va.us
ktaylor@t-mlaw.com
Virgin Islands
ytharpes@mail.senate.gov.vi
tbolt@vilaw.com
Vermont
cgravel@gravshea.com
clisman@lisman.com
lsmiddy@vermontlaw.edu
rcassidy@hoffcurtis.com
daglaw@sover.net
Washington
J_m.appelwick@courts.wa.gov
raron@u.washington.edu
usmjcimbr@hotmail.com
cooper_de@leg.wa.gov
Wisconsin
bruce.munson@legis.state.wi.us
ljbugge@itis.com
peter.dykman@legis.state.wi.us
Rep.Gundrum@legis.state.wi.us
Sen.George@legis.state.wi.us
Sen.Huelsman@legis.state.wi.us
West Virginia
fordlaw@inetone.net
jmcclaugherty@jacksonkelly.com
stamps4@aol.com
UCITA is bad for users of Free Software, but it's also bad for users of proprietary software. It lends validity to the concept of a shrink-wrap license, which means the software vendor can impose pretty much arbitrary restrictions on the use of a software package. Suddenly all those EULAs become legally binding contracts. All it would take to restrict your rights as a customer is a list of terms. It's way too easy.
Just imagine restrictions on the number of people allowed to use a software program, or website terms stipulating that whatever you write becomes the property of the company behind the website. Such terms are not unheard of, and UCITA would turn these and many others into binding restrictions.
"In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
It seems to only apply where there is a *contract*, which isn't relevant to most OS Projects.
It might be bad for end-users if it makes the "we offer no warranty whatsoever but we take your first born child" EULAs valid, but it seems irrelevent to those of us who never use them.
Tell me how that's wrong...?
You're only jealous cos the little penguins are talking to me.
I said UCITA is "bad for users of Free Software" when I really meant to say that it's bad for Free Software in general (the FSF has a good explanation of it).
Having said that, UCITA is indeed bad for users of Free Software. When Free Software authors are held liable for defects while software companies are allowed to disclaim liability (exactly the opposite of the way it should be!), both the developers and users of Free Software suffer. When proprietary vendors are allowed to create closed and legally inaccessible file formats, the developers and users of Free Software suffer greatly.
UCITA is an immense threat to anybody who is not a big corporation.
"In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
It should be 644 wich is that the owner can change it and everyone lese just read it. 666 is evil and if anyone can write to it it isnt safe. Take a look at what services you run and also look for new accounts. Install a firewall or go the fast lane and use something like firestarter that do it for you. Change your passwords to anything very hard to guess and throw a dictionary at. Most breakins is still done with passwords guessed or socially engineered. The bad thing about legit logins with stolen passwords is that they are hard to detect if you use your computer much.
HTTP/1.1 400
http://www.ucitaonline.com/slhpmau.html#5
In this page UcitaOnline tells something about linux and free software. I'have some trouble to understand the real sense (perhaps becaus I'm Italian and I'm not aquainted with polital English).
Any comment?
Pila
---Pila---
example:
"God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
Dear Red Hat,
We have received your letter dated 29 July 2002 requesting that we rescind the UCITA regulations. Rest assured that we have been completely unaware of the deleterious impact these regulations might have on open source software; had we known we would never have adopted them at all. The Commissioners apologize for any inconvenience this has caused, and will now move to reverse UCITA's adoption immediately. Thank you for bringing these issues to our attention, and please don't hesitate to contact us again if you have any further concerns.
Sincerely,
The National Conference of Commissioners on Uniform State Laws
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
I have read the articles here and on several other sites, and I've read many Infoworld articles over the past few years on UCITA, and I _still_ don't see how it is damaging to Open Source. As pointed out earlier, this page seeks to address the concerns of Open Source advocates, and does a good job of such. I have understood the dangers of large proprietary corps like M$ being able to turn software off and abuse consumers in other ways, but I have not been able to find a single credible reference to how UCITA will hurt Linux developers or users. Can someone post a rational and clear explanation using traceable references to UCITA language that demonstrates the potential for harm? I'm certain that many others would also appreciate clarification.
Thanks
Great, how many of these people really need penis enlargers? Or hot naked coeds? Hmm, then again, they're politicans, they probably have enough of that. OTOH, at least it would wake them up to spam..
What time is it/will be over there? Check with my iPhone app!
UCITA is pro-commercial allowing the crappy shrink wrapped cr@p to live on. If it was rversed, it would help the end user by making the companies that made it more respnosible.
Seeing that, me thinks that it would also help open ource by making it harder for closed source companies to compete.
Think about it, what if M$ HAD to fix all the bugs with M$ SQL...could it compete with MySql ?
-- I doubt, therefore I might be.
Now, I used a EULA (if you like) on my installer to disclaim responsibility if the program breaks and other various stuff.
Now, as I see it (and please correct me if i'm wrong) the UCITA would benifit me because my disclaimers would be legally enforcable. If the UCITA went away, then I would be stuck in a rather tricky situation where I could be held liable for all the stuff that my licence disclaims.
Or am I wrong? Can someone please explain how the UCITA would appect the hobbyiest programmer like myself that doesn't use the GPL (and hence doesn't distribute source).
Avantslash - View Slashdot cleanly on your mobile phone.
See: http://www.nccusl.org/nccusl/UCITA-2001-comm-fin.h tm.
It has a report that discusses many aspects of UCITA.
-- Esa Pulkkinen
It's a set of default laws regarding software development/distribution that apply where the parts have not agreed on anything. Plus a set of mandatory laws which can't be disagreed upon "to protect the user".
Does this mean that UCITA removes the responsibility from the shoulders of the luser in case something goes wrong?
Will it allow people to treat their computers like imported au pairs, with any results being the programmers responsibilty? What if someone deletes all their stuff with fdisk?
What if they use 'find / > /dev/hda'? Who's to blame?
I would assume that if the user is stupid and root at the same time, that's his/her/its problem, and no matter how many laws you have, idiots can only blame themselves for being idiots.
Of course, I'm not from the USA. In my country, Norway, lawyers can't even take percentages of the winnings to keep idiots from the nothing-to-loose suing. (And may I say, that's the best law since Thou shalt not kill)
If any of the above are the developers fault, can't you just put a notice on kernel.org/gnu.org that "You have entered restricted web space, please leave at once. Do not download anything." I'm sure you could somehow convince a jury that the luser 'hacked' kernel.org/gnu.org to gain access to data that wasn't intended for him/her/it in the first place (I mean, if it's illegal to use people's wide open SMB shares, surely the same applies to HTTP?)
Yeah ok the grammar may not be "Senator level", but the parent has made a good point! I'm glad I'm in the UK; the current patent, DMCA etc laws in the US completely stifle any possibility of anyone coming up with any new invention or marketable idea. Sure, you might be able to start a ball rolling, but as soon as it looks like your idea might make money you'll find [INSERT SOULLESS CORPORATION] unleashing their little pet lawyers at you to either (a) convince some half-witted jury they own the patent or (b) bankrupt you, then take the idea...
I'm almost glad I live in the UK...
Code, Hardware, stuff like that.
So if I supply people with products based upon freely available open source code, and these people pay me for these products, they should expect the products to work properly without damaging their equipment or data? Some people sure have a lot of nerve...
Of course, you may have some people with ear-pieces, wearing black suits, come to your house because of it. Then again, it seems all you have to do is leave off the return address and the FBI will NEVER be able to find you. Perhaps I shouldn't have mentioned that... If you don't know enough not to include the return address, you ought to spend a few years in jail.
Note, sugar will work in place of coffee creamer. Flower may even work in a pinch (but be warned, you may be mistaken for a scientific genius).
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Dear Red Hat,
We have received your letter dated 29 July 2002 requesting that we rescind the UCITA regulations. Rest assured that we have been completely unaware of the deleterious impact these regulations might have on open source software; had we known we would never have adopted them at all. The Commissioners apologize for any inconvenience this has caused, and will now move to reverse UCITA's adoption immediately. Thank you for bringing these issues to our attention, and please don't hesitate to contact us again if you have any further concerns.
Sincerely,
The National Conference of Commissioners on Uniform State Laws
PS: As you know the common practice of democrassy in this country, I shall remind you that my account number is 57895213582356AZ5574 at First Geneva.
Thanks for your contribution.
What the UCITA does is make the click-through and shrinkwrap licensing have the force of law. Though I don't like this prospect, it can be used to keep free software authors out of legal trouble.
The society for a thought-free internet welcomes you.
It looks like theyve got the techies to write something again... Doh..
Here's my list of bad things and suggestion
If anyone can reply with an even better corrected we may have somthing worth sending..
'I write to you'
you don't say?, put this at the end sig e.g. bill gates, OBO Microsoft.
'on behalf of Red Hat, Inc., a software services company which also distributes the open source operating system Linux.'
Ok I'm a linuxish techie I understand distribution in this context, what they do is 'Provide an intergrated package of open source and proriatary software running on a Linux operating system[ and supporting services].'
This isn't great but it's a lot better, 1st I've mentioned proriatary software/closed source software which would work under UCITA. The writer could then use this as a hammer to beet UCITA over the head with. X software can meet the UCITA, but an equally good piece of software cannot because if is open source and not cenrally supported, but somehow we manage to get the support we need etc....
Ok I've attacked the first paragraph
NCCUSL Commissioners,
Red Hat, Inc., has build up a strong businness provding software services and the Red Hat Linux distribution, an intergrated package of, open source and proriatary software running on a Linux operating system.
We are making what we appreciate is an extraordinary request. That you reverse the 1999 decision [passed by who] to adopt UCITA.
Personally I think the 'what we appreciate ' is a bit pointless if you didn't appreciate someting then you wouldn't have expressed an opinon about it[that it is extraordinary]
I think that sells the argument a bit better and gives Red hat some more ammunition.
thank God the internet isn't a human right.
I sent out the letter to the people in Michigan. You know what I got in return?
"Matthew, Do you know the meaning of spam? I have now received the same
message four times this morning. You are not helping your case. JJW"
from James J. White [jjwhite@umich.edu]
Get this mo'fo'
The dingo ate my sig.
what if M$ HAD to fix all the bugs with M$ SQL...could it compete with MySql
MySQL isn't even as good as Access, let alone SQL Server. My SQL is more like a free version of FileMaker.
you should check out this bio of our state's only commissioner and here is a list of his law firm's clients. This can help you structure the e-mail you send to be taken more seriously. Note the number of large corporations on this list...hopefully he isn't too selfish and will listen to his constituents.
Nope, no sig
From: CompuServe Postmaster
To: Blind.Copy.Receiver@compuserve.com
Subject: Undeliverable Message: Delivery report for message to darlinghallrae
Date: 25 Jul 2002 10:10:47 -0400
Message "UCITA Reversal", sent at 10:10 EDT on 25-Jul-02, could not be
delivered to darlinghallrae at 10:10 EDT on 25-Jul-02 because the recipient
mailbox is full.
"Nothing was broken, and it's been fixed." -- Jon Carroll
If, like me, you've never heard of UCITA and are looking to form your own opinion, a summary is available here:
I hope, before you formed that opinion, that you crossreferenced the UCITA promotional link you provided with other, more balanced links, almost all of which are critical of UCITA (including every software manufacturer, be it open source or proprietary, with the exception of Microsoft which as everyone here knows has its own, monopolistic agenda).
Do not be misled by one promotional site being run by the very persons who introduced the legislation to begin with. They are not trying to give you a balanced perspective on the issue.
The Future of Human Evolution: Autonomy
Barn.Door.Close
Error 1306: Horse not found.
It's already gone through the system, it's already become law. Most importantly as far as they're concerned, it's alread been paid for.
What are the odds your so called 'public servants' will suddenly have a change of heart, mend their evil ways, and reverse it?
- Bob Frankston
Build stuff. Stuff that walks, stuff that rolls, whatever.
I have opposed UCITA since it was hijacked by the BSA in 1995. I remain
on the standby drafting committee to try to moderate its effects. The
Massachusetts delegatiion, supported by the Governor's Office, the
Attorney General and many legislators, oppose UCITA and are unlikely to
adopt it. I do agree with the view that it establishes a certain business
model (1992 shrink wrap) that is inappropriate at this time of change in
business models, both to new ones and back to old ones, and that it is
important to oppose UCITA at the national level.
Thank you for your input.
Steve Chow
Mostly I got back autoresponders, but I did get this message, so at least open-source has one friend, even if not for the same reasons:
It seems to me that the following clause, added to the GPL, would take care of a lot of these problems:
That is, if I can't offer it to you without warrenty, I don't offer it at all, and you have no right to use it. This should at least provide grounds for a countersuit.How do the people who write these laws stay in office?
How do they stay ALIVE?
OFS(Open file Standards) are a cause that we can get support from all computer users, as it benefits Linux but also Mac, Solaris and even M$ OS users.
A good argument to use is that the requirements to make information open and publicly available is discriminatory to poor people if the file standards require paying the M$ tax. An amendment to the FOIA (Freedom Of Information Act) at the federal and state levels is what to ask for. When the Feds require open file standards, Linux will become much more competitive. Once the files standards are open, Linux can easily succeed.
Be aware that GIF, JPG, are not open standards. Even PDF cannot be modified to add functionality. If Adobe decides to come out with a super set of PDF and collect royalties they have every right to do so. What we should push for is for the government (particularly the Federal level) to support open standards, free to all, much as the bureau of standards has done for units of measure (let's hope no one claims a patent on the meter).
Furthermore, we need to ask that all the extensions of government web pages be free of proprietary structures so that any browser will be assured of displaying the page content without depending on proprietary plugins.
A sample letter for your federal and state representatives is at http://xtronics.com/reference/openfiles.htm
Here's a better one. (Yes, it's Stallman, and I find him annoying too. But at least it's just as unbalanced as the original link, which was probably planted here on /. by a UCITA lobby group.)
Plus it's on the EFF website, which is an organization I don't find annoying.
It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
This would have been more helpful if they hadn't left their offices for the conference by now.
There is at least one organization out there dedicated exclusively to amending/overturning UCITA. They go by the name AFFECT (Americans For Fair Electronic Commerce Transactions). Unsurprisingly, they're made up largely of librarians and IT types.
If you're interested in more information about the act, or maybe going a step further than just sending an email you might check out their websit.
http://www.4cite.org/
Now let's see.
How much did Red Hat donate to our last campaign?
Nothing, I see. And how much did Microsoft give us?
Oh.. Nice number, like it. Put their mail in the trash nothing that's going to threaten my campaign budget is going be released from my office.
Or green, independent, etc. They'll dismiss you as a nutball, and assume that your vote won't count anyway. Say "I have not decided whether to vote Democrat or Republican."