pair pickups about food-rescue-robot HOT 4 CLOSED

Yes, this has been on my todo list for some time and is actually quite high
on the list currently. I've wanted to implement it as a many-to-many
between schedules and volunteers so that any number of volunteers can be
assigned to one pickup. If you decide to do this, it would definitely be
valuable for other groups, since many of them have combo-pickups like this
and currently just assign it to one of the volunteers.

Incidentally, I committed some fixes and improvements recently that you may
want to pull down to your fork. I'm headed off to the Nepali Himalaya on a
research trip for the next 5-6 weeks, so I'll be (much) slower than usual
to respond, but will be back state-side mid November.

On Thu, Sep 26, 2013 at 8:49 AM, rahulbot [email protected] wrote:

At a recent outreach meeting a bunch of people wanted support for
pair-pickups. The idea would be that one or two people could sign up for a
slot. Has that come up for you? How have you handled it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3
.

Caleb

from food-rescue-robot.

FYI - I'm working on this now. Lots of touch points, so it may take a bit.

from food-rescue-robot.

I think I've got this working. I'm going to test a bit more locally before sending over a pull request. A lot of places this had to change, so you definitely will want to test it a bunch first. A few points I'm already aware of:

• the new migration copies current and former volunteers to the new schedule_volunteers tables - this is not undoable, so backup your database first!
• I changed the language to reflect the idea that a volunteer can 'take' or 'leave' a pickup
• I cleaned up the rake tasks to be more rails like, so you'll need to change your cron to something like rake foodrobot:generate_logs , etc (ie. they are namespaced under foodrobot)
• if more than one person is on a pickup, whose responsibility is it to fill in the log? for now I did a quick hack and made it the "first" volunteer that we pester via email reminders. I'm open to changing this, perhaps we need to add a "primary" column to the schedule_volunteers table to indicate who is in change? Or maybe pester them all until someone fills out a log? Dunno what the best answer is here going forward (maybe my hack is fine since the people know each other IRL).
• all the urls in the reminder urls are now pulled from the config.action_mailer.default_url_options variable in the appropriate config.environments file

from food-rescue-robot.

This is great. Thanks, Rahul. I'll pull it in first chance I get.

On #4, I'd say we should pester all of them. "Many hands make work light"
as they say. As a nicety, we could send an email to the folks who /didn't/
fill it in, telling it has been, so they don't duplicate effort. I'll add
this as a todo on my trello board.

Incidentally, I just brought an intern on the project (local CS+Nonprofits
fellowship), so there may be some more active development on my branch in
the coming months. I'll let you know when there are substantial changes.

Cheers,

Caleb

Caleb

On Fri, Jan 10, 2014 at 1:50 PM, rahulbot [email protected] wrote:

I think I've got this working. I'm going to test a bit more locally before
sending over a pull request. A lot of places this had to change, so you
definitely will want to test it a bunch first. A few points I'm already
aware of:

• the new migrationhttps://github.com/rahulbot/food-rescue-robot/blob/master/db/migrate/20131226160442_create_schedule_volunteers.rbcopies current and former volunteers to the new schedule_volunteers tables
• this is not undoable, so backup your database first!
• I changed the language to reflect the idea that a volunteer can
  'take' or 'leave' a pickup
• I cleaned up the rake taskshttps://github.com/rahulbot/food-rescue-robot/blob/master/lib/tasks/foodrobot.raketo be more rails like, so you'll need to change your cron to something like rake
  foodrobot:generate_logs , etc (ie. they are namespaced under foodrobot)
• if more than one person is on a pickup, whose responsibility is it
  to fill in the log? for now I did a quick hack and made it the "first"
  volunteerhttps://github.com/rahulbot/food-rescue-robot/blob/master/lib/food_robot.rb#L22that we pester via email reminders. I'm open to changing this, perhaps we
  need to add a "primary" column to the schedule_volunteers table to
  indicate who is in change? Or maybe pester them all until someone fills out
  a log? Dunno what the best answer is here going forward (maybe my hack is
  fine since the people know each other IRL).
• all the urls in the reminder urls are now pulled from the
  config.action_mailer.default_url_options variable in the appropriate
  config.environments file

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-32059396
.

Caleb

from food-rescue-robot.