Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: domain of hedhman@gmail.com designates
 64.233.184.236 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:from:organization:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
        b=WreY15HNDElZlODJzLzH1JXeCHiwQJcjsyjTjspIEnxX36dmsqLylYMmn1Ntnz5yn/IIBWJhpkVSYx51QjqRou+Prso32m8TeZOs9N0F8+msAxMr8WiE1y7uuNLBYKOb1yPyDtmKEZi6RM0xk07grGAJjh14x/eDPGoqtTEW+hs=
From: Niclas Hedhman <niclas@hedhman.org>
Organization: Private
To: legal-discuss@apache.org
Subject: JBoss trademark issue
Date: Sun, 25 Mar 2007 22:48:25 +0800
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200703252248.25663.niclas@hedhman.org>
Sender: Niclas Hedhman <hedhman@gmail.com>


Gang,

We all know what happened to JBoss open source project, JBoss trademark owned 
by Marc Fleury and JBoss Inc aggressive protection of the trademark.

For fledgling open source projects, that are not backed by ASF/FSF, are there 
any tips on what can be done to avoid future community disaster of such kind. 
For instance, are there any ways to "disable" trademarks from future 
registrations? If not, what else can be done to calm the participants from 
same thing happening again?

The only thing I can think of myself is that someone registers the trademark, 
and license it perpetually, just like source code. But whoever that is, isn't 
likely to "protect" the trademark (too costly), and I recall that the 
statement being "If you don't protect it, you loose it."


Thanks for any advice.


Cheers
Niclas

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org