Bundler Rails Girls Summer of Code Plan

Joyce and I met up in Santa Monica and did some pair programming. Then we met with our coach Jessica Suttles. We saw where we are going to be working, met the cats, her flat mate and she gave us a plan for our summer. . .

Bundler Rails Girls Summer of Code Plan

1. Use Bundler, and take notes about what is good and what is bad about using it. We want to fix the bad things!
1. Improve [site documentation](http://gembundler.com)
1. Improve `bundle help` [man page documentation](http://gembundler.com/v1.3/man/bundle.1.html)
1. [Triage issues](https://github.com/bundler/bundler/blob/master/CONTRIBUTE.md#bug-triage)
1. After taking notes about bad things, and starting to reproduce other people's problems, is there anything that you _want_ to work on? because if you're motivated to do it, chances are much higher you will want to stick with it until you figure it out.
1. If not, we have a bunch of things that would make bundler better but not enough people working on them. Some of these are repeats of the steps above, but that would be fine. They need lots of doing. :)

Bundler tasks

(I'm pretty sure we can find a decent number of additional tasks that fall in the easy and medium levels by just going through the open tickets. --andre)

easy

ticket triage (try to repro, ask for more information)
update the documentation if it’s wrong or confusing
add documentation for things people open tickets about
help confused people in #bundler on freenode
add a useful error message when dependencies are circular (https://github.com/bundler/bundler/issues/2506)

medium

Patch level support (add :patchlevel argument to the “ruby” Gemfile method)
Send useful user agent with HTTP requests (@indirect has started this, it's about 80% done in user_agent branch)
Add read-through caching to the bundler-api server (save local copies of requested gems and serve those next time)
Plugin-command support (search PATH for a command and run it if it exists)
Stop saving options passed to install (this confuses people, and we’re hoping to make it better)

hard

Source disambiguation (@ckrailo has started this)
Checksum generation (@hone has started this)
Plugin callback/hook support (register code that will run when a gemfile is read, resolver is run, gem is installed, etc)
Ruby API for bundle information (Ruby class that encapsulates a parsed gemfile and provides information about gems, groups, without status, and other handy things)

Platform support (create separate lockfile entries if install is run on jruby, windows, etc)