Last modified: 2014-11-07 17:51:09 UTC
Yuvi's description of the task: If you guys are worried about this taking too much of analytics' time, here is a proposal: 1. Someone authorizes the machine 2. I set myself a 2 week deadline, working solely on 'volunteer time' (all of Quarry and a lot of other things were built in a similar way), setting it up and securing it there. It will be super protected (hehe) at this point, with very limited access and no publicity. 3. The analytics team plays with this, and then decides what to do. 4. I will continue to maintain Quarry anyway - we're close to reaching 1000 individual queries run, and that's with very limited publicity! All code will be labs/prod agnostic as well. Plus it's written with similar frameworks to other projects analytics is already doing (flask, celery), so not too much of a tech jump there if you guys decide to add more features.
