put more example programs under (explicit) permissive license

[catseye]

@aturley and @mtve -- assuming you are who I think you are (and if you're not, please let me know) -- hi guys! Would you consider putting your old Befunge-93 example programs into the public domain (or at least under some kind of permissive license)? Not that I expect it makes much material difference, but it's a nice gesture, I find.

I'll also contact Wim Rijnders with the same question (but he doesn't appear to be on github.) I couldn't locate any other example authors for sure.

[wimrijnders]

I am too on github!

Message understood, I'll see what I can dig up. The idea is to add them to this repo? That would be fine with me, if you set up a license - Creative Commons, or anything similar is ok.

Now, excuse me for a while, I need to delve into the catacombs for my befunge work......

[wimrijnders]

I see that my two major masterpieces are in the repo already, namely befbef.bf and wumpus.bf. The other stuff will prob not be as interesting, but will look for them anyway.

[catseye]

@wimrijnders -- Isn't it beautiful that searching github for "Wim Rijnders" returns 89 users, not one of whom is you? I should have known to try without a space!

Ever since http://esolangs.org/ came about, I've mostly been putting my own example programs in the public domain (just saying "this work is in the public domain" somewhere on it or near it). The CC equivalent is http://creativecommons.org/publicdomain/zero/1.0/ (and there is also http://unlicense.org/) and arguably I should be using something like this with all its legal rigour, instead of making what amounts to an offhand remark.

So I'll propose CC0 1.0 Universal for compatibility with esolangs.org, but if you prefer something else, let me know.

(I should probably also import the bugfixed version of befbef you mention on your page if it's not already here, too.)

[wimrijnders]

On Sun, Aug 26, 2012 at 11:56 PM, Cat's Eye Technologies <
[email protected]> wrote:

@wimrijnders https://github.com/wimrijnders -- Isn't it beautiful that
searching github for "Wim Rijnders" returns 89 users, not one of whom is
you? I should have known to try without a space!

Bah. They're just abandoned forks. Ignore them.

Funny, yes, that a space, or lack of one, should make so much difference. I
will submit an issue report to myself to officially remove the space from
my name. That should fix things. But seriously, it looks like a mishap in
the github search.

Ever since http://esolangs.org/ came about, I've mostly been putting my
own example programs in the public domain (just saying "this work is in the
public domain" somewhere on it or near it). The CC equivalent is
http://creativecommons.org/publicdomain/zero/1.0/ (and there is also
http://unlicense.org/) and arguably I should be using something like this
with all its legal rigour, instead of making what amounts to an offhand
remark.

So I'll propose CC0 1.0 Universal for compatibility with esolangs.org,
but if you prefer something else, let me know.

CC would be my first choice as well. Basically, anything that states 'Do
what you want with this, but you can't blame the original author for
anything' is fine with me.

(I should probably also import the bugfixed version of befbef you mention
on your page if it's not already here, too.)

Go right ahead http://wimrijnders.nl/other/befunge/befbef2.bf. I'm
somewhat tempted to pull a fork and add it, but you can do it as well.

Regards,

Wim.

[catseye]

Sorted. Thank you, kind sir -- space or no space.

[aturley]

Hey, yeah, it's me. I'm not even sure I have access to most of what I wrote anymore, but if you have anything I did then I'll do whatever needs to be done to make it CC.

[catseye]

Sorry, I should have been more specific about the fact that I was just referring to the example sources that are already in the Befunge-93 distribution -- I wasn't expecting anyone to dig anything else up.

@aturley -- one program is definitely yours: http://catseye.tc/projects/befunge-93/eg/aturley.bf ... and another one is possibly yours: http://catseye.tc/projects/befunge-93/eg/selflist.bf

Can I just take your statement "I'll do whatever needs to be done to make it CC" as permission to go ahead and make your sources CC? I think I can, although the logic there feels vaguely Hofstadter-y...

[aturley]

Ah, yeah, no problem. I hereby release that code under CC 1.0 Universal.

[catseye]

Cool, thanks! Can you confirm that it was indeed you who wrote selflist.bf? (I realize asking you to recall something like that after more than 15 years may be asking a lot -- I apologize.)

The only reason there's doubt as to its provenance was because I had a few sources that I had saved off the mailing list that I later added to the archive, but neglected to double-check who wrote them at the time. I did write "Andrew Turley?" in the author column, so I must have had some idea that it was you.

It appears it was the first Befunge-93 quine, whoever wrote it.

[aturley]

Ah, I'd love to take credit (and I do love a good quine), but I honestly can't recall if that was mine or not. But the sigfile/Serpinski generator is definitely mine.

[catseye]

Oh well. Done. Thank you for playing Nostalgia Esolang, you can pick up your prize at the door! 🍆

[mtve]

Hello Chris!

Very nice to hear you! Sorry for delay, I was on vacation.

It's a big honour, so "do what you want" license is perfectly ok for me.

Thanks again for Befunge and for all your other projects!

mtve

On Mon, Aug 27, 2012 at 12:38 AM, Cat's Eye Technologies <
[email protected]> wrote:

@aturley https://github.com/aturley and @mtve https://github.com/mtve-- assuming you are who I think you are (and if you're not, please let me
know) -- hi guys! Would you consider putting your old Befunge-93 example
programs into the public domain (or at least under some kind of permissive
license)? Not that I expect it makes much material difference, but it's a
nice gesture, I find.

I'll also contact Wim Rijnders with the same question (but he doesn't
appear to be on github.) I couldn't locate any other example authors for
sure.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2.

[catseye]

Nice to hear from you too! Thank you very much; I've noted that your example sources are now distributed under the CC0.