Bob La Quey wrote: > On Tue, Apr 15, 2008 at 11:06 PM, Joshua Penix <[EMAIL PROTECTED]> wrote: >> On Apr 14, 2008, at 5:16 PM, Doug LaRue wrote: >> >> >>> Moving the next stage to a meeting room is a good idea but I sure wish >>> Josh would chime in and direct some of this since he's the guy who'll make > >> >> >> > > the choice of what/where/when and how it all happens. >> >> Chiming in. :) I'm glad this discussion got started without me, and I'm >> sorry it took me this long to catch up on it... as it now seems to have >> headed in a direction away from where I was intending. >> >> I'll be clear about this - Linux advocacy is the job of KPLUG, not SDCS. >> Something along the lines of Linux CD distribution, even of the educational >> sort, may very well be worth discussing but not as a SDCS project. This is >> not to say that a SDCS project wouldn't involve the use of Linux, but if the >> biggest topic of discussion is about the OS choice, then we're not thinking >> big enough. >> >> I view SDCS as an OS-agnostic organization whose strength is in its >> volunteer resources and community contacts. Unfortunately those strengths >> have diminished significantly over the last ~10 years. The big question is >> whether or not it's worth putting effort into exercising what's left >> (including a reasonable size treasury made up of donations that were already >> given to the SDCS in good faith) and maybe rebuilding the enthusiasm that >> has been lost. I believe it is, but am still working to develop my vision >> of exactly how and where. >> >> I keep asking myself two core questions: >> >> 1) What can we do? >> >> 2) Who can we do it for? >> >> I think collecting a reasonable brainstorm about #1 is the first step. >> What can a group of volunteers of varying technical capabilities reasonably >> do? Once we have a small sample selection of things that we *can* do, I >> don't have any problem spending some hours on the phone introducing SDCS to >> anyone in need who will listen to a ~30-60 second elevator pitch. And we >> may not even wind up doing anything that was on the original list, but >> having such a list will get the listener's brain juices flowing about what >> might be useful for their particular organization. >> >> I don't think getting into the administrative front-office network is wise, >> but Lan is starting down a good "who" track with his post about the >> California public schools needing help due to restricted funding. Merge >> that with Doug's "what" suggestion about an in-school online forum and I >> think we're getting somewhere. Think harder about the "use" picture - >> students and/or teachers having a digital communication tool that they >> wouldn't otherwise have. Think instant messaging or voice messaging mixed >> with a collaborative learning website. Maybe a streaming video server for >> reviewing class lectures at leisure. I may be wildly off base, but this are >> the general sorts of ideas I'm looking for. I don't want implementation >> specifics... those come later. Yes, I can see FLOSS projects being central >> to all of the above ideas, but that's just a natural function of "build >> something digital in the year 2008 with the best bang for the buck." >> >> So help me do some more brainstorming... WHAT CAN WE DO? Think of SDCS as >> a business that needs a few bullet points for its marketing brochure. >> >> -- >> Joshua Penix http://www.binarytribe.com >> Binary Tribe Linux Integration Services & Network Consulting >> > > If you look at what is happening it is called Web 2.0, facebook, ning, orkut, > picasa, flickr, del.icio.us ... all that you guys are discussing is so > far behind > the curve as to be irrelevant. > > I know I am just an old fart enamoured with "new, shiny" but so are 70 million > face book members ... > > Meanwhile Obama rasies $40 million in one moth because his crew > gets it. > > Get with the program folks.
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? Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
