Thank you for your kind comments. SD is open source, so Mark and I do this for fun, not for profit. Our focus has been to give the MV community an easily installable more complete and tested version of the OpenQM 2.6.6 version that was released 19 years ago and converted to 64 bit several years ago by the ScarletDME developers. I think we have succeeded in making the system more reliable and secure. For me, every three or four months I will suddenly get the urge to work on something or suggest a new feature or do documentation. We want the system to be useful to others, but the progress is slow. We would need significant additional contributors to enhance the core parts of the system, to create better documentation or to have a better web site.
As an example, my latest interest is to try running various AI code evaluation tools against the C code that is a part of the base system, make the suggested changes and see if the system still works. Will this have any practical use and would it be the best investment of my time if this was being done for profit; probably not. But it is what interests me right now, so that is what I am doing.
Occasionally I will suggest a feature to Mark that requires his skill set. If he finds it interesting it gets done (and vice versa).
Since we do this in our free time, our focus has been on security first. We got rid of remote telnet access and made SSH the only remote connection option. Mark created a Python based compiler and then we did some other work to replace all the binary bits that still remained in ScarletDME. Any binary files needed are created during the installation process. The reason that we did this was to mitigate the complaints that parts of ScarletDME were not auditable. Every part of SD can be reviewed as it is all text, no binary parts remain in the source repository. We also added the abiltiy to encrypt files. The GPL version of openQM did not include the encryption features found in the commercial version. Our encryption features are fairly minimal, but they do allow for data to be encrypted. As part of the security focus we removed the user and accounts functions and replaced them with user and group accounts all located under /home/sd. This allowed us to enforce security permissions more easily.
Mark also added some fun extras like embedded Python. The only features that are removed in the most current version are the menu and screen builders that were a part of openQM and ScarletDME. We had originally removed PROCs and Pick compatibility features but have now returned them to version 1.02.
Much of the internal work on SD was done by Mark. My work was mostly the forking process from ScarletDME including removing the ScarletDME and openQM branding as we wanted to make clear that this was a separate project and that the prior developers should not be associated with any failures on our part or our decisions to modify and/or remove features. However we do credit them for their work in our contributors file. I also created the original installsd and deletesd scripts to make the process of maintaining the SD system easier than was true with either the open source version of openQM or ScarletDME. Mark and I have continued to refine these scripts to make them more bullet proof and support a larger number of Linux distributions. I do try to test the installer when new distribution versions are released, but it is time consuming.
Anyway, I hope that gives anyone interested an overview of our slow but steady progress in refurbishing this somewhat antique database.