Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
MIME-Version: 1.0
References: <CA+ULb+u+7k7fbGz1bmNAyATUfUrY-Lj8-BoSKD4RJAFOoZYzaw@mail.gmail.com>
 <CCDF5D3C-EB56-4CAB-A537-3509A65203BD@apache.org> <CA+ULb+stFoqh2-0TFNiyr9t8LmdHKNN5ZVfaAciMCr_E83eDGQ@mail.gmail.com>
 <6EAAE263-9555-4520-80F6-5A2112A5AFD4@apache.org> <CAOPnHqcA3p8KhcOcFZTbwTiG_+OxJUaL+YNZ20g=tSvMx9Yj0w@mail.gmail.com>
 <CAKgUS2BVFCXBN5-ccT1=N=y58XRuQiTUD6z_Mx-M6uwrffxTjw@mail.gmail.com>
 <F734237186262828.804D40A2-DAA4-47C4-8F87-773C2C85C8DF@mail.outlook.com>
 <CADvk=Ga7=PB6fdVREUKH9+785pvRHHGQpVbbZNvKoJxhFv3gjg@mail.gmail.com>
 <EAA317AE-793E-4FD2-9380-A355DF9CBE53@apache.org> <CA+ULb+scuR5E5sJUKearfe1oCNVAkkp4oFi6tras7AmTNiO6iQ@mail.gmail.com>
 <CAM4sjbnEdM2CT9eEiVU5omjDgdzmOKX57tJa72VTYkhUin3uUA@mail.gmail.com>
 <CAM4sjbnCTs2m1OMSKOGsgnCrRdRe1zY0itz=ishkk0FtymNbUw@mail.gmail.com>
 <CADvk=GYC7avQn=8hNG-hosDBJeqWnPXUXaAnYwe4pnHfZKQZ_w@mail.gmail.com> <CA+ULb+uOhYLAU-oK-w_1w6sj30f9pnrpMoKo6ictxu=FgH1waA@mail.gmail.com>
In-Reply-To: <CA+ULb+uOhYLAU-oK-w_1w6sj30f9pnrpMoKo6ictxu=FgH1waA@mail.gmail.com>
From: Kyle Dunn <kdunn@pivotal.io>
Date: Wed, 21 Sep 2016 18:09:09 +0000
Message-ID: <CADvk=GbSY+18Nps+C1OMVfHoFa66Dry1sfpzSKtKw+=qjU_78w@mail.gmail.com>
Subject: Re: libhdfs3 development is still going on outside of ASF
To: dev@hawq.incubator.apache.org
Content-Type: multipart/alternative; boundary=001a1145a3c4adf940053d08717b
archived-at: Wed, 21 Sep 2016 18:09:26 -0000

--001a1145a3c4adf940053d08717b
Content-Type: text/plain; charset=UTF-8

> Personally, I suggest that whoever was managing the library in a separate repo
on GH (and it sounds like Zhanwei Wang is that person) pings the submitters
of all the oustanding PRs (via comment on the PR) telling them to resubmit
via HAWQ's JIRA.

I 100% disagree with this. As a gesture of appreciation - we should be
migrating things for the users, precisely for what you pointed out about
things being poorly managed up to this point. We should be striving to
avoid a fork + isolated development at all costs.

If a few of us divide and conquer this can be tackled very quickly. Who is
willing to chip in here and do something "out of job scope" in support of
the HAWQ community? It's easy to claim we care about open source and
community, but who is actually willing to go out of their way to do whats
right here?

On Wed, Sep 21, 2016 at 11:29 AM Roman Shaposhnik <roman@shaposhnik.org>
wrote:

> On Wed, Sep 21, 2016 at 10:08 AM, Kyle Dunn <kdunn@pivotal.io> wrote:
> > What have we decided here? Fold libhdfs3 back into HAWQ for the near term
> > and revisit spinning it out in a dedicated submodule / repo down the
> road?
>
> To me this sounds like a near term decision. IOW, the other repo is clearly
> read/only at this point.
>
> > Do we need to have a consensus vote for this action?
>
> I don't think we have any contrarian opinion. I appreciated what Matthew
> Rocklin
> had to say, but to me it sounds like his interest will be taken care
> of long term.
> Matt, please let us know if you disagree.
>
> Now,
>
> > As for the outstanding PRs and issues in the current repo, who will be
> > moving those to HAWQ? Are we expecting users to do this?
>
> Well, see -- that's *exactly* the problem with how this project was
> managed.
> At this point we can't even reach the interested parties in a broadcast
> manner.
>
> Personally, I suggest that whoever was managing the library in a separate
> repo on GH (and it sounds like Zhanwei Wang is that person) pings the
> submitters of all the oustanding PRs (via comment on the PR) telling them
> to resubmit via HAWQ's JIRA.
>
> > I'm taking the
> > "liberty" of responding to each of these users explaining the situation
> but
> > would like to know what to report on that front.
>
> That's exactly the right thing to do. So I guess it is you and Zhanwei Wang
> on the hook to do that.
>
> Thanks,
> Roman.
>
-- 
*Kyle Dunn | Data Engineering | Pivotal*
Direct: 303.905.3171 <3039053171> | Email: kdunn@pivotal.io

--001a1145a3c4adf940053d08717b--