It has taken the Open Source Initiative(OSI) eight months to come to the conclusion that the OVPL and OVLPL do not comply with the Open Source Definition(OSD), and therefor will not be approved for use by the OSI. This has been a long and frustrating battle, however, I'm glad there is now some resolution. My response to the OSI had a touch of annoyance about it. I also posed a few questions to the OSI regarding their stance on future licenses to ensure everyone understands their new 'line in the sand'(the request and response is not yet archived online). If nothing else I can say that I helped shape the future of how the OSI interpret and enforce the OSD.

The result of this is that it is time to rethink what license is required for Argot. My initial feeling is that it is unlikely to be an OSI approved license. This gives more freedom in taloring the license to best fit Argot and users needs. The downside is that Argot doesn't get the OSI logo on it; c'est la vie.

The final nail in the coffin of OVPL is not quite finalised. We may look at using a BSD license back for contributions. However it will need some discussion to decide how this will effect the license.

In Argot news, the Argot Network Resolution code has been added to the Java and C# versions of Argot. It has been added in a way that abstracts the functionality away from any transport. It requires that the developer provide the transport mechanism as part of their peer to peer or client server protocol. That finishes up the functionality for those versions.

Only a few more things to do before release. Sort out this license issue and port the Argot Network Resolution code to C. Easy!