RFC: YAPC Code of conduct up on github?

[Rob Kinyon]

Yes, any official amendments would have to go past lawyers. But, I suspect a few things will happen here:
1. The YAPC-NA organization on github will serve as the transmission medium for all YAPC-related documents. I remember having issues with this in the handover between Pittsburgh and columbus, even though we all knew each other IRL. 
2. The official document(s) can also have a history of discussion that can inform how to interpret and apply it. 
3. If we as a community feel that an amendment is needed, we can work out the spirit of the thing in a branch and submit the diff to the lawyers via TPF as a code review.

There is nothing to lose by putting the docs in the one place we KNOW everyone at a YAPC will have an account on and know how to use and who has a vested interest in making sure things remain up (unlike Google). 

Sent from my iPhone

On Mar 22, 2013, at 20:17, Robert Blackwell <robert at robertblackwell.com> wrote:

> I think this is a great idea to have the community work on the Code of
> Conduct but do note that TPF has/had a lawyer helping to write a Code
> of Conduct. Can someone from TPF chime to say if we can run a new
> community edited Code of Conduct by the lawyers and what would the
> timeframe be?  There already is a CoC for YAPC::NA,
> http://www.yapcna.org/yn2013/code-of-conduct.html.
> 
> Robert
> 
> On Fri, Mar 22, 2013 at 8:09 PM, Chris Weyl <cweyl at alumni.drew.edu> wrote:
>> Awesome!  Thanks Rob :)
>> 
>> I _think_ we can just pull the code listed on the yapc site as a starting
>> point, right?  (I mean, there's nothing More Official out there we should
>> use, yes?)
>> 
>>                           -Chris
>> 
>> 
>> On Fri, Mar 22, 2013 at 5:05 PM, Rob Kinyon <rob.kinyon at gmail.com> wrote:
>>> 
>>> There is already a yapc account on github (I just tried to register it and
>>> failed) that has one of rblackwe's repositories starred.
>>> 
>>> So, I went ahead and created the yapc-na organization. Stevan and Perigrin
>>> and I are the initial owners and I will gladly bow out when asked.
>>> 
>>> I've also created https://github.com/YAPC-NA/code-conduct that anyone can
>>> fork and provide a markdown or POD of the code of conduct. I will happily
>>> accept pull requests to get this baby started.
>>> 
>>> Rob
>>> 
>>> 
>>> On Fri, Mar 22, 2013 at 7:48 PM, Chris Weyl <cweyl at alumni.drew.edu> wrote:
>>>> 
>>>> Hey all --
>>>> 
>>>> Apologies if this is already the case, or has been discussed already.
>>>> But given what happened at pycon in the last week or so, I think we should
>>>> also post our code of conduct on github such that we can all fork, edit, and
>>>> submit suggested edits as pull requests.  (details to be hammered out, yes,
>>>> but the same basic workflow as any other pull-req)
>>>> 
>>>> http://www.wired.com/wiredenterprise/2013/03/pycon-github/
>>>> 
>>>> I know I was reading our code of conduct yesterday, and thinking how I'd
>>>> like to see some language in there talking about not just gender, sexual
>>>> orientation and ethnicity (among others), but also about gender identity,
>>>> gender expression, and national origin...  so I'd be first in there with a
>>>> pull request :)
>>>> 
>>>> Thoughts?  What would it take to do this?
>>>> 
>>>> Thanks-
>>>>                                        -Chris
>>>> 
>>>> --
>>>> Chris Weyl
>>>> Ex astris scientia
>>>> 
>>>> _______________________________________________
>>>> yapc mailing list
>>>> yapc at pm.org
>>>> http://mail.pm.org/mailman/listinfo/yapc
>>> 
>>> 
>>> 
>>> 
>>> --
>>> Thanks,
>>> Rob Kinyon
>> 
>> 
>> 
>> 
>> --
>> Chris Weyl
>> Ex astris scientia
>> 
>> _______________________________________________
>> yapc mailing list
>> yapc at pm.org
>> http://mail.pm.org/mailman/listinfo/yapc
> _______________________________________________
> yapc mailing list
> yapc at pm.org
> http://mail.pm.org/mailman/listinfo/yapc