Afraid not @peerchemist .
There was a bug in the Nu client which meant that multiple votes for the same motion hash by the same custodian were being counted as multiple votes rather than just one. The incorrect vote count was being reported by the RPC call to the client and hence reported by Assistant and the Block Explorer.
This means that the vote to open source fell just short of the pass target. In order to have it pass unequivocally, so that the vote can stand up to Blockchain interrogation we need everyone who voted before to continue voting.
I feel quietly confident that the motion will pass quickly with this last push and the source can be opened within the existing 45 day window.
It’s a shame that this bug reared its head for this (already contentious) motion but, if anything, it highlights one of the benefits that open sourcing the code would have in allowing other eyes to identify these potential pitfalls before they become issues.
More information here: Error in motion counting method found
@assistant motion vote 6f361693a7b248730b41d4292f89dc6f6f166bc8