Cocos2D Sources: Zynga Copyright Added

On May 28, 2011, in Games, by Steffen Itterheim

As @GeekAndDad pointed out on Twitter the majority of the cocos2d source code has been updated with a Zynga Copyright. This is in reference to two commits (1) (2) on github in the develop branch of cocos2d-iphone.

The MIT License header now begins with:

* cocos2d for iPhone: http://www.cocos2d-iphone.org
*
* Copyright (c) 2008-2010 Ricardo Quesada
* Copyright (c) 2011 Zynga Inc.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the “Software”), to deal
* […]

Meaning?

This just means that changes made in 2011 to the cocos2d source code are copyright by Zynga. Which is to be expected, now that Ricardo is an employee of Zynga.

It doesn’t change anything regarding the MIT license. And it doesn’t imply a transfer of copyright. In fact, since Ricardo is still listed as copyright owner for the years 2008-2010 it is suggesting that there was no transfer of copyright.

Also note that some of the source code in the cocos2d-iphone project is copyright by other developers or companies, whose copyright has not been changed. This includes classes like CCActionEase, CCActionGrid, CCActionPageTurn3D, CCBlockSupport, CCGrabber, CCMotionStreak, CCTexture2D - just to name a few.


This article was brought to you by ...

I very much enjoy the learning process, the pushing of boundaries (mine and yours and that of technology), having the freedom to pursue whatever is on my mind, to boldly program what no one has programmed before, and to write about what I've learned. Help me help you by browsing the products in the Learn Cocos2D Store.


Tagged with: • • • • • • • •  

3 Responses to “Cocos2D Sources: Zynga Copyright Added”

  1. Joey says:
    May 28, 2011 at 01:07

    I’m scared. Kobold2d bring it on! 😀

  2. MarcPires says:
    May 29, 2011 at 21:33

    I don’t think it may some day be turned closed source. But it’s wise to keep eyes opened.

    • Steffen Itterheim says:
      May 29, 2011 at 22:06

      The project itself will stay open source. There’s just going to be additional closed source code being developed that we’ll never see, of course.