subject:"Re\: Importing Source Code"

Re: Importing Source Code

2018-10-12 Thread Lucas Bonatto Miguel

I was using other repo information, now it worked. Thanks.

We've imported Marvin's code to the incubator repo.


On Fri, Oct 12, 2018 at 1:24 PM Luciano Resende 
wrote:

> What repository are you using?
>
> Note that the writable repository information is
> https://gitbox.apache.org/repos/asf/incubator-marvin.git
> On Thu, Oct 11, 2018 at 8:42 PM Lucas Bonatto Miguel
>  wrote:
> >
> > Guys, I am trying to push the code to the incubator repo but it looks
> like
> > my user has no write permissions.
> >
> > I already created my apache account and I associated my apache e-mail
> with
> > my GitHub account. Am I missing something?
> >
> >
> > > *remote: Permission to apache/incubator-marvin.git denied to
> > > lucasbm88.fatal: unable to access
> > > 'https://github.com/apache/incubator-marvin/
> > > ': The requested URL
> returned
> > > error: 403*
> >
> >
> >
> >
> > On Tue, Oct 9, 2018 at 8:11 PM Willian Leite 
> > wrote:
> >
> > > +1
> > >
> > > Em ter, 9 de out de 2018 às 13:24, Alan Silva
> > >  escreveu:
> > >
> > > > +1 here too.
> > > >
> > > > Let's go to the merge, guys! :)
> > > >
> > > > On Tue, Oct 9, 2018 at 3:11 PM Lucas Bonatto Miguel <
> > > lucasb...@apache.org>
> > > > wrote:
> > > >
> > > > > I saw two +1s Daniel, Imo you're good to merge.
> > > > >
> > > > > Go go go. :)
> > > > >
> > > > > Regards,
> > > > > Lucas
> > > > >
> > > > > On Tue, Oct 9, 2018 at 12:18 PM Luciano Resende <
> luckbr1...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > If the community is ok, you should be able to follow the steps
> from
> > > > > > the link below to push the repository as a mirror of the current
> one
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
> > > > > >
> > > > > > On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
> > > > > >  wrote:
> > > > > > >
> > > > > > > To me it look like perfect. What is the next step? Could I
> help?
> > > > > > >
> > > > > > > Atenciosamente,
> > > > > > > Rafael J. R. Novello
> > > > > > >
> > > > > > > Skype: rafael.novello
> > > > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > > > >
> > > > > > >
> > > > > > > Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> > > > > > > daniel.takabaya...@gmail.com> escreveu:
> > > > > > >
> > > > > > > > Hello Guys, anyone has something to say?
> > > > > > > >
> > > > > > > > Sent from my iPhone
> > > > > > > >
> > > > > > > > > On Oct 4, 2018, at 7:40 AM, Rafael Novello <
> > > > > > rafa.reis.nove...@gmail.com>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > All the history was preserved! I think we are fine!
> > > > > > > > >
> > > > > > > > > Best!
> > > > > > > > > Atenciosamente,
> > > > > > > > > Rafael J. R. Novello
> > > > > > > > >
> > > > > > > > > Skype: rafael.novello
> > > > > > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > > > > > > > lucasbona...@gmail.com> escreveu:
> > > > > > > > >
> > > > > > > > >> +1
> > > > > > > > >>
> > > > > > > > >> Looks good to me. We should prioritize better READMEs in
> the
> > > > near
> > > > > > > > future.
> > > > > > > > >> For the scope of this story I think you did a good job.
> > > > > > > > >>
> > > > > > > > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > > > > > > > >> daniel.takabaya...@gmail.com> wrote:
> > > > > > > > >>
> > > > > > > > >>> Ok guys, I finished the merge of our 3 main repos:
> > > > > > > > >>>
> > > > > > > > >>>
> > > > > > > > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > > > > > > > >>> *
> > > > > > > > >>>
> > > > > > > > >>> *https://github.com/marvin-ai/marvin-public-engines
> > > > > > > > >>> *
> > > > > > > > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > > > > > > > >>> *
> > > > > > > > >>>
> > > > > > > > >>> Into this one ...
> > > > > > > > >>>
> > > > > > > > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > > > > > > > >>> *
> > > > > > > > >>>
> > > > > > > > >>> All commits history remained and ... please check and
> feel
> > > free
> > > > > to
> > > > > > > > >>> collaborate before we replicate into our apache account.
> And
> > > > any
> > > > > > > > problem
> > > > > > > > >>> ...let me know!
> > > > > > > > >>>
> > > > > > > > >>> Thanks,
> > > > > > > > >>> Taka
> > > > > > > > >>>
> > > > > > > > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > > > > > > > >>> daniel.takabaya...@gmail.com> escreveu:
> > > > > > > > >>>
> > > > > > > >  Sounds good.
> > > > > > > > 
> > > > > > > >  Em ter, 2 de out de 2018 às

Re: Importing Source Code

2018-10-11 Thread Lucas Bonatto Miguel

Guys, I am trying to push the code to the incubator repo but it looks like
my user has no write permissions.

I already created my apache account and I associated my apache e-mail with
my GitHub account. Am I missing something?


> *remote: Permission to apache/incubator-marvin.git denied to
> lucasbm88.fatal: unable to access
> 'https://github.com/apache/incubator-marvin/
> ': The requested URL returned
> error: 403*




On Tue, Oct 9, 2018 at 8:11 PM Willian Leite 
wrote:

> +1
>
> Em ter, 9 de out de 2018 às 13:24, Alan Silva
>  escreveu:
>
> > +1 here too.
> >
> > Let's go to the merge, guys! :)
> >
> > On Tue, Oct 9, 2018 at 3:11 PM Lucas Bonatto Miguel <
> lucasb...@apache.org>
> > wrote:
> >
> > > I saw two +1s Daniel, Imo you're good to merge.
> > >
> > > Go go go. :)
> > >
> > > Regards,
> > > Lucas
> > >
> > > On Tue, Oct 9, 2018 at 12:18 PM Luciano Resende 
> > > wrote:
> > >
> > > > If the community is ok, you should be able to follow the steps from
> > > > the link below to push the repository as a mirror of the current one
> > > >
> > > >
> > > >
> > >
> >
> https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
> > > >
> > > > On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
> > > >  wrote:
> > > > >
> > > > > To me it look like perfect. What is the next step? Could I help?
> > > > >
> > > > > Atenciosamente,
> > > > > Rafael J. R. Novello
> > > > >
> > > > > Skype: rafael.novello
> > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > >
> > > > >
> > > > > Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> > > > > daniel.takabaya...@gmail.com> escreveu:
> > > > >
> > > > > > Hello Guys, anyone has something to say?
> > > > > >
> > > > > > Sent from my iPhone
> > > > > >
> > > > > > > On Oct 4, 2018, at 7:40 AM, Rafael Novello <
> > > > rafa.reis.nove...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > All the history was preserved! I think we are fine!
> > > > > > >
> > > > > > > Best!
> > > > > > > Atenciosamente,
> > > > > > > Rafael J. R. Novello
> > > > > > >
> > > > > > > Skype: rafael.novello
> > > > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > > > >
> > > > > > >
> > > > > > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > > > > > lucasbona...@gmail.com> escreveu:
> > > > > > >
> > > > > > >> +1
> > > > > > >>
> > > > > > >> Looks good to me. We should prioritize better READMEs in the
> > near
> > > > > > future.
> > > > > > >> For the scope of this story I think you did a good job.
> > > > > > >>
> > > > > > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > > > > > >> daniel.takabaya...@gmail.com> wrote:
> > > > > > >>
> > > > > > >>> Ok guys, I finished the merge of our 3 main repos:
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > > > > > >>> *
> > > > > > >>>
> > > > > > >>> *https://github.com/marvin-ai/marvin-public-engines
> > > > > > >>> *
> > > > > > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > > > > > >>> *
> > > > > > >>>
> > > > > > >>> Into this one ...
> > > > > > >>>
> > > > > > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > > > > > >>> *
> > > > > > >>>
> > > > > > >>> All commits history remained and ... please check and feel
> free
> > > to
> > > > > > >>> collaborate before we replicate into our apache account. And
> > any
> > > > > > problem
> > > > > > >>> ...let me know!
> > > > > > >>>
> > > > > > >>> Thanks,
> > > > > > >>> Taka
> > > > > > >>>
> > > > > > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > > > > > >>> daniel.takabaya...@gmail.com> escreveu:
> > > > > > >>>
> > > > > >  Sounds good.
> > > > > > 
> > > > > >  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> > > > > > >> luckbr1...@gmail.com
> > > > > > 
> > > > > >  escreveu:
> > > > > > 
> > > > > > > So, before pushing to the apache repo, make a draft repo
> > > outside
> > > > > > >> apache
> > > > > > > and let couple people to review
> > > > > > >
> > > > > > > The  you can push to apache... as a mirror.
> > > > > > >
> > > > > > > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > > > > > > daniel.takabaya...@gmail.com> wrote:
> > > > > > >
> > > > > > >> Ok, now is clear
> > > > > > >>
> > > > > > >> This is the repo
> > > > > > >>  >
> > I
> > > am
> > > > > > >> going
> > > > > > >> to push the new merged code. Another question is about the
> > > > license,
> > > > > > >>> right
> > > > > > >> now all files has this license here:
> > > > > > >>
> > > > > > >> #

Re: Importing Source Code

2018-10-09 Thread Willian Leite

+1

Em ter, 9 de out de 2018 às 13:24, Alan Silva
 escreveu:

