No problem!

Then, could you make an official Tajo git repository 'contrib', then? I
will make a pull request there.

Thank you for your comment.

Warmly,
Dongjoon.

On Tuesday, March 24, 2015, Jaehwa Jung <blrunner@apache.org> wrote:

> Hello Dongjoon
>
> Thanks for your contribution and it looks good.
>
> But I suggest to maintain it within another repository like emrboot-strap.
> Hadoop and Hadoop ecosystem, such as, Hive don't maintain their docker
> image within their source tree. It would be good to maintain within docker
> repository or others.
>
> Best Regards
> Jaehwa
> 2015. 3. 23. 오후 10:07에 "Dongjoon Hyun" <dongjoon@apache.org <javascript:;>>님이
> 작성:
>
> > That looks a clear and best policy. I totally agree with you.
> > You mean '/contrib/dockerfiles', right? I will update my pull request.
> > For the maintainer issue, I insist to use the current one. :-)
> >
> > By the way, we need to setup Dockerhub for automated Docker image
> building
> > and registration.
> > Unfortunately, I found that userid 'tajo' in Dockerhub had used by
> another
> > user already.
> > It seems that we cannot use 'https://registry.hub.docker.com/u/tajo/'.
> >
> > Instead, I think we are able to try to get a really Official Repository
> for
> > Tajo.
> > Other open source software communities, e.g.
> Ubuntu/CentOS/Postgres/MySQL,
> > have theirs.
> > It will be 'https://registry.hub.docker.com/_/tajo/'.  (Note: '_'
> instead
> > of 'u')
> >
> > In this case, I think you are the right person to contact Dockerhub
> > officially.
> > Could you contact Dockerhub, please?
> >
> > Warmly,
> > Dongjoon.
> >
> >
> > On Mon, Mar 23, 2015 at 8:26 PM, Hyunsik Choi <hyunsik@apache.org
> <javascript:;>> wrote:
> >
> > > Excellent work!
> > >
> > > In my opinion, you are the best maintainer because you've made it.
> > > Honestly, I don't have any knowledge about docker. I would appreciate
> > > it if you continue to maintain it now. I think other guys will also
> > > contribute it later.
> > >
> > > The docker image is necessary, but this is not directly related to
> > > Tajo core. So, I'd like to suggest to make it as a contribute package.
> > > For example, Hadoop maintains or maintained some packages like Hadoop
> > > streaming and EMR script as contribute packages. If we do, we should
> > > make '/contrib' directory, and we will maintain the docker images in
> > > the contrib directory.
> > >
> > > How do you think about that?
> > >
> > > Best regards,
> > > Hyunsik
> > >
> > >
> > > On Sat, Mar 21, 2015 at 11:01 PM, Dongjoon Hyun <dongjoon@apache.org
> <javascript:;>>
> > > wrote:
> > > > Hi, all.
> > > >
> > > > I made a proposal for supporting official Tajo docker images.
> > > >
> > > > https://issues.apache.org/jira/browse/TAJO-1423
> > > > (It's a WISH issue.)
> > > >
> > > > Briefly, Docker images provide OS + SW + parameters together for
> > various
> > > > purpose, e.g. easy deploying or testing.
> > > >
> > > > This issue is just for receiving your comments and advices.
> > > >
> > > > To Hyunsik,
> > > > I included your name in this script without your permission. Really
> > sorry
> > > > for that.
> > > > It's just because I was not sure which email is preferred by Tajo
> > > > community. So I think you are the best person. (It's my intention.)
> > > >
> > > > Could you be a maintainer for docker images, if this issue is
> accepted?
> > > >
> > > > Warmly,
> > > > Dongjoon.
> > >
> >
>