SPUG: SPUG Program Committee Meeting - rewrite the community

[Michael R. Wolf]

I propose that the next SPUG meeting be a "program committee" meeting.  For
those who don't like committees or meetings, let's call it a working session
- brainstorming, visioning, planning, and committing to deliverable
meetings.

I would facilitate (not lead - we'll all do that) such a meeting on the
regularly scheduled SPUG night - November 15 at a place TBD (ideas?).

I've been inactive with SPUG lately, as I've joined the board of another
professional group.  That group has a program committee, and typically has
one or two people responsible for each meeting.  With that kind of load,
burnout isn't a big problem - make your meeting happen, then sit back and
enjoy some other team's meeting.  I've also been active in a group that
planned a calendar of topics a year out, even though they didn't have
speakers.  The organizer knew (from talking to the members) what was of
interest, and set a long-term plan.  If we did that, it'd give that
meeting's leader a long time to research the topic, find appropriate
speaker(s), let the speaker(s) prepare, and appropriately plan the meeting
without having to do a last-minute crunch.

Many of us are programmers in the sense of writing computer programs.  
Anyone interested in joining me to become programmers in the sense of
providing events (i.e. programming)?

Pair-wise, or group-wise, Programming Anyone?

Let's play!

Michael Wolf

P.S.  Let's rewrite the community.

    Perl 5 was my rewrite of Perl. 
    I want Perl 6 to be the community's rewrite of Perl 
    and of the community.
      -- Larry Wall, State of the Onion speech, TPC4

-- 
Michael R. Wolf
    All mammals learn by playing!
        MichaelRWolf at att.net