Source Code License


You appear to have missed a key sentence:

Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to Defold and to recipients of software distributed by Defold a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

The copyright license is granted to both defold and the users equally.




No, I didn’t miss that- maybe I should have addressed it. That does indeed seem to grant the same rights to anyone who gets the contribution. But note, it is only the contribution that is granted that right. So while technically I could use this to claim I have the right to use any code that was contributed under the CLA however I see fit, it is practically impossible to extract the contribution from the larger project, owned by the Defold Foundation. If King granted the code to the Defold Foundation under the terms of the CLA, then the whole license question is moot- because the CLA would supersede the project license. If King instead granted copyright control of the code under different terms, then the Foundation would have additional rights to the project as a whole.

Even if King did grant the code to the Foundation under the CLA, I am not going to take it and say “see, the CLA says I can release a commercial version of the engine” but I would want to follow the communities own intent in my use of the code. Right now, that intent seems to be under the terms of the Defold License.

That brings us back to the question of how to best achieve the Foundation’s goals of building a healthy, thriving ecosystem and community around the code, and what license would best achieve that goal.



Whilst you claim you want a debate about how to best achieve the foundation’s goals, you have made several mistaken bad-faith assumptions about the license, admitted yourself that you hadn’t read the CLA when you started the thread, have been a member of the defold community for just two days, and have already stated that you have no intention of using defold. All of those things make it very difficult for you to take part in a community discussion. furthermore, the CLA has already been updated after you made a suggestion about a significant flaw, an hour after you made that post.



What you’re saying here is that you want defold to be free and open source so that users are able to use a variety of business models they choose to monetise their creations.



It might be a little bit off-topic, but I watched it today and it somehow remainds of the situation :smiley:

Especially the part about negative feedbacks that are the loudest in the internet



I’m really not following you on this. Everything I have said about the license has been true- further, nothing I have said has been said in bad faith. I apologize if it has come off that way.

Yes, I hadn’t read the CLA, I couldn’t find a link to it anywhere. That is why I asked for it. Asking for a link so I could read it was part of my good faith effort to understand it. Further, once provided with the link, I read it, and I was right about what it said, so I don’t know what relevance that has to your point?

I never said that. I said I won’t use it with its current license.

So what your saying is that I have already made a positive contribution to this community, through this thread? Your welcome. (And especially thanks you to @britzl for being so responsive and getting that improvement made!)

I have listed several reasons why I feel that an Open Source license such as the Apache 2.0 License would be better for the Defold Engine, and the community. To summarize:

  1. It would be more compatible with other Open Source projects, allowing better collaboration between these projects.

  2. It would better promite the use of open source licenses- one of the stated purposes of the Defold Foundation.

  3. It would be better for the community because any member of the community- a user of the engine, and contributor to the engine source, and designer, documentation writer, or anyone else) would have the ability to benefit financially from their involvement in the community, in a variety of different ways.

Can I clarify anything else for you?



Thanks for your clarifications! You’ve won me over. I appreciate the time you took to explain everything.

I’m on my way to McDonald’s now to convince them to give me some OpenSource hamburgers for free, and then refuse them on the grounds that they aren’t vegetarian.



I agree. I would also have wanted an MIT or Apache license. This is what we use for all of the other repositories we have open sourced, including the build server.

But it was the requirement from the founder that a non commercialisation clause was added to the license of the main repository containing the editor and engine. It was either that or no foundation and no source code.

This is something I have a problem understanding. Godot has a lot of contributors. As far as I can tell the contributors work on Godot without compensation. Are your saying that they contribute based on some potential future earnings when Godot is sold by someone?



Thank you for sharing more information about the license situation!

To answer you questions about Godot- the Godot core team have a Patreon account that brings in over $10,000 per month- this money is used to pay for their full time salaries. I am not sure how many developers they have at the moment- I think they have 3, but maybe it is only 2- and they are closing in on enough funding to add another. Godot has also received significant grant funding from the Mozilla Foundation and other organizations. They have also participated in the Google Summer of Code.

These are opportunities likely closed to the Defold due to its current license. I have also seen job ads seeking both employees and contractors to work on Godot- I imagine many of these engagements result in contributions flowing back into the project. With the Defold License, the type of engagement a consultant might enter into is likely limited- as the license forbids any form of commercialization. Even if it isn’t intended to prevent hiring a consultant to work on the engine… I think many would shy away from such engagements due to the license forbidding any form of commercialization.

The opportunities that Godot have because of its license also help them to bring in additional contributors who aren’t being paid directly for the work they are doing. Many Google Summer of Code participants go on to become regular contributors to the projects they work on.

One of the biggest reasons for me to choose Open Source is to avoid vendor lock-in- if for some reason I am not a good customer fit for a vendor- especially if there is a mismatch in business models- I don’t want the vendor to be trapped into serving me- nor do I want to be trapped into that vendor. I want know that there is at least the potential to hire some one or pay a company to create the product and service I need, without being restricted by the software license. (Obviously there will always be the restriction of what I am willing to pay versus what a potential vendor is willing to accept for the work!) If I have that option open, I am more willing to build on a product and trust in its future. But if a product can’t be commercialized, it causes me much reason to be concerned for its future.

I hope this makes sense. I understand that there may not be anything anyone on the Defold team can do right now about it.



Hmm, maybe i truly misundertsand the sitiation, but what you’re describing vis a vis Godot seems pretty much the same as with Defold. My reading of the announcement is that Bjorn and other(s) will be working on Defold full time, with pay, initially from a King contribution, and eventually through donation and other support (patreon, git, etc) similar to your $2500 per bloke Godot situation as described.

There is nothing (that i can see) in the licence that says someone who is a regular quality contributor can’t be hired by the Foundation and paid for their work, and nothing (that i can see…) That imposes any limitations on you using Defold, including modifying the h*ll out of it to make your niche application, other than you can’t then resell your cool new modded-Defold editor/engine, only the app/game you made with it. Again, as far as I can see i dont see a clause that says the Defold Foundation can legally stop you from selling your game because you made significant changes to your own copy of the engine that aren’t in line with their vision of the direction of the feature-packed, slim, engine they’re maintaining and offering for free.

I dunno, I’m not a lawyer, certainly not a Swedish lawyer, I’m not even a real game dev. @britzl, help us understand.

1 Like


Some people are clearly personally interpreting things in the license that the Defold team did not intend. @britzl has said he is working with their legal to get some clarity so that needs to be waited on.



Like I said previously, I don’t know what the intent is- I know that software licenses, like any legal document, can be tricky to get right. I know that “otherwise commercialize” is extremely broad. I know that others have used similar clauses before and there has been debate over what that means- with some saying it is so broad that it is unenforceable, and others saying that it makes it impossible to use for any commercial activity, including work for hire, and others come to some middle of the road conclusion.

@ryanscottlandry that was my understanding as well, but I don’t know what the arrangement is for employing them. And it may be all fine and good for the Foundation- but there are going to be a lot of others who won’t touch it in any way for pay.

Hopefully there will be some improvements to the license. Hopefully this discussion will have contributed in some small way to making the project better, even if I don’t get what I desire of having the Apache 2.o license adopted.



I might be the last one who joined the Defold forum before the switch to the new license and with it in a way confirming Defold as my tech of choice for the future. I did go through the previous license before doing so, to check if there is anything that would hinder my ability to use Defold in my future games.

Time investment for adjusting to new language and learning the “Defold api” / has to spread on more than one project for me to find it financially viable (indie game market is tough) and with that, license has to fit several projects.

While I liked the summary of previous license terms the section about not allowing Defold to be used for games that involve real money gambling, software that promotes violence, degrades ethnic groups etc. worried me a bit as to what would the actual interpretation of that be.

Did that mean you can’t use it for fighting games or shooting games which tend to have some sort of WW2 or fighting terrorist theme, because that kind of games are not in line with the engine owner’s ip/public image or if that was there just to avoid any legal liabilities in case someone used the software for things not allowed by Swedish/International law, like terrorism.

Defold license clears that up and I think the limitations that it has will benefit the Defold foundation goals and game makers using the software the most (even more than MIT license would).

  • community gets bigger
  • number of assets increases
  • more jobs/software where Defold engine can be used

I would like to congratulate and thank everyone that made this transition possible. :slightly_smiling_face:
The way that license is summarised and presented on the website with marked changes to the Apache 2.0 is something that should be the norm.



This will likely happen in the future. People can get hired by the Defold foundation to work on the code.

Correct. You can sell games created using a modified version of Defold.