LOst does have a right to his code, but this is supposedly a community project, how can someone contribute to the engine if they can't see the code? What I'm saying is that LOst must have a reason to not take advantage of all the benefits opening the code would bring. So, I'll ask again, LOst would you mind sharing your reasons why you believe keeping the code closed will be more beneficial than opening it? Is it a general fear that you'll lose control of the code? Show me how to contribute code and I'll help like I said. Joining in with the staff and not paying attention the community is not an option for me, I'm sure there are other programmers hovering around that would contribute if it was easy to. About my post being irrelevant, well, I've posted my advice, you guys can take it or disregard it, that's your prerogative. But I'd like to think what I said had some effect on the announcement Canned Karma just posted. As it is I don't have time to join as a full time member. I have a bunch of other responsibilities that I've been letting slip recently (like running http://nehe.gamedev.net/ and reviewing articles for http://www.gamedev.net/ and helping to fix bugs in the upcoming Ubuntu 10.04 release, and fixing the DirectDraw surface ref-counting in Wine and I have my own personal projects on top of that - just in case you wanted evidence for my "snub"). Also, to whomever it was that said "this is a professional project now and should be closed" - erm, yeah sure, because open projects are never professional (e.g. Apache, Linux, Wine etc. etc.). sigh. @Canned Karma - Thanks for the announcement, definitely looks like a step in the right direction to me. Nice one! (Although my reservations about the closed source engine still stand) I'll continue to hover around the forums, I might even attempt some artwork when time permits (I can basically find my way around Inkscape).