#Adium update code
This will allow improvements and security updates to the core ChatSecure code to be more readily available to whitelabeled apps.Īfter that is complete, we will begin splitting up the monolithic framework into smaller and more manageable frameworks: UI, network stack, database, and encryption layer. Each of these components will need to be split into reusable components with no cross-dependencies.įor the first step, we will create a monolithic ChatSecure framework that includes the entirety of the ChatSecure iOS code as a reusable library. Right now there is a tight coupling (aka spaghetti code) between the UI, XMPP network stack, database, and encryption layer. This will require a very large refactor of the existing ChatSecure code into reusable components. In short, just give us proper attribution, and publicly distribute any source code changes you’ve made to our framework. Organizations that wish to release closed source / commerical / proprietary apps will also be able to use the code as long as they follow the terms of the MPL 2.0. It doesn’t virally spread its terms to the rest of your program like the GPL, there’s no issue with static linking like the LGPL, and it is fully compatible with the App Store. It is most similar to the LGPL in that binary distributions require attribution and that modifications to the code need to be publicly available.
#Adium update license
This is the license used by Firefox and VLC for iOS. Splitting that framework into multiple sub-frameworks each concerned with a single domain: UI, network, database, encryption.Īdditionally, to accomodate forks and other open source projects that wish to reuse our code, we will be relicensing these reusable components under the copyleft MPL 2.0 license.Creating a monolithic framework containing almost all of the existing ChatSecure iOS code.Now that we are also working on a whitelabeled version of ChatSecure ourselves, the pain of keeping the two versions in sync has made it apparent that a major refactor needs to happen as soon as possible. Although many people and organizations have requested license exemptions since our move to the GPL, we haven’t had the time or legal resources to grant any. The GPL license also currently prevents people from legally shipping forks or devirative works that include our code to the App Store (without an exemption). There are a lot of cross-dependencies, assumptions about the ChatSecure brand, and some unfortunate spaghetti code that has accumulated over the last few years of development. I’ve noticed that many apps have been appropriating ChatSecure iOS code for their whitelabeled products, even though the code is not currently suitable for this purpose. AugChatSecure Core ChatSecure Core Motivation
0 kommentar(er)
