Thanks for helping advance this Ayush! I saw that the commit history was not retained. Is there any reason for dropping it? Keeping the history and the people who contributed thus far would be nice to have.
For the contribution model to this repository, I would recommend the usual process. Raise a JIRA ticket, file a PR, wait for review, and then merge. Best, Stamatis On Tue, Jan 23, 2024 at 8:45 AM Ayush Saxena <ayush...@gmail.com> wrote: > > This is the new repo: > https://github.com/apache/hive-dev-box > > It has the initial code from Zoltan, LICENSE, NOTICE & Disclaimer-WIP > file + I added Apache Header to all the files wherever possible. We need a > docker space to push these built images, have requested INFRA for the same. > > The repo is in WIP stage, If you find something problematic, please push a > fix to the repo or let me know. > > Some observations: > * The build command works on x86 box only not on aarch64, > * The github action to push the images doesn't work, that needs to be fixed > > -Ayush > > On Mon, 22 Jan 2024 at 21:55, Ayush Saxena <ayush...@gmail.com> wrote: > > > I think we are now not using Zoltan's repo. We are using a fork from a > > contributor in the hive code.[1], I will go ahead and create a repo under > > Apache Hive for hive-dev-box tomorrow & put the LICENSE, NOTICE & > > DISCLAIMER-WIP files in it, Then will take things from there, atleast it > > would be a starting point and all of us can take care of things from there > > slowly-slowly :-) > > > > Shout out, if anyone has objections around it. > > > > -Ayush > > > > > > [1] > > https://github.com/apache/hive/blob/1aeaff2057a2f4c241f8bcc53a2a529e6e7f45d4/Jenkinsfile#L124C44-L124C65 > > > > On Wed, 6 Sept 2023 at 20:11, Stamatis Zampetakis <zabe...@gmail.com> > > wrote: > > > >> Based on the discussion under LEGAL-653, it seems that the only > >> requirement to migrate the repos under the Apache namespace is to > >> apply the AL2 license in the majority of the files in there. > >> > >> I am looking for volunteers so that we can review the existing code in > >> those repo and apply the AL2 license where possible. Depending on how > >> many people step up we can divide the work accordingly. > >> > >> It would be interesting to see if we can use RAT [1] to > >> automate/assist in this process. > >> > >> Best, > >> Stamatis > >> > >> [1] https://creadur.apache.org/rat/apache-rat-plugin/usage.html > >> > >> On Thu, Aug 24, 2023 at 11:05 AM Stamatis Zampetakis <zabe...@gmail.com> > >> wrote: > >> > > >> > For the licensing question, I just created LEGAL-653 [1]. > >> > > >> > [1] https://issues.apache.org/jira/browse/LEGAL-653 > >> > > >> > On Thu, Aug 24, 2023 at 11:55 AM Stamatis Zampetakis <zabe...@gmail.com> > >> wrote: > >> > > > >> > > Creating the new repos should be kind of trivial. I think I will be > >> > > able to do it using https://selfserve.apache.org/. > >> > > > >> > > Since this will bring quite a bit of code under the ASF I will wait a > >> > > couple of days till I create the new repos. > >> > > > >> > > Once this is done, I think we can simply push the content from the old > >> > > repos to the new ones. To avoid any kind of IP problems it would be > >> > > best if Zoltan does this step. > >> > > > >> > > One thing that we may need to be careful about is the licensing of > >> > > these repos. We are not going to make source releases from there but > >> > > since the code will be under the ASF namespace people will assume that > >> > > it is ASF licensed so they may start copy-pasting stuff from there. > >> > > > >> > > Is there anything preventing us from putting the code under the AL2 > >> license? > >> > > > >> > > Best, > >> > > Stamatis > >> > > > >> > > On Wed, Aug 23, 2023 at 6:14 PM Attila Turoczy > >> > > <aturo...@cloudera.com.invalid> wrote: > >> > > > > >> > > > Thank you, Stamatis! Also, Zoltan for the "donation" :) > >> > > > > >> > > > -Attila > >> > > > > >> > > > On Wed, Aug 23, 2023 at 4:53 PM Ayush Saxena <ayush...@gmail.com> > >> wrote: > >> > > > > >> > > > > +1, > >> > > > > Thanx Stamatis foe initiating this. This was something which was > >> in my > >> > > > > mind as well since long but couldn’t find time. > >> > > > > > >> > > > > -Ayush > >> > > > > > >> > > > > > On 23-Aug-2023, at 6:19 PM, Zoltan Haindrich <k...@rxd.hu> > >> wrote: > >> > > > > > > >> > > > > > Hey Stamatis! > >> > > > > > > >> > > > > > I'm happy to donate these repos / help with the migration! > >> > > > > > I should have done it earlier - but it was never top > >> priority...thank > >> > > > > you for initiating it! > >> > > > > > > >> > > > > > cheers, > >> > > > > > Zoltan > >> > > > > > > >> > > > > >> On 8/23/23 14:00, Stamatis Zampetakis wrote: > >> > > > > >> Hi all, > >> > > > > >> Our precommit infrastructure uses code that resides in the > >> following > >> > > > > repos. > >> > > > > >> * https://github.com/kgyrtkirk/hive-test-kube > >> > > > > >> * https://github.com/kgyrtkirk/hive-toolbox > >> > > > > >> * https://github.com/kgyrtkirk/hive-dev-box > >> > > > > >> These are mainly maintained by Zoltán Haindrich who is always > >> helpful > >> > > > > >> and kind to investigate and resolve issues. > >> > > > > >> For facilitating contributions from the apache community and > >> also > >> > > > > >> removing some burden from Zoltan's shoulders it may be a good > >> time to > >> > > > > >> migrate those and put them under the apache namespace. > >> > > > > >> For the initial migration, we could have a straightforward 1 > >> to 1 > >> > > > > >> mapping as shown below: > >> > > > > >> * https://github.com/apache/hive-test-kube > >> > > > > >> * https://github.com/apache/hive-toolbox > >> > > > > >> * https://github.com/apache/hive-dev-box > >> > > > > >> How do you feel about this? > >> > > > > >> Best, > >> > > > > >> Stamatis > >> > > > > > >> > >
