www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <d...@iq80.com>
Subject Re: JBoss trademark issue
Date Mon, 26 Mar 2007 16:47:49 GMT
I don't think it is this complex.  In most cases I see the process is  
as follows:

1. John Doe starts project XYZ
2. John Doe registers the XYZ trademark privately. (has to not  
company yet)
3. Project grows with the efforts of the community.
4. John Doe and others starts XYZ Corp.
5. XYZ Inc enforces trademark protection against some of the
    very people who made it successful.

There is nothing wrong with this except for step 3.  I'd guess this  
same scam happened with copyright before licenses were certified and  
classified.  Now days the community has expectations that a copyright  
license must be certified, but they have not expectations for  
trademarks.

-dain

On Mar 25, 2007, at 10:37 AM, Niclas Hedhman wrote:

> On Sunday 25 March 2007 23:58, Geir Magnusson Jr. wrote:
>> I'm familiar with what happened there.  But that's independent of the
>> trademark issue you bring up..
>
> Agree. Let's move JBoss out of the equation. My mistake to assume  
> it was a
> well-understood scenario.
>
> The question revolves around;
>
> 1.  WXYZ community was created, by a group of people who likes WX.
> 2.  The project change name to XYZ
> 3.  John Doe registers the XYZ trademark privately.
> 4.  The community grows, and project becomes successful.
> 5.  Many companies provides support and other services around XYZ.
> 6.  John Doe and others starts XYZ Corp.
> 7.  XYZ Inc enforces trademark protection against some of the
>     very people who made it successful.
>
>
> Any suggestions on how to pre-empt such scenario, so that people  
> who has been
> involved or observed this happening in the past is not reluctant to
> collaborate on new exciting technologies.
>
> I think the key is XYZ trademark, and possibly XYZ Corp.
>
>
> 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
>


---------------------------------------------------------------------
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


Mime
View raw message