<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi everyone,<div><br></div><div>As a quick update, the community code of conduct has now been publicized on the Summit website, wrapped in more event-specific language recommended by this thread and the PyCon code of conduct. There is also a clear process for reporting and responding to any complaints.</div><div><br></div><div><a href="http://www.openstack.org/summit/openstack-summit-hong-kong-2013/the-openstack-summit-code-of-conduct/">http://www.openstack.org/summit/openstack-summit-hong-kong-2013/the-openstack-summit-code-of-conduct/</a></div><div><br></div><div>We're planning to promote the code of conduct in an email blast to all registered attendees this week, make printed copies available at the registration desk on-site and provide a reminder on the back of each badge. We're also sending it directly to sponsors because there are special notes about booth and party conduct.</div><div><br></div><div>Please let us know if you have any additional feedback or ideas.</div><div><br></div><div>Thanks!</div><div>Lauren</div><div><br><div><div>On Oct 3, 2013, at 9:58 AM, Lauren Sell <<a href="mailto:lauren@openstack.org">lauren@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Anne, David,<div><br></div><div>Yes, the transparency committee update is on the board meeting agenda, but I think the code of conduct for our Summit is a different issue.</div><div><br></div><div>The transparency committee had three main tasks: develop a written policy documenting our approach to transparency, investigate creating an independent ombudsman, and figuring out a way to move non-confidential Board communications to a public mailing list. I circulated the transparency policy on the Foundation mailing list (<a href="http://lists.openstack.org/pipermail/foundation/2013-July/001447.html">http://lists.openstack.org/pipermail/foundation/2013-July/001447.html</a>) for comment, and we're hoping to review the policy in today's Board meeting. You can see the latest version here (<a href="https://docs.google.com/a/openstack.org/document/d/1sGBtza-mjRXcDzFBSS9aUrYlAtu1se-eerHZN16DPyU/edit">https://docs.google.com/a/openstack.org/document/d/1sGBtza-mjRXcDzFBSS9aUrYlAtu1se-eerHZN16DPyU/edit</a>).</div><div><br></div><div>Regarding the Summit code of conduct, I have an update since my last email about working on reporting/response procedures. We have a draft going here (<a href="https://etherpad.openstack.org/reporting-response-procedures">https://etherpad.openstack.org/reporting-response-procedures</a>) and had a good call with the Ada Initiative last week for input. We're also planning to engage with them to train our event staff before the Summit. I'd welcome any feedback on the procedures, as well as if there are any other policies we should be looking at (our procedures are based largely on PyCon, also influenced by Ada Initiative) or other organizations we should be engaging with along these lines.</div><div><br></div><div>While we won't be able to change the official code of conduct before the Summit, we can wrap it with more specific behavior examples like David had suggested and publicize the reporting/response procedures on our website, in a pre-event email to attendees and on-site. If there are any issues in the meantime, the Foundation staff, including Jonathan, Stef, Tom and me, are always available and happy to get involved. </div><div><br></div><div>As a reminder, I encourage anyone who is interested to dial into the board meeting. The meeting invites are always posted to the Foundation mailing list, and there's a link to register in the agenda: <a href="https://wiki.openstack.org/wiki/Governance/Foundation/3Oct2013BoardMeeting">https://wiki.openstack.org/wiki/Governance/Foundation/3Oct2013BoardMeeting</a></div><div><br></div><div>Thanks,</div><div>Lauren</div><div><br></div><div><div>On Oct 1, 2013, at 12:53 PM, David Mortman <<a href="mailto:launchpad@mortman.com">launchpad@mortman.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Thanks Anne!<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 1:37 PM, Anne Gentle <span dir="ltr"><<a href="mailto:anne@openstack.org" target="_blank">anne@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi David and list and everybody, <br><br>The Board meets Oct 3, and Josh has an agenda item for the Transparency WorkGroup. <a href="https://wiki.openstack.org/wiki/Governance/Foundation/3Oct2013BoardMeeting" target="_blank">https://wiki.openstack.org/wiki/Governance/Foundation/3Oct2013BoardMeeting</a> <span class="HOEnZb"><font color="#888888"><br>
<div><br></div><div>Anne<br></div></font></span><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 1, 2013 at 12:25 PM, David Mortman <span dir="ltr"><<a href="mailto:launchpad@mortman.com" target="_blank">launchpad@mortman.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So given that it's been nearly two weeks since anyone has responded is it time to rebrand it the Opacity Committee?<br>
</div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 18, 2013 at 8:23 PM, David Mortman <span dir="ltr"><<a href="mailto:launchpad@mortman.com" target="_blank">launchpad@mortman.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Joshua,<br><br></div>I found this answer hilariously short and opaque especially given the context of it being part of the Transparency Committee. Can you go into more details about what has been discussed in the past as well as what might be proposed at the next board meeting. Speaking of which, when is the next board meeting anyways?<br>
<br>thanks<span><font color="#888888"><br><br>-David<br><br></font></span></div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 17, 2013 at 1:08 PM, Joshua McKenty <span dir="ltr"><<a href="mailto:joshua@pistoncloud.com" target="_blank">joshua@pistoncloud.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">David - yes, the ombudsperson office is one of the goals of the Transparency Committee, and we've got an agenda item to dig into again at the next board meeting.<div>
<br><div>
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="word-wrap:break-word"><div>--</div><div><br></div><div>Joshua McKenty</div><div>Chief Technology Officer</div><div>Piston Cloud Computing, Inc.</div><div><a href="tel:%2B1%20%28650%29%20242-5683" value="+16502425683" target="_blank">+1 (650) 242-5683</a></div>
<div><a href="tel:%2B1%20%28650%29%20283-6846" value="+16502836846" target="_blank">+1 (650) 283-6846</a></div><div><a href="http://www.pistoncloud.com/" target="_blank">http://www.pistoncloud.com</a></div><div><br></div>
<div>
"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."</div></div></div>
</div>
<br></div><div><div><div>On Sep 15, 2013, at 5:18 PM, David Mortman <<a href="mailto:launchpad@mortman.com" target="_blank">launchpad@mortman.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">
<div><div>Joshua,<br><br></div>I'll leave it up to the event staff to determine how they want to handle it in this on-site case. Certainly someone needs to be empowered or the exercise is pointless. For the community as a whole, does the Board of Directors have the authority to create an ombuds office?<br>
<br></div>-DM<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Sep 15, 2013 at 12:44 PM, Joshua McKenty <span dir="ltr"><<a href="mailto:joshua@pistoncloud.com" target="_blank">joshua@pistoncloud.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">David, while I think having an onsite group able to field complaints and address incidents is critical, we need to make sure that such a group has the ability to address any complaints. So I'd suggest we pass this directly to the foundation staff, and make sure that the event coordination team is coached appropriately. Having community members act as ombudsperson is both complicated from a legal standpoint, and potentially inappropriate.<div>
<br></div><div>Lauren, can you make sure the on-site events team is briefed on the proposed code-of-conduct, and is ready to respond to any complaints that might arise?</div><div><div><br><div>
<div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">
<div style="word-wrap:break-word"><div>--</div><div><br></div><div>Joshua McKenty</div><div>Chief Technology Officer</div><div>Piston Cloud Computing, Inc.</div><div><a href="tel:%2B1%20%28650%29%20242-5683" value="+16502425683" target="_blank">+1 (650) 242-5683</a></div>
<div><a href="tel:%2B1%20%28650%29%20283-6846" value="+16502836846" target="_blank">+1 (650) 283-6846</a></div><div><a href="http://www.pistoncloud.com/" target="_blank">http://www.pistoncloud.com</a></div><div><br></div>
<div>
"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."</div></div></div>
</div>
<br></div><div><div><div>On Sep 15, 2013, at 3:59 AM, David Mortman <<a href="mailto:launchpad@mortman.com" target="_blank">launchpad@mortman.com</a>> wrote:</div><br></div><blockquote type="cite">
<div><div dir="ltr">On Thu, Sep 12, 2013 at 4:26 PM, David Mortman <span dir="ltr"><<a href="mailto:launchpad@mortman.com" target="_blank">launchpad@mortman.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"> Agreed. There should be at least a small group, especially for events, so that one person doesn't get hammered but also so there's a committee to make judgement calls etc. Love the idea of some training too.<br>
</div></div>
</blockquote></div><br></div><div class="gmail_extra">Given the closeness of the summit (only 2 months away), it's seems like a good idea to put together the initial group of folks who can be the onsite committee to help address any issues that hopefully won't arise. While I'll continue to participate in this effort, unfortunately, I won't be attending the summit myself so I can't help onsite. I will however like nominate both Anne Gentle and George Reese be initial members of the committee. Anyone else interested? A group of three is probably plenty.<br>
<br></div><div class="gmail_extra">thanks<br></div><div class="gmail_extra">-David<br></div></div></div><div>
_______________________________________________<br>Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</div></blockquote></div><br></div></div></blockquote></div><br></div>
</blockquote></div><br></div></div></blockquote></div><br></div>
</div></blockquote></div><br></div>
</div></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>
</blockquote></div><br></div></blockquote></div><br></div></body></html>