APM: Activity?

Jeremy Fluhmann fluhmann at gmail.com
Wed Jun 27 12:09:23 PDT 2012


In case anyone is interested  -  irc.perl.org   #austin.pm

On Thu, Jun 21, 2012 at 5:42 PM, Jeremy Fluhmann <fluhmann at gmail.com> wrote:

> In case it affects the decision for the soon-to-be upcoming date of the
> next meeting - http://geekaustin.org/guide-austin-tech-meetups.  The 4th
> Wednesday doesn't have anything going on if anyone is up for even just an
> Austin PM Social Hour (perl -e "print qq{wink } x 2;")
>
>
> On Thu, Jun 21, 2012 at 12:18 PM, Jeremy Fluhmann <fluhmann at gmail.com>wrote:
>
>> Now that I live in Austin, I'm definitely up for getting back into the
>> Perl community.  I'll help in any way I can for any movement to get monthly
>> meeting going again.  Do we have a current list of potential meeting
>> venues?  Any potential pizza sponsors? (Pizza seems to be the de facto
>> standard on groups, but any "food/drink" sponsor would be welcomed, I'm
>> sure).
>>
>> Cheers,
>> Jeremy
>> --
>>
>> Jeremy Fluhmann
>> *http://twitter.com/jfluhmann*
>> *http://identi.ca/jfluhmann
>> http://jfluhmann.edublogs.org
>> Texas Open Source Project - http://texos.org
>> Texas Linux Fest - http://www.texaslinuxfest.org*
>>
>> On Fri, Jun 8, 2012 at 4:33 PM, Patrick R. Michaud <pmichaud at pobox.com>wrote:
>>
>>> On Tue, Jun 05, 2012 at 10:10:41AM -0500, Mark Lehmann wrote:
>>> > It takes a lot of effort to coordinate events.  I'd be happy if someone
>>> > else wanted to coordinate.
>>> > [...]
>>>
>>> I don't know if this will help here, but one of the user groups
>>> I frequently attend started having monthly "meeting managers".
>>> We got the idea from Perl's new release manager process, which
>>> in turn got it from Parrot.
>>>
>>> In Perl/Parrot, each monthly release has a separate "release manager"
>>> that is responsible for the tasks associated with that month's release.
>>> The procedure is all well documented, so someone just volunteers for
>>> a month, follows the steps, and a release comes out.
>>>
>>> In the user group scenario, each regularly scheduled meeting has
>>> someone volunteer to be that meeting's "coordinator" (or whatever
>>> you wish to call it).  That person is responsible for arranging a
>>> speaker or event, making the meeting announcements, etc. for the
>>> given month.  The meeting manager can *be* the speaker, but isn't
>>> required to be.  And of course the manager can delegate out as
>>> desired/necessary.
>>>
>>> The whole point is that the work of setting up a meeting (or release)
>>> doesn't fall to the same person month after month after month to
>>> the point that he/she burns out or runs out of ideas.  Also,
>>> having more managers brings more ideas and improvements into the
>>> process.
>>>
>>> It's worked reasonably well at the UG that I attend; perhaps
>>> it can work for you as well.
>>>
>>> Lastly, I'd be happy to come down to Austin sometime and give a
>>> presentation.  :-)
>>>
>>> Hope this helps,
>>>
>>> Pm
>>> _______________________________________________
>>> Austin mailing list
>>> Austin at pm.org
>>> http://mail.pm.org/mailman/listinfo/austin
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/austin/attachments/20120627/1d3803f8/attachment.html>


More information about the Austin mailing list