[Ongoing series of blog posts to inform
potential developers, users and (hopefully investors) about this new app
ecosystem I am architecting, designing, developing and deploying. More details
at this page]
Code development always brings up the question of code
visibility. Should it be open sourced or closed source?
This Project TD could be a complete waste of everybody who
is involved. Or it could be something really cool. Or somewhere in between.
Yet, as I enter my fifth year of being a trainer, I have proof to show that at
least some of my stuff has become useful to others. This project (and all its
related resources) might become useful to at least one other person. Perhaps
more if I am lucky.
Then, there are the personal benefits I have enjoyed, thanks
to open source software. I use Firefox extensively. VLC player, another
software that has really made my life better. Back when I could not afford
Office products from Microsoft, I used OpenOffice as well as LibreOffice. Then,
there are all those free code that is available online which has helped me
All in all, at this point, the decision to go open source is
obvious, as long as all materials related to project TD is used for
non-commercial purposes, and the user links back to project TD related
resources. I may add some more conditions, but for now, this is all there is to
[Last Updated February 10th 2017]
Follow me on twitter, facebook and instagram for more