For many months the board has been asking the Maven project to obtain
proper attribution from Sonatype for Apache's Maven trademark.
Sonatype has thus far failed to comply. The Sonatype website states
only that Apache Maven is a trademark of the ASF, not that Maven
alone is also a trademark of
Jason, the board has not leaked the information, so rest assured
it was not from us. Also rest assured that no one questions
Sonatypes committment to the users nor your pursuit of innovation.
We only question why Sonatype refuses to attribute Maven as
a mark of the ASF, even after I was assured by
Doug, this is only part of the story but if we are strictly talking about
trademarks here then people should understand what that discussion is about.
What Sonatype was seeking was the use of Maven Central as a service mark in
very much the same way Doug Cutting's company, Cloudera, has been
Jason, please stop confusing the issue. In both cases you mention
below, the PMCs have been very VERY involved in tracking ALL
trademark issues, and have been even more vigilant with those
entities in which they are a part of as far as employment (I
would encourage you to look over, for example,
On Jun 17, 2011, at 7:36 AM, Jim Jagielski wrote:
Jason, the board has not leaked the information, so rest assured
it was not from us.
I'm not sure what information you're referring to.
Also rest assured that no one questions
Sonatypes committment to the users nor your pursuit of
Jim, just get on the phone and sort it out. It's not that hard.
On Jun 17, 2011, at 9:09 AM, Jim Jagielski wrote:
Jason, please stop confusing the issue. In both cases you mention
below, the PMCs have been very VERY involved in tracking ALL
trademark issues, and have been even more vigilant
On 06/17/2011 03:03 PM, Jason van Zyl wrote:
What Sonatype was seeking was the use of Maven Central as a service
mark in very much the same way Doug Cutting's company, Cloudera, has
been granted a memorandum of understanding (MOU) for the service mark
Hadoop World.
That's a separate issue
...@sonatype.com wrote:
From: Jason van Zyl ja...@sonatype.com
Subject: Re: PMC change explanation?
To: Jim Jagielski j...@jagunet.com
Cc: Doug Cutting cutt...@apache.org, Maven Developers List
dev@maven.apache.org, Apache Board bo...@apache.org
Date: Friday, June 17, 2011, 1:31 PM
Jim, just get
The bottom line is that this is likely easy to resolve very quickly. A call
between a representative Apache board member, a Sonatype representative, and a
secretary to agree on the actions, and carry them out. That seems like a pretty
easy plan of action. Anything else just says to me that the
Not sure what there is to sort out... But of course,
you are also welcome to get on the phone and sort it
out as well.
On Jun 17, 2011, at 9:31 AM, Jason van Zyl wrote:
Jim, just get on the phone and sort it out. It's not that hard.
On Jun 17, 2011, at 9:09 AM, Jim Jagielski wrote:
Jason,
the fastest way to resolve the issue.
LieGrue,
strub
--- On Fri, 6/17/11, Jason van Zyl ja...@sonatype.com wrote:
From: Jason van Zyl ja...@sonatype.com
Subject: Re: PMC change explanation?
To: Jim Jagielski j...@jagunet.com
Cc: Doug Cutting cutt...@apache.org, Maven Developers List
dev
Email coming your way.
On Jun 17, 2011, at 9:44 AM, Jim Jagielski wrote:
Not sure what there is to sort out... But of course,
you are also welcome to get on the phone and sort it
out as well.
On Jun 17, 2011, at 9:31 AM, Jason van Zyl wrote:
Jim, just get on the phone and sort it out.
The below shows that you are extremely out of touch regarding
what has been going on. As such, I have no problems with
ignoring it.
On Jun 17, 2011, at 9:55 AM, Jason van Zyl wrote:
The bottom line is that this is likely easy to resolve very quickly. A call
between a representative Apache
Jim,
Your misunderstanding of someone else's point of view and dismissing it out of
hand without any further discussion is what got us here in the first place. You
have no problems ignoring whatever you feel like which generally makes it hard
to arrive at a resolution. Your job as an ASF Board
FWIW, I'm glad the PMC has had the chance to participate in saying what
it wants in the MOU with Sonatype. Unfortunately, such participation has
to happen as we have time, and since we're a project of volunteers it
may not happen on the timescales that companies are used to. So, if the
buck
Jason, all I can say in response is that I am impressed with
both your reinterpretation of history as well as the size
of your stugots in somehow placing the blame on the board
and myself.
We have made incredible progress, and your sweeping and baseless
arguments are impeding and damaging that. I
As an introduction to those here in Maven land, I'm the VP of Brand
Management at the Apache Software Foundation, and I and my officer's
committee at trademarks@ are responsible for setting brand policy for
all Apache projects, including trademark usage by third parties.
Since this includes
On Jun 17, 2011, at 11:02 AM, Jim Jagielski wrote:
Jason, all I can say in response is that I am impressed with
both your reinterpretation of history as well as the size
of your stugots in somehow placing the blame on the board
and myself.
As I am impressed with yours. When things are not
Jason,
Your synopsis is pretty much complete and total hogwash. Except for
the board action, the PMC has been very, very involved for quite a
long time. Since you are not on the PMC, maybe you didn't know that.
In which case, please don't attempt to imagine what is happening;
reality is sooo much
Is there a forthcoming explanation for a seemingly Maven PMC shakeup?
I find it odd that consistently excellent contributors such as Lukas,
Brian, et al are suddenly not on the Maven PMC. This is concerning as
these are people who have drastically improved and moved Maven
forward. It's very
Only speaking for myself, I would like to stress that I stepped back
from the PMC for purely personal reasons. Though it certainly
facilitated my decision, the events that occupied the PMC at the time
are in no causal relation to my retirement.
Said events will hopefully be explained by
Jeff,
I believe this strictly falls within the purview of the Apache Board to
explain. In particular Jim, Doug and Shane.
Only the board has the right to reveal the business that has been transacted on
private lists.
Rest assured that's Sonatype's commitment to Maven users and our pursuit of
I find it somewhat bewildering that there is no post of the vote or the
results on the dev and users mailing lists I can see. Nor does the web
site seem to be updated.
http://maven.apache.org/team-list.html
I would have expected more transparency from Apache.
manfred
Jeff,
I believe this
change explanation?
From: manf...@mosabuam.com
To: dev@maven.apache.org
CC: bo...@apache.org
I find it somewhat bewildering that there is no post of the vote or the
results on the dev and users mailing lists I can see. Nor does the web
site seem to be updated.
http://maven.apache.org/team
responsabilité pour le contenu fourni.
Date: Thu, 16 Jun 2011 08:24:35 -0700
Subject: Re: PMC change explanation?
From: manf...@mosabuam.com
To: dev@maven.apache.org
CC: bo...@apache.org
I find it somewhat bewildering that there is no post of the vote or the
results on the dev and users
donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Date: Thu, 16 Jun 2011 08:24:35 -0700
Subject: Re: PMC change explanation?
From: manf...@mosabuam.com
To: dev@maven.apache.org
CC: bo...@apache.org
que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.
Date: Thu, 16 Jun 2011 08:24:35 -0700
Subject: Re: PMC change explanation?
From: manf...@mosabuam.com
To: dev@maven.apache.org
CC: bo...@apache.org
I
pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 16 Jun 2011 15:28:11 -0400
Subject: Re: PMC change explanation?
From: bimargul
Just to make a couple of things clear, that weren't stated elsewhere in the
thread:
On 16/06/2011, at 11:42 PM, Jeff Jensen wrote:
It's very concerning that a heavy committer such as Benjamin
is no longer committing as he has done very useful, fantastic work.
There has been no change to who
Subject: Re: PMC change explanation?
From: bimargul...@gmail.com
To: dev@maven.apache.org
Martin,
I don't think that your message helps anyone here. Jason's email is a
very gracious acknowledgement of the governance of the Apache Software
Foundation. The changes in the Maven PMC result
30 matches
Mail list logo