Get Legal - but not too soon
[Posted May 3, 2006 by corbet]

The OpenOffice.org marketing team, sensing an opportunity in the latest
round of Business Software Alliance attacks on companies using "pirated"
software, has
announced the
"Get Legal - Get OpenOffice.org" campaign. It
features a cute logo (seen on the right) and a web page discussing the
difficulties in remaining in compliance with proprietary software
licenses. OpenOffice.org, of course, offers a way out: switch to free
software, make no license payments, and be entirely in compliance with the
law.
The heavy-handed techniques employed by groups like the BSA have always
been destined to play into the hand of free software advocates. Even
companies with strict "a license for every copy" policies (and strict
enforcement to back those policies up) can find themselves with unlicensed
copies of software on their machines. The BSA, with its rewards for
employees who turn in their companies and its police raids, can make the
cost of those unlicensed copies very high. And, even if a company is able
to stay in complete compliance, it bears the costs of license tracking and
software audits. So OpenOffice.org is right to capitalize on this
behavior; free software does, indeed, offer a way to avoid the expensive
hassles which can accompany proprietary code.
When LWN posted a pointer to
this campaign on May 1, however, the OpenOffice.org marketing team was
not amused. One participant exclaimed:
Jesus what an idiot. Makes you wonder if they're purposely trying
to wreck the campaign before it takes off.... I'm CC'ing this
message to lwn to see if someone can at least smack that poster for
us.
Your editor idiot, feeling suitably smacked, withdrew the
posting. It is certainly not LWN's wish to "wreck" the efforts of free
software projects.
This episode raises an interesting question with regard to how free
software projects deal with their user communities. The usual rule is
"release early, release often"; the idea being that the opportunity
to obtain input from a wider community should be taken at the earliest
possible time. There is little to be gained by holding on to work which is
intended to be released anyway.
That ethic appears to be changing in some places, however. Companies
perform free software work behind closed doors and release the result in
one big pile with the obligatory press release. Releasing code earlier, it
is said, is just an invitation to "bike sheds" and "stop energy," and an
impediment to actually getting the work done. And marketing campaigns are,
it would seem, so fragile that any visibility in the wider community
threatens to "wreck" them. So work must be withheld until it is finished,
ready to present itself in its final form.
It is worth asking whether press releases are really the
best way for free software projects to interact with the rest of the
world. A press release is fine as a way of gaining the attention of the
mainstream media, but there is little in our community which needs to be
kept secret until the PR has been officially distributed. It is hard to
imagine that the strong message behind the "Get Legal" campaign can truly
be compromised if the community knows, before the press release hits the
net, that such a campaign is being developed. In fact, it's even possible
that people outside of the core marketing group could have useful input
which could make the campaign stronger.
The value in the free software process is not just in the delivery of
something cool on a date picked by somebody in the marketing department - it's
in the process. Without the process, all you have is another
corporate product, albeit with less restrictive conditions and a nicer
price tag. At times, we may all be tempted by the idea of dispensing with
an open development process (and the community which goes with it) in the
name of faster development or a splashier release. But going that way has
its costs, and risks taking us closer to the proprietary systems that we
have worked so hard to replace.
(
Log in to post comments)