On Wed, Apr 16, 2008 at 2:28 AM, James G. Sack (jim) <[EMAIL PROTECTED]> wrote:
snip > > Heh. Good points, but I think that falls (mostly) into the /how/ > category, and IMO, is not the right thing to spend time on until getting > more of the /what/ and probably /why/. I wouldn't dispute that > awareness of these methods and examples do lead to new ideas on what > might be undertaken. > > And it's admittedly hard to avoid talking about the /how/ just to make > ideas more concrete or to illustrate by example. But I'm convinced that > the attention spent on that should be deliberately limited, in favor of > the broader preparatory questions. > > Actually, in this case the /who/ needs to be continually kept in mind, > as well. We're talking about SDCS, not KPLUG. And, of course, we're > talking about the larger community as well -- some of which (schools, > libraries, etc) has in fact been part of the discussion, I'm happy to > acknowledge. > > Maybe some think I'm belaboring a moot point, and feel the why and what > are already understood. Sorry, I think that would be a somewhat reckless > assumption. I don't think it's just me, is it?. It's useful to have a > target in mind before you draw the bowstring, eh? [how's that go?] > > To follow my own advice, here are a few thoughts to stir around: > > why: > we (SDCS and sigs) have resources going underutilized > there are community needs we are especially equipped to help with > we could increase our own satisfaction by doing good > we could increase our recognition by doing useful things > (dare I say it) to keep SDCS viable -- a side benefit maybe > > what: > assist computer users generally > assist underprivileged & disadvantaged > assist groups or institutions (schools, libs) with compatible goals > indirectly assist via communication & information technology > contribute to emergency preparedness and response > ---lesser/future goals might include: > foster professional and academic purposes > > who: > SDCS (sigs -- let's catalog their interests and resources) > friends, orgs, commercial supporters, .. > SDCOE and other institutions > community segments -- determine needs, geo/demo-graphics, etc > ---eventually, upon actually _doing_ something: > individuals (project leaders, contributors, advisors, ..) > ---also important: > let's make sure of sig buy-in, before going too far > maybe even "buy-in" is too strong, let's _involve_ them first > promotion and negotiation -- Josh, you there? ;-) > > The why's needs at least some elaboration and consensus. > The what's needs a lot of further brainstorming and refining. > All could use somebody's notekeeping and editorial efforts -- wiki? > > ==> Now, how do we expand this discussion beyond this KPLUG list? > > ==> What else? I wonder if we might not be framing the questions a bit incorrectly, vis-a-vis outreach. Much of this discussion, so far,(Sorry don't have time to read the whole thread, so appologies if this is covered later.) has been focused on what we might teach or do and how/where we might teach or do it. I wonder if it might be more prodictive to ask those in the community we presume we'll be reaching out to to tell us what they don't know. This as opposed to what they want to learn, which tends to get a lot of blank stares and little else. The answers we get to that type of question might better inform our ideas as to who, what, where, and how, as well as help keep attendance more consistent over time. This would need to be an ongoing process to keep up with changing needs. Just a thought. RD -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
