Make Easter Egg GPL Compliant

[filosofo]

The easter egg is funny; it has soul; I'm not complaining about it per se.

However, to be compliant with the ​GPL 2, we must distribute the WordPress "source code," which is

the preferred form of the work for making modifications to it.

It should be obvious that obfuscated code is not "the preferred form of the work for making modifications to it," and in fact the ​FSF says explicitly

Obfuscated “source code” is not real source code and does not count as source code."

The attached patch provides an un-obfuscated version of the easter egg code, to bring the code into compliance with the GPL.

Thiis is unobfuscated? :-D

Everything is either un-obscured or explained in a comment.

What is the easter egg anyway?

Replying to caesarsgrunt:

What is the easter egg anyway?

I take it you never had a customer wake you up in the middle of the night because his site got hacked... Try comparing a revision to itself to see what it looks like.

Hehe... never came across that! I'm glad to see someone with commit access has a sense of humour. :-D

I'm pretty sure the easter egg works very well w/o dvortr. So the patch could be improved to have the text as plain so it's easier to be edited, IMHO "the preferred form of the work for making modifications to it" and this would not destroy the joke at all.

We don't have to distribute it with WordPress. What if the obfuscated version just linked to the non-obfuscated version? That should satisfy the requirement.

Yes, I think that would meet the requirements of the GPL.

If we put that at, e.g., a wordpress.org FTP resource, we could add the source for the obscured JS and compiled Flash in some of the third-party code we're using. Though not required, having those third-party sources would keep everything in place and ensure that they are still available even if the originals disappear.

(In [16826]) Link to unobfuscated JS. Props filosofo. fixes #15262