[Name Clash] Hoodie / https://github.com/hoodiehq / http://hood.ie

[janl]

Dear Uber Engineering team,

congratulations on open sourcing such an impressive piece of work!

I’m the co-initiator of the Hoodie (http://hood.ie / https://github.com/hoodiehq) open source project and I’d like to discuss the name clash of the two projects.

Hoodie is an open source, offline-first, web application development backend (think of an open source Firebase, but with first class offline data sync support) that just celebrated its fourth birthday.

We realise that there is little technical overlap, maybe aside from Hoodie being built on Apache CouchDB, itself a big data solution with incremental map reduce (since about 2007). I also happen to be the Vice President of Apache CouchDB at the Apache Software Foundation.

Hoodie prides itself in being an open and inclusive community, and a recognised positive influence on the open source community at large.

We now see Uber is ramping up PR for this project, so we are starting to get worried.

We are a volunteer-run organisation, so we can’t possibly compete with Uber’s corporate resources, so we hope we solve this amicably and before it is too hard for Uber to change the name.

If you’d like to discuss this privately, feel free to reach out to me via email: jan@apache.org

Best Jan —

[prazanna]

Hey Jan,

Thanks for bringing this up. Sorry about the oversight. We will most certainly change the project name. The name (Hoodie) was an extension of HUDI - Hadoop Upsert anD Incrementals.

In 3 days, we have a strata talk , where we are talking about Hoodie. We may not be able to change the name everywhere before then, but we will change it soon after and also mention about the name change in the talk (to avoid any confusion).

Hope this does not concur a lot of inconvenience to the hood.ie project. Btw, tried out the quickstart and I think its awesome. Good luck with your project. Will update the this ticket once, we change the name reference in all places.

Cheers Prasanna

[janl]

@prazanna thank you for replying so soon and thank you for taking quick action.

No worries about a transition phase.

And good luck with the strata talk! :)

Thank you for the kind words about Hood.ie!

Best Jan —

[prazanna]

Hey @janl,

I spoke to people concerned and got the go ahead to change the name. I have set up the maven central artifacts as com.uber.hoodie:hoodie-client etc. Changing this would involve a lot of work around internal projects.

I would like to change the github project url to github.com/uber/hoodielib and make sure all the external reference and documentation/slides refers as hoodielib. Wanted to run this by you and ask how does that sound to you?

[prazanna]

ping @janl. Would referring to this hoodie as hoodielib in all the places alleviate any confusions developers might have?

[gr2m]

@prazanna I feard hoodielib is not better than just hoodie. We would very much appreciate if you could change the name entirely, without hoodie being part of its name.

[prazanna]

@gr2m

Fair Enough. Coming up with a totally different name would involve quite a bit of changes from our side

1. Maven artifacts needs to be changed and deployment process to maven central needs to change http://repo1.maven.org/maven2/com/uber/hoodie/
2. Internal production systems needs to be upgraded
3. Preserve history and move github project under a different name
4. Internal approval of the new name - back and forth with legal

This is going to take us months, which is why I initially thought of having hoodie in the name and still be able to avoid confusion. But looks like concern persists. By the way, would naming it a little different (like hudi for hadoop upsert and incrementals) would still concern you right? In this case we can keep the maven artifacts as is. Please let me know.

Anyways will keep this issue updated once we have a plan and have a more concrete plan and timeline.

cc @vinothchandar

-Prasanna

[janl]

hudi would be fine by us, if that makes things easier for you.

[janl]

Also: thanks again for taking this seriously!

[janl]

bump

[vinothchandar]

@janl we have already incorporated the name change in an incubator proposal, such that we can batch the above changes together. but, that seems to be taking a while. We have clarified this in our slides/talks as promised before.

I can rename the repository here on github, in the meantime. Does that suffice? (I was n't sure how forks would be impacted by that change). lmk if you have more comments.

[gr2m]

forks won't be affected by the name change. And GitHub will redirect from https://github.com/uber/hoodie to https://github.com/uber/hudi

[vinothchandar]

@gr2m I got as far as https://help.github.com/articles/renaming-a-repository/ . have you done this before? What I was asking was : would the lineage of forks be preserved? If you can confirm, then I can rename the repo and close the issue

[vinothchandar]

Got around to testing this off another project

Checked out code continues to work.

$ git push origin master
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 295 bytes | 295.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
remote: This repository moved. Please use the new location:
remote:   git@github.com:vinothchandar/kv-perf-tool.git
To ssh://github.com/vinothchandar/kv-perf
   b9e448d..2c250f8  master -> master

and fork lineage shows

[vinothchandar]

renamed the repo and doc url. we will use hudi externally going forward.. Closing issue. thank you for your patience.

[gr2m]

Thank you!