On Jan 26, 2008 9:16 PM, Matthieu Riou [EMAIL PROTECTED] wrote:
On Jan 26, 2008 8:29 AM, Robert Burrell Donkin
[EMAIL PROTECTED] wrote:
On Jan 25, 2008 9:18 PM, Roland Weber [EMAIL PROTECTED] wrote:
Noel J. Bergman wrote:
Normally, I would suggest that if we have people wanting
On Wednesday 23 January 2008 04:27, Paul Fremantle wrote:
I agree with the general point about the legality of using the
org.apache namespace. However, I think there is a significant issue
here. People assume that org.apache code is from Apache. And the
reasoning that its too much effort to
On Jan 25, 2008 9:18 PM, Roland Weber [EMAIL PROTECTED] wrote:
Noel J. Bergman wrote:
Normally, I would suggest that if we have people wanting to work on a
project, that we bring it back to life here.
+1
I'm curious how this is supposed to happen? We recently had
two independent
On Jan 26, 2008 8:29 AM, Robert Burrell Donkin
[EMAIL PROTECTED] wrote:
On Jan 25, 2008 9:18 PM, Roland Weber [EMAIL PROTECTED] wrote:
Noel J. Bergman wrote:
Normally, I would suggest that if we have people wanting to work on a
project, that we bring it back to life here.
+1
+1, I
On Jan 26, 2008 8:29 AM, Robert Burrell Donkin
[EMAIL PROTECTED] wrote:
On Jan 25, 2008 9:18 PM, Roland Weber [EMAIL PROTECTED] wrote:
Noel J. Bergman wrote:
Normally, I would suggest that if we have people wanting to work on a
project, that we bring it back to life here.
+1
I'm
Noel J. Bergman wrote:
Normally, I would suggest that if we have people wanting to work on a
project, that we bring it back to life here.
I'm curious how this is supposed to happen? We recently had
two independent inquiries [1,2] of people wanting to work on
a failed incubator project called
Noel J. Bergman [EMAIL PROTECTED] writes:
When forking Apache licensed code, one does _not_ need to change the
package name, or anything else in the source code. One arguably
shouldn't then re-publish the binaries or source as Apache Foo [1], but
the code itself can use the same namespace.
Confirm that we were past the legal hurdles. Community was the issue
here with TSIK.
thanks,
dims
On Jan 23, 2008 1:50 PM, Noel J. Bergman [EMAIL PROTECTED] wrote:
I don't know anything about the legal side, but it would seem to me to
be quite unacceptable to publish new releases with
Michael Wechner wrote:
J Aaron Farr wrote:
If the fork wishes to do more than patch up the original or wishes to
create its own identity unique from the Apache original, then it would
be wise to rename the packages, but there is no legal requirement to
do so.
believing you that there is
Michael Wechner wrote:
If the fork wishes to do more than patch up the original or wishes to
create its own identity unique from the Apache original, then it would
be wise to rename the packages, but there is no legal requirement to
do so.
believing you that there is no legal requirement
J Aaron Farr wrote:
The legal committee has previously been tasked with a fork FAQ
that would cover this and the PRC team is currently working on a
trademarks FAQ that should also cover this.
And this is neither of those groups, nor have those other tasks been completed.
FWIW, your claim is
very much agreed and I guess if one can show a migration path (as I
have suggested) which doesn't break too much, then I think nobody
should mind renaming the packages.
But with the ASF member hat on I think the package org.apache.*
is something which the ASF should protect, just as the
Janne Jalkanen schrieb:
very much agreed and I guess if one can show a migration path (as I
have suggested) which doesn't break too much, then I think nobody
should mind renaming the packages.
But with the ASF member hat on I think the package org.apache.* is
something which the ASF should
On Jan 23, 2008 11:26 AM, Simon Kitching [EMAIL PROTECTED] wrote:
Niall Pemberton schrieb:
On Jan 23, 2008 7:23 AM, Paul Fremantle [EMAIL PROTECTED] wrote:
Niall
Asking someone politely to rename the package is hardly throwing our
weight around.
Well you were talking about need
I guess the big point here is what is the big issue with changing the
package name in the code? When people see a class that's in an
org.apache.*package, they assume that it's from the ASF. Leaving it
in an
ASF-namespaced package has two problems here:
1. People will assume that it's ASF code.
James Carman wrote:
I guess the big point here is what is the big issue with changing the
package name in the code? When people see a class that's in an
org.apache.*package, they assume that it's from the ASF. Leaving it
in an
ASF-namespaced package has two problems here:
1. People will
On 1/23/08, Richard S. Hall [EMAIL PROTECTED] wrote:
James Carman wrote:
I guess the big point here is what is the big issue with changing the
package name in the code? When people see a class that's in an
org.apache.*package, they assume that it's from the ASF. Leaving it
in an
The main point in this discussion is that not changing the package
names is not illegal, but it's definitely uncool and goes against a
pretty well adhered to convention.
+1
Legally, all we can do is ask them
to change the package names and if they don't, there's nothing we can
do (at least
James Carman wrote:
On 1/23/08, Richard S. Hall [EMAIL PROTECTED] wrote:
James Carman wrote:
I guess the big point here is what is the big issue with changing the
package name in the code? When people see a class that's in an
org.apache.*package, they assume that it's from the ASF.
Now, if we, with 2.8, have to change to org.apache.*, we will
obviously break compatibility with any of the existing plugins.
Any advice or policies?
We ought to have this as an FAQ. Roller and Wicket, for example, had to
deal with it, amongst others.
--- Noel
On 1/23/08, Richard S. Hall [EMAIL PROTECTED] wrote:
James Carman wrote:
It seems that there are two discussions going on at the same time:
1. Whether it is cool for people to do this.
2. Whether we should try to stop people from doing this.
I am pretty sure that we all agree that it
But I believe that the IP is
tainted (and constrained) for TSIK, which is why it failed in the first
place.
No, it failed really because there weren't enough people interested
and working on it. All the legal IP issues were cleared.
-Hans
It seems that there are two discussions going on at the same time:
1. Whether it is cool for people to do this.
2. Whether we should try to stop people from doing this.
I am pretty sure that we all agree that it is not cool (1), so I wasn't
talking about this.
Regarding (2), I think
Hans Granqvist wrote:
I believe that the IP is tainted (and constrained) for TSIK, which is
why
it failed in the first place.
No, it failed really because there weren't enough people interested
and working on it. All the legal IP issues were cleared.
If that is the case, let's see if it
On 1/23/08, Paul Fremantle [EMAIL PROTECTED] wrote:
It seems that there are two discussions going on at the same time:
1. Whether it is cool for people to do this.
2. Whether we should try to stop people from doing this.
I am pretty sure that we all agree that it is not cool
Assaf Arkin [EMAIL PROTECTED] writes:
On 1/22/08, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
When forking Apache licensed code, one does _not_ need to change the
package name, or anything else in the source code. One arguably
shouldn't then re-publish the binaries or source as Apache Foo [1], but
the code itself can use the same namespace.
there is no legal requirement to [rename
J Aaron Farr wrote:
If the fork wishes to do more than patch up the original or wishes to
create its own identity unique from the Apache original, then it would
be wise to rename the packages, but there is no legal requirement to
do so.
believing you that there is no legal requirement (I
Hans
My understanding is that you do need to change the package names, but
I'd like to see who else chimes in here.
Any decent Java IDE will rename the packages and fix up the code
without too much hassle.
Paul
On 1/22/08, Hans Granqvist [EMAIL PROTECTED] wrote:
Hi
I want to move a failed
agree that rename is required.
Carl.
Paul Fremantle wrote:
Hans
My understanding is that you do need to change the package names, but
I'd like to see who else chimes in here.
Any decent Java IDE will rename the packages and fix up the code
without too much hassle.
Paul
On 1/22/08, Hans
?
Please could you clarify this?
Gilles
-Original Message-
From: Carl Trieloff [mailto:[EMAIL PROTECTED]
Sent: mardi 22 janvier 2008 16:13
To: general@incubator.apache.org
Subject: Re: moving a failed incubation project
agree that rename is required.
Carl.
Paul
PROTECTED]
Sent: mardi 22 janvier 2008 16:13
To: general@incubator.apache.org
Subject: Re: moving a failed incubation project
agree that rename is required.
Carl.
Paul Fremantle wrote:
Hans
My understanding is that you do need to change the package names, but
I'd like to see who else
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
responsibility to verify that the license in the code is correct.
What you can't do is to use
Hi folks,
IIRC, the AL says to not use the name of Apache for
advertising the product. It doesn't say anything
about package names. There is other code out there
that uses org.apache namespaces, to provide
compatibility with Commons Logging for example.
There is also non-Apache code in org.apache
On Jan 22, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
responsibility to verify
Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
responsibility to verify that the license in the code is correct
rigorously to
protect our brand image.
Paul
On Jan 22, 2008 8:12 PM, Niall Pemberton [EMAIL PROTECTED] wrote:
On Jan 22, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project
:
On Jan 22, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
responsibility to verify
]
wrote:
On Jan 22, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is
dead.
What you can do is to use the code in another project, and assume all
responsibility
On Jan 22, 2008, at 12:50 PM, Niall Pemberton wrote:
What you can't do is to use the Apache brand for another project,
meaning to use the package names including apache if it's not an
Apache project.
I thought the whole point of the AL was that pepople could take code
away and do whatever
.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code in another project, and assume all
responsibility to verify that the license in the code is correct.
What you can't do is to use the Apache brand for another project
22, 2008 8:12 PM, Niall Pemberton [EMAIL PROTECTED] wrote:
On Jan 22, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is dead.
What you can do is to use the code
Michael Wechner schrieb:
Paul Fremantle wrote:
I agree with the general point about the legality of using the
org.apache namespace. However, I think there is a significant issue
here. People assume that org.apache code is from Apache.
agreed. Hence I would also suggest that when moving
, 2008 6:23 PM, Craig L Russell [EMAIL PROTECTED] wrote:
I think the terminology in the subject is wrong.
You are not moving a failed incubation project. That project is
dead.
What you can do is to use the code in another project, and assume all
responsibility to verify
Hi
I want to move a failed incubation project (TSIK) to Google Code,
but the source is full of org.apache.* packages, so I'm not sure
what the right way to do this is. (The code would keep the same
ASF 2.0 license.)
Changing the package names will break any and all code, so if
it'd be great if
45 matches
Mail list logo
