Hey All, Thank you Alessandro and Stamatis for the suggestion to cool off.
I think I was seeing the state and the messages at the wrong time - and was writing a message light headed; I should have seen the step forward...or at least have taken a break before hitting reply
Ayush: sorry for being out of line - I think we could have taken a different route to review these things a bit and only retain what's needed - so that unnecessary things doesn't make it in...
but its fine this way as well; it can be removed later as well cheers, Zoltan On 1/23/24 12:31, Alessandro Solimando wrote:
Hey guys, I advise you to take Stamatis' suggestion and cool it off for a bit, this is getting personal and you know it's only counterproductive. Having worked with both of you, I know you have always done everything in the best interest of the project and always acted in good faith, no reason to look for further reasons on past and current choices. You might not agree on what's best now, but I am pretty sure you will accept whatever the community thinks it's best, so an alternative is to cast a vote and act based on the outcome, the Apache way! :) Best regards, Alessandro On Tue, 23 Jan 2024 at 11:15, Ayush Saxena <ayush...@gmail.com> wrote:Ok Zoltan, you are always right, but listening to other people sometimes doesn't hurt, maybe even if they aren't as smart as you (like me & everyone you consider not so smart like you). Let me ask something: * If something breaks like code or something like that? What do you do? Humiliate or throw sarcastic comments? -> In general no, We go and help fix it, or ask the guy to revert it & share what you feel is right? if there isn't an agreement, we discuss not like "Whatever you want to do", for you that might be fancy, but not for others -> You don't like an approach? The way I did it? or "I did it" It is all Ok, that apache repo actually gives rights to all the hive committers, whether I know them, you know them or nobody knows them. anyone can do what they like & consider good for Apache Hive, that is opensource. The amount of time we are spending on this thread, that much time would have sorted things out -> Your response mechanism? How tough is it to spread a sense of inclusive community? How tough is it to write in a humble way? I am not convinced with this approach? I know a better approach? That is X->Y->Z, We should do that? or I will go ahead and do that? Did anyone stop anyone from doing anything here? What is the point being proven, that someone is superior & can go freely & yell or scold people, or it is demonstrating "I deserve respect not the others" -> Is there a discussion about the topic? How long do you want the discussion? If you were particular about an approach, you could have shared it, I went wrong, you can still share it, you don't want me to do it, you can still do it yourself, and believe me even if you screw up things. None of us will come up & throw any tantrums or sarcastic comments. That is not most of us. I maybe wrong, anyone can be wrong, the only person who didn't do anything wrong or broke anything is someone who didn't do anything ambitious... I will still try to answer your questions ZoltanI was replacing the CI I've used it to get a good base ground forrunning the tests - as it could prepare a lot of things already. I had to do a lot of things - and the move of the repo was never at the top of the list... It is all "I" my friend, you thought, till you were only using it, it was good. But Hive started using it, It wasn't. How many Apache projects rely on even making a JDK change for their test to run on external folks, using your personal fork itself at the very first point was violation of apache way. Migration should have been done first, or other alternatives should have been explored rather than relying on some non apache forkThat's not true either as you can see in a week-or-so old comment from meAnd again, You want all "Apache" contributors to follow your repo & follow these comments? -> Reading the comment? We push it our own docker hub space & push a commit to my own docker hub space or rely on "you" to build or add "me" as a collaborator? The project & its component aren't own by any of the member, good news not me, bad news not by you either. The project & it is infra, CI resources are owned by the Project PMC (not any member) & the PMC is no way superior to any contributor. That is basic Apache stuff, I know you know them better than me. I still don't want to drag it further, Zoltan you are the most important person in this thread, the code is in your repo, whatever way you want, we will get that done the same way. Does that make you happy? But please get away with this attitude, none of us, not me, nor any contributor is at mercy of anyone else, everyone is equal, equal right, have all rights to make mistakes, discuss, get them corrected & still come back to this place without any humiliation with his head held high. Community over Code I think you will retrospect, you are a respected member of the community & will work in a way it is good & peaceful for all, rest I can't help it. I will let Stamatis & you or anyone you like go forward with this. Stamatis has all rights around the repo, if you want any deletion or so, rest INFRA ticket can get anything sorted, if it requires me to write something, I can accept it was my bad, fortunately I don't have ego issues :-) With a heavy heart!!! -Ayush On Tue, 23 Jan 2024 at 15:05, Zoltan Haindrich <k...@rxd.hu> wrote:On 1/23/24 10:10, Ayush Saxena wrote:Ok I will get the repo deleted. I am not taking any sarcastic commentsfrom Zoltan at this stage. Believe me I am not getting anything forhavingmy name there.Why I did this? Someone was so obsessed with getting his name checked into the "ApacheCode" that he developed something on his fork & checked in that code totheApache Hive code, so,professional.I don't aggree - as this is just not true! This project was created way-way back to aid my own efforts - didn't even looked like it will be used like this later. so I've created a separate repo - as there would have been not muchreasonto wait for approvals on tool changes only I use! I was using it for years - and when I was replacing the CI I've used ittoget a good base ground for running the tests - as it could prepare a lotofthings already. I had to do a lot of things - and the move of the repo was never at the top of the list... ...and it never proved to be a bottleneck; as you can just fork&upload a new image and reference that instead...Many Hive Commiters have rights is a wrong phrase to quote: Many HiveCommitter who are your friends have rights. To push an image we need to catch Zoltan, but ok dowhatever you want.That's not true either as you can see in a week-or-so old comment fromme (https://github.com/kgyrtkirk/hive-dev-box/pull/15#issuecomment-1893414474)describing how you could push a new image and use that instead ; bypassing me entirely... The PR with that changed docker image to `wecharyu/hive-dev-box:executor` got merged a few days back...so as of now the hive ci doesn't have much connection to the original repo.I just want to say, Zoltan, you might be a very good developer, butplease change your "whatever you want to do" tone, I think you went forward and done something before even writing a single line - or did I miss it?Not following this furtherhave it your way! cheers, Zoltan-Ayush On Tue, 23 Jan 2024 at 14:30, Zoltan Haindrich <k...@rxd.hu <mailto:k...@rxd.hu>> wrote:> I just copied the repo: cp -R and Put Zoltan's name & referenceto his> repo. I didn't knew any better way than that, you candefinitelyforce push> with another fancy approach lol...what a sophisticated approach - I wonder if you don't knowthe`fancy approach` then why you've done it?I wonder what you've copied - because you missed the addition ofthegithub action which builds the image for every PRNow you are the sole contributor of all existing stuff(congrats)...but do whatever you want...It was always there and available to use - many hive commiters hadpush and approve rights on those repos.I think you might also want to do the same withhttps://github.com/kgyrtkirk/hive-toolbox < https://github.com/kgyrtkirk/hive-toolbox>because your contribution references it here:https://github.com/apache/hive-dev-box/blob/663625bc74e799f35c6bab1c1485530367287c61/tools/install_toolbox#L21C1-L21C115<https://github.com/apache/hive-dev-box/blob/663625bc74e799f35c6bab1c1485530367287c61/tools/install_toolbox#L21C1-L21C115and probably also cp -R https://github.com/kgyrtkirk/hive-test-kube/ <https://github.com/kgyrtkirk/hive-test-kube/>cheers, Zoltan On 1/23/24 09:29, Ayush Saxena wrote: > I just copied the repo: cp -R and Put Zoltan's name & referenceto his> repo. I didn't knew any better way than that, you can definitelyforce push> with another fancy approach, just c-pick the other commits forNOTICE & all> on top of it. The old code & commits had some clouderareferences, which I> personally wanted to avoid, but yep we can take another approachas well.> Good with me. > > For the Jira, yep we should, we aren't going to release this, sofor fix> version, maybe I will create a dev-box-1.0.0 which we can use toresolve> the tickets, shouldn't put main repo versions, else that willpopup in our> release notes, or let me know if you want a separate Jiraprojectunder> Hive for these repos as well, We can explore that route if folksfeel that> way. > > -Ayush > > > On Tue, 23 Jan 2024 at 13:35, Stamatis Zampetakis <zabe...@gmail.com <mailto:zabe...@gmail.com>> wrote:> >> Thanks for helping advance this Ayush! >> >> I saw that the commit history was not retained. Is there anyreason>> for dropping it? Keeping the history and the people whocontributed>> thus far would be nice to have. >> >> For the contribution model to this repository, I wouldrecommendthe>> 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<mailto:ayush...@gmail.com>> wrote:>>> >>> This is the new repo: >>> https://github.com/apache/hive-dev-box <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 whereverpossible. We need>> a >>> docker space to push these built images, have requested INFRAfor 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, thatneedsto be>> fixed >>> >>> -Ayush >>> >>> On Mon, 22 Jan 2024 at 21:55, Ayush Saxena <ayush...@gmail.com<mailto:ayush...@gmail.com>> wrote:>>> >>>> I think we are now not using Zoltan's repo. We are using afork from a>>>> contributor in the hive code.[1], I will go ahead and createarepo>> 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 ofthings from>> there >>>> slowly-slowly :-) >>>> >>>> Shout out, if anyone has objections around it. >>>> >>>> -Ayush >>>> >>>> >>>> [1] >>>> >>https://github.com/apache/hive/blob/1aeaff2057a2f4c241f8bcc53a2a529e6e7f45d4/Jenkinsfile#L124C44-L124C65<https://github.com/apache/hive/blob/1aeaff2057a2f4c241f8bcc53a2a529e6e7f45d4/Jenkinsfile#L124C44-L124C65>>>> >>>> On Wed, 6 Sept 2023 at 20:11, Stamatis Zampetakis <zabe...@gmail.com <mailto:zabe...@gmail.com>>>>>> wrote: >>>> >>>>> Based on the discussion under LEGAL-653, it seems that theonly>>>>> requirement to migrate the repos under the Apache namespaceis to>>>>> apply the AL2 license in the majority of the files in there. >>>>> >>>>> I am looking for volunteers so that we can review theexisting 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 < https://creadur.apache.org/rat/apache-rat-plugin/usage.html>>>>>> >>>>> On Thu, Aug 24, 2023 at 11:05 AM Stamatis Zampetakis < >> zabe...@gmail.com <mailto:zabe...@gmail.com>> >>>>> wrote: >>>>>> >>>>>> For the licensing question, I just created LEGAL-653 [1]. >>>>>> >>>>>> [1] https://issues.apache.org/jira/browse/LEGAL-653 <https://issues.apache.org/jira/browse/LEGAL-653>>>>>>> >>>>>> On Thu, Aug 24, 2023 at 11:55 AM Stamatis Zampetakis < >> zabe...@gmail.com <mailto:zabe...@gmail.com>> >>>>> wrote: >>>>>>> >>>>>>> Creating the new repos should be kind of trivial. I thinkIwill>> be >>>>>>> able to do it using https://selfserve.apache.org/ <https://selfserve.apache.org/>.>>>>>>> >>>>>>> Since this will bring quite a bit of code under the ASF Iwill>> wait a >>>>>>> couple of days till I create the new repos. >>>>>>> >>>>>>> Once this is done, I think we can simply push the contentfrom>> the old >>>>>>> repos to the new ones. To avoid any kind of IP problems itwould>> be >>>>>>> best if Zoltan does this step. >>>>>>> >>>>>>> One thing that we may need to be careful about is thelicensing of>>>>>>> these repos. We are not going to make source releases fromthere>> but >>>>>>> since the code will be under the ASF namespace people willassume>> that >>>>>>> it is ASF licensed so they may start copy-pasting stufffrom>> there. >>>>>>> >>>>>>> Is there anything preventing us from putting the codeunderthe>> 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 <mailto:ayush...@gmail.com>> >>>>> wrote: >>>>>>>> >>>>>>>>> +1, >>>>>>>>> Thanx Stamatis foe initiating this. This was somethingwhich>> 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 <mailto:k...@rxd.hu>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hey Stamatis! >>>>>>>>>> >>>>>>>>>> I'm happy to donate these repos / help with themigration!>>>>>>>>>> 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 inthe>>>>> following >>>>>>>>> repos. >>>>>>>>>>> * https://github.com/kgyrtkirk/hive-test-kube <https://github.com/kgyrtkirk/hive-test-kube>>>>>>>>>>>> * https://github.com/kgyrtkirk/hive-toolbox <https://github.com/kgyrtkirk/hive-toolbox>>>>>>>>>>>> * https://github.com/kgyrtkirk/hive-dev-box <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 apachecommunity>> and >>>>> also >>>>>>>>>>> removing some burden from Zoltan's shoulders it maybe a>> good >>>>> time to >>>>>>>>>>> migrate those and put them under the apache namespace. >>>>>>>>>>> For the initial migration, we could have astraightforward>> 1 >>>>> to 1 >>>>>>>>>>> mapping as shown below: >>>>>>>>>>> * https://github.com/apache/hive-test-kube <https://github.com/apache/hive-test-kube>>>>>>>>>>>> * https://github.com/apache/hive-toolbox <https://github.com/apache/hive-toolbox>>>>>>>>>>>> * https://github.com/apache/hive-dev-box <https://github.com/apache/hive-dev-box>>>>>>>>>>>> How do you feel about this? >>>>>>>>>>> Best, >>>>>>>>>>> Stamatis >>>>>>>>> >>>>> >>>> >> >
OpenPGP_signature.asc
Description: OpenPGP digital signature
