📄 00000044.htm
字号:
the use of a trademark as a way to make sure that such squatting <BR> activity does NOT happen. <BR> <BR> - Being "specific" is _good_. Being specific largely avoids the <BR> problem of many people/organizations wanting the same name. We had an <BR> example long ago of somebody who would have wanted to register "Linux <BR> Expert" as a servicemark, yet obviously that is a pretty generic term. <BR> Not good, if it means that there will be confusion about who owns the <BR> term. <BR> <BR> In contrast (to give some tangible examples), something like "VA <BR> Linux" or "Red Hat Linux" oviously isn't a generic term: it's a very <BR> _targeted_ term for something very specific. Those kinds of names do <BR> not detract from other peoples ability to call _their_ Linux company <BR> something else. <BR> <BR> - Finally, you have to judge the "officialdom" and the importance of <BR> the business side of your usage. Not because I or anybody else really <BR> cares all that much, but more because of the "pain factor" if the name <BR> is asked for by somebody else. <BR> <BR> Basically, ask yourself the question: "What if somebody else had a <BR> project, and happened to chose the same name for his project as I have <BR> for mine, how strong a protection do I want for MY version of the <BR> project?" <BR> <BR> Also, ask yourself: "Would anybody ever have reason to question the <BR> name, and do I need to make provisions for protecting this particular <BR> instance of it" (and note that "anybody" may not be me as the <BR> trademark owner myself, but it may be a competitor who wants to make <BR> life uncomfortable for you) <BR> <BR> If you decide that you want some official protection from the mark, <BR> that probably means that you want to own your own version of the <BR> trademark, ie a "service mark" or a "combination mark". There are <BR> obvious cases where such a thing is wanted - you should not be <BR> surprised to hear that various Linux companies own their own <BR> combination marks, or have at the very least gotten that ownership <BR> verbally approved by me pending getting the paperwork done. <BR> <BR> So basically, in case the trademark issue comes up, you should make <BR> your own judgement. If you read and understood the above, you know <BR> pretty much what my motivation is - I hate the paperwork, and I think <BR> all of this is frankly a waste of my time, but I need to do it so that <BR> in the future I don't end up being in a position I like even less. <BR> <BR> And I'm _not_ out to screw anybody. In order to cover the costs of <BR> paperwork and the costs of just _tracking_ the trademark issues (and <BR> to really make it a legally binding contract in the first place), if <BR> you end up going the whole nine yards and think you need your own <BR> trademark protection, there is a rather nominal fee(*) associated with <BR> combination mark paperwork etc. That money actually goes to the Linux <BR> International trademark fund, so it's not me scalping people if <BR> anybody really thought that that might be the case ;) <BR> <BR> I hope people understand what happened, and why it happened, and why <BR> it really hasn't changed anything that we had to assert the trademark <BR> issue publically for the first time this week. And I hope people feel <BR> more comfortable about it. <BR> <BR> And finally - I hope that people who decide due to this that what they <BR> really want is trademark protection for their own Linux trademark, <BR> that they could just wait a week or two, or contact maddog at Linux <BR> International rather than me. We're finally getting the shroud of <BR> secrecy lifted from transmeta (hey, we'll have a real web-site and <BR> zdtv is supposed to webcast the announcement tomorrow), and I'd rather <BR> worry about trademarks _next_ week. <BR> <BR> Ok? <BR> Linus <BR> <BR> (*) "Nominal fee". What an ugly sentence. It's one of those things <BR> that implies that if you have to ask, you can't afford it. In reality, <BR> it's more a thing where both intent and the size of the project will <BR> make a difference - and quite frankly it's also a way to slightly <BR> discourage people who aren't really serious about it in the first <BR> place. <BR> <BR> - <BR> To unsubscribe from this list: send the line "unsubscribe <BR> linux-kernel" in the body of a message to <A HREF="mailto:majordomo@vger.rutgers.edu">majordomo@vger.rutgers.edu</A> <BR> Please read the FAQ at <A HREF="http://www.tux.org/lkml/">http://www.tux.org/lkml/</A> <BR> <BR> (Rat附注: Tux就是Linux的憨态可掬的LinuxPenguin的名字啦. 呵呵...怎么 <BR> 发音偶还不懂的说. 哪位知道? 我现在还没有查阅资料呢. :-) ) <BR>========End=============== <BR>-- <BR>|======================+========================+====================| <BR>| 以无法为有法 , | 拳本无法,有法也空; | 我爱GNU/Linux, | <BR>| 以无限为有限 | 一法不立,无法不容。| 因为我爱自由! | <BR>| | | | <BR>| 截拳道宗师-李小龙 | 意拳宗师-王芗斋 | 土人 Linuxrat | <BR>|======================+========================+====================| <BR> <BR>※ 来源:·BBS 水木清华站 smth.org·[FROM: 202.112.168.253] <BR><CENTER><H1>BBS水木清华站∶精华区</H1></CENTER></BODY></HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -