Currently getting an alpha / minimum viable product done. This should be fairly easy, it's mostly CRUD. After that, we can better focus on working with the local development team. UI work is going on in branch add_active_scaffold so we can easily do another UI less dependent on active scaffold, if that makes sense.
Most helpful feature to work on would be a tree interface for selecting codes for a project/activity/line item, along with fields to enter amounts or %'s for that code. No work has been done on that as of yet.
Greg is going to integrate file uploading from github.com/rwandaonrails/csv-uploader.
We may switch to Rails 3 after we have some alpha working.
Nothing is sacred, be vocal about ways to improve anything we are doing.
Join the discussion at: groups.google.com/group/rwandaonrails
Tracker should be public at this point. Click the “Join Project” button after visiting this website to get more than read access.
Let Greg know if you're available to do some pairing/mentoring! Mega bonus points.
More info on collaborating with local Rwandan team can be got by emailing firstname.lastname@example.org.
Please fork and clone the git repository. Then install rvm using the instructions below. We use rvm to standardize the Ruby and Gem environments across Developers on the project and help new devs get up and running quickly.
install RVM if not already installed, see rvm.beginrescueend.com/rvm/install/ . Google / ask Greg if you have trouble.
git checkout add_active_scaffold
rvm install ree
Now we'll import the rvm gemset from default.gems.
rvm gemset create ree-1.8.7-2010.02@resource_tracking
rvm gemset import resource_tracking
Note: if you have an error with database gem you won't be using, you can ignore it.
Now, # cp config/database.yml.sample config/database.yml # edit config/datbase.yml per your environment. This file is not tracked by git. # create .rvmrc file so whenever we cd to RAILS_ROOT we are using the right Ruby version and gem set.
echo 'rvm ree-1.8.7-2010.02@resource_tracking' > .rvmrc
Now you can choose a feature for the alpha, developing on a local feature branch (as per: reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html). Let Greg / the mailing list know if you have any questions. Thanks!