<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Chicken Scratchings from Karen</title>
	<atom:link href="http://localfoodcolumbus.org/2009/03/chicken-scratchings-from-karen/feed/" rel="self" type="application/rss+xml" />
	<link>http://localfoodcolumbus.org/2009/03/chicken-scratchings-from-karen/</link>
	<description>Local food &#38; urban agriculture news, Columbus, OH</description>
	<lastBuildDate>Thu, 20 Aug 2009 21:16:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: frijolitofarmer</title>
		<link>http://localfoodcolumbus.org/2009/03/chicken-scratchings-from-karen/#comment-162</link>
		<dc:creator>frijolitofarmer</dc:creator>
		<pubDate>Tue, 31 Mar 2009 17:23:12 +0000</pubDate>
		<guid isPermaLink="false">http://localfoodcolumbus.wordpress.com/2009/03/23/chicken-scratchings-from-karen/#comment-162</guid>
		<description>You know what I&#039;d like to see, Karen? Since you&#039;re so good at networking and seem to always know what meetings are being held where and what group is doing what, I think it would be useful if you focused your writing on reporting these things. Let everyone know through this site when and where they can go to meetings or other events to get involved.

You go to a lot of meetings yourself, so why not report back here about what was said, like you did in this post about the OEFFAdirect conversation? I think that would be the greatest contribution you could make to Local Food Columbus, acting as our reporter in the field, blogging about what&#039;s coming up and what just happened. I think this will draw a lot more positive attention to this site than the usual stream-of-consciousness rants where you throw a dozen different ideas into the blender. More importantly, you&#039;ll be facilitating getting other people involved by letting them know specifically HOW to get involved. 90% of success is showing up, and many of us--myself included--seem to be chronically out of the loop when it comes to knowing when and where to show up.

When putting together a report on an event--whether upcoming or something that&#039;s already occurred--remember &quot;Who, What, When, Where, Why, and How.&quot; What&#039;s the NAME of the group holding the meeting? What&#039;s the name of the person to contact for more information? What is the subject of the meeting or purpose of an event? What is the objective of the group holding the meeting? What time and date does it start? How long will it run? Is it a one-time thing, weekly, monthly? Where is it? Is there admission? Is membership required? Parking available? If you can&#039;t find out the address, does the building/park/etc. have a name? Can you give directions on how to get there? How can people get involved? Do they need to bring anything? Finally, what&#039;s important about this cause? Why should people care? How does it affect them or their community?

If you keep a checklist of these questions with you when you go to meetings and keep written notes of the answers, you&#039;ll have incredibly useful information to share with people, and I think you&#039;ll be amazed at how much more receptive people are to what you write. If you decide to do this, I&#039;ll be happy to help you edit your reports before we post them.</description>
		<content:encoded><![CDATA[<p>You know what I&#8217;d like to see, Karen? Since you&#8217;re so good at networking and seem to always know what meetings are being held where and what group is doing what, I think it would be useful if you focused your writing on reporting these things. Let everyone know through this site when and where they can go to meetings or other events to get involved.</p>
<p>You go to a lot of meetings yourself, so why not report back here about what was said, like you did in this post about the OEFFAdirect conversation? I think that would be the greatest contribution you could make to Local Food Columbus, acting as our reporter in the field, blogging about what&#8217;s coming up and what just happened. I think this will draw a lot more positive attention to this site than the usual stream-of-consciousness rants where you throw a dozen different ideas into the blender. More importantly, you&#8217;ll be facilitating getting other people involved by letting them know specifically HOW to get involved. 90% of success is showing up, and many of us&#8211;myself included&#8211;seem to be chronically out of the loop when it comes to knowing when and where to show up.</p>
<p>When putting together a report on an event&#8211;whether upcoming or something that&#8217;s already occurred&#8211;remember &#8220;Who, What, When, Where, Why, and How.&#8221; What&#8217;s the NAME of the group holding the meeting? What&#8217;s the name of the person to contact for more information? What is the subject of the meeting or purpose of an event? What is the objective of the group holding the meeting? What time and date does it start? How long will it run? Is it a one-time thing, weekly, monthly? Where is it? Is there admission? Is membership required? Parking available? If you can&#8217;t find out the address, does the building/park/etc. have a name? Can you give directions on how to get there? How can people get involved? Do they need to bring anything? Finally, what&#8217;s important about this cause? Why should people care? How does it affect them or their community?</p>
<p>If you keep a checklist of these questions with you when you go to meetings and keep written notes of the answers, you&#8217;ll have incredibly useful information to share with people, and I think you&#8217;ll be amazed at how much more receptive people are to what you write. If you decide to do this, I&#8217;ll be happy to help you edit your reports before we post them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

