Re: [UG-ADMINS] Code of Conduct, Rules, etc.

[email protected] (Eric Van Johnson)
Newsgroups ug.admins
Message-ID <CAMp+vwXNiwNT+c4bq5qVHqcubFnjPsfT+OZYktBxv5WnfCh4pQ@mail.gmail.com>
CoC is the fire extinguisher of user groups. You don't think you need one,
don't really want people looking at it, but in the event something goes
wrong, it's nice to have one laying around :-)


Eric

twitter <http://twitter.com/#!/shocm>: @shocm <http://twitter.com/#!/shocm> |
@sdphp <https://twitter.com/sdphp> | http://www.sdphp.org | http://shocm.me/

*No trees were killed in sending this message, but a large number of
electrons were terribly inconvenienced*.


On Thu, Apr 24, 2014 at 8:55 AM, Lorna Mitchell <[email protected]> wrote:

> I am not sure where I stand on whether codes of conduct are needed by user
> groups or not, but it certainly does not depend on whether something bad
> has already happened at your group.  As someone already mentioned, a CoC at
> an event or user group shows that someone has considered how to handle any
> problems that do arise.  On a very personal level, I feel confident that
> someone, somewhere, would at least listen if the unthinkable should happen.
>  And people with that attitude tend to run events without issues, strangely
> enough!
>
> Lorna
>
>
>
> On 24 April 2014 13:45, Adam Culp <[email protected]> wrote:
>
> > Although I did publish a CoC at SunshinePHP (http://sunshinephp.com) I
> > mistakenly did not feel the need to do so for SoFloPHP
> > (http://soflophp.org).  A user group tends to be more intimate, and
> > communication happens much more quickly and quietly...so I thought.
> >
> > Last year I had one incident resulting in a member being asked to leave,
> > which resulted in a blanket email to our members informing them of our
> > unpublished CoC.  It was also this occurrence that resulted in my adding
> > 4 co-organizers to help keep an eye on things in my absence if I'm
> > travelling.
> >
> > I would caution those who don't speak openly about this to your
> > members.  Don't make a big "stink" about it, but at the same time make
> > something public so members can feel comfortable and know what to do in
> > case of one "bad apple".
> >
> > As for a mission statement, I have that on the landing page of the user
> > group. http://soflophp.org.
> >
> > I've also set the meetup.com "thanks for joining" email to carry a
> > message setting clear bounds for recruiters.
> >
> > Regards,
> > Adam Culp
> > 561-870-6361
> > Twitter: @adamculp
> > LinkedIn: http://www.linkedin.com/in/adamculp
> >
> > On 04/23/2014 05:00 PM, Jeremy Lindblom wrote:
> > > Do any of your user groups publish a code of conduct? group rules?
> > mission
> > > statements? or any other documents? Just curious.
> > >
> > > --
> > > *Jeremy Lindblom*
> > > PHP Software Engineer at Amazon Web Services <http://aws.amazon.com/>
> > > Co-author of the AWS SDK for PHP <http://aws.amazon.com/sdkforphp/>
> > > Co-organizer of the Seattle PHP User Group <
> > http://www.meetup.com/php-49/>
> > > @jeremeamia <https://twitter.com/jeremeamia> | http://webjeremy.com |
> > > https://github.com/jeremeamia
> > >
> >
> >
> > --
> > Usergroup Coordination Mailing List (http://ug.php.net)
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
>
>
> --
> Lorna Mitchell
> http://lornajane.net
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.