* Email on generation is a good idea. Also, I don't have a Gem cache system yet which will help.
* Flickering is because some of the inputs have to compute a lot of values @ Backbone model layer. Definitely opportunity for optimization.
* Thanks :)
* A lot of users have asked for user contributed features. The problem is it's hard to extract an API from my generation system but I hope to in the future.
* Very doable. I just haven't written private repo support in because I'd have to deal a lot of auth/selection issues which isn't a priority right now.
* Vagrant would be great.
For a lot of these, I just don't have time yet but all candidates for the future.
presumably each step is being done as a git commit, so there'd need to be a git install done locally for creation, then zipping, then cleanup afterwards. I don't think it's unreasonable, but I'm guessing there's some 'post to github' gem that's being used directly right now and this other option would require more work.
* Email on generation is a good idea. Also, I don't have a Gem cache system yet which will help.
* Flickering is because some of the inputs have to compute a lot of values @ Backbone model layer. Definitely opportunity for optimization.
* Thanks :)
* A lot of users have asked for user contributed features. The problem is it's hard to extract an API from my generation system but I hope to in the future.
* Very doable. I just haven't written private repo support in because I'd have to deal a lot of auth/selection issues which isn't a priority right now.
* Vagrant would be great.
For a lot of these, I just don't have time yet but all candidates for the future.
Thanks again.