> +1 here too.
>
> Let's go to the merge, guys! :)
>
> On Tue, Oct 9, 2018 at 3:11 PM Lucas Bonatto Miguel 
> wrote:
>
> > I saw two +1s Daniel, Imo you're good to merge.
> >
> > Go go go. :)
> >
> > Regards,
> > Lucas
> >
> > On Tue, Oct 9, 2018 at 12:18 PM Luciano Resende 
> > wrote:
> >
> > > If the community is ok, you should be able to follow the steps from
> > > the link below to push the repository as a mirror of the current one
> > >
> > >
> > >
> >
> https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
> > >
> > > On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
> > >  wrote:
> > > >
> > > > To me it look like perfect. What is the next step? Could I help?
> > > >
> > > > Atenciosamente,
> > > > Rafael J. R. Novello
> > > >
> > > > Skype: rafael.novello
> > > > Blog: http://rafanovello.blogspot.com.br/
> > > >
> > > >
> > > > Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> > > > daniel.takabaya...@gmail.com> escreveu:
> > > >
> > > > > Hello Guys, anyone has something to say?
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On Oct 4, 2018, at 7:40 AM, Rafael Novello <
> > > rafa.reis.nove...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > All the history was preserved! I think we are fine!
> > > > > >
> > > > > > Best!
> > > > > > Atenciosamente,
> > > > > > Rafael J. R. Novello
> > > > > >
> > > > > > Skype: rafael.novello
> > > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > > >
> > > > > >
> > > > > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > > > > lucasbona...@gmail.com> escreveu:
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> Looks good to me. We should prioritize better READMEs in the
> near
> > > > > future.
> > > > > >> For the scope of this story I think you did a good job.
> > > > > >>
> > > > > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > > > > >> daniel.takabaya...@gmail.com> wrote:
> > > > > >>
> > > > > >>> Ok guys, I finished the merge of our 3 main repos:
> > > > > >>>
> > > > > >>>
> > > > > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > > > > >>> *
> > > > > >>>
> > > > > >>> *https://github.com/marvin-ai/marvin-public-engines
> > > > > >>> *
> > > > > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > > > > >>> *
> > > > > >>>
> > > > > >>> Into this one ...
> > > > > >>>
> > > > > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > > > > >>> *
> > > > > >>>
> > > > > >>> All commits history remained and ... please check and feel free
> > to
> > > > > >>> collaborate before we replicate into our apache account. And
> any
> > > > > problem
> > > > > >>> ...let me know!
> > > > > >>>
> > > > > >>> Thanks,
> > > > > >>> Taka
> > > > > >>>
> > > > > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > > > > >>> daniel.takabaya...@gmail.com> escreveu:
> > > > > >>>
> > > > >  Sounds good.
> > > > > 
> > > > >  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> > > > > >> luckbr1...@gmail.com
> > > > > 
> > > > >  escreveu:
> > > > > 
> > > > > > So, before pushing to the apache repo, make a draft repo
> > outside
> > > > > >> apache
> > > > > > and let couple people to review
> > > > > >
> > > > > > The  you can push to apache... as a mirror.
> > > > > >
> > > > > > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > > > > > daniel.takabaya...@gmail.com> wrote:
> > > > > >
> > > > > >> Ok, now is clear
> > > > > >>
> > > > > >> This is the repo
> > > > > >> 
> I
> > am
> > > > > >> going
> > > > > >> to push the new merged code. Another question is about the
> > > license,
> > > > > >>> right
> > > > > >> now all files has this license here:
> > > > > >>
> > > > > >> # Copyright [2017] [B2W Digital]
> > > > > >> #
> > > > > >> # Licensed under the Apache License, Version 2.0 (the
> > > "License");
> > > > > >> # you may not use this file except in compliance with the
> > > License.
> > > > > >> # You may obtain a copy of the License at
> > > > > >> #
> > > > > >> #http://www.apache.org/licenses/LICENSE-2.0
> > > > > >> #
> > > > > >> # Unless required by applicable law or agreed to in writing,
> > > > > software
> > > > > >> # distributed under the License is distributed on an "AS IS"
> > > BASIS,
> > > > > >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
> express
> > > or
> > > > > >> implied.
> > > > > >> # See the License for the specific language governing
> > > permissions
> > > > > and
> > > > > >> # limitations

Re: Importing Source Code

2018-10-09 Thread Alan Silva

+1 here too.

Let's go to the merge, guys! :)

On Tue, Oct 9, 2018 at 3:11 PM Lucas Bonatto Miguel 
wrote:

> I saw two +1s Daniel, Imo you're good to merge.
>
> Go go go. :)
>
> Regards,
> Lucas
>
> On Tue, Oct 9, 2018 at 12:18 PM Luciano Resende 
> wrote:
>
> > If the community is ok, you should be able to follow the steps from
> > the link below to push the repository as a mirror of the current one
> >
> >
> >
> https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
> >
> > On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
> >  wrote:
> > >
> > > To me it look like perfect. What is the next step? Could I help?
> > >
> > > Atenciosamente,
> > > Rafael J. R. Novello
> > >
> > > Skype: rafael.novello
> > > Blog: http://rafanovello.blogspot.com.br/
> > >
> > >
> > > Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> > > daniel.takabaya...@gmail.com> escreveu:
> > >
> > > > Hello Guys, anyone has something to say?
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Oct 4, 2018, at 7:40 AM, Rafael Novello <
> > rafa.reis.nove...@gmail.com>
> > > > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > All the history was preserved! I think we are fine!
> > > > >
> > > > > Best!
> > > > > Atenciosamente,
> > > > > Rafael J. R. Novello
> > > > >
> > > > > Skype: rafael.novello
> > > > > Blog: http://rafanovello.blogspot.com.br/
> > > > >
> > > > >
> > > > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > > > lucasbona...@gmail.com> escreveu:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> Looks good to me. We should prioritize better READMEs in the near
> > > > future.
> > > > >> For the scope of this story I think you did a good job.
> > > > >>
> > > > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > > > >> daniel.takabaya...@gmail.com> wrote:
> > > > >>
> > > > >>> Ok guys, I finished the merge of our 3 main repos:
> > > > >>>
> > > > >>>
> > > > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > > > >>> *
> > > > >>>
> > > > >>> *https://github.com/marvin-ai/marvin-public-engines
> > > > >>> *
> > > > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > > > >>> *
> > > > >>>
> > > > >>> Into this one ...
> > > > >>>
> > > > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > > > >>> *
> > > > >>>
> > > > >>> All commits history remained and ... please check and feel free
> to
> > > > >>> collaborate before we replicate into our apache account. And any
> > > > problem
> > > > >>> ...let me know!
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Taka
> > > > >>>
> > > > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > > > >>> daniel.takabaya...@gmail.com> escreveu:
> > > > >>>
> > > >  Sounds good.
> > > > 
> > > >  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> > > > >> luckbr1...@gmail.com
> > > > 
> > > >  escreveu:
> > > > 
> > > > > So, before pushing to the apache repo, make a draft repo
> outside
> > > > >> apache
> > > > > and let couple people to review
> > > > >
> > > > > The  you can push to apache... as a mirror.
> > > > >
> > > > > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > > > > daniel.takabaya...@gmail.com> wrote:
> > > > >
> > > > >> Ok, now is clear
> > > > >>
> > > > >> This is the repo
> > > > >>  I
> am
> > > > >> going
> > > > >> to push the new merged code. Another question is about the
> > license,
> > > > >>> right
> > > > >> now all files has this license here:
> > > > >>
> > > > >> # Copyright [2017] [B2W Digital]
> > > > >> #
> > > > >> # Licensed under the Apache License, Version 2.0 (the
> > "License");
> > > > >> # you may not use this file except in compliance with the
> > License.
> > > > >> # You may obtain a copy of the License at
> > > > >> #
> > > > >> #http://www.apache.org/licenses/LICENSE-2.0
> > > > >> #
> > > > >> # Unless required by applicable law or agreed to in writing,
> > > > software
> > > > >> # distributed under the License is distributed on an "AS IS"
> > BASIS,
> > > > >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
> > or
> > > > >> implied.
> > > > >> # See the License for the specific language governing
> > permissions
> > > > and
> > > > >> # limitations under the License.
> > > > >>
> > > > >> should we change this before the import commit or later is ok?
> > > > >>
> > > > >> Thanks,
> > > > >> Taka
> > > > >>
> > > > >>
> > > > >> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> > > > >>> luckbr1...@gmail.com>
> > > > >> escreveu:
> > > > >>
> > > > >>> This is

Re: Importing Source Code

2018-10-09 Thread Lucas Bonatto Miguel

I saw two +1s Daniel, Imo you're good to merge.

Go go go. :)

Regards,
Lucas

On Tue, Oct 9, 2018 at 12:18 PM Luciano Resende 
wrote:

