JamesLMilner on master
TypeScript types: Separate out … (compare)
@morganherlocker I had one other question about mapbox open source (heh, for now). It might be different for you guys, depending on how pay / time works, but bosses here were wondering what approach to take to limit amount of time people spend actively maintaining working on open source stuff.
obviously, as you pointed out on twitter, build everything like it's going to be an open package, so that fits nicely into our workflow with no real impact on time, other than time spent making things more ready w/ docs and tests, but we want that anyway. The question more is, how much time is okay to be spending maintaining packages that we have published, on the clock. and how to we set expectations about that.
so I was curious if mapbox had any specific mechanism for that or if it's more.. you know what you should be working on, if working on this package more gets you there, then do it, if not, maintain off the clock
node bench.jsto see the number of operations per second for any function. https://dl.dropbox.com/s/16v5j5y5dpubzyv/Screenshot%202015-05-05%2012.09.55.png?dl=0