BLU meetings - what would you like to see?

[bhorne at lynx.dac.neu.edu (Bill Horne)]

John,

Your note raises a basic question, and I'll speak to that issue first.

The question is: "What are we trying to accomplish?".  Everything else
flows from it, especially the technical level of our meetings. 

If we're trying to explore the bleeding edge of Linux / GNU / open source
software, then *more* technical topics may be in order.  If the aim of
the BLU is to help those already working with Linux to expand their
knowledge, the current level would be (IMHO) about right.  If, however,
we're trying to introduce the average Wintel user to Linux, then we're
going to have to seek a much lower level. 

I'll leave that (admittedly thorny) issue for others to answer: suffice
to say, I think the BCS went wrong when it tried to serve average users
after they'd turned off their brains and switched to Windoze.  FWIW, I
think the BLU should try to introduce technical professionals (e.g.,
system administrators, engineers, IS managers, etc.) to Linux as an
alternative to Windows.  Also, I favor separate classes for newcomers,
coupled with the InstallFests.

There are, however, some things we can do that will improve the
presentations no matter what level they're designed for. 

I think the most productive change would be to ask the presenters to
provide more background material.  It's not that we need "less
technical" topics - it's impossible to get less technical than Windoze,
so I don't think we should try - but we *could* make it easier for those
whom are just getting started to follow up on the ideas presented.

I suggest that we start a "standard" list of things every presenter
should distribute: in addition to the material that is specific to the
topic, we could benefit from some added handouts:

* A diagram showing the <topic>'s use in a typical corporate data
  processing environment, with "executive summary" overviews of what
  it does and what's required to make it work.

* Documentation pointers for HOWTOs, and lists of publications 
  available, including ISBNs.  

* A detailed, step-by-step list of what a user needs to do to get
  <topic> running.  Now, before everyone's eyes glaze over, let me say
  that I know it's impossible to explain everything - but it is not that
  hard to provide a guide that will allow experienced users, system
  professionals, or even Linux newbies to connect the dots between 
  the "looks nice" demo and the point where they say "I can do that".

For those with extra time, or whom want to "try out" a corporate
presentation in a safe environment, some added material may be in order:

* A comparison to other commercial and non-commercial products that
  perform similar functions, with pros and cons.

* A report on what hardware is required, with "Don't even think about it"
  / minimum / average / "you're wasting your money" hardware requirements.
  I'd especially like to see reports showing how users can put older
  386/486 units back into service with <topic>.

* A list of transition issues, such as file conversions, user
  retraining, any needed hardware changes, or other steps a corporation
  might take to implement <topic> in place of Wintel boxes.

HTH.

Bill Horne


> 
> In the past, I've tended to seek out technical speakers and topics for our 
> Linux meetings. Now that Linux is becoming more mainstream, we can start
> scheduling less technical topics. I'd like to hear what people think about
> this, and about what you'd like to see at our meetings.
> 
> Thanks.
> 
> --
> John Abreau / Executive Director, Boston Linux & Unix 
> Email: jabr at blu.org / URL: http://www.blu.org
> ICQ#28611923
> -----------------------------------------------------------------------
>     Your mouse has moved. Windows NT must be restarted for the change
>     to take effect. Reboot now?  [ OK ]
> -----------------------------------------------------------------------
> 
> 
> 
> -
> Subcription/unsubscription/info requests: send e-mail with
> "subscribe", "unsubscribe", or "info" on the first line of the
> message body to discuss-request at blu.org (Subject line is ignored).
> 


-- 

Bill Horne
bhorne at lynx.neu.edu       


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).