Could a little write-up be provided on the rationale in not providing the code for various pieces of the Quantopian API. Some examples include:
Optimize API
Risk model implementation
QTradableStocksUS
My thinking is that the benefits would outweigh the risks in publishing code, and that this would extend to the SaaS model for Quantopian Enterprise users (who would be risking their own capital in using the Quantopian platform, and thus would be motivated to have a look "under the hood" for a variety of obvious reasons).
I realize that I've brought this topic up numerous times, but I have not been satisfied with the response. If the rationale can be explained, including how not sharing code is in the interest of both Quantopian Community and Quantopian Enterprise users, I will relent. It is an important topic, I feel, since the openness of the platform is one of its real pluses. Unless there is a compelling reason, the code should be available (as presumably it would be to developers at traditional hedge funds). What am I missing?
I do recognize that a lot of code has been shared, and zipline and zipline-live are supported. Also, Quantopian generally supports open-source in the software community. However, certain chunks of Quantopian API code are held back, and that is the focus of my inquiry.