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 bei
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
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
On 1/23/24 10:10, Ayush Saxena wrote:
Ok I will get the repo deleted. I am not taking any sarcastic comments from
Zoltan at this stage. Believe me I am not getting anything for having my name
there.
Why I did this?
Someone was so obsessed with getting his name checked into the "Apache Code"
Hey team,
Initially we had zero people willing to help and advance this topic.
Now we have more than three and I am sure everyone has good
intentions.
Let's not forget that in Apache the community is more important than
code. If we have a healthy community we can fix any kind of problem in
the co
Ok I will get the repo deleted. I am not taking any sarcastic comments from
Zoltan at this stage. Believe me I am not getting anything for having my
name there.
Why I did this?
Someone was so obsessed with getting his name checked into the "Apache
Code" that he developed something on his fork & c
I was thinking of pushing the current state of Zoltan's branch to the
new apache remote. I did this just now in
https://github.com/apache/hive-dev-box/tree/main branch.
I can cherry-pick the remaining commits from master and drop that
branch unless we have other things to consider as well. Please s
> I just copied the repo: cp -R and Put Zoltan's name & reference to his
> repo. I didn't knew any better way than that, you can definitely force push
> with another fancy approach
lol...what a sophisticated approach - I wonder if you don't know the `fancy
approach` then why you've done it?
I
I just copied the repo: cp -R and Put Zoltan's name & reference to his
repo. I didn't knew any better way than that, you can definitely force push
with another fancy approach, just c-pick the other commits for NOTICE & all
on top of it. The old code & commits had some cloudera references, which I
p
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
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
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 star
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
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 wrote:
>
> Creating the new repos should be kind of trivial. I think I will be
> able to do it using https://selfserve.apache.org/.
>
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 t
Thank you, Stamatis! Also, Zoltan for the "donation" :)
-Attila
On Wed, Aug 23, 2023 at 4:53 PM Ayush Saxena 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, Zolta
+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 wrote:
>
> Hey Stamatis!
>
> I'm happy to donate these repos / help with the migration!
> I should have done it ea
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
18 matches
Mail list logo
