Extra exposure is good. My concerns would be more along what & how to do it rather than if or if not.
Policy has been that anyone can join our mailing list and no one posts jobs except through gatekeepers; a number of world-wide PerlMongers are on multiple PM lists and wade in on our technical Q&A and we appreciate that. Our LinkedIn group has only accepted those who actually attended meetings.(This should include our expatriot members and our out of town speakers.) We have referred headhunters to the posting rules for the mailing list and jobs.perl.org. I would expect our Facebook page/group to have similar policy. KISS - The more content you duplicate the more work it is to maintain and/or the faster it gets stale. Links to our wiki and other resources and the other key Perl Community sites are lower maintenance. The Wiki remains the official central site to which others point. Facebook appss have repeated serious security problems, not just the obvious privacy issues. (It is facebook security month, google Faxx. I suspect LinkedIn apps may too, we won't use them.) Avoiding exposing our friends to bugs not of their choosing, avoiding Apps on Boston.pm page, is in line with KISS. Any group resource should have at least two admins so it doesn't get orphaned temporarily or permanently. Our Resources - boston.pm.org wiki boston-pm list and -announce list #boston.pm on irc.perl.org Boston.pm group on linkedin (*) Boston.PM page on FB (*) #boston.pm and @Boston.pm Twitter ? (*) = proposed We do NOT have a Meetup or Gcal. If we need a non-wiki calendar, I'd see Gcal as more Open than FB. -- Bill [email protected] [email protected] _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
