I wanted to preserve the history but I needed to make sure that there were no more sensitive files in the code base accidentally being made public. To start with, I have set up build automation, reformatted the code, removed secret files from the code base and started a new change history for the code. Things will be rough in the beginning but we have to start somewhere and improve from there. I would rather that you didn't see those things. There are ugly things in the code that should have been done better. Opening up a project after almost 9 years is not an easy task. Even if someone tries to steal my work now, you guys know. It was considered many times but protecting my child always weighed more.īy now DISE has a community and a lot of people know who made DISE. I debated with myself whether I should open-source the project and risk people stealing my hard work and taking credit for it. The project was neglected for several years in a somewhat incomplete state, yet it was impossible to abandon it. Did you know that I have kept giving free support since the first release? That still applies today even though I haven't given it much love over the recent years.ĭISE has always been mostly a one-man project that took a lot of effort which has not given me a whole lot in return. DISE has been a project most dear to me ever since it was born in year 2011.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |