Also, intentional namespace pollution with existing backup tool, which IS gpl'ed.
Not cool. Not cool at all.
____________________________________
(response, since I'm submitting 'too fast'... ):
Github has commercial repos, and private repos.
It's pretty simple, really. If you want the free options on GH, you choose from a list of standard Open Source licenses. https://github.com/blog/1964-open-source-license-usage-on-gi...
It's also asked you create a LICENSE file, to go along with this.
Their license, however, is very much NON-FREE. As in, if I click clone, since I work for an employer of 50k people, I'm in violation. Full stop. And we're not even talking about developing on it, or submitting PR's, or what have you. This is simple copy which puts me in violation.
It's very much against the spirit of GitHub, and probably against the license on GH as well.
And it also is attempting to dilute another project that does similarly. Just so happens they're 2 letters different. Duplicacy vs Duplicity. That's an asshole thing to do.
Here's a few names I just devised: ClouDuplicate , Clouder, DupliCloud, CfC (cloud file cloud)..
Instead, it's very uncool to try to pollute an existing namespace of the same thing. Talking about pro-level bad will here.