incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de.INVALID>
Subject Re: [VOTE] Drop incubating requirement of Maven artifacts
Date Wed, 04 Jan 2017 06:28:18 GMT
I guess you are talking about log4j/log4j or the various commons-* groupIds?
This is true, but for completness sake I want to point out that there is a difference to use
a different _unused_ groupId vs using a _foreign_ one.

I guess everyone would agree that the ASF does not like to publish artifacts with a com.oracle
groupId, right?

I'm a bit surprised that groovy still uses the org.codehaus groupId, but I guess they have
a deal with Ben (the former owner and thus (former?) copyright holder of 'Codehaus').
So while this will work for now I guess that even groovy will move to org.apache.groovy in
the long term (maybe with a new major version). 

It's not a big deal YET, but http://codehaus.org is not reachable anymore. And if anyone buys
this domain he will have a much better position regarding trademarks than we do.
What if someone buys the codehaus.org domain and publishes own artifacts under org.codehaus.groovy?
Can we even prevent someone else to e.g publish org.codehaus.groovyng artifacts?

LieGrue,
strub

> Am 04.01.2017 um 02:49 schrieb John D. Ament <johndament@apache.org>:
> 
> On Tue, Jan 3, 2017 at 8:43 PM Daniel Dekany <ddekany@freemail.hu> wrote:
> 
>> Tuesday, January 3, 2017, 11:10:24 PM, Stian Soiland-Reyes wrote:
>> 
>> [snip]
>>> The workaround of publishing binaries without any -incubator/-incubating
>>> markers by using a non-apache group/name is probably a somewhat workable
>>> solution for larger established projects like Groovy, but may also work
>>> against community as it de-emphasises ASF, and outsiders might so easily
>>> realise that the community is changing before graduation.
>> [snip]
>> 
>> Note that the non-Apache group/name is not meant to be a workaround to
>> avoid "-incubating". It's about not burdening the Java ecosystem with
>> a groupId change.
>> 
> 
> Just to point out, again, there are even top level projects that don't
> publish under org.apache.  There's no requirement to do so.
> 
> 
>> 
>> --
>> Thanks,
>> Daniel Dekany-incubating
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message