You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@hadoop.apache.org by Will Norris <wn...@twitter.com.INVALID> on 2022/05/05 17:57:54 UTC
Publishing hadoop-lzo maven package in com.hadoop namespace
Hey Hadoop folks,
I'm honestly not sure the best place to post this, but general@ seemed
reasonable enough. I've just opened an issue, HADOOP-18223
<https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
opinions on Twitter publishing our hadoop-lzo package on maven central
under the current com.hadoop groupId. We've published it this way on
maven.twttr.com for quite a few years, but are trying to remove that single
point of failure <https://github.com/twitter/hadoop-lzo/issues/148> for
downstream users.
I can't imagine too many people will have strong opinions about this, but
since it's not our namespace, I wanted to talk with folks before we did
anything.
-will
Re: Publishing hadoop-lzo maven package in com.hadoop namespace
Posted by Will Norris <wn...@twitter.com.INVALID>.
oh certainly, that's always an option. And sounds like the one we'll
pursue.
On Fri, May 6, 2022 at 7:59 AM Steve Loughran <st...@cloudera.com.invalid>
wrote:
> it;s com.hadoop, but still tainted.
>
> couldn't we have com.twitter.hadoop?
>
> On Fri, 6 May 2022 at 15:23, Sean Busbey <sb...@apple.com.invalid>
> wrote:
>
> > As an ASF project we can not distribute GPL code. As an ASF project it’s
> > also our job to defend our trademarks.
> >
> > We should actively prevent this GPL code from going to maven central with
> > our name attached to it.
> >
> >
> >
> > > On May 5, 2022, at 1:49 PM, Wei-Chiu Chuang <we...@apache.org>
> wrote:
> > >
> > > Please be careful.
> > > Sorry but hadoop-lzo is GPL licensed. Internally at my employer we
> don't
> > > use/ship hadoop-lzo because of the licensing concerns.
> > >
> > > I suppose since the code is GPL we as an Apache project want to stay
> away
> > > from it?
> > >
> > > On Thu, May 5, 2022 at 11:17 AM Ayush Saxena <ay...@gmail.com>
> wrote:
> > >
> > >> Didn’t read it full. But seems related to some code change in Hadoop
> > Common
> > >> Forwarded to common-dev
> > >>
> > >> Begin forwarded message:
> > >>
> > >>> From: Will Norris <wn...@twitter.com.invalid>
> > >>> Date: 5 May 2022 at 11:28:35 PM IST
> > >>> To: general@hadoop.apache.org
> > >>> Subject: Publishing hadoop-lzo maven package in com.hadoop namespace
> > >>>
> > >>> Hey Hadoop folks,
> > >>>
> > >>> I'm honestly not sure the best place to post this, but general@
> seemed
> > >>> reasonable enough. I've just opened an issue, HADOOP-18223
> > >>> <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
> > >>> opinions on Twitter publishing our hadoop-lzo package on maven
> central
> > >>> under the current com.hadoop groupId. We've published it this way on
> > >>> maven.twttr.com for quite a few years, but are trying to remove that
> > >> single
> > >>> point of failure <https://github.com/twitter/hadoop-lzo/issues/148>
> > for
> > >>> downstream users.
> > >>>
> > >>> I can't imagine too many people will have strong opinions about this,
> > but
> > >>> since it's not our namespace, I wanted to talk with folks before we
> did
> > >>> anything.
> > >>>
> > >>> -will
> > >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: common-dev-help@hadoop.apache.org
> >
> >
>
Re: Publishing hadoop-lzo maven package in com.hadoop namespace
Posted by Steve Loughran <st...@cloudera.com.INVALID>.
it;s com.hadoop, but still tainted.
couldn't we have com.twitter.hadoop?
On Fri, 6 May 2022 at 15:23, Sean Busbey <sb...@apple.com.invalid> wrote:
> As an ASF project we can not distribute GPL code. As an ASF project it’s
> also our job to defend our trademarks.
>
> We should actively prevent this GPL code from going to maven central with
> our name attached to it.
>
>
>
> > On May 5, 2022, at 1:49 PM, Wei-Chiu Chuang <we...@apache.org> wrote:
> >
> > Please be careful.
> > Sorry but hadoop-lzo is GPL licensed. Internally at my employer we don't
> > use/ship hadoop-lzo because of the licensing concerns.
> >
> > I suppose since the code is GPL we as an Apache project want to stay away
> > from it?
> >
> > On Thu, May 5, 2022 at 11:17 AM Ayush Saxena <ay...@gmail.com> wrote:
> >
> >> Didn’t read it full. But seems related to some code change in Hadoop
> Common
> >> Forwarded to common-dev
> >>
> >> Begin forwarded message:
> >>
> >>> From: Will Norris <wn...@twitter.com.invalid>
> >>> Date: 5 May 2022 at 11:28:35 PM IST
> >>> To: general@hadoop.apache.org
> >>> Subject: Publishing hadoop-lzo maven package in com.hadoop namespace
> >>>
> >>> Hey Hadoop folks,
> >>>
> >>> I'm honestly not sure the best place to post this, but general@ seemed
> >>> reasonable enough. I've just opened an issue, HADOOP-18223
> >>> <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
> >>> opinions on Twitter publishing our hadoop-lzo package on maven central
> >>> under the current com.hadoop groupId. We've published it this way on
> >>> maven.twttr.com for quite a few years, but are trying to remove that
> >> single
> >>> point of failure <https://github.com/twitter/hadoop-lzo/issues/148>
> for
> >>> downstream users.
> >>>
> >>> I can't imagine too many people will have strong opinions about this,
> but
> >>> since it's not our namespace, I wanted to talk with folks before we did
> >>> anything.
> >>>
> >>> -will
> >>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>
>
Re: Publishing hadoop-lzo maven package in com.hadoop namespace
Posted by Sean Busbey <sb...@apple.com.INVALID>.
As an ASF project we can not distribute GPL code. As an ASF project it’s also our job to defend our trademarks.
We should actively prevent this GPL code from going to maven central with our name attached to it.
> On May 5, 2022, at 1:49 PM, Wei-Chiu Chuang <we...@apache.org> wrote:
>
> Please be careful.
> Sorry but hadoop-lzo is GPL licensed. Internally at my employer we don't
> use/ship hadoop-lzo because of the licensing concerns.
>
> I suppose since the code is GPL we as an Apache project want to stay away
> from it?
>
> On Thu, May 5, 2022 at 11:17 AM Ayush Saxena <ay...@gmail.com> wrote:
>
>> Didn’t read it full. But seems related to some code change in Hadoop Common
>> Forwarded to common-dev
>>
>> Begin forwarded message:
>>
>>> From: Will Norris <wn...@twitter.com.invalid>
>>> Date: 5 May 2022 at 11:28:35 PM IST
>>> To: general@hadoop.apache.org
>>> Subject: Publishing hadoop-lzo maven package in com.hadoop namespace
>>>
>>> Hey Hadoop folks,
>>>
>>> I'm honestly not sure the best place to post this, but general@ seemed
>>> reasonable enough. I've just opened an issue, HADOOP-18223
>>> <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
>>> opinions on Twitter publishing our hadoop-lzo package on maven central
>>> under the current com.hadoop groupId. We've published it this way on
>>> maven.twttr.com for quite a few years, but are trying to remove that
>> single
>>> point of failure <https://github.com/twitter/hadoop-lzo/issues/148> for
>>> downstream users.
>>>
>>> I can't imagine too many people will have strong opinions about this, but
>>> since it's not our namespace, I wanted to talk with folks before we did
>>> anything.
>>>
>>> -will
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: Publishing hadoop-lzo maven package in com.hadoop namespace
Posted by Wei-Chiu Chuang <we...@apache.org>.
Please be careful.
Sorry but hadoop-lzo is GPL licensed. Internally at my employer we don't
use/ship hadoop-lzo because of the licensing concerns.
I suppose since the code is GPL we as an Apache project want to stay away
from it?
On Thu, May 5, 2022 at 11:17 AM Ayush Saxena <ay...@gmail.com> wrote:
> Didn’t read it full. But seems related to some code change in Hadoop Common
> Forwarded to common-dev
>
> Begin forwarded message:
>
> > From: Will Norris <wn...@twitter.com.invalid>
> > Date: 5 May 2022 at 11:28:35 PM IST
> > To: general@hadoop.apache.org
> > Subject: Publishing hadoop-lzo maven package in com.hadoop namespace
> >
> > Hey Hadoop folks,
> >
> > I'm honestly not sure the best place to post this, but general@ seemed
> > reasonable enough. I've just opened an issue, HADOOP-18223
> > <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
> > opinions on Twitter publishing our hadoop-lzo package on maven central
> > under the current com.hadoop groupId. We've published it this way on
> > maven.twttr.com for quite a few years, but are trying to remove that
> single
> > point of failure <https://github.com/twitter/hadoop-lzo/issues/148> for
> > downstream users.
> >
> > I can't imagine too many people will have strong opinions about this, but
> > since it's not our namespace, I wanted to talk with folks before we did
> > anything.
> >
> > -will
>
Fwd: Publishing hadoop-lzo maven package in com.hadoop namespace
Posted by Ayush Saxena <ay...@gmail.com>.
Didn’t read it full. But seems related to some code change in Hadoop Common
Forwarded to common-dev
Begin forwarded message:
> From: Will Norris <wn...@twitter.com.invalid>
> Date: 5 May 2022 at 11:28:35 PM IST
> To: general@hadoop.apache.org
> Subject: Publishing hadoop-lzo maven package in com.hadoop namespace
>
> Hey Hadoop folks,
>
> I'm honestly not sure the best place to post this, but general@ seemed
> reasonable enough. I've just opened an issue, HADOOP-18223
> <https://issues.apache.org/jira/browse/HADOOP-18223>, to solicit any
> opinions on Twitter publishing our hadoop-lzo package on maven central
> under the current com.hadoop groupId. We've published it this way on
> maven.twttr.com for quite a few years, but are trying to remove that single
> point of failure <https://github.com/twitter/hadoop-lzo/issues/148> for
> downstream users.
>
> I can't imagine too many people will have strong opinions about this, but
> since it's not our namespace, I wanted to talk with folks before we did
> anything.
>
> -will