<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>+1<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>We want wide inclusion and also need to organize so we don’t waste a lot of people’s time. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think it’s important to be transparent that we’re getting organized.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I understand the urgency and desire for involvement. We took a lot of small steps to get here and I expect that we’ll follow the same approach.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rob<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><a name="_____replyseparator"></a><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Joshua McKenty [mailto:joshua@pistoncloud.com] <br><b>Sent:</b> Tuesday, November 12, 2013 3:27 PM<br><b>To:</b> Mark McLoughlin<br><b>Cc:</b> Hirschfeld, Rob; fungi@yuggoth.org; Mark.Radcliffe@dlapiper.com; foundation@lists.openstack.org; openstack-tc@lists.openstack.org<br><b>Subject:</b> Re: [OpenStack Foundation] OpenStack core and interoperability -> Meeting 11/20 in SFO<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ironically, the goal of this meeting is to address a lot of what you're asking for - wiki page, mailing list, schedule and doodles for meetings, logistics around using IRC, etc. As Rob pointed out, this isn't the kickoff - it's just he and I attacking the logistics.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I love the idea of having some TC folks involved, too. <o:p></o:p></p><div><div><div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>--<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>Joshua McKenty<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>Chief Technology Officer<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>Piston Cloud Computing, Inc.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>+1 (650) 242-5683<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>+1 (650) 283-6846<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'><a href="http://www.pistoncloud.com">http://www.pistoncloud.com</a><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:13.5pt;font-family:"Helvetica","sans-serif";color:black'>"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."<o:p></o:p></span></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Nov 12, 2013, at 1:10 PM, Mark McLoughlin <<a href="mailto:markmc@redhat.com">markmc@redhat.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><p class=MsoNormal>Hi Rob,<br><br>This just came up in the TC meeting and I volunteered to pass on some<br>feedback that I think we were all agreed on:<br><br> * This discussion is inevitably going to get pretty technical as we <br> start grappling with what will be required and what won't be. The <br> TC feels it should have some involvement in that and would like to <br> nominate some of its members to join.<br><br> * It would be great to open these discussions as widely as possible. <br> An all day, in-person meeting in SF, with 8 days warning is <br> particularly difficult for interested people to join in with. The <br> TC favours IRC for meetings, but conference calls could work too.<br><br>Also, it would be great to have a wiki page describing the goal of the<br>committee, who's involved, what the mailing list is, tracking the<br>outcomes of meetings, etc.<br><br>Thanks,<br>Mark.<br><br>On Mon, 2013-11-11 at 16:53 -0600, <a href="mailto:Rob_Hirschfeld@Dell.com">Rob_Hirschfeld@Dell.com</a> wrote:<br><br><o:p></o:p></p><p class=MsoNormal>Thanks Josh.<br><br>I thought to add the specific that we know so far.<br><br>If any can join, we're talking about Wed 11/20 at the Piston SFO office. The meeting will be *all day* but you can attend parts<br><br>IMHO, this is planning for the kick-off, not the actual kick-off. However, we need to decide quickly if a by-laws change is needed. That's the primary objective for this meeting.<br><br>Here's a tentative agenda (to be ordered based on availability of Mark Radcliff)<br><br>Objective: Determine if a by-laws change is needed & plan for kick-off.<br><br>Some topics to review:<br><br>* Process & Logistics<br><br>* Name of committee (Alan was suggesting "elephant" as a follow on for "spider")<br><br>* Should be change the bylaws to be more process (less project) oriented? If so, how/when?<br><br>* Review the principles, make sure the text makes sense<br><br>* Identify "elephants" in the process that we need to address/avoid/postpone<br><br>* Timeline for implementation<br><br>* Identify technical gaps (beyond RefStack)<br><br>* RefStack review & planning<br><br>* Discuss community involvement process<br><br><br>From: Joshua McKenty [mailto:joshua@<a href="http://pistoncloud.com">pistoncloud.com</a>]<br>Sent: Monday, November 11, 2013 12:59 PM<br>To: Jeremy Stanley; Hirschfeld, Rob<br>Cc: <a href="mailto:foundation@lists.openstack.org">foundation@lists.openstack.org</a><br>Subject: Re: [OpenStack Foundation] OpenStack core and interoperability<br><br>Rob Hirschfeld and I are chairing the newly approved Interoperability Committee, and we have a kickoff meeting next week. I'm reasonably confident that we'll have a preliminary model for FITS certification by the time of the Icehouse Summit.<br><br>We're going to repurpose the existing FITS mailing list for this, so if you want to follow along, you should sign up there.<br><br>--<br><br>Joshua McKenty<br>Chief Technology Officer<br>Piston Cloud Computing, Inc.<br>+1 (650) 242-5683<br>+1 (650) 283-6846<br><a href="http://www.pistoncloud.com">http://www.pistoncloud.com</a><br><br>"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."<br><br>On Nov 10, 2013, at 3:03 PM, Jeremy Stanley <<a href="mailto:fungi@yuggoth.org%3cmailto:fungi@yuggoth.org">fungi@yuggoth.org<mailto:fungi@yuggoth.org</a>>> wrote:<br><br><br>On 2013-10-31 18:06:03 -0500 (-0500), Mark Collier wrote:<br>[...]<br><br>As of January 1st, 2012, your product must pass any Faithful<br>Implementation Test Suite (FITS) defined by the Technical<br>Committee that will be made available on <a href="http://www.openstack.org">http://www.openstack.org</a><br>/FITS , to verify that you are implementing a sufficiently<br>current and complete version of the software (and exposing<br>associated APIs) to ensure compatibility and interoperability.<br>[...]<br><br>"OpenStack FITS. Coming soon. The OpenStack Faithful Implementation<br>Test Suite will be available in early 2012."<br><br>I guess we're a little behind there. Is there any benefit to<br>revising that ETA or do we wait until there's a more solid timeline<br>established?<br>--<br>Jeremy Stanley<br><br>_______________________________________________<br>Foundation mailing list<br><a href="mailto:Foundation@lists.openstack.org%3cmailto:Foundation@lists.openstack.org">Foundation@lists.openstack.org<mailto:Foundation@lists.openstack.org</a>><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation">http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation</a><br><br>_______________________________________________<br>Foundation mailing list<br><a href="mailto:Foundation@lists.openstack.org">Foundation@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation">http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation</a><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>