[OpenStack-DefCore] Suggestions on trademark changes, possible meeting 10/2 or earlier

Joshua McKenty joshua at pistoncloud.com
Tue Sep 23 18:08:32 UTC 2014


I’d like to nominate Simon to take over my co-chair position. I’m done. 

--

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 23, 2014, at 11:03 AM, Simon Anderson <simon at dreamhost.com> wrote:

> Rob, candidly, I think you are way overstating things and being disrespectful of the Board in referring to the careful discussion and debate around DefCore as "thrash". 
> 
> The Board is very diverse, as it should be, and in the thick of considering an extremely important issue that will have ramifications for the health and growth of the OpenStack community in years to come. It's very important that members of the Board feel fully able to take time to consider and respond to evolving community inputs on DefCore, without being criticized for not dancing to any other stakeholders tune.
> 
> I think you are getting too personally attached to the DefCore process. You've been instrumental in leading it so far, but you should carefully think about whether you can shift to the more patient, objective and non-judgmental approach that will be needed to see it through to its conclusion. 
> 
> 
> Best,
> Simon
> 
> On Tue, Sep 23, 2014 at 9:36 AM, <Rob_Hirschfeld at dell.com> wrote:
> Dell Customer Communication
> 
> > From: Simon Anderson [mailto:simon at dreamhost.com] Hi Rob, I may have
> > heard a different output from the Board call - which was that the Foundation staff would work on some multi-TM proposals and share them with the DefCore committee/Board. So Jonathan, Mark and Lauren may already be working on them.
> 
> Simon, I heard a lot of different positions taken.  There was no clear guidance from the board in this regard and I believe our charter is to propose a variety of options for discussion.   One could/should be "stay the course" and others should explore "levels" like the TC are discussing.  Another path would be to accelerate the "submarks" like you've suggested as an addition to the core/base mark we've put into the process.
> 
> My issue is NOT with the changes proposed (there are several reasonable options) but with the continuous thrash in the board meeting that dilutes our effectiveness.  These issues and discussions should have been raised before the meeting so that we could adjust the agenda.
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140923/ba3f3764/attachment.html>


More information about the Defcore-committee mailing list