You read my post incorrectly. I did not say we would do nothing - I said it would go open source OR we would take it over - "do nothing" was not an option.
Yes, Glen has been slow to adopt the few 2.0 changes that needed to be made - he has not understood all of them because he has not switched to 2.0. However, AFAIK, that is the only plug-in still having 2.0 issues. The others have been modified to be compliant, and many are now in the move to .NET. In fact, one of the big changes Glen has never made in the plug-in was to support device codes going to the 99 range and having to wrap and use another house code when you run out - that is back from the 1.7 days.
There were VERY FEW changes needed to work well with 2.0 - the truth is that Glen, just like HST, has to watch his bottom line, and so he tries to get paying work and cannot spend a lot of time without compensation on providing a free plug-in.
Comments here state that support of the plug-in would be difficult, and we cannot confirm more than a couple of dozen users, so if we decide to move it to open source, could you blame us? In open source, Glen himself could continue to work on it without any changes. I would think there would be more positive feedback on the open source option. Rather than not supporting it at all or leaving it using script based support, we paid Glen some money to write it, but it never attracted that many users. If we released it to open source, where else could somebody get a 98% complete plug-in to work on?