FAQ about Corona opensource
Vlad Sherban, product manager of Corona Labs:
The transition of Corona to an open source model of development was one of the main priorities since Corona Labs was acquired by Appodeal in 2017. I am pleased to say that this milestone is very close. Open source has become a backbone supporting modern computing. Tech giants and small firms build their businesses around open source technologies. For Corona, going open source will bring transparency of the development process and provide the ability for users to contribute features or bug fixes to make the project better for everyone.
Corona Labs will continue to have a team and infrastructure to support our flourishing plugin ecosystem and infrastructure, and to keep up Corona to date with the ever-changing requirements and updates coming from the application stores.
Enabled by open source, development of new features, bug fixes and support will transition to be more community driven, with our help and guidance. I have high hopes for the future of Corona, and ultimately going open source will provide confidence in the future of the engine and opportunity to grow community involvement in engine development.
How I can build game through the open source engine?
Where are developers talking about the Corona’s open sourced activity?
Does open source mean you'll rely on the community for most of the new features?
We’ll be pleased if the community gets more involved and initiates new features that help to improve user’s projects. Indubitably, we will collect all the ideas to discuss them together and choose which items to implement. Corona’s team will manage these processes and implement the features.
Using an open source game engine is safe for my projects?
Yes, absolutely. Many popular game engines are fully open sourced. You may easily find the dozens of open source game engines on GitHub or other places.
What will happen to my purchases from the Corona Marketplace?
We are not going to make changes to the Corona Marketplace. Don’t worry, our store will continue to work the same as before: you may buy and sell your projects and earn income. Feel free to mail us about the Marketplace to firstname.lastname@example.org.
How will paid plugins work?
Paid and free plugins will continue to work same as they worked before the transition to the open source model of development. You can buy plugins from our Marketplace and start to use it in builds according to their documentation.
Can I disable the Splash Screen without buying a plugin because the source code is open?
Simple answer: only if you want to make open source games/apps. There are three scenarios that you can choose from.
- You can download the Corona source code under the GPLv3 license, disable the splash screen and build your games and apps, however, those games have to be distributed under the GPLv3 license, i.e you have to make your source available. Games and apps based on the open source distribution of Corona you be distributed using same license (GPLv3).
- You can download the Corona source code, negotiate a commercial license agreement with Corona Labs and build a version of Corona that doesn’t require a splash screen. With this, you can then distribute your games and apps without opening your own source.
- Continue to use Corona with a splash screen or purchase the Splash Screen Control plugin, which helps Corona Labs continue to keep Corona up-to-date. This is the easiest and recommended way to go.
What license will Corona use?
Corona will be dual-licensed under both a commercial and open source licenses.
- A commercial license is available that will allow you to build commercial products based on the Corona source code. You will need to enter into an agreement with Corona Labs to get rights to uses source code as commercially licensed. Example of when such a license is required is to customize the engine to a specific commercial game.
- Alternatively, you choose to use Corona under GNU General Public License version 3 (GPLv3). This license is available to everyone, but all products built on top of code licensed this way must retain the same license and become open source themselves. Example for using this license is in non-commercial open source games, educational purposes or to contribute to the engine.
If you just want to build games using Corona nothing would change for you. You can still download public release or daily builds and build commercial software with it for free without any royalties or limits.
How does open source help us with a business based on Corona?
We believe that going open source will bring transparency to the process of development of the engine. This way our users would be able to see exactly what team is doing and where the project is going. We think this should give you confidence in the future of Corona. For some businesses, having an open source engine is a great opportunity to contribute needed features in a timely fashion, or get a commercial license for source code and customize the engine for their needs.
How can I contribute to the Corona open source engine?
If you want to get more involved, there are plenty things you can do, like testing, providing support on forums, implementing features and bug fixes, help us with documentation, tutorials, marketing, and promo materials, and many other ways to contribute. We are still at the beginning of figuring out the processes with the community and we are looking for participation of experienced users. Please, message us about your ideas about Corona development, or how you want to contribute and applicable skills to email@example.com or to @coronarob in Slack, #opensource. Let’s discuss it!
Open source details
What will get open sourced and what will core team support?
We will open source most of Corona’s code and resources with the exception of some plugins, the Corona Marketplace code, www.coronalabs.com, and our build infrastructure. The open source team will manage all of engine and infrastructure and will develop new features, fix bugs, support the engine with the participation from the community. This is not a final or exhaustive list and we may open source more as we move forward.
Is the Corona team still internally active on the engine?
Yes, absolutely. We have a stable product right now and we are planning to keep it up to date with the latest requirements and releases of iOS/Android. This means that you will be able to build your apps and games for Android and iOS devices.
What are the responsibilities of Corona Labs engineers right now?
Our team would be actively involved in development of the open source product: providing support, bug fixes, platform updates of the engine. We are also responsible to maintain the stability of the Corona Marketplace and plugin ecosystem.
How you track community issues like bugs and new features?
We are using GitHub’s issue tracker for bugs and feedback form for feature requests. Going to open source doesn’t detain bug fixing. For your convenience, we moved all open tickets to the GitHub’s issue tracker. Please look through existing issues to try to find the answer to your question before creating a new one. Follow these recommendations for using Issues. We will continue to use feedback.coronalabs.com for feature requests. You will find a step-by-step form there.
What about Corona Lab’s business model?
The Corona business model remains unchanged. We plan to continue to sell plugins in The Corona Marketplace, have revenue share based plugins and provide premium support. Additionally, we are planning to license source code for commercial usage. We are still looking to expand our earnings to have more resources to develop a better engine. This is not final and may change, any advice from the community is welcome.
What about plans for the future, the 2019 Roadmap?
We are looking forward to the new open sourced life stage of the Corona.
In 2019 our main focus will be on developing the community around Corona. The main product focus for the beginning of 2019 will be to modernize the Android build system. Next year’s roadmap is in works now.