14:00:41 <bh526r> #startmeeting Weekly Technical Discussion
14:00:41 <collabot`> Meeting started Thu Jan 17 14:00:41 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:41 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:41 <collabot`> The meeting name has been set to 'weekly_technical_discussion'
14:00:57 <bh526r> #topic Roll Call
14:01:18 <bh526r> #info Bin Hu
14:12:20 <bh526r> #info David McBride
14:17:00 <bh526r> #info Pierre Lynch
14:18:18 <bh526r> #info Bin sent meeting invite on Dec 20, 2018, and thought the invite would be on everyone's calendar
14:19:06 <bh526r> #info It turned out that the calendar got messed up, so only 3 persons showed up in the meeting
14:20:15 <bh526r> #info Bin will make sure that Bin will send/re-send the meeting invite on Monday or Tuesday before the meeting on Thursday so that the correct calendar invite will be on everyone's calendar
14:23:03 <bh526r> #info Al Morton
14:23:20 <bh526r> #info Jento
14:25:26 <bh526r> #info Jack Morgan
14:43:45 <bh526r> #topic ONS-NA Activity - Co-located Developer Event
14:44:14 <mbuil_> bh526r: did you move the strategy meeting to next week?
14:44:46 <bh526r> mbuil: looks like calendar messed up, and there are only 5 persons here
14:45:00 <bh526r> So we decide to move strategic discussion to next week
14:45:25 <bh526r> Now we are discussing some random topic, e.g. developer event co-located with ONS-NA in San Jose
14:46:59 <mbuil_> bh526r: ok :). As I told you, this meeting collides with an internal meeting I cannot miss :(
14:47:11 <bh526r> every week?
14:55:20 <mbuil_> bh526r: yes :(. I don't need to be active all the time, so I could check the chat and ask questions
15:00:29 <bh526r> Let me think about if there is a different time. The challenge is that other 6am weekdays are all set for other conference calls, and many other people may have conflicts if we change to a different time.
15:02:36 <bh526r> #info We discussed logistics, format, etc. and the target is not to overlap with ONAP developer event.
15:03:34 <bh526r> #info We will find more information, and get more input, and make a go / no-go decision asap. Because we need to take care of logistics if the decision is to go.
15:03:51 <bh526r> #topic Demo Topics for ONS-NA
15:04:39 <bh526r> #info Bin forwarded Brandon's email to tsc and tech-discuss mailing list. All are encouraged to think about and propose demo topics for ONS-NA
15:04:49 <bh526r> #info Past demo is here:
15:05:01 <bh526r> #link https://www.linuxfoundation.org/blog/2018/08/building-in-the-open-ons-europe-demos-highlight-networking-industry-collaboration/
15:05:21 <bh526r> #topic AOB
15:05:30 <bh526r> #info None. Meeting adjourned
15:05:36 <bh526r> #endmeeting