Open Stack

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.

I love the idea of having some TC folks involved, too. 
--

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 Nov 12, 2013, at 1:10 PM, Mark McLoughlin <markmc at redhat.com> wrote:

> Hi Rob,
> 
> This just came up in the TC meeting and I volunteered to pass on some
> feedback that I think we were all agreed on:
> 
>  * This discussion is inevitably going to get pretty technical as we 
>    start grappling with what will be required and what won't be. The 
>    TC feels it should have some involvement in that and would like to 
>    nominate some of its members to join.
> 
>  * It would be great to open these discussions as widely as possible. 
>    An all day, in-person meeting in SF, with 8 days warning is 
>    particularly difficult for interested people to join in with. The 
>    TC favours IRC for meetings, but conference calls could work too.
> 
> Also, it would be great to have a wiki page describing the goal of the
> committee, who's involved, what the mailing list is, tracking the
> outcomes of meetings, etc.
> 
> Thanks,
> Mark.
> 
> On Mon, 2013-11-11 at 16:53 -0600, Rob_Hirschfeld at Dell.com wrote:
>> Thanks Josh.
>> 
>> I thought to add the specific that we know so far.
>> 
>> 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
>> 
>> 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.
>> 
>> Here's a tentative agenda (to be ordered based on availability of Mark Radcliff)
>> 
>> Objective:  Determine if a by-laws change is needed & plan for kick-off.
>> 
>> Some topics to review:
>> 
>> *         Process & Logistics
>> 
>> *         Name of committee (Alan was suggesting "elephant" as a follow on for "spider")
>> 
>> *         Should be change the bylaws to be more process (less project) oriented?  If so, how/when?
>> 
>> *         Review the principles, make sure the text makes sense
>> 
>> *         Identify "elephants" in the process that we need to address/avoid/postpone
>> 
>> *         Timeline for implementation
>> 
>> *         Identify technical gaps (beyond RefStack)
>> 
>> *         RefStack review & planning
>> 
>> *         Discuss community involvement process
>> 
>> 
>> From: Joshua McKenty [mailto:joshua at pistoncloud.com]
>> Sent: Monday, November 11, 2013 12:59 PM
>> To: Jeremy Stanley; Hirschfeld, Rob
>> Cc: foundation at lists.openstack.org
>> Subject: Re: [OpenStack Foundation] OpenStack core and interoperability
>> 
>> 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.
>> 
>> We're going to repurpose the existing FITS mailing list for this, so if you want to follow along, you should sign up there.
>> 
>> --
>> 
>> 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 Nov 10, 2013, at 3:03 PM, Jeremy Stanley <fungi at yuggoth.org<mailto:fungi at yuggoth.org>> wrote:
>> 
>> 
>> On 2013-10-31 18:06:03 -0500 (-0500), Mark Collier wrote:
>> [...]
>> 
>> As of January 1st, 2012, your product must pass any Faithful
>> Implementation Test Suite (FITS) defined by the Technical
>> Committee that will be made available on http://www.openstack.org
>> /FITS , to verify that you are implementing a sufficiently
>> current and complete version of the software (and exposing
>> associated APIs) to ensure compatibility and interoperability.
>> [...]
>> 
>> "OpenStack FITS. Coming soon. The OpenStack Faithful Implementation
>> Test Suite will be available in early 2012."
>> 
>> I guess we're a little behind there. Is there any benefit to
>> revising that ETA or do we wait until there's a more solid timeline
>> established?
>> --
>> Jeremy Stanley
>> 
>> _______________________________________________
>> Foundation mailing list
>> Foundation at lists.openstack.org<mailto:Foundation at lists.openstack.org>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
>> 
>> _______________________________________________
>> Foundation mailing list
>> Foundation at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/foundation/attachments/20131112/c549353e/attachment.html>