Torque3D MIT and ADDOnS

#1 I don't see why they wouldn't.

#2 We're definitely going to continue to sell add-ons.

#3 Could prove to be a bit messy if people want to fork T3D on Github. They wouldn't actually be able to put their project source there, if it contained closed-source addons. There are options like Bitbucket which have private repositories, but having things on Github seems like it would be much easier, especially in terms of pull requests.

#4 I'm guessing it wont be long before the first screwup and AFX or ACK or any of the other close source addons get posted to an open repo or download site anyway even if its through a misconception of sorts.

As an owner of those two products, the whole OS thing isnt going to really effect me any many positive ways at the moment anyway. That being said, i'm assuming that it is not legal to distribute non source AFX and ACK base projects to torque owner team members who arent owners of those products anyway. Ive never understoood EULA BS, even dumbed down explanations often mess with my head anyway.

#5 It's quite simple in my opinion, if you don't own it then you can't use it or have access to it. Whether or not Torque itself is open source (with the MIT license) or not has no bearing on the end use of 3rd party products. It's up to 'us' to observe proper due diligence in a situation when using other code/content with OS T3D

#6 GitHub has private repositories aswell, just costs a few bucks each month.

Edit:
@Bloodknight you are right actually that AFX and ACK can't sell their products to people using Open Source unless they update their file headers and eventual changes where necessary.
I do believe that AFX uses almost purely custom code tho so it might not be that big a problem.

#7 They can sell their code to anyone using T3D OS, but those people cannot redistribute it as open source, which is the key. That is why we're doing a code sweep to ensure that what we are putting up does not have any proprietary code.