Quote:
Originally Posted by mobilegamer999
Why not just build upon TBA's codebase?
The main reason is that its not THAT simple, TBA would not let some random outsider start modifying their code and pushing it live to the website. Even if they let us help them with their code, every time more people are added to a project, the slower changes become and the less often changes can be made.
Open Source?
I can almost guarantee that we will not open-source the website. Our biggest reason for this is that we made the API public and extremely easy to get started with so that there was no need to open-source the website. While we wont be open-sourcing the website, we WILL be providing very simple/easy to read code example for how to do just about every feature on the website in many common languages (C#, Java, Ruby, PHP, etc.)
|
Of course TBA does not let random outsiders push code live to the website. I have contributed code to TBA, but ultimately Greg was the one that pushed it to the server. Would you let me push code live to TFA?
Open source is not equal to no security.
Your reason for not making TFA open source is not a real reason. As others have pointed out making an API and open sourcing a software project are two mutually exclusive actions. If you simply made the decision not to open source TFA then that is your reason, not that TFA has an API.
With respect to the accusations of this being a "hobby project", I think people need to give you guys a chance. Where would TBA be today if people wrote it off as a "hobby project"? I don't mean to be mean to you guys with my above comments, but just as you guys want to make sure people don't have misconceptions about TFA, I want to make sure they don't have misconceptions about TBA.