[mdlug] [Fwd: [Announce] Our Next MUG Meeting is Tuesday, December 12, 2006 at 6:30PM]

[Raymond McLaughlin]

-------- Original Message --------
Subject: 	[Announce] Our Next MUG Meeting is Tuesday, December 12, 2006
at 6:30PM
Date: 	Wed, 06 Dec 2006 09:14:15 -0500
From: 	Duane Brown <dobwan at earthlink.net>
To: 	announce at mug.org



  Our Next MUG <http://www.mug.org/twiki/bin/view/Mugwiki/WebHome>
  Meeting is Tuesday, December 12, 2006 at 6:30PM.


      The Topic is the: Linux Powered Office Infrastructure
      <http://www.mug.org/twiki/bin/view/Mugwiki/LPOI>

Various people will be contributing segments to the presentation (and
I'm sure there will lots of discussion about additional options).

We started this exercise at the October and November meetings with
discussions to identify the required functions and the software
candidates to fulfill those requirements. At the December meeting we
will give a brief introduction to some of the options.

Here is the situation. Someone that you know, your brother-in-law, your
cousin, your minister, your ...., well someone, wants to setup a back
office computing operation for a small business, or an organization, or
something. They know that you are a computer expert. They ask you what
to do.

You, being completely committed to open software and not being quick
enough to have hidden, want to respond with a complete solution. What do
you do?

What functions might they need? What software should you install to meet
those needs? Then how do you setup those software systems and how do you
administer them? Don't worry about money. There is none. You will be
using mostly hand-me-down hardware and only new store-bought-stuff if
absolutely necessary and if the price is low.

An introduction to the various components with a chance for feedback, to
get an idea of what our membership would like to hear more about at
future meetings.

It has been mentioned that we could try to actually install and
configure parts of this. There seems to be far too many things in our
solution to install anything during the meeting. If anyone wants
guidance with selection, installation, setup and administration of these
parts bring it up and I'm sure someone will be more than glad to help.

*Free and Open Source Software (FOSS) is a requirement, where possible.*

We started this exercise at the October and November meetings with
discussions to identify the required functions and the software
candidates to fulfill those requirements. At the December meeting we
will give a brief introduction to each of them. There will probably be
far too many things in our 'Back Office' solution to install or
configure them during the meeting.

We may have presentations on installation and configuration of the
various pieces of the Linux Powered Office Infrastructure at future
meetings.

Linux Powered Office Infrastructure
<http://www.mug.org/twiki/bin/view/Mugwiki/LPOI> Our current list of
possible components

------------------------------------------------------------------------

If you have topics for future meetings you would like us to cover please
email the board <mailto:board at mug.org>, thanks.

------------------------------------------------------------------------


      Where:

The MUG meetings are held at:

Farmington Community Library - Main Branch <http://www.farmlib.org>
32737 W. 12 Mile Rd.
Farmington Hills, MI 48334-3302

Click here
<http://www.mapquest.com/maps/map.adp?country=US&addtohistory=&formtype=address&searchtype=address&cat=&address=32737%20W%2012%20Mile%20Rd&city=Farmington%20Hills&state=MI&zipcode=48334%2d3302&searchtab=home>
for a map of the area.


      When:

the meetings are on the 2nd Tuesday of each month.

6:00pm 	Doors open, registration
6:30pm 	Meeting starts, Mug business
6:45pm 	Main presentation
8:15pm 	2nd Presentation
8:45pm 	Meeting adjourns
9:00pm 	Dinner at a local establishment

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: file:///tmp/nsmail.asc
URL: <http://mdlug.org/pipermail/mdlug/attachments/20061206/78aeb12b/attachment-0001.asc>