Naming Open-Source Software
Suppose your favorite lunch spot offered you a glass of sweetened, carbonated water, caramel-colored, with natural and artificial flavors and caffeine. Would you drink it? Would you want to know who made it? Would you want to know in advance that your drink will taste like the sweetened, carbonated water that you enjoyed so much several days earlier?
Now, supposed your favorite lunch spot offered you a Pepsi. Would your questions about quality (good or bad) and product consistency suddenly go away? What would you select if given the choice between a Coca-Cola and a Melvyn's Cola? Would you be more likely to select a product simply because you are familiar with its name and reputation?
We are all caught up in marketing. Television and other advertising media continually inundate us with product names that we almost automatically add to our vocabulary, as if they were words in the English language. But these product names are not words in the traditional sense, nor are they intended to be so used. Terms like Windows, Apple, Java, Apache, Linux, Jabber and JBoss are marketing names—trademarks. When carefully selected and protected, and through effective marketing, trademarks can become badges of quality, expertise and reputation.
Trademarks are potentially among the most valuable assets of companies that market free and open-source software. For some projects, a trademark is much more important than the license under which the software is distributed.
Trademarks are a form of intellectual property, but they are very different from patents, which protect invention; copyrights, which protect expression; and trade secrets, which protect a company's confidential information. Trademarks are brand names of products or services. They serve to protect the reputation of a product.
More specifically, a trademark is a word, name, symbol or device used to identify a company's products and to distinguish those products from the competition. A service mark is the same as a trademark except it is used to identify and distinguish services rather than products. A trade name identifies a company rather than that company's individual products or services. The same symbol might function as a trademark, a service mark and a trade name, depending on the context in which it is used. Here I will generally use the term trademark and ignore the subtle distinctions of service marks and trade names.
A company doesn't acquire trademark rights simply by choosing a trademark or even by stating its intent to use it. Trademarks (or service marks) in the United States are established by actual use in conjunction with specific goods (or services). There are advantages to registering trademarks with the US Patent and Trademark Office, but registration alone doesn't make a trademark valid or valuable. Only actual use of a trademark on goods, and a marketing campaign to breed familiarity among consumers, can create a valid and valuable trademark.
Free and open-source products pose difficult marketing problems. The licenses under which such products are distributed require the distribution of source code and permit the creation and distribution of derivative works. It is difficult for a distributor of such products to compete on price alone because almost any knowledgeable company can undercut the price by simply copying the original software.
Trademarks can be particularly useful in this kind of environment. First, a company needs to demonstrate that its software is of high quality, reliable, efficient, feature-rich and user-friendly. It can promise continual enhancements, product support, user groups and undertake other goodwill-creating activities. Then over time, through marketing efforts, that company's customers will begin to associate its trademarks and service marks with those products and services. New or repeat customers will pay for goods and services they perceive to be worth the price, and they will select preferentially products whose trademarks they identify.
Trademarks can also limit certain kinds of forking of free and open-source code. While your software license may allow others to make derivative works of your code, the license doesn't allow (indeed, there is a legal reason why it cannot allow) others to apply your trademark to their derivative works.
In any industry where it is not technically difficult to create a new product, whether it be the cola beverage industry or the free and open-source software industry, trademarks and service marks can provide the best protection for a company's products and services.
We see this every day when customers order Coca-Cola and Pepsi rather than Melvyn's Cola. That is why customers buy Red Hat Linux rather than El Cheapo Linux. That is why Apache servers dominate the Web, rather than servers based on generic copies of the Apache code.
And that is why, if you are wise in selecting, perfecting and using your trademarks and service marks, you can protect the market for your free and open-source software products from competitors who merely want to copy your work and make money off your well-earned goodwill.
In future articles, I will describe how you should select a good trademark and explain what you need to do to use it and protect it properly.
Legal advice must be provided in the course of an attorney-client relationship specifically with reference to all the facts of a particular situation and to the law in your jurisdiction. Even though an attorney wrote this article, the information in this article must not be relied upon as a substitute for obtaining specific legal advice from a licensed attorney.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Why Python?
- Linux Systems Administrator
- Tech Tip: Really Simple HTTP Server with Python
- Build a Skype Server for Your Home Phone System
- Dynamic DNS
31 min 32 sec ago
- Reply to comment | Linux Journal
1 hour 30 min ago
- Reply to comment | Linux Journal
2 hours 20 min ago
- Not free anymore
6 hours 22 min ago
10 hours 9 min ago
- Reply to comment | Linux Journal
10 hours 17 min ago
- Understanding the Linux Kernel
12 hours 32 min ago
15 hours 1 min ago
- Kernel Problem
1 day 1 hour ago
- BASH script to log IPs on public web server
1 day 5 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?