Tomorrow's flow

[Derek Shanahan]

All,

I'd like to have a rough schedule for the day tomorrow so a) I can
focus the non-devs effectively b) we have an idea of when breaks/
touching base might happen.

My thinking was that after we say hello to everyone I can gather non-
devs to discuss the various ways they might contribute (allowing for
anyone to suggest more, of course). I outlined a few of those buckets
in an earlier post.

As the group self-organizes I think it prudent to identify a few
'check in' times; progress updates, blockers, ideas, etc.

My thinking was that every two hours might work. I think it likely
that means the first checkin happens around 11:30 or noon; and would
be a good precursor to lunch.

Thoughts?

Derek

[Boris Mann]

Please just nail down a schedule and be prepared to announce it. I am personally out of town for looking at this and will just be showing up tomorrow morning.

--
--
Open Food - http://open-food.org/
You received this message because you are subscribed to the Google
Groups "Open Food" group.
For more options, visit this group at
http://groups.google.com/group/open-food?hl=en

--
Boris

778-968-2171
http://bmann.ca

[Tom Carchrae]

I'm just landed from GMT, body arrived, the airline is sending along brain when it arrives.  kids brains appear lost.  please use incoherent ramblings as inspiration only.  do not consume. 

...continuing on from the ideas laid out in the previous mail ("Organized work for non-devs to do" - icons, data work/functionality, etc), something along the lines of

Morning:  

* devs work on API tech, rough concepts, maybe get test api running and some quick and dirty apps running off it

* non-devs work on possible application ideas, brainstorm ways of using open food api (concepts mainly, both existing and novel, eg, show me all the restaurants with food inspector reports that serve yak.  (eg, yukkyyak.com !) and so on)

Afternoon

* piece together how API fits concepts, test how easy it is to provide data from api, flexibility, extensibllity

* non-devs, critique API, shoot it down, pick pick, etc

[Derek Shanahan]

Okay so the day's schedule will look like this (I will print this and
work with Sarah to update it + manage the crowd/schedule):

9am CheckIn

9:20am: Welcome - Anthony or Boris or Kalv
9:30am
Housekeeping for all hack day attendees. - Derek
- schedule
- wifi passwords, bathroom location
- where people can hack - food versus non-food

Everyone gets to work.

11:30am
Break to provide updates.
12
Lunch

1pm
Reconvene and get back to work.

3pm
Break to provide updates.

6pm
End of day updates.
Dinner break.

> >> Open Food -http://open-food.org/

> >> You received this message because you are subscribed to the Google
> >> Groups "Open Food" group.
> >> For more options, visit this group at
> >>http://groups.google.com/group/open-food?hl=en
>
> > --
> > Boris
> > 778-968-2171
> >http://bmann.ca
>
> >  --
> > --

> > Open Food -http://open-food.org/

[Kalvir Sandhu]

Thanks for planning this a little.

My only feedback would be to leave out the updates every 2 hours, if somebody wants an update they can wonder over and ask quickly, we don't have much time in the day, so let's just work heard till the end of play.  I don't think there will be much to report in 2 hours and I guess there will be lunch for some people to catch among themselves on what's going on.

We need to focus on getting something usable, small and useful out in day, sure in our groups we'll need to plan a little but we need to keep talk to only what's necessary.

-- 
Kalv

--

--

Open Food - http://open-food.org/

[Derek Shanahan]

Roger that. Updates will be left off schedule.