> If the community is ok, you should be able to follow the steps from
> the link below to push the repository as a mirror of the current one
>
>
> https://help.github.com/articles/importing-a-git-repository-using-the-command-line/
>
> On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
>  wrote:
> >
> > To me it look like perfect. What is the next step? Could I help?
> >
> > Atenciosamente,
> > Rafael J. R. Novello
> >
> > Skype: rafael.novello
> > Blog: http://rafanovello.blogspot.com.br/
> >
> >
> > Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> > daniel.takabaya...@gmail.com> escreveu:
> >
> > > Hello Guys, anyone has something to say?
> > >
> > > Sent from my iPhone
> > >
> > > > On Oct 4, 2018, at 7:40 AM, Rafael Novello <
> rafa.reis.nove...@gmail.com>
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > All the history was preserved! I think we are fine!
> > > >
> > > > Best!
> > > > Atenciosamente,
> > > > Rafael J. R. Novello
> > > >
> > > > Skype: rafael.novello
> > > > Blog: http://rafanovello.blogspot.com.br/
> > > >
> > > >
> > > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > > lucasbona...@gmail.com> escreveu:
> > > >
> > > >> +1
> > > >>
> > > >> Looks good to me. We should prioritize better READMEs in the near
> > > future.
> > > >> For the scope of this story I think you did a good job.
> > > >>
> > > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > > >> daniel.takabaya...@gmail.com> wrote:
> > > >>
> > > >>> Ok guys, I finished the merge of our 3 main repos:
> > > >>>
> > > >>>
> > > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > > >>> *
> > > >>>
> > > >>> *https://github.com/marvin-ai/marvin-public-engines
> > > >>> *
> > > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > > >>> *
> > > >>>
> > > >>> Into this one ...
> > > >>>
> > > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > > >>> *
> > > >>>
> > > >>> All commits history remained and ... please check and feel free to
> > > >>> collaborate before we replicate into our apache account. And any
> > > problem
> > > >>> ...let me know!
> > > >>>
> > > >>> Thanks,
> > > >>> Taka
> > > >>>
> > > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > > >>> daniel.takabaya...@gmail.com> escreveu:
> > > >>>
> > >  Sounds good.
> > > 
> > >  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> > > >> luckbr1...@gmail.com
> > > 
> > >  escreveu:
> > > 
> > > > So, before pushing to the apache repo, make a draft repo outside
> > > >> apache
> > > > and let couple people to review
> > > >
> > > > The  you can push to apache... as a mirror.
> > > >
> > > > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > > > daniel.takabaya...@gmail.com> wrote:
> > > >
> > > >> Ok, now is clear
> > > >>
> > > >> This is the repo
> > > >>  I am
> > > >> going
> > > >> to push the new merged code. Another question is about the
> license,
> > > >>> right
> > > >> now all files has this license here:
> > > >>
> > > >> # Copyright [2017] [B2W Digital]
> > > >> #
> > > >> # Licensed under the Apache License, Version 2.0 (the
> "License");
> > > >> # you may not use this file except in compliance with the
> License.
> > > >> # You may obtain a copy of the License at
> > > >> #
> > > >> #http://www.apache.org/licenses/LICENSE-2.0
> > > >> #
> > > >> # Unless required by applicable law or agreed to in writing,
> > > software
> > > >> # distributed under the License is distributed on an "AS IS"
> BASIS,
> > > >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
> or
> > > >> implied.
> > > >> # See the License for the specific language governing
> permissions
> > > and
> > > >> # limitations under the License.
> > > >>
> > > >> should we change this before the import commit or later is ok?
> > > >>
> > > >> Thanks,
> > > >> Taka
> > > >>
> > > >>
> > > >> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> > > >>> luckbr1...@gmail.com>
> > > >> escreveu:
> > > >>
> > > >>> This is a little bit different because it's the first code
> import.
> > > >>>
> > > >>> As a suggestion, how about you create a repository somewhere in
> > > >> GitHub
> > > >>> when you are ready to import, let the community do a quick
> review,
> > > >> and
> > > >>> we can then import it as a replica.
> > > >>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
> > > >>>  wrote:
> > >

Re: Importing Source Code

2018-10-09 Thread Luciano Resende

If the community is ok, you should be able to follow the steps from
the link below to push the repository as a mirror of the current one

https://help.github.com/articles/importing-a-git-repository-using-the-command-line/

On Tue, Oct 9, 2018 at 10:37 AM Rafael Novello
 wrote:
>
> To me it look like perfect. What is the next step? Could I help?
>
> Atenciosamente,
> Rafael J. R. Novello
>
> Skype: rafael.novello
> Blog: http://rafanovello.blogspot.com.br/
>
>
> Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
> daniel.takabaya...@gmail.com> escreveu:
>
> > Hello Guys, anyone has something to say?
> >
> > Sent from my iPhone
> >
> > > On Oct 4, 2018, at 7:40 AM, Rafael Novello 
> > wrote:
> > >
> > > +1
> > >
> > > All the history was preserved! I think we are fine!
> > >
> > > Best!
> > > Atenciosamente,
> > > Rafael J. R. Novello
> > >
> > > Skype: rafael.novello
> > > Blog: http://rafanovello.blogspot.com.br/
> > >
> > >
> > > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > > lucasbona...@gmail.com> escreveu:
> > >
> > >> +1
> > >>
> > >> Looks good to me. We should prioritize better READMEs in the near
> > future.
> > >> For the scope of this story I think you did a good job.
> > >>
> > >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> > >> daniel.takabaya...@gmail.com> wrote:
> > >>
> > >>> Ok guys, I finished the merge of our 3 main repos:
> > >>>
> > >>>
> > >>> *https://github.com/marvin-ai/marvin-python-toolbox
> > >>> *
> > >>>
> > >>> *https://github.com/marvin-ai/marvin-public-engines
> > >>> *
> > >>> *https://github.com/marvin-ai/marvin-engine-executor
> > >>> *
> > >>>
> > >>> Into this one ...
> > >>>
> > >>> *https://github.com/marvin-ai/incubator-apache-marvin
> > >>> *
> > >>>
> > >>> All commits history remained and ... please check and feel free to
> > >>> collaborate before we replicate into our apache account. And any
> > problem
> > >>> ...let me know!
> > >>>
> > >>> Thanks,
> > >>> Taka
> > >>>
> > >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > >>> daniel.takabaya...@gmail.com> escreveu:
> > >>>
> >  Sounds good.
> > 
> >  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> > >> luckbr1...@gmail.com
> > 
> >  escreveu:
> > 
> > > So, before pushing to the apache repo, make a draft repo outside
> > >> apache
> > > and let couple people to review
> > >
> > > The  you can push to apache... as a mirror.
> > >
> > > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > > daniel.takabaya...@gmail.com> wrote:
> > >
> > >> Ok, now is clear
> > >>
> > >> This is the repo
> > >>  I am
> > >> going
> > >> to push the new merged code. Another question is about the license,
> > >>> right
> > >> now all files has this license here:
> > >>
> > >> # Copyright [2017] [B2W Digital]
> > >> #
> > >> # Licensed under the Apache License, Version 2.0 (the "License");
> > >> # you may not use this file except in compliance with the License.
> > >> # You may obtain a copy of the License at
> > >> #
> > >> #http://www.apache.org/licenses/LICENSE-2.0
> > >> #
> > >> # Unless required by applicable law or agreed to in writing,
> > software
> > >> # distributed under the License is distributed on an "AS IS" BASIS,
> > >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > >> implied.
> > >> # See the License for the specific language governing permissions
> > and
> > >> # limitations under the License.
> > >>
> > >> should we change this before the import commit or later is ok?
> > >>
> > >> Thanks,
> > >> Taka
> > >>
> > >>
> > >> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> > >>> luckbr1...@gmail.com>
> > >> escreveu:
> > >>
> > >>> This is a little bit different because it's the first code import.
> > >>>
> > >>> As a suggestion, how about you create a repository somewhere in
> > >> GitHub
> > >>> when you are ready to import, let the community do a quick review,
> > >> and
> > >>> we can then import it as a replica.
> > >>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
> > >>>  wrote:
> > 
> >  Hey guys, I will try to finish this by today. But then I need to
> > >>> open
> > >>> any PR or what??
> > 
> >  As is my first time as Apache contributor I’m a little lost about
> > >>> the
> > >>> correct procedure. Could you clarify this Luciano?
> > 
> >  Sent from my iPhone
> > 
> > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
> > >>> lucasbona...@gmail.com> wrote:
> >

Re: Importing Source Code

2018-10-09 Thread Rafael Novello

To me it look like perfect. What is the next step? Could I help?

Atenciosamente,
Rafael J. R. Novello

Skype: rafael.novello
Blog: http://rafanovello.blogspot.com.br/


Em ter, 9 de out de 2018 às 14:08, Daniel Takabayashi <
daniel.takabaya...@gmail.com> escreveu:

> Hello Guys, anyone has something to say?
>
> Sent from my iPhone
>
> > On Oct 4, 2018, at 7:40 AM, Rafael Novello 
> wrote:
> >
> > +1
> >
> > All the history was preserved! I think we are fine!
> >
> > Best!
> > Atenciosamente,
> > Rafael J. R. Novello
> >
> > Skype: rafael.novello
> > Blog: http://rafanovello.blogspot.com.br/
> >
> >
> > Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> > lucasbona...@gmail.com> escreveu:
> >
> >> +1
> >>
> >> Looks good to me. We should prioritize better READMEs in the near
> future.
> >> For the scope of this story I think you did a good job.
> >>
> >> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> >> daniel.takabaya...@gmail.com> wrote:
> >>
> >>> Ok guys, I finished the merge of our 3 main repos:
> >>>
> >>>
> >>> *https://github.com/marvin-ai/marvin-python-toolbox
> >>> *
> >>>
> >>> *https://github.com/marvin-ai/marvin-public-engines
> >>> *
> >>> *https://github.com/marvin-ai/marvin-engine-executor
> >>> *
> >>>
> >>> Into this one ...
> >>>
> >>> *https://github.com/marvin-ai/incubator-apache-marvin
> >>> *
> >>>
> >>> All commits history remained and ... please check and feel free to
> >>> collaborate before we replicate into our apache account. And any
> problem
> >>> ...let me know!
> >>>
> >>> Thanks,
> >>> Taka
> >>>
> >>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> >>> daniel.takabaya...@gmail.com> escreveu:
> >>>
>  Sounds good.
> 
>  Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> >> luckbr1...@gmail.com
> 
>  escreveu:
> 
> > So, before pushing to the apache repo, make a draft repo outside
> >> apache
> > and let couple people to review
> >
> > The  you can push to apache... as a mirror.
> >
> > On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > daniel.takabaya...@gmail.com> wrote:
> >
> >> Ok, now is clear
> >>
> >> This is the repo
> >>  I am
> >> going
> >> to push the new merged code. Another question is about the license,
> >>> right
> >> now all files has this license here:
> >>
> >> # Copyright [2017] [B2W Digital]
> >> #
> >> # Licensed under the Apache License, Version 2.0 (the "License");
> >> # you may not use this file except in compliance with the License.
> >> # You may obtain a copy of the License at
> >> #
> >> #http://www.apache.org/licenses/LICENSE-2.0
> >> #
> >> # Unless required by applicable law or agreed to in writing,
> software
> >> # distributed under the License is distributed on an "AS IS" BASIS,
> >> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >> # See the License for the specific language governing permissions
> and
> >> # limitations under the License.
> >>
> >> should we change this before the import commit or later is ok?
> >>
> >> Thanks,
> >> Taka
> >>
> >>
> >> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> >>> luckbr1...@gmail.com>
> >> escreveu:
> >>
> >>> This is a little bit different because it's the first code import.
> >>>
> >>> As a suggestion, how about you create a repository somewhere in
> >> GitHub
> >>> when you are ready to import, let the community do a quick review,
> >> and
> >>> we can then import it as a replica.
> >>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
> >>>  wrote:
> 
>  Hey guys, I will try to finish this by today. But then I need to
> >>> open
> >>> any PR or what??
> 
>  As is my first time as Apache contributor I’m a little lost about
> >>> the
> >>> correct procedure. Could you clarify this Luciano?
> 
>  Sent from my iPhone
> 
> > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
> >>> lucasbona...@gmail.com> wrote:
> >
> > Hey Luciano, Daniel and I started working on it this weekend, it
> >>> is
> >>> being a
> > bit more tricky then we thought. We should have the code pushed
> >> by
> >>> the end
> > of this week.
> >
> > - Lucas
> >
> >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
> >>> luckbr1...@gmail.com> wrote:
> >>
> >> Any progress here? Any help needed?
> >>
> >> Note that the software grant process is not a blocker on having
> >>> the
> >>

Re: Importing Source Code

2018-10-09 Thread Daniel Takabayashi

Hello Guys, anyone has something to say?

Sent from my iPhone

> On Oct 4, 2018, at 7:40 AM, Rafael Novello  
> wrote:
> 
> +1
> 
> All the history was preserved! I think we are fine!
> 
> Best!
> Atenciosamente,
> Rafael J. R. Novello
> 
> Skype: rafael.novello
> Blog: http://rafanovello.blogspot.com.br/
> 
> 
> Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
> lucasbona...@gmail.com> escreveu:
> 
>> +1
>> 
>> Looks good to me. We should prioritize better READMEs in the near future.
>> For the scope of this story I think you did a good job.
>> 
>> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
>> daniel.takabaya...@gmail.com> wrote:
>> 
>>> Ok guys, I finished the merge of our 3 main repos:
>>> 
>>> 
>>> *https://github.com/marvin-ai/marvin-python-toolbox
>>> *
>>> 
>>> *https://github.com/marvin-ai/marvin-public-engines
>>> *
>>> *https://github.com/marvin-ai/marvin-engine-executor
>>> *
>>> 
>>> Into this one ...
>>> 
>>> *https://github.com/marvin-ai/incubator-apache-marvin
>>> *
>>> 
>>> All commits history remained and ... please check and feel free to
>>> collaborate before we replicate into our apache account. And any problem
>>> ...let me know!
>>> 
>>> Thanks,
>>> Taka
>>> 
>>> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
>>> daniel.takabaya...@gmail.com> escreveu:
>>> 
 Sounds good.
 
 Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
>> luckbr1...@gmail.com
 
 escreveu:
 
> So, before pushing to the apache repo, make a draft repo outside
>> apache
> and let couple people to review
> 
> The  you can push to apache... as a mirror.
> 
> On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> daniel.takabaya...@gmail.com> wrote:
> 
>> Ok, now is clear
>> 
>> This is the repo
>>  I am
>> going
>> to push the new merged code. Another question is about the license,
>>> right
>> now all files has this license here:
>> 
>> # Copyright [2017] [B2W Digital]
>> #
>> # Licensed under the Apache License, Version 2.0 (the "License");
>> # you may not use this file except in compliance with the License.
>> # You may obtain a copy of the License at
>> #
>> #http://www.apache.org/licenses/LICENSE-2.0
>> #
>> # Unless required by applicable law or agreed to in writing, software
>> # distributed under the License is distributed on an "AS IS" BASIS,
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> implied.
>> # See the License for the specific language governing permissions and
>> # limitations under the License.
>> 
>> should we change this before the import commit or later is ok?
>> 
>> Thanks,
>> Taka
>> 
>> 
>> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
>>> luckbr1...@gmail.com>
>> escreveu:
>> 
>>> This is a little bit different because it's the first code import.
>>> 
>>> As a suggestion, how about you create a repository somewhere in
>> GitHub
>>> when you are ready to import, let the community do a quick review,
>> and
>>> we can then import it as a replica.
>>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
>>>  wrote:
 
 Hey guys, I will try to finish this by today. But then I need to
>>> open
>>> any PR or what??
 
 As is my first time as Apache contributor I’m a little lost about
>>> the
>>> correct procedure. Could you clarify this Luciano?
 
 Sent from my iPhone
 
> On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
>>> lucasbona...@gmail.com> wrote:
> 
> Hey Luciano, Daniel and I started working on it this weekend, it
>>> is
>>> being a
> bit more tricky then we thought. We should have the code pushed
>> by
>>> the end
> of this week.
> 
> - Lucas
> 
>> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
>>> luckbr1...@gmail.com> wrote:
>> 
>> Any progress here? Any help needed?
>> 
>> Note that the software grant process is not a blocker on having
>>> the
>> code imported and these can occur in parallel.
>> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>>  wrote:
>>> 
>>> Yes...the ideia is to merge all repos but keeping the history
>> of
>>> all
>>> commits.
>>> I did this once in the past and is pretty easy and reliable.
>>> 
>>> About the grant any information or request to B2W, I can
>>> arrange.
>>> Just
>> let
>>> me know @Lucas Bonatto Miguel  .
>>> 
>>> Em

Re: Importing Source Code

2018-10-04 Thread Rafael Novello

+1

All the history was preserved! I think we are fine!

Best!
Atenciosamente,
Rafael J. R. Novello

Skype: rafael.novello
Blog: http://rafanovello.blogspot.com.br/


Em qui, 4 de out de 2018 às 06:50, Lucas Bonatto Miguel <
lucasbona...@gmail.com> escreveu:

> +1
>
> Looks good to me. We should prioritize better READMEs in the near future.
> For the scope of this story I think you did a good job.
>
> On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
> daniel.takabaya...@gmail.com> wrote:
>
> > Ok guys, I finished the merge of our 3 main repos:
> >
> >
> > *https://github.com/marvin-ai/marvin-python-toolbox
> > *
> >
> > *https://github.com/marvin-ai/marvin-public-engines
> > *
> > *https://github.com/marvin-ai/marvin-engine-executor
> > *
> >
> > Into this one ...
> >
> > *https://github.com/marvin-ai/incubator-apache-marvin
> > *
> >
> > All commits history remained and ... please check and feel free to
> > collaborate before we replicate into our apache account. And any problem
> > ...let me know!
> >
> > Thanks,
> > Taka
> >
> > Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> > daniel.takabaya...@gmail.com> escreveu:
> >
> > > Sounds good.
> > >
> > > Em ter, 2 de out de 2018 às 11:44, Luciano Resende <
> luckbr1...@gmail.com
> > >
> > > escreveu:
> > >
> > >> So, before pushing to the apache repo, make a draft repo outside
> apache
> > >> and let couple people to review
> > >>
> > >> The  you can push to apache... as a mirror.
> > >>
> > >> On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> > >> daniel.takabaya...@gmail.com> wrote:
> > >>
> > >>> Ok, now is clear
> > >>>
> > >>> This is the repo
> > >>>  I am
> going
> > >>> to push the new merged code. Another question is about the license,
> > right
> > >>> now all files has this license here:
> > >>>
> > >>> # Copyright [2017] [B2W Digital]
> > >>> #
> > >>> # Licensed under the Apache License, Version 2.0 (the "License");
> > >>> # you may not use this file except in compliance with the License.
> > >>> # You may obtain a copy of the License at
> > >>> #
> > >>> #http://www.apache.org/licenses/LICENSE-2.0
> > >>> #
> > >>> # Unless required by applicable law or agreed to in writing, software
> > >>> # distributed under the License is distributed on an "AS IS" BASIS,
> > >>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > >>> implied.
> > >>> # See the License for the specific language governing permissions and
> > >>> # limitations under the License.
> > >>>
> > >>> should we change this before the import commit or later is ok?
> > >>>
> > >>> Thanks,
> > >>> Taka
> > >>>
> > >>>
> > >>> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> > luckbr1...@gmail.com>
> > >>> escreveu:
> > >>>
> >  This is a little bit different because it's the first code import.
> > 
> >  As a suggestion, how about you create a repository somewhere in
> GitHub
> >  when you are ready to import, let the community do a quick review,
> and
> >  we can then import it as a replica.
> >  On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
> >   wrote:
> >  >
> >  > Hey guys, I will try to finish this by today. But then I need to
> > open
> >  any PR or what??
> >  >
> >  > As is my first time as Apache contributor I’m a little lost about
> > the
> >  correct procedure. Could you clarify this Luciano?
> >  >
> >  > Sent from my iPhone
> >  >
> >  > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
> >  lucasbona...@gmail.com> wrote:
> >  > >
> >  > > Hey Luciano, Daniel and I started working on it this weekend, it
> > is
> >  being a
> >  > > bit more tricky then we thought. We should have the code pushed
> by
> >  the end
> >  > > of this week.
> >  > >
> >  > > - Lucas
> >  > >
> >  > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
> >  luckbr1...@gmail.com> wrote:
> >  > >>
> >  > >> Any progress here? Any help needed?
> >  > >>
> >  > >> Note that the software grant process is not a blocker on having
> > the
> >  > >> code imported and these can occur in parallel.
> >  > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
> >  > >>  wrote:
> >  > >>>
> >  > >>> Yes...the ideia is to merge all repos but keeping the history
> of
> >  all
> >  > >>> commits.
> >  > >>> I did this once in the past and is pretty easy and reliable.
> >  > >>>
> >  > >>> About the grant any information or request to B2W, I can
> > arrange.
> >  Just
> >  > >> let
> >  > >>> me know @Lucas Bonatto Miguel  .
> >  > >>>
> >  > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel

Re: Importing Source Code

2018-10-04 Thread Lucas Bonatto Miguel

+1

Looks good to me. We should prioritize better READMEs in the near future.
For the scope of this story I think you did a good job.

On Wed, Oct 3, 2018 at 12:05 PM Daniel Takabayashi <
daniel.takabaya...@gmail.com> wrote:

> Ok guys, I finished the merge of our 3 main repos:
>
>
> *https://github.com/marvin-ai/marvin-python-toolbox
> *
>
> *https://github.com/marvin-ai/marvin-public-engines
> *
> *https://github.com/marvin-ai/marvin-engine-executor
> *
>
> Into this one ...
>
> *https://github.com/marvin-ai/incubator-apache-marvin
> *
>
> All commits history remained and ... please check and feel free to
> collaborate before we replicate into our apache account. And any problem
> ...let me know!
>
> Thanks,
> Taka
>
> Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
> daniel.takabaya...@gmail.com> escreveu:
>
> > Sounds good.
> >
> > Em ter, 2 de out de 2018 às 11:44, Luciano Resende  >
> > escreveu:
> >
> >> So, before pushing to the apache repo, make a draft repo outside apache
> >> and let couple people to review
> >>
> >> The  you can push to apache... as a mirror.
> >>
> >> On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> >> daniel.takabaya...@gmail.com> wrote:
> >>
> >>> Ok, now is clear
> >>>
> >>> This is the repo
> >>>  I am going
> >>> to push the new merged code. Another question is about the license,
> right
> >>> now all files has this license here:
> >>>
> >>> # Copyright [2017] [B2W Digital]
> >>> #
> >>> # Licensed under the Apache License, Version 2.0 (the "License");
> >>> # you may not use this file except in compliance with the License.
> >>> # You may obtain a copy of the License at
> >>> #
> >>> #http://www.apache.org/licenses/LICENSE-2.0
> >>> #
> >>> # Unless required by applicable law or agreed to in writing, software
> >>> # distributed under the License is distributed on an "AS IS" BASIS,
> >>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >>> implied.
> >>> # See the License for the specific language governing permissions and
> >>> # limitations under the License.
> >>>
> >>> should we change this before the import commit or later is ok?
> >>>
> >>> Thanks,
> >>> Taka
> >>>
> >>>
> >>> Em seg, 1 de out de 2018 às 19:24, Luciano Resende <
> luckbr1...@gmail.com>
> >>> escreveu:
> >>>
>  This is a little bit different because it's the first code import.
> 
>  As a suggestion, how about you create a repository somewhere in GitHub
>  when you are ready to import, let the community do a quick review, and
>  we can then import it as a replica.
>  On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
>   wrote:
>  >
>  > Hey guys, I will try to finish this by today. But then I need to
> open
>  any PR or what??
>  >
>  > As is my first time as Apache contributor I’m a little lost about
> the
>  correct procedure. Could you clarify this Luciano?
>  >
>  > Sent from my iPhone
>  >
>  > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
>  lucasbona...@gmail.com> wrote:
>  > >
>  > > Hey Luciano, Daniel and I started working on it this weekend, it
> is
>  being a
>  > > bit more tricky then we thought. We should have the code pushed by
>  the end
>  > > of this week.
>  > >
>  > > - Lucas
>  > >
>  > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
>  luckbr1...@gmail.com> wrote:
>  > >>
>  > >> Any progress here? Any help needed?
>  > >>
>  > >> Note that the software grant process is not a blocker on having
> the
>  > >> code imported and these can occur in parallel.
>  > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>  > >>  wrote:
>  > >>>
>  > >>> Yes...the ideia is to merge all repos but keeping the history of
>  all
>  > >>> commits.
>  > >>> I did this once in the past and is pretty easy and reliable.
>  > >>>
>  > >>> About the grant any information or request to B2W, I can
> arrange.
>  Just
>  > >> let
>  > >>> me know @Lucas Bonatto Miguel  .
>  > >>>
>  > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
>  > >>> lucasbona...@gmail.com> escreveu:
>  > >>>
>  >  I can help with the grant process, should we request the
> current
>  > >> copyright
>  >  owner to sign this (
>  >  http://www.apache.org/licenses/proposed/software-grant.txt)
>  document?
>  > >> Any
>  >  other special instructions?
>  > 
>  >  Regarding the repos, I'm pretty sure we can add the original
>  repos as
>  > >> new
>  >  remotes, rebase them into the new Apache repo and move the
> files
>  to

Re: Importing Source Code

2018-10-03 Thread Daniel Takabayashi

Ok guys, I finished the merge of our 3 main repos:


*https://github.com/marvin-ai/marvin-python-toolbox
*

*https://github.com/marvin-ai/marvin-public-engines
*
*https://github.com/marvin-ai/marvin-engine-executor
*

Into this one ...

*https://github.com/marvin-ai/incubator-apache-marvin
*

All commits history remained and ... please check and feel free to
collaborate before we replicate into our apache account. And any problem
...let me know!

Thanks,
Taka

Em ter, 2 de out de 2018 às 11:48, Daniel Takabayashi <
daniel.takabaya...@gmail.com> escreveu:

> Sounds good.
>
> Em ter, 2 de out de 2018 às 11:44, Luciano Resende 
> escreveu:
>
>> So, before pushing to the apache repo, make a draft repo outside apache
>> and let couple people to review
>>
>> The  you can push to apache... as a mirror.
>>
>> On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
>> daniel.takabaya...@gmail.com> wrote:
>>
>>> Ok, now is clear
>>>
>>> This is the repo
>>>  I am going
>>> to push the new merged code. Another question is about the license, right
>>> now all files has this license here:
>>>
>>> # Copyright [2017] [B2W Digital]
>>> #
>>> # Licensed under the Apache License, Version 2.0 (the "License");
>>> # you may not use this file except in compliance with the License.
>>> # You may obtain a copy of the License at
>>> #
>>> #http://www.apache.org/licenses/LICENSE-2.0
>>> #
>>> # Unless required by applicable law or agreed to in writing, software
>>> # distributed under the License is distributed on an "AS IS" BASIS,
>>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>>> implied.
>>> # See the License for the specific language governing permissions and
>>> # limitations under the License.
>>>
>>> should we change this before the import commit or later is ok?
>>>
>>> Thanks,
>>> Taka
>>>
>>>
>>> Em seg, 1 de out de 2018 às 19:24, Luciano Resende 
>>> escreveu:
>>>
 This is a little bit different because it's the first code import.

 As a suggestion, how about you create a repository somewhere in GitHub
 when you are ready to import, let the community do a quick review, and
 we can then import it as a replica.
 On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
  wrote:
 >
 > Hey guys, I will try to finish this by today. But then I need to open
 any PR or what??
 >
 > As is my first time as Apache contributor I’m a little lost about the
 correct procedure. Could you clarify this Luciano?
 >
 > Sent from my iPhone
 >
 > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
 lucasbona...@gmail.com> wrote:
 > >
 > > Hey Luciano, Daniel and I started working on it this weekend, it is
 being a
 > > bit more tricky then we thought. We should have the code pushed by
 the end
 > > of this week.
 > >
 > > - Lucas
 > >
 > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
 luckbr1...@gmail.com> wrote:
 > >>
 > >> Any progress here? Any help needed?
 > >>
 > >> Note that the software grant process is not a blocker on having the
 > >> code imported and these can occur in parallel.
 > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
 > >>  wrote:
 > >>>
 > >>> Yes...the ideia is to merge all repos but keeping the history of
 all
 > >>> commits.
 > >>> I did this once in the past and is pretty easy and reliable.
 > >>>
 > >>> About the grant any information or request to B2W, I can arrange.
 Just
 > >> let
 > >>> me know @Lucas Bonatto Miguel  .
 > >>>
 > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
 > >>> lucasbona...@gmail.com> escreveu:
 > >>>
 >  I can help with the grant process, should we request the current
 > >> copyright
 >  owner to sign this (
 >  http://www.apache.org/licenses/proposed/software-grant.txt)
 document?
 > >> Any
 >  other special instructions?
 > 
 >  Regarding the repos, I'm pretty sure we can add the original
 repos as
 > >> new
 >  remotes, rebase them into the new Apache repo and move the files
 to the
 >  appropriated folders, this would keep the history of all repos.
 > 
 >  Regards,
 >  Lucas
 > 
 >  On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende <
 luckbr1...@gmail.com>
 >  wrote:
 > 
 > > So, what's the goal here?
 > >
 > > A pure merge will get a repository without history. Is this the
 >  intention?
 > >
 > > Otherwise, we can import one repository (maybe with the most
 code, or
 > >

Re: Importing Source Code

2018-10-02 Thread Daniel Takabayashi

Sounds good.

Em ter, 2 de out de 2018 às 11:44, Luciano Resende 
escreveu:

> So, before pushing to the apache repo, make a draft repo outside apache
> and let couple people to review
>
> The  you can push to apache... as a mirror.
>
> On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
> daniel.takabaya...@gmail.com> wrote:
>
>> Ok, now is clear
>>
>> This is the repo
>>  I am going to
>> push the new merged code. Another question is about the license, right now
>> all files has this license here:
>>
>> # Copyright [2017] [B2W Digital]
>> #
>> # Licensed under the Apache License, Version 2.0 (the "License");
>> # you may not use this file except in compliance with the License.
>> # You may obtain a copy of the License at
>> #
>> #http://www.apache.org/licenses/LICENSE-2.0
>> #
>> # Unless required by applicable law or agreed to in writing, software
>> # distributed under the License is distributed on an "AS IS" BASIS,
>> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>> # See the License for the specific language governing permissions and
>> # limitations under the License.
>>
>> should we change this before the import commit or later is ok?
>>
>> Thanks,
>> Taka
>>
>>
>> Em seg, 1 de out de 2018 às 19:24, Luciano Resende 
>> escreveu:
>>
>>> This is a little bit different because it's the first code import.
>>>
>>> As a suggestion, how about you create a repository somewhere in GitHub
>>> when you are ready to import, let the community do a quick review, and
>>> we can then import it as a replica.
>>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
>>>  wrote:
>>> >
>>> > Hey guys, I will try to finish this by today. But then I need to open
>>> any PR or what??
>>> >
>>> > As is my first time as Apache contributor I’m a little lost about the
>>> correct procedure. Could you clarify this Luciano?
>>> >
>>> > Sent from my iPhone
>>> >
>>> > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
>>> lucasbona...@gmail.com> wrote:
>>> > >
>>> > > Hey Luciano, Daniel and I started working on it this weekend, it is
>>> being a
>>> > > bit more tricky then we thought. We should have the code pushed by
>>> the end
>>> > > of this week.
>>> > >
>>> > > - Lucas
>>> > >
>>> > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende <
>>> luckbr1...@gmail.com> wrote:
>>> > >>
>>> > >> Any progress here? Any help needed?
>>> > >>
>>> > >> Note that the software grant process is not a blocker on having the
>>> > >> code imported and these can occur in parallel.
>>> > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>>> > >>  wrote:
>>> > >>>
>>> > >>> Yes...the ideia is to merge all repos but keeping the history of
>>> all
>>> > >>> commits.
>>> > >>> I did this once in the past and is pretty easy and reliable.
>>> > >>>
>>> > >>> About the grant any information or request to B2W, I can arrange.
>>> Just
>>> > >> let
>>> > >>> me know @Lucas Bonatto Miguel  .
>>> > >>>
>>> > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
>>> > >>> lucasbona...@gmail.com> escreveu:
>>> > >>>
>>> >  I can help with the grant process, should we request the current
>>> > >> copyright
>>> >  owner to sign this (
>>> >  http://www.apache.org/licenses/proposed/software-grant.txt)
>>> document?
>>> > >> Any
>>> >  other special instructions?
>>> > 
>>> >  Regarding the repos, I'm pretty sure we can add the original
>>> repos as
>>> > >> new
>>> >  remotes, rebase them into the new Apache repo and move the files
>>> to the
>>> >  appropriated folders, this would keep the history of all repos.
>>> > 
>>> >  Regards,
>>> >  Lucas
>>> > 
>>> >  On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende <
>>> luckbr1...@gmail.com>
>>> >  wrote:
>>> > 
>>> > > So, what's the goal here?
>>> > >
>>> > > A pure merge will get a repository without history. Is this the
>>> >  intention?
>>> > >
>>> > > Otherwise, we can import one repository (maybe with the most
>>> code, or
>>> > > most history) and then start merging the other two (which you
>>> will
>>> > > then lose the history). In this scenario, at least some history
>>> is
>>> > > preserved.
>>> > >
>>> > > Also, we need to start working on the software grant process to
>>> > > officially donate the code to Apache.
>>> > >
>>> > > Thanks
>>> > >
>>> > > -- Forwarded message -
>>> > > From: Daniel Takabayashi 
>>> > > Date: Thu, Sep 20, 2018 at 2:59 PM
>>> > > Subject: Re: Welcome to Marvin podling
>>> > > To: 
>>> > >
>>> > >
>>> > > Great Luciano! Thanks...
>>> > >
>>> > > So...now I going to start the merge of the 3 main repos:
>>> > >
>>> > > marvin-python-toolbox
>>> > > marvin-engine-executor
>>> > > marvin-public-engines
>>> > >
>>> > > I think this will be easy...This will generate our first

Re: Importing Source Code

2018-10-02 Thread Luciano Resende

So, before pushing to the apache repo, make a draft repo outside apache and
let couple people to review

The  you can push to apache... as a mirror.

On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
daniel.takabaya...@gmail.com> wrote:

> Ok, now is clear
>
> This is the repo
>  I am going to
> push the new merged code. Another question is about the license, right now
> all files has this license here:
>
> # Copyright [2017] [B2W Digital]
> #
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> #http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
>
> should we change this before the import commit or later is ok?
>
> Thanks,
> Taka
>
>
> Em seg, 1 de out de 2018 às 19:24, Luciano Resende 
> escreveu:
>
>> This is a little bit different because it's the first code import.
>>
>> As a suggestion, how about you create a repository somewhere in GitHub
>> when you are ready to import, let the community do a quick review, and
>> we can then import it as a replica.
>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
>>  wrote:
>> >
>> > Hey guys, I will try to finish this by today. But then I need to open
>> any PR or what??
>> >
>> > As is my first time as Apache contributor I’m a little lost about the
>> correct procedure. Could you clarify this Luciano?
>> >
>> > Sent from my iPhone
>> >
>> > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
>> lucasbona...@gmail.com> wrote:
>> > >
>> > > Hey Luciano, Daniel and I started working on it this weekend, it is
>> being a
>> > > bit more tricky then we thought. We should have the code pushed by
>> the end
>> > > of this week.
>> > >
>> > > - Lucas
>> > >
>> > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende 
>> wrote:
>> > >>
>> > >> Any progress here? Any help needed?
>> > >>
>> > >> Note that the software grant process is not a blocker on having the
>> > >> code imported and these can occur in parallel.
>> > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>> > >>  wrote:
>> > >>>
>> > >>> Yes...the ideia is to merge all repos but keeping the history of all
>> > >>> commits.
>> > >>> I did this once in the past and is pretty easy and reliable.
>> > >>>
>> > >>> About the grant any information or request to B2W, I can arrange.
>> Just
>> > >> let
>> > >>> me know @Lucas Bonatto Miguel  .
>> > >>>
>> > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
>> > >>> lucasbona...@gmail.com> escreveu:
>> > >>>
>> >  I can help with the grant process, should we request the current
>> > >> copyright
>> >  owner to sign this (
>> >  http://www.apache.org/licenses/proposed/software-grant.txt)
>> document?
>> > >> Any
>> >  other special instructions?
>> > 
>> >  Regarding the repos, I'm pretty sure we can add the original repos
>> as
>> > >> new
>> >  remotes, rebase them into the new Apache repo and move the files
>> to the
>> >  appropriated folders, this would keep the history of all repos.
>> > 
>> >  Regards,
>> >  Lucas
>> > 
>> >  On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende <
>> luckbr1...@gmail.com>
>> >  wrote:
>> > 
>> > > So, what's the goal here?
>> > >
>> > > A pure merge will get a repository without history. Is this the
>> >  intention?
>> > >
>> > > Otherwise, we can import one repository (maybe with the most
>> code, or
>> > > most history) and then start merging the other two (which you will
>> > > then lose the history). In this scenario, at least some history is
>> > > preserved.
>> > >
>> > > Also, we need to start working on the software grant process to
>> > > officially donate the code to Apache.
>> > >
>> > > Thanks
>> > >
>> > > -- Forwarded message -
>> > > From: Daniel Takabayashi 
>> > > Date: Thu, Sep 20, 2018 at 2:59 PM
>> > > Subject: Re: Welcome to Marvin podling
>> > > To: 
>> > >
>> > >
>> > > Great Luciano! Thanks...
>> > >
>> > > So...now I going to start the merge of the 3 main repos:
>> > >
>> > > marvin-python-toolbox
>> > > marvin-engine-executor
>> > > marvin-public-engines
>> > >
>> > > I think this will be easy...This will generate our first PR,
>> right?
>> > >
>> > >
>> > >
>> > > --
>> > > Luciano Resende
>> > > http://twitter.com/lresende1975
>> > > http://lresende.blogspot.com/
>> > >
>> > 
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Luciano Resende
>> > >>

Re: Importing Source Code

2018-10-02 Thread Luciano Resende

The license header updates and any other migration can happen at apache.
It’s also good to update the readme of the original repositories mentioned
it moved to apache, and the  make them read only so  o PRs and/or issues
are created.

On Tue, Oct 2, 2018 at 12:07 Daniel Takabayashi <
daniel.takabaya...@gmail.com> wrote:

> Ok, now is clear
>
> This is the repo
>  I am going to
> push the new merged code. Another question is about the license, right now
> all files has this license here:
>
> # Copyright [2017] [B2W Digital]
> #
> # Licensed under the Apache License, Version 2.0 (the "License");
> # you may not use this file except in compliance with the License.
> # You may obtain a copy of the License at
> #
> #http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
>
> should we change this before the import commit or later is ok?
>
> Thanks,
> Taka
>
>
> Em seg, 1 de out de 2018 às 19:24, Luciano Resende 
> escreveu:
>
>> This is a little bit different because it's the first code import.
>>
>> As a suggestion, how about you create a repository somewhere in GitHub
>> when you are ready to import, let the community do a quick review, and
>> we can then import it as a replica.
>> On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
>>  wrote:
>> >
>> > Hey guys, I will try to finish this by today. But then I need to open
>> any PR or what??
>> >
>> > As is my first time as Apache contributor I’m a little lost about the
>> correct procedure. Could you clarify this Luciano?
>> >
>> > Sent from my iPhone
>> >
>> > > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel <
>> lucasbona...@gmail.com> wrote:
>> > >
>> > > Hey Luciano, Daniel and I started working on it this weekend, it is
>> being a
>> > > bit more tricky then we thought. We should have the code pushed by
>> the end
>> > > of this week.
>> > >
>> > > - Lucas
>> > >
>> > >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende 
>> wrote:
>> > >>
>> > >> Any progress here? Any help needed?
>> > >>
>> > >> Note that the software grant process is not a blocker on having the
>> > >> code imported and these can occur in parallel.
>> > >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>> > >>  wrote:
>> > >>>
>> > >>> Yes...the ideia is to merge all repos but keeping the history of all
>> > >>> commits.
>> > >>> I did this once in the past and is pretty easy and reliable.
>> > >>>
>> > >>> About the grant any information or request to B2W, I can arrange.
>> Just
>> > >> let
>> > >>> me know @Lucas Bonatto Miguel  .
>> > >>>
>> > >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
>> > >>> lucasbona...@gmail.com> escreveu:
>> > >>>
>> >  I can help with the grant process, should we request the current
>> > >> copyright
>> >  owner to sign this (
>> >  http://www.apache.org/licenses/proposed/software-grant.txt)
>> document?
>> > >> Any
>> >  other special instructions?
>> > 
>> >  Regarding the repos, I'm pretty sure we can add the original repos
>> as
>> > >> new
>> >  remotes, rebase them into the new Apache repo and move the files
>> to the
>> >  appropriated folders, this would keep the history of all repos.
>> > 
>> >  Regards,
>> >  Lucas
>> > 
>> >  On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende <
>> luckbr1...@gmail.com>
>> >  wrote:
>> > 
>> > > So, what's the goal here?
>> > >
>> > > A pure merge will get a repository without history. Is this the
>> >  intention?
>> > >
>> > > Otherwise, we can import one repository (maybe with the most
>> code, or
>> > > most history) and then start merging the other two (which you will
>> > > then lose the history). In this scenario, at least some history is
>> > > preserved.
>> > >
>> > > Also, we need to start working on the software grant process to
>> > > officially donate the code to Apache.
>> > >
>> > > Thanks
>> > >
>> > > -- Forwarded message -
>> > > From: Daniel Takabayashi 
>> > > Date: Thu, Sep 20, 2018 at 2:59 PM
>> > > Subject: Re: Welcome to Marvin podling
>> > > To: 
>> > >
>> > >
>> > > Great Luciano! Thanks...
>> > >
>> > > So...now I going to start the merge of the 3 main repos:
>> > >
>> > > marvin-python-toolbox
>> > > marvin-engine-executor
>> > > marvin-public-engines
>> > >
>> > > I think this will be easy...This will generate our first PR,
>> right?
>> > >
>> > >
>> > >
>> > > --
>> > > Luciano Resende
>> > > http://twitter.com/lresende1975
>> > > http://lresende.blogspot.com/
>> >

Re: Importing Source Code

2018-10-01 Thread Luciano Resende

This is a little bit different because it's the first code import.

As a suggestion, how about you create a repository somewhere in GitHub
when you are ready to import, let the community do a quick review, and
we can then import it as a replica.
On Mon, Oct 1, 2018 at 7:06 PM Daniel Takabayashi
 wrote:
>
> Hey guys, I will try to finish this by today. But then I need to open any PR 
> or what??
>
> As is my first time as Apache contributor I’m a little lost about the correct 
> procedure. Could you clarify this Luciano?
>
> Sent from my iPhone
>
> > On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel  
> > wrote:
> >
> > Hey Luciano, Daniel and I started working on it this weekend, it is being a
> > bit more tricky then we thought. We should have the code pushed by the end
> > of this week.
> >
> > - Lucas
> >
> >> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende  
> >> wrote:
> >>
> >> Any progress here? Any help needed?
> >>
> >> Note that the software grant process is not a blocker on having the
> >> code imported and these can occur in parallel.
> >> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
> >>  wrote:
> >>>
> >>> Yes...the ideia is to merge all repos but keeping the history of all
> >>> commits.
> >>> I did this once in the past and is pretty easy and reliable.
> >>>
> >>> About the grant any information or request to B2W, I can arrange. Just
> >> let
> >>> me know @Lucas Bonatto Miguel  .
> >>>
> >>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
> >>> lucasbona...@gmail.com> escreveu:
> >>>
>  I can help with the grant process, should we request the current
> >> copyright
>  owner to sign this (
>  http://www.apache.org/licenses/proposed/software-grant.txt) document?
> >> Any
>  other special instructions?
> 
>  Regarding the repos, I'm pretty sure we can add the original repos as
> >> new
>  remotes, rebase them into the new Apache repo and move the files to the
>  appropriated folders, this would keep the history of all repos.
> 
>  Regards,
>  Lucas
> 
>  On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
>  wrote:
> 
> > So, what's the goal here?
> >
> > A pure merge will get a repository without history. Is this the
>  intention?
> >
> > Otherwise, we can import one repository (maybe with the most code, or
> > most history) and then start merging the other two (which you will
> > then lose the history). In this scenario, at least some history is
> > preserved.
> >
> > Also, we need to start working on the software grant process to
> > officially donate the code to Apache.
> >
> > Thanks
> >
> > -- Forwarded message -
> > From: Daniel Takabayashi 
> > Date: Thu, Sep 20, 2018 at 2:59 PM
> > Subject: Re: Welcome to Marvin podling
> > To: 
> >
> >
> > Great Luciano! Thanks...
> >
> > So...now I going to start the merge of the 3 main repos:
> >
> > marvin-python-toolbox
> > marvin-engine-executor
> > marvin-public-engines
> >
> > I think this will be easy...This will generate our first PR, right?
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
> 
> >>
> >>
> >>
> >> --
> >> Luciano Resende
> >> http://twitter.com/lresende1975
> >> http://lresende.blogspot.com/
> >>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Importing Source Code

2018-10-01 Thread Daniel Takabayashi

Hey guys, I will try to finish this by today. But then I need to open any PR or 
what??

As is my first time as Apache contributor I’m a little lost about the correct 
procedure. Could you clarify this Luciano?

Sent from my iPhone

> On Oct 1, 2018, at 6:50 PM, Lucas Bonatto Miguel  
> wrote:
> 
> Hey Luciano, Daniel and I started working on it this weekend, it is being a
> bit more tricky then we thought. We should have the code pushed by the end
> of this week.
> 
> - Lucas
> 
>> On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende  wrote:
>> 
>> Any progress here? Any help needed?
>> 
>> Note that the software grant process is not a blocker on having the
>> code imported and these can occur in parallel.
>> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>>  wrote:
>>> 
>>> Yes...the ideia is to merge all repos but keeping the history of all
>>> commits.
>>> I did this once in the past and is pretty easy and reliable.
>>> 
>>> About the grant any information or request to B2W, I can arrange. Just
>> let
>>> me know @Lucas Bonatto Miguel  .
>>> 
>>> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
>>> lucasbona...@gmail.com> escreveu:
>>> 
 I can help with the grant process, should we request the current
>> copyright
 owner to sign this (
 http://www.apache.org/licenses/proposed/software-grant.txt) document?
>> Any
 other special instructions?
 
 Regarding the repos, I'm pretty sure we can add the original repos as
>> new
 remotes, rebase them into the new Apache repo and move the files to the
 appropriated folders, this would keep the history of all repos.
 
 Regards,
 Lucas
 
 On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
 wrote:
 
> So, what's the goal here?
> 
> A pure merge will get a repository without history. Is this the
 intention?
> 
> Otherwise, we can import one repository (maybe with the most code, or
> most history) and then start merging the other two (which you will
> then lose the history). In this scenario, at least some history is
> preserved.
> 
> Also, we need to start working on the software grant process to
> officially donate the code to Apache.
> 
> Thanks
> 
> -- Forwarded message -
> From: Daniel Takabayashi 
> Date: Thu, Sep 20, 2018 at 2:59 PM
> Subject: Re: Welcome to Marvin podling
> To: 
> 
> 
> Great Luciano! Thanks...
> 
> So...now I going to start the merge of the 3 main repos:
> 
> marvin-python-toolbox
> marvin-engine-executor
> marvin-public-engines
> 
> I think this will be easy...This will generate our first PR, right?
> 
> 
> 
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
> 
 
>> 
>> 
>> 
>> --
>> Luciano Resende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
>>

Re: Importing Source Code

2018-10-01 Thread Lucas Bonatto Miguel

Hey Luciano, Daniel and I started working on it this weekend, it is being a
bit more tricky then we thought. We should have the code pushed by the end
of this week.

- Lucas

On Thu, 27 Sep 2018 at 2:04 PM Luciano Resende  wrote:

> Any progress here? Any help needed?
>
> Note that the software grant process is not a blocker on having the
> code imported and these can occur in parallel.
> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>  wrote:
> >
> > Yes...the ideia is to merge all repos but keeping the history of all
> > commits.
> > I did this once in the past and is pretty easy and reliable.
> >
> > About the grant any information or request to B2W, I can arrange. Just
> let
> > me know @Lucas Bonatto Miguel  .
> >
> > Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
> > lucasbona...@gmail.com> escreveu:
> >
> > > I can help with the grant process, should we request the current
> copyright
> > > owner to sign this (
> > > http://www.apache.org/licenses/proposed/software-grant.txt) document?
> Any
> > > other special instructions?
> > >
> > > Regarding the repos, I'm pretty sure we can add the original repos as
> new
> > > remotes, rebase them into the new Apache repo and move the files to the
> > > appropriated folders, this would keep the history of all repos.
> > >
> > > Regards,
> > > Lucas
> > >
> > > On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
> > > wrote:
> > >
> > > > So, what's the goal here?
> > > >
> > > > A pure merge will get a repository without history. Is this the
> > > intention?
> > > >
> > > > Otherwise, we can import one repository (maybe with the most code, or
> > > > most history) and then start merging the other two (which you will
> > > > then lose the history). In this scenario, at least some history is
> > > > preserved.
> > > >
> > > > Also, we need to start working on the software grant process to
> > > > officially donate the code to Apache.
> > > >
> > > > Thanks
> > > >
> > > > -- Forwarded message -
> > > > From: Daniel Takabayashi 
> > > > Date: Thu, Sep 20, 2018 at 2:59 PM
> > > > Subject: Re: Welcome to Marvin podling
> > > > To: 
> > > >
> > > >
> > > > Great Luciano! Thanks...
> > > >
> > > > So...now I going to start the merge of the 3 main repos:
> > > >
> > > > marvin-python-toolbox
> > > > marvin-engine-executor
> > > > marvin-public-engines
> > > >
> > > > I think this will be easy...This will generate our first PR, right?
> > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > http://twitter.com/lresende1975
> > > > http://lresende.blogspot.com/
> > > >
> > >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: Importing Source Code

2018-10-01 Thread Alan Silva

Hi to all,

Sorry for my delay I was really busy during those days with customers and
conferences, but is there anything I can do to help with importing the
source code?

I think it would be cool for us to try to create migration tasks and work
together on them, what do you guys think?




On Thu, Sep 27, 2018 at 6:04 PM Luciano Resende 
wrote:

> Any progress here? Any help needed?
>
> Note that the software grant process is not a blocker on having the
> code imported and these can occur in parallel.
> On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
>  wrote:
> >
> > Yes...the ideia is to merge all repos but keeping the history of all
> > commits.
> > I did this once in the past and is pretty easy and reliable.
> >
> > About the grant any information or request to B2W, I can arrange. Just
> let
> > me know @Lucas Bonatto Miguel  .
> >
> > Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
> > lucasbona...@gmail.com> escreveu:
> >
> > > I can help with the grant process, should we request the current
> copyright
> > > owner to sign this (
> > > http://www.apache.org/licenses/proposed/software-grant.txt) document?
> Any
> > > other special instructions?
> > >
> > > Regarding the repos, I'm pretty sure we can add the original repos as
> new
> > > remotes, rebase them into the new Apache repo and move the files to the
> > > appropriated folders, this would keep the history of all repos.
> > >
> > > Regards,
> > > Lucas
> > >
> > > On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
> > > wrote:
> > >
> > > > So, what's the goal here?
> > > >
> > > > A pure merge will get a repository without history. Is this the
> > > intention?
> > > >
> > > > Otherwise, we can import one repository (maybe with the most code, or
> > > > most history) and then start merging the other two (which you will
> > > > then lose the history). In this scenario, at least some history is
> > > > preserved.
> > > >
> > > > Also, we need to start working on the software grant process to
> > > > officially donate the code to Apache.
> > > >
> > > > Thanks
> > > >
> > > > -- Forwarded message -
> > > > From: Daniel Takabayashi 
> > > > Date: Thu, Sep 20, 2018 at 2:59 PM
> > > > Subject: Re: Welcome to Marvin podling
> > > > To: 
> > > >
> > > >
> > > > Great Luciano! Thanks...
> > > >
> > > > So...now I going to start the merge of the 3 main repos:
> > > >
> > > > marvin-python-toolbox
> > > > marvin-engine-executor
> > > > marvin-public-engines
> > > >
> > > > I think this will be easy...This will generate our first PR, right?
> > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > http://twitter.com/lresende1975
> > > > http://lresende.blogspot.com/
> > > >
> > >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>


-- 
*Alan Silva* | Solutions Architect
t. +55 (11) 99951- <00>5242 e. alan.si...@cloudera.com
cloudera.com 

[image: Cloudera] 

[image: Cloudera on Twitter]  [image:
Cloudera on Facebook]  [image: Cloudera
on LinkedIn]

Re: Importing Source Code

2018-09-27 Thread Luciano Resende

Any progress here? Any help needed?

Note that the software grant process is not a blocker on having the
code imported and these can occur in parallel.
On Thu, Sep 20, 2018 at 9:47 PM Daniel Takabayashi
 wrote:
>
> Yes...the ideia is to merge all repos but keeping the history of all
> commits.
> I did this once in the past and is pretty easy and reliable.
>
> About the grant any information or request to B2W, I can arrange. Just let
> me know @Lucas Bonatto Miguel  .
>
> Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
> lucasbona...@gmail.com> escreveu:
>
> > I can help with the grant process, should we request the current copyright
> > owner to sign this (
> > http://www.apache.org/licenses/proposed/software-grant.txt) document? Any
> > other special instructions?
> >
> > Regarding the repos, I'm pretty sure we can add the original repos as new
> > remotes, rebase them into the new Apache repo and move the files to the
> > appropriated folders, this would keep the history of all repos.
> >
> > Regards,
> > Lucas
> >
> > On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
> > wrote:
> >
> > > So, what's the goal here?
> > >
> > > A pure merge will get a repository without history. Is this the
> > intention?
> > >
> > > Otherwise, we can import one repository (maybe with the most code, or
> > > most history) and then start merging the other two (which you will
> > > then lose the history). In this scenario, at least some history is
> > > preserved.
> > >
> > > Also, we need to start working on the software grant process to
> > > officially donate the code to Apache.
> > >
> > > Thanks
> > >
> > > -- Forwarded message -
> > > From: Daniel Takabayashi 
> > > Date: Thu, Sep 20, 2018 at 2:59 PM
> > > Subject: Re: Welcome to Marvin podling
> > > To: 
> > >
> > >
> > > Great Luciano! Thanks...
> > >
> > > So...now I going to start the merge of the 3 main repos:
> > >
> > > marvin-python-toolbox
> > > marvin-engine-executor
> > > marvin-public-engines
> > >
> > > I think this will be easy...This will generate our first PR, right?
> > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Importing Source Code

2018-09-20 Thread Daniel Takabayashi

Yes...the ideia is to merge all repos but keeping the history of all
commits.
I did this once in the past and is pretty easy and reliable.

About the grant any information or request to B2W, I can arrange. Just let
me know @Lucas Bonatto Miguel  .

Em qui, 20 de set de 2018 às 18:43, Lucas Bonatto Miguel <
lucasbona...@gmail.com> escreveu:

> I can help with the grant process, should we request the current copyright
> owner to sign this (
> http://www.apache.org/licenses/proposed/software-grant.txt) document? Any
> other special instructions?
>
> Regarding the repos, I'm pretty sure we can add the original repos as new
> remotes, rebase them into the new Apache repo and move the files to the
> appropriated folders, this would keep the history of all repos.
>
> Regards,
> Lucas
>
> On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
> wrote:
>
> > So, what's the goal here?
> >
> > A pure merge will get a repository without history. Is this the
> intention?
> >
> > Otherwise, we can import one repository (maybe with the most code, or
> > most history) and then start merging the other two (which you will
> > then lose the history). In this scenario, at least some history is
> > preserved.
> >
> > Also, we need to start working on the software grant process to
> > officially donate the code to Apache.
> >
> > Thanks
> >
> > -- Forwarded message -
> > From: Daniel Takabayashi 
> > Date: Thu, Sep 20, 2018 at 2:59 PM
> > Subject: Re: Welcome to Marvin podling
> > To: 
> >
> >
> > Great Luciano! Thanks...
> >
> > So...now I going to start the merge of the 3 main repos:
> >
> > marvin-python-toolbox
> > marvin-engine-executor
> > marvin-public-engines
> >
> > I think this will be easy...This will generate our first PR, right?
> >
> >
> >
> > --
> > Luciano Resende
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>

Re: Importing Source Code

2018-09-20 Thread Lucas Bonatto Miguel

I can help with the grant process, should we request the current copyright
owner to sign this (
http://www.apache.org/licenses/proposed/software-grant.txt) document? Any
other special instructions?

Regarding the repos, I'm pretty sure we can add the original repos as new
remotes, rebase them into the new Apache repo and move the files to the
appropriated folders, this would keep the history of all repos.

Regards,
Lucas

On Thu, Sep 20, 2018 at 6:19 PM Luciano Resende 
wrote:

> So, what's the goal here?
>
> A pure merge will get a repository without history. Is this the intention?
>
> Otherwise, we can import one repository (maybe with the most code, or
> most history) and then start merging the other two (which you will
> then lose the history). In this scenario, at least some history is
> preserved.
>
> Also, we need to start working on the software grant process to
> officially donate the code to Apache.
>
> Thanks
>
> -- Forwarded message -
> From: Daniel Takabayashi 
> Date: Thu, Sep 20, 2018 at 2:59 PM
> Subject: Re: Welcome to Marvin podling
> To: 
>
>
> Great Luciano! Thanks...
>
> So...now I going to start the merge of the 3 main repos:
>
> marvin-python-toolbox
> marvin-engine-executor
> marvin-public-engines
>
> I think this will be easy...This will generate our first PR, right?
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

Re: Importing Source Code

21 matches

Site Navigation

Mail list logo

Footer information