Wesley Beary

@mburumaxwell Thanks for the interest in helping out. I think you are definitely on the right track and that sounds like a good approach. There are probably also some tests...

@mburumaxwell feel free to make the PR now if you'd like. We can always squash or rearrange commits later if need be, and the sooner it's available the sooner I...

@ZiNTeR Even in anonymous it might be doing things based on location. In general I think it will, unfortunately, be pretty hard for us to figure out why these numbers...

I'm afraid I haven't personally worked with or on this in quite some time. That definitely sounds like a great addition that I would certainly welcome and support if you...

@MartimSchnack - I'm not really actively using this at present, so not sure when I would get to it. I'd be happy to help you through a pull request to...

Thanks! On Mon, Nov 2, 2015 at 8:46 AM, Paulo Henrique Lopes Ribeiro < [email protected]> wrote: > fog-aliyun is already released and active. See [here[( > https://github.com/fog/fog-aliyun). > > —...

Sounds great, thanks! On Wed, Jun 8, 2016 at 3:31 PM, Paulo Henrique Lopes Ribeiro < [email protected]> wrote: > @jntullo https://github.com/jntullo Awesome. This wiki page > https://github.com/fog/fog/wiki/Create-New-Provider-from-Scratch should > help...

@tokengeek - thanks for the heads up. I think maybe I had seen something about this a long time ago and subsequently forgotten about it. Migrating sounds good, though I'd...

Performance is another part that has irked me with travis and seems to be much better with github (ie time from pull request creation to finished tests seems to be...

Thanks for sharing further info. The changes within travis seem to be moving in a direction that isn't great for us (and the experience so far has already been not...