home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!ames!haven.umd.edu!mimsy!nmrdc1!dsc3pzp
- From: dsc3pzp@nmrdc1.nmrdc.nnmc.navy.mil (Philip Perucci)
- Newsgroups: comp.os.linux
- Subject: Re: Advice on organizing linux users locally
- Message-ID: <C0AIu5.JAK@nmrdc1.nmrdc.nnmc.navy.mil>
- Date: 3 Jan 93 18:18:04 GMT
- References: <93Jan2.021018ast.52@ug.cs.dal.ca> <1993Jan3.065400.18858@news.uiowa.edu>
- Organization: Naval Medical Research & Development Command
- Lines: 40
-
- In article <1993Jan3.065400.18858@news.uiowa.edu> miranda@eng.uiowa.edu writes:
- >Obviously, I am _very interested_ in the type of activities that linux
- >users/hackers can appreciate. although not a hacker myself, I LIKE this
- >OS. So, please, leep this thread going and contribute if you have something
- >to say. thanks. Adios. -JEM-
-
- I tend to "fly alone", and do OK with FAQ, READMEs, and USENET. Having said
- that...
-
- It seems to me that one way to proceed would be the following:
-
- 1) Have someone volunteer to be Linux User Group Coordinator (LUGC?).
-
- 2) LUGC post "form" for people to fill out. Would include, minimally,
- the following:
-
- o Name
- o Address
- o Voice phone
- o E-mail address
- o System type
- o Distribution type (SLS/GCC/MCC/other, version of kernel, etc.)
- o Specify whether potential "Local Coordinator" or "Local Member"
- (Local Coordinator would be responsible for coordinating with
- the LUGC)
-
- 3) LUGC collect responses, break-down responses into geographic regions
- each region headed by Local Coordinator.
-
- 4) Send individual "regional" lists to Local Coordinators.
-
- 5) Cross fingers...
-
- $00.02 exhausted...
-
- --
- ===========================================================================
- phil perucci | "Any opinions expressed are solely my own views and
- ssb1pzp@digex.com | do not reflect the position of any organization"
- ===========================================================================
-