Campus Kitchen

A Campus Kitchen is an on-campus student service program that is a member of the nonprofit organization, The Campus Kitchens Project. At a Campus Kitchen, students use on-campus kitchen space and donated food from their cafeterias to prepare and deliver nourishing meals to their communities.

The organization is headquartered in Washington, D.C. on the campus of Gonzaga College High School. There are currently 63 Campus Kitchens, located in Saint Louis, Missouri; Evanston, Illinois; Milwaukee, Wisconsin; Minneapolis, Minnesota; Spokane, Washington; Mankato, Minnesota; Washington, D.C.; Lexington, Virginia; Winston-Salem, North Carolina; Kearney, Nebraska; Williamsburg, Virginia; Gettysburg, Pennsylvania; Baltimore, Maryland; and more (see full list of Campus Kitchens below).

Operations

  • Each Campus Kitchen is hosted by a school who shares space in one dining hall's kitchen, which is termed the "Campus Kitchen." (Usually, this space is used during less busy or off-hours for the dining hall, such as evenings and weekends.)
  • Students go to dining halls and cafeterias at designated times to pick up unserved, usable food. (The dining services companies who donate are protected from liability concerns under the Bill Emerson Good Samaritan Food Donation Act.)
  • Students prepare meals using that donated food, as well as food from local food banks, restaurants, grocery stores and farmers markets.
  • Then, students deliver meals free of charge to individuals and agencies in the school's neighboring community in need of food assistance. Agencies include homeless shelters, food banks, soup kitchens, and individuals or families in need of food assistance.
  • Student volunteers also provide empowerment-based education to clients, such as nutrition education to children, healthy cooking classes to families and culinary job training to unemployed adults.

History

The Campus Kitchens Project was developed in 2001 as a national outgrowth of DC Central Kitchen, a successful local community kitchen model in Washington DC.

In 1989, Robert Egger, founder and CEO of DC Central Kitchen, pioneered the idea of recycling food from around Washington DC and using it as a tool to train unemployed adults to develop valuable work skills. DCCK became a national model, and as the idea grew, and groups around the country started to open kitchens, Robert started looking for a way to engage the thousands of underutilized school cafeterias and student volunteers in the effort, particularly in rural communities. In the mid-1990s, he piloted a job training program in 10 schools across the U.S. with the American School Food Service, with funding from the USDA.

In 1999, two Wake Forest University students, Jessica Shortall and Karen Borchert, created a small student organization called Homerun that engaged students in cooking and delivering dinners to folks in the community. What started as a hobby instead became a successful campus organization. After graduating, Borchert came to work at DCCK.

In 2001, the two concepts came together, and with a start-up grant from the Sodexo Foundation, The Campus Kitchens Project piloted its first program at Saint Louis University in Missouri.

Current locations

gollark: "Search packages" is `pacman -Ss [whatever]`, "install" is `pacman -S [whatever]`, "update repos and update all packages" (it is apparently unsafe to update only individual packages) is `pacman -Syu`.
gollark: You pick a "subcommand" with a capital-letter flag like `-S` (sync, which seems to be a fancy word for "Install packages"), `-Q` (query information aboud stuff) and then pass extra flags to configure how that works.
gollark: > what's a pacman-like CLI?Arch Linux (btw I use that) has a neat package manager called `pacman`.> what counts as package updating support?Updating packages without breaking things horribly, including not overwriting user-edited (config) files.> and library interface as in an API you can use from scripts?Precisely.
gollark: Oh, and a library interface.
gollark: Well, I would want a pacman-like CLI, probably configurable repos, multiple files in a package, good package updating support, and... other stuff?

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.