20:11:27 <regXboi> #startmeeting
20:11:27 <odl_meetbot> Meeting started Thu Apr 10 20:11:27 2014 UTC.  The chair is regXboi. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:11:27 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
20:11:32 <regXboi> #chair alagalah
20:11:32 <odl_meetbot> Current chairs: alagalah regXboi
20:14:03 <mickey_spiegel> #here
20:14:27 <regXboi> #topic role call
20:14:38 <regXboi> #info regXboi (Ryan)
20:14:59 <mestery> #info mestery (Kyle)
20:15:06 <dvorkinista> #info dvorkin(...)
20:15:11 <regXboi> #link https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4PO9GTADM5ZZWKPF30D5WC98O-9VIB for future meetings
20:15:16 <alagalah> #info alagalah
20:15:37 <hemanthravi> https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4PO9GTADM5ZZWKPF30D5WC98O-9VIB
20:15:42 <dconde> https://meetings.webex.com/collabs/#/meetings/detail?uuid=M4PO9GTADM5ZZWKPF30D5WC98O-9VIB
20:16:45 <regXboi> #topic architectural overlap
20:17:02 <regXboi> #info mickey_spiegel asking about email sent to the list about architectural overlap
20:20:18 <alagalah> #info distinction from regXboi on data base vs a data store
20:20:46 <alagalah> #info the data store group needs to decide the structure
20:22:34 <alagalah> #info dvorkinista states its a series of trees (the data) and how its stored is an implementation detail decided by the data store group, but regXboi wants to have options on how this is implemented
20:24:14 <alagalah> lenrow: Canyou IRC your point so I can #info it please?
20:24:57 <alagalah> dconde: Please email me the video of our model discussion please
20:27:08 <regXboi> is it my phone or is the conference room really really muddy?
20:27:27 <alagalah> We have a laptop on a box blocking the speaker
20:27:30 <RobDolin> @regXboi - Audio or video from the conf room?
20:27:35 <regXboi> audio
20:28:44 <regXboi> #topic what release to aim for
20:28:45 <RobDolin> IIRC, OpenDaylight has five USB speakers that they used for Hackfests, we might try asking @Phil Robb for one for this meeting.
20:28:56 <alagalah> #info want to leverage MD SAL but waiting to see what they propose
20:29:08 <regXboi> #info do we want to aim for hyrdogen?
20:29:14 <mestery> Good idea RobDolin
20:29:23 <regXboi> #info er correction: helium
20:30:27 <RobDolin> #action RobDolin to reach-out to Phil to see if we can get a speaker on loan for this meeting
20:31:02 <regXboi> #link https://wiki.opendaylight.org/view/Project_Proposals:Dynamic_Resource_Reservation
20:31:16 <alagalah> Thanks I found it
20:31:39 <regXboi> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan
20:36:47 <regXboi> #agreed we will try to target helium
20:37:13 <alagalah> #topic Architecture
20:37:19 <regXboi> #agreed we will listen to the new MD-SAL proposal from Jan on Monday and see if it can meet our needs
20:38:42 <regXboi> #info proposal to schedule architecture either T, W, or F morning PT
20:39:00 <fabian> i'd appreciate us mornings, sitting here in Europe, Heidelberg
20:39:30 <fabian> s/us/US
20:40:42 <alagalah> #info Architecture meeting will be 11am Pacific Fridays
20:41:05 <regXboi> #agreed architecture 11 AM PT Friday
20:41:30 <regXboi> #topic Model Team
20:41:33 <alagalah> #topic Model team meeting
20:41:36 <mestery> How many sub teams are there? And is each one planning to have a meeting? Because this will clearly not scale.
20:41:50 <alagalah> mestery: 5
20:42:00 <RobDolin> #info Groups:
20:42:01 <mestery> So, 5 hours of meetings a week on top of all the ohter ones?
20:42:03 <RobDolin> #info 1: Architecture
20:42:07 <mestery> Is this a workable thing going forward?
20:42:20 <RobDolin> #info 5: Policy repo
20:42:20 <regXboi> #chair RobDolin
20:42:20 <odl_meetbot> Current chairs: RobDolin alagalah regXboi
20:42:20 <mestery> regXboi: ^^^ Your thoughts?
20:42:24 <RobDolin> #info: 8: Data store
20:42:32 <RobDolin> #info 9: Operational space
20:42:34 <regXboi> mestery: I'm not going to be on all of them
20:42:34 <s3wong> mestery: my guess is architecture and model will eventually be going away
20:42:36 <RobDolin> #info 10: Renderers
20:42:47 <alagalah> #info 1 arch, 2 model, 5 policy repo 8 data store 9 operational state 10 renderers
20:42:52 <tbachman> operational "state"?
20:42:56 <mestery> Just trying to see if we can contain the insanity around meeting explosion.
20:42:58 <RobDolin> #info 2: Model
20:43:06 <regXboi> oh it's too late for that !
20:43:16 <regXboi> that train left the station months ago
20:43:24 <mestery> regXboi: If we're spending time planning in meetings planning more meetings, you're right.
20:44:10 <alagalah> #info 2. model at 10am pac Friday
20:44:35 <RobDolin> #topic Policy Reposityr team meeting
20:44:36 <regXboi> #topic Policy Repo sub-group
20:44:47 <regXboi> heh - colliding scribes :)
20:44:51 <RobDolin> :)
20:48:21 <alagalah> #info scheduling this one for 9am Mondays
20:49:04 <alagalah> #topic 8 Data store meeting
20:49:26 <alagalah> #info regXboi is the temporary leader of this
20:50:30 <alagalah> #info 8am pacific Monday
20:50:39 <alagalah> #info IRC only for time being
20:50:42 * mestery likes IRC only, way to go regXboi
20:51:37 <alagalah> #info changed to 7am ... LOCKED ... IRC only
20:51:39 <regXboi> #agreed 7am pacific Monday
20:52:58 <alagalah> #topic Operation state meeting
20:53:14 <alagalah> #info 1:30pm IRC meeting Wednesdays
20:53:32 <alagalah> #topic Renderer meeting
20:55:37 <s3wong> #info regXboi requested that all the datastore team-members to attend next Monday's ODL TWS meeting
20:55:49 <regXboi> #info Data store will not meet 4/14 otherwise
21:02:12 <alagalah> #topic Subgroup inter-relations
21:02:36 <alagalah> #info dconde to publish the matrix of subgroup members and leads, leads will manage any overlap
21:04:21 <alagalah> #topic Committers
21:04:50 <alagalah> #info regXboi suggests that 2 committers need to +1 before we plus +2 code in
21:05:06 <alagalah> #info regXboi points out +1 is not cumulative
21:08:05 <regXboi> #endmeeting