[Chicago] Chipy Thursday Meetup

[Samuel Lahti]

The question was not, why has chipy not operated with a CoC for 10 years,
the question was, what is motivating people to abandon professional
conduct. I'm seeing a lot of +1's for adopting generally accepted CoC's
On Feb 11, 2014 10:00 PM, "Brian Curtin" <brian at python.org> wrote:

> On Tue, Feb 11, 2014 at 9:50 PM, Geoff Brown <geoffbrown at comcast.net>
> wrote:
> > I imagine I'm not alone in wondering why after ten years there is a
> level of
> > urgency to develop a code of conduct
> > and have financial transparency that would warrant abandoning
> professional
> > behavior?
> > Professional conduct would dictate that one bring up matters of
> reputation
> > and performance in person and preferably
> > in private. What am I missing here??
> >
> > May Guido help us if we do get a Code of Conduct.
>
> You're definitely not alone, but the state of open source software
> communities is significantly different in 2014 than it was in 2004, or
> so I'm told - I was a sophomore in college. It's a lot different from
> 2006 when I got involved.
>
> PyCon operated for 10 years before a CoC came up, and now you would be
> hard pressed to find a tech conference without one. If you find one,
> I'm fairly certain it's under pressure to get a CoC. Recent diversity
> efforts have been successful in forcing change across the community
> when it comes to conduct, and it's only getting stronger.
>
> The PSF operated for roughly the same time without a code, and now not
> only are we extending that CoC out into the actions we take and things
> we provide, the first check we do when evaluating grant proposals for
> user groups, conferences, or requests to use our resources is if a
> group has a code of conduct.
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> https://mail.python.org/mailman/listinfo/chicago
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20140211/30aecab1/attachment-0001.html>