Any word on whether or not Backup Buddy works on domains beyond the number of SUPPORT licenses purchased yet, Chip?

I read these ongoing discussions about whether a person should be able to charge for work they did under GPL.

As far as I’m concerned it’s karma! Why should anyone who has done a sh-tload of work on something, and who would like to paid something for it, NOT be paid, because of some interpretation?

Let’s say I develop a humungous application using Excel. it’s free for anyone to do the same, but it was ME who did it. if someone else doesn’t like it, then go make your own application, or, in this case a plugin.

Karma – what goes around comes around.

Like I say, just my 2c worth!

Cheers

Philip

Have you had a chance to give it a try yet?

I believe I saw a screenshot that showed BackUpBuddy requiring a user to enter the domain that the software was being used on. I would assume that is to “phone home” and check that the license covers operation for said domain in order to function. Does the software do this? If yes, doesn’t that prevent me from redistributing the plugin as I see fit, as required by the GPL?

Fair questions. I’ve never tried installing my copy of BackupBuddy on more than two sites, so I honestly can’t answer your question. I don’t know what would happen if it were attempted to be used on a third site.

If it fails to function as intended, then yes: I’d say that their implementation violates the GPL. I’ll give it a try on a separate web site, and let you know.

Well, I believe it does. But I don’t have a vested interest in the outcome of the argument. I was just expressing my opinion, which I still hold.

Expressing your opinion is all well and good, but you’re not really explaining why you believe Thesis and BackupBuddy are related in this circumstance.

Similarities:

1) They’re both PHP code
2) They’re both WordPress extensions
3) Both must be purchased for use

Differences:

1) BackupBuddy is and was always GPL. Thesis was formerly all-rights-reserved, but recently became split-GPL.

Why none of it matters:

1) PHP is run-time compiled code. Thus, having possession of a PHP application or code is equivalent to having the source for that code. The code is the source.

2) The issue regarding purchase cost is completely irrelevant. The GPL explicitly allows it. The Thesis debate never had anything to do with purchase cost, and the question of availability of BackupBuddy plugin source code likewise has absolutely nothing to do with its purchase cost.

Ok… as I view the membership plans (which I’ve looked at numerous times before you provided the link), I am unable to “get” it. If I pay for a 2 site license… I am technically paying for support and updates for 2 sites for 1 year, but… am I free to use the code on as many domains/sites/blogs as I wish? I ask, because that information isn’t clearly defined, and actually looks like a “no.”

I believe I saw a screenshot that showed BackUpBuddy requiring a user to enter the domain that the software was being used on. I would assume that is to “phone home” and check that the license covers operation for said domain in order to function. Does the software do this? If yes, doesn’t that prevent me from redistributing the plugin as I see fit, as required by the GPL?