[OpenStack-DefCore] Reminder: DefCore Scale.10 Tomorrow (Wed) @ 9 PT
Egle Sigler
ushnishtha at hotmail.com
Wed Apr 1 16:09:41 UTC 2015
Hi Everyone,
Today's meeting is call-in only and on etherpad, no screen sharing.
Dial this number:
+1.860.970.0010
Conference ID:
933-636-202
https://etherpad.openstack.org/p/DefCoreScale.10
-Egle
Date: Tue, 31 Mar 2015 11:15:49 -0700
From: rob at zehicle.com
To: defcore-committee at lists.openstack.org
Subject: Re: [OpenStack-DefCore] Reminder: DefCore Scale.10 Tomorrow (Wed) @ 9 PT
sorry, forgot the call in details:
# Call in Information:
https://etherpad.openstack.org/p/DefCoreScale.10
Join the meeting: https://join.me/933-636-202
On a computer, use any browser with Flash. Nothing to download.
On a phone or tablet, launch the join.me app and enter meeting code:
933-636-202
Join the audio conference:
Dial a phone number and enter access code, or connect via internet.
By phone:
United States - Camden, DE +1.302.202.5900
United States - Detroit, MI +1.734.746.0035
United States - Hartford, CT +1.860.970.0010
United States - Los Angeles, CA +1.213.226.1066
United States - New York, NY +1.646.307.1990
United States - San Francisco, CA +1.415.655.0381
United States - Saugus, MA +1.781.666.2350
United States - Tampa, FL +1.813.769.0500
Access Code 933-636-202#
On 03/31/2015 11:13 AM, Rob Hirschfeld
wrote:
https://etherpad.openstack.org/p/DefCoreScale.10
# DefCore Scale.10
2015, April 1 @ 9am PT
Previous: https://etherpad.openstack.org/p/DefCoreScale.9
Following: https://etherpad.openstack.org/p/DefCoreScale.11
# Call in Information: TBD
# Summary: TBD
# Agenda
* Review and Prepare 2015.next for April Board Meeting
* Identity test (under development, to be completed by Friday)
https://review.openstack.org/#/c/166327/
* Plan for moving additional items into OpenStack/DefCore repo
* DefCore & TC Interlock
* Discuss UUID vs Test Names as ID
* Initial discussion about API additions?
*
http://lists.openstack.org/pipermail/openstack-dev/2015-March/059765.html
* "What I'm suggesting is that Defcore should not just specify
which API features need to be supported, but also specify that
nonstandard API features must not be added to the APIs its
covering." --Jeremy Stanley
* What to do about overlapping capabilities (see below)
# Roll Call
_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
--
Rob
____________________________
Rob Hirschfeld, 512-773-7522
I am in CENTRAL (-6) time
http://robhirschfeld.com
twitter: @zehicle, github: cloudedge & ravolt
_______________________________________________
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/20150401/e55a86f3/attachment.html>
More information about the Defcore-committee
mailing list