What is all this whitelab, turbo, and leased stuff?
They had a bunch of options they experimented with over the years for different payment models. If you are curious:
whitelabel - an option to remove all mentions of the geo company or software name from the admin. IIRC they were approached by some big company that wanted that option in the past.
leased - they offered leased license for a while. Think of it like "software as a service" - Where you would pay monthly, it was slightly less than what you would pay if you kept up to date with both downloads access and paid support, but if you stopped paying, it would expire the license and you would be locked out. Thus "leased". A few used it but not enough so they stopped offering it to new clients.
Turbo: not sure, I think that was something they added after I left
print: for a while they were working on making a "print ad" edition of the software. Where you basically used it to keep track of classifieds, but it had no "browsing" built in. It was meant to export the listings that you would then feed in to your own in-house software for adding them into a newspaper or magazine or whatever. Not sure if it was ever finished or sold but I am not sure that it was.
What I would do is remove the front end parts that are not used or needed, then look at what was removed, look at the back end and remove the stuff that tries to set it.
When I'm doing a search and destroy like this, I find it helps to keep notes. Like I make a checklist, if I remove a thing I add it to the checklist. Once I'm done I go over the checklist items, searching the code for places that still use each one. If I find one and it turns out it is still needed, I leave it. If I find another use but that other place maybe is not needed, I add it to the list and keep going. It involves lots of going over the same items until you either remove all the sub-parts then the thing itself, or you run into a place that needs it to stay so you check it off that way.
Since it is pretty heavy with the old licensing checks, I can take this one over if you want. I also have access to the original git repo so I can look at the history that might help determine if something is still needed or not. Just let me know.
vicos59
commented
2 years ago
They had a bunch of options they experimented with over the years for different payment models. If you are curious:
What I would do is remove the front end parts that are not used or needed, then look at what was removed, look at the back end and remove the stuff that tries to set it.
When I'm doing a search and destroy like this, I find it helps to keep notes. Like I make a checklist, if I remove a thing I add it to the checklist. Once I'm done I go over the checklist items, searching the code for places that still use each one. If I find one and it turns out it is still needed, I leave it. If I find another use but that other place maybe is not needed, I add it to the list and keep going. It involves lots of going over the same items until you either remove all the sub-parts then the thing itself, or you run into a place that needs it to stay so you check it off that way.
Since it is pretty heavy with the old licensing checks, I can take this one over if you want. I also have access to the original git repo so I can look at the history that might help determine if something is still needed or not. Just let me know.
Originally posted by @jonyo in https://github.com/geodesicsolutions-community/geocore-community/issues/147#issuecomment-1061806267