So given that it's been nearly two weeks since anyone has responded is it time to rebrand it the Opacity Committee?
On Wed, Sep 18, 2013 at 8:23 PM, David Mortman <launch...@mortman.com>wrote: > Joshua, > > 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? > > thanks > > -David > > > > On Tue, Sep 17, 2013 at 1:08 PM, Joshua McKenty <jos...@pistoncloud.com>wrote: > >> 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. >> >> -- >> >> Joshua McKenty >> Chief Technology Officer >> Piston Cloud Computing, Inc. >> +1 (650) 242-5683 >> +1 (650) 283-6846 >> http://www.pistoncloud.com >> >> "Oh, Westley, we'll never survive!" >> "Nonsense. You're only saying that because no one ever has." >> >> On Sep 15, 2013, at 5:18 PM, David Mortman <launch...@mortman.com> wrote: >> >> Joshua, >> >> 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? >> >> -DM >> >> >> On Sun, Sep 15, 2013 at 12:44 PM, Joshua McKenty >> <jos...@pistoncloud.com>wrote: >> >>> 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. >>> >>> 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? >>> >>> -- >>> >>> Joshua McKenty >>> Chief Technology Officer >>> Piston Cloud Computing, Inc. >>> +1 (650) 242-5683 >>> +1 (650) 283-6846 >>> http://www.pistoncloud.com >>> >>> "Oh, Westley, we'll never survive!" >>> "Nonsense. You're only saying that because no one ever has." >>> >>> On Sep 15, 2013, at 3:59 AM, David Mortman <launch...@mortman.com> >>> wrote: >>> >>> On Thu, Sep 12, 2013 at 4:26 PM, David Mortman <launch...@mortman.com>wrote: >>> >>>> 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. >>>> >>> >>> 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. >>> >>> thanks >>> -David >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : openstack@lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >>> >> >> >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
