Follow up to Creative Commons etc..

In the end, i added the ability for codebeach.org users to release their source either under public domain or under BSD, Creative Commons, Apache License or MIT/X11. Some developers seemed interested in the project but couldn’t stand to lose copyright on their code. I understand them, and i’ll try to make it as painless as possible for both contributers and users of code.

Ah, as a sidenote, CodeBeach finally sports a commenting system!

8 Responses to “Follow up to Creative Commons etc..”

  1. Blake C. Says:

    Lame.

    If a few developers don’t understand the value of the Public Domain “license”, then they can go rot. If you change the license, there is nothing to separate your site from every other site. Public Domain is what made CodeBeach worthwhile.

    I am sorry to see it go.

  2. Michele Balistreri Says:

    Public domain is not gone, is still the default choice. Also, i’m curious which other site you’re talking about is to share code between mac developers and has that set of features πŸ˜‰

  3. Blake C. Says:

    I mean every site that does not use “Public Domain”. Cocoadev, Cocoadevcentral, and google are good starting points.

    My point was that we have many geniuses writing excellent code, but they limit our use of their code with restrictive licenses. CodeBeach seemed(at first) to be a repository of code that was not encumbered by such licenses. Now, I don’t know what it is.

    I’ve been rewriting protected code for years, and have been wishing for something like the original CodeBeach the whole time. I was overjoyed when I saw CB. But now, it seems to be exactly like all the other projects whose license I couldn’t agree with.

    We’re all semi-intellignet. Can’t we share our code freely, with no restrictions?

  4. Blake C. Says:

    oops- “semi-intelligent”

    the irony does not escape me πŸ™‚

  5. Michele Balistreri Says:

    Well as you may know I wasn’t too glad either to add those other license, but it was either that or no contributions. Also the licenses added are not restrictive at all, they mostly require copyright notice to remain intact on source code and some require credits. Note that code found on mailing lists is usually public domain and that simple snippets on codebeach can only be public domain.

  6. Blake C. Says:

    I understand that some devs require recognition, and some do not. And I greatly appreciate your efforts with this site. I also sincerely hope that more Mac devs can submit their code in the future, with no attribution or license required.

    The minute we add legal notices to our code is the minute we become lawyers.

    I don’t know about you guys, but I’m a Coder.

    Cheers.

  7. Michele Balistreri Says:

    Yeah yeah still have seen nothing from you there! As i said, give the good example! πŸ˜›

  8. Blake C. Says:

    Touché!

    We should let someone else respond to this thread πŸ˜›

    Chat soon.