The biggest news is that, as we talked about in February, we shut off new account creation. If you want an account, please contact us at firstname.lastname@example.org and we can manually create one for you. We have selected a replacement technology for the ReCaptcha that should help ensure users are legitimate individuals and are creating only one account. We may save that for the new UI, which will be deployed at the end of May. More on that in a bit.
We’re exploring Twitter Digits, which will require new accounts to have a phone number that can receive an SMS message and will limit the use of a phone number to a single account. We are also talking about simply re-enabling new account creation on the Open Hub using the current mechanism in the hopes that the spammers have dropped us from their site lists. However, one suspects their systems have a significant degree of automation. Therefore, on one hand we can wire up a new account verification model and carry it forward if it works as desired even if we only have less than two months on the current platform, or we can restore the old mechanism and hope we don’t get slammed right away, or we can do nothing until the new code is ready (which is the least desirable option since legitimate folks are looking to get accounts on the Open Hub). Active conversations are happening today.
Beyond re-enabling new account creation, most of our focus remains on Project PURR — Platform Upgrade Ruby and Rails. This project is a migration of all the User Interface code to the latest stable version of Ruby and Rails. This was a big undertaking and we are executing it well. Two thirds of the way through the project and we have migrated about 130 models, 50 controllers, 400 views, over 100 asset files, plus a smattering of decorators, validators, null models, mailers, etc. Additionally, there is over 2K lines of tests in 270 test files with over 99% code coverage for the Ruby and Rails code. We are focused on migrating only those models that are needed to display the UI. There are models that are used by both the backend analytics as well as the UI, so we are migrating only the UI related code.
We set a six month timeline to complete this work and are well on target to complete on time. The best part is that there shouldn’t be much of a change that anyone notices. The look and feel of the web application will remain the same, although we should pick up some improved mobile layout by using Bootstrap 3. That said, we are not spending extra effort at this point to optimize the mobile experience; we still get a tiny percentage of traffic from mobile devices, which can be interpreted both ways as an argument both for and against mobile UI optimization.
You might also like
The Cadence of Creation: on understanding the creation account of Genesis ~ an archaeological dig into the Hebrew mindset of antiquity (The Three Creation Accounts of Scripture Book 1)