Hi, As you may have noticed on the user list, Sqoop2 confuses the hell out of everyone.
Part of the problem is the name - Sqoop2 sounds newer and therefore better. People expect better quality and more features - which we don't deliver :( Therefore, I propose finding Sqoop2 a project code name. This way it will sound experimental and will not have the number "2" next to it. We can use the code name to mark the branches in the repo, the documentation, the Hue frontend, etc. This will prevent confusion as the name Sqoop will go back to refer to just one project, and one that actually works. Suggested names: Project Pelican (Based on the animal on O'Reilly's Sqoop book) Project Schlep (Yiddish for "moving heavy package") Friends, contributors, committers and PMC members - please respond with either: * Vote (+1) on one of the names above * Your own suggestion We'll be looking to close the vote by August 1st (Next week). Gwen
