Meals minutes: 2014-07-16

Agenda:

Review of Meals Jobs Descriptions

Minutes:

MONKEY summary:
Willie
* ask Tammy to do some book-keeping work for her meals committee labor
* compile a new allergens list and ask Adi to update the template.
* ask Nancy for a copy of the shopping list email from May 2012, and then
ask the people who have done inventory shopping recently to add to it, and
poll the community for additions.
Tammy
* review meals committee job descriptions, make sure they're accurate
and generic
* For Hobart issues, like E3 errors, we ought to create a
troubleshooting cheat sheet and post it on the wall above the Hobart
* put the proportions on the side of the big rice cooker: 1 cup white
rice to 1 cup water OR 1 cup brown rice to 1.5 cups water.
Elph
* send a reminder email to people to move grills.
* Elph will add a label to discard the extra rice cooker in December if
we haven't found the insert.
Malcolm
* ask Adi to send late menu posting reminders to meals@ mailing list



Attending: Willie, Malcolm, Becky H, and Elph

Becky stopped by from work, basically they would like us to review each of
our job descriptions. MONKEY: Perhaps we could hand these off to Tammy
since she hasn't been able to attend meetings? Malcolm was unaware that she
was part of the committee, and that we ought to reach out to her
specifically when we schedule the next meeting.

Becky points out that we ought to try out new people. Most specifically
this refers to the counted members, but also other jobs. Our current
committee members have recently turned over, though we ought to consider
ancillary jobs. On the other hand, the number of people who are willing to
cook tend to run lower than the number of shifts we need to fill.

Work would like us to think about contingency hours. Are they working? Can
we come up with one-time jobs to use up some of the backlog? Committees
aren't designed to manage labor, but instead managing the issues around
their field of interest. There's nobody who is receiving hours to manage
people who are doing the work. A lot of people don't understand the
concept, or how to know if they have hours remaining. How do we make it
easy, and how do we put in incentives and drawbacks for using these up, or
not.

We ought to make work assignments smaller allotments of hours (like moving
head cooks from 4 hours to 2). Perhaps we could move head cooks from 2
hours down to 1, in other words... one dinner per season. This could lead
to people having more variety of jobs, but smaller assignments.

There is some confusion around the boundaries between committees, like
meals and CH for the kitchen, and grounds and buildings.

We ought to send out a reminder of the lockup position job description.

CH could put a note on the hamper that says wet things should not be left
overnight. Instead, they ought to do something else, like spread out around
the edge of the hamper, so that it will dry, and it's clear that it's a CH
towel.

Send out reminder of job descriptions to grill cleaners.

MONKEY: Elph will send a reminder email to people to move grills.

MONKEY: For Hobart issues, like E3 errors, we ought to create a cheat
sheet... perhaps Tammy could do this?

Hope reclaimed her small rice cooker, there are 2 little ones, one is
missing a pan.
There are 3 rice cookers, a large one (ricemaster) with aluminum. One small
one with stainless steel, and another is missing the pan. We couldn't get a
large one with a stainless steel insert. There is occasional use for a
smaller one, let's get rid of the missing insert one.

MONKEY: Elph will add a label to discard the extra rice cooker in December
if we haven't found the insert.

MONKEY: Tammy - put the proportions on the side of the big rice cooker: 1
cup white rice to 1 cup water OR 1 cup brown rice to 1.5 cups water.

Future of online meals system...
summary is that for short term we're fine on all accounts, hardware,
hosting and development.

Mid-range, it would be nice to host it externally. The data is already
replicated externally. It would be great to have a plan generated that saw
the hosting move one year from now.

Longer-term, have somebody re-write the code into something more portable.
The data is available for import. The signup for looking at the meals and
having the cooks enter their menus, etc. The billing and cron jobs for
email of alerts is more complicated.

Note: the CH reservation system is hooked into authentication and meals.

MONKEY: Willie will compile a new allergens list and ask Adi to update the
template.

Ping cooks who have had problems updating their menus on time and ask if
they would prefer getting a text. Is there an alternate email to a
housemate? Can we assign someone to contact people when there's only a few
days left and they haven't posted one to leave them a note, knock on their
door, etc. Perhaps this could trigger an email to meals if there has been
no menu posted 72 hours in advance. MONKEY: Malcolm will handle this.

MONKEY: Willie will ask Nancy for a copy of the email from May 2012, and
then ask the people who have done inventory shopping recently to add to it,
and poll the community for additions.

Next meeting, August 19th, 9-10pm in the sitting room.