17:42:57 <colindixon> #startmeeting tws
17:42:57 <odl_meetbot> Meeting started Mon Apr 11 17:42:57 2016 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:42:57 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:42:57 <odl_meetbot> The meeting name has been set to 'tws'
17:43:03 <colindixon> #topic openflowplugin migration
17:43:19 <colindixon> #info abhijitkumbhare says that they have input from most projects on the spreadsheet, still reaching out to a few
17:43:39 <colindixon> #action abhijitkumbhare will put down a loose plan about when/how to do the migration, current plan is OFP M3
17:43:40 <anipbu> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=251530127
17:43:43 <colindixon> #undo
17:43:43 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x25abd90>
17:43:51 <colindixon> #link https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=251530127 the tracking spreadsheet
17:44:07 <colindixon> #info colindixon also suggests downstream projects get it written down on their release plans so they know what they need to do and whent
17:44:13 <colindixon> #topic demos/tutorials at openstack in austin
17:44:32 <colindixon> #info CaseyODL and gzhao are looking for people to do demos, reach out to them if you're willling, they currently only have 1-2
17:44:45 <colindixon> #info they will also have videos going on in the background, if you have a demo video, let them know
17:44:51 <colindixon> #info live is still preferrred
17:44:55 <colindixon> #topic tutorials project
17:45:09 <colindixon> #info CaseyODL asks if renaming the coretutorials project would be a good idea if it's where we're going to house demos
17:45:36 <colindixon> #info colindixon says he doesn't thing the name is the problem, the problem is finding people to care for and maintain tutorials and demos, that's failed twice now: coretutorials and tookit
17:45:44 <colindixon> #info vishnoianil suggests using interns
17:46:06 <colindixon> #info colindixon suggests making sure the code is tested as best we can (testing tutorials is hard)
17:47:08 <colindixon> #info at the very least projects should need to run through the tutorial/demo manually at M5 of one of the RCs at the end of the release if we really want to have them work for each release
17:47:59 <colindixon> #info vishnoianil's idea is less about using interns, but instead having some crowdsourced, hackathon where we have 5-6 people try to write a tutorial demo in a given topic area, pick the best one and give them some kind of "award" as well as hosting that repo
17:48:21 <colindixon> #info vishnoianil these could then be not really maintained because they could exit for only a release at a time, or one of the hack-a-thons would upgrade an old one to the new releas
17:48:44 <colindixon> #info CaseyODL says that we will have 3 interns working on some of this soon (different from vishnoianil's suggestion)
17:49:59 <colindixon> #info colindixon thinks maybe having them live in people's projects in a way so that if they break, they break that project, and that project has to fix it and it's encouraged to actually maintain it
17:50:35 <colindixon> #info vishnoianil points out that's one kind of tutorial, which is very project specific, like showing how to use OpenFlow plugin to install a flow, meter, and group, while others are maybe spread over multiple projects
17:50:56 <colindixon> #info we don't have good ideas for the second kind that we're aware of
17:51:34 <colindixon> #info anipbu and CaseyODL both say (and colindixon and anipbu agree) that we really do need a centralized list of the tutorials and demos that are avialable even if they're not centralized in the code repositories
17:52:05 <colindixon> #info having a demo/tutorial template with system test showing how to test it would be really awesome to help people get started
17:54:40 <colindixon> #info we already have system tests that do some of these tutorials, e.g., we have system tests for vishnoianil's idea around doing flows, meters and groups
17:54:58 <gzhao> CaseyODL: and booth volunteers, I am going to send an email soon but will let you preview first.
17:55:09 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:End_to_End_Flows abhijitkumbhare points out that this is already written up on the wiki here
17:55:48 <vishnoianil> #link https://github.com/opendaylight/ovsdb/tree/master/resources/commons
17:55:59 <colindixon> #info vishnoianil says that OVSDB also has a postman collection of rest calls to exercise various features (see the line above this one)
17:56:56 <colindixon> #info abhijitkumbhare points out that the end-to-end flows might need updating of the wiki page, colindixon notes it woudl be really cool if the tutorial instructions pulled the code snippets, e.g., REST URLs and bodies, directly from the system test so they they were always up-to-date
17:57:19 <colindixon> #info that's really hard with the wiki, maybe easier with AsciiDoc or readthedocs
17:57:36 <colindixon> #info it can also be made moot if we updated correctly every time for every release, but that's been hard in the past
17:58:26 <colindixon> #topic next week's TWS
17:58:40 <colindixon> #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas
17:58:53 <colindixon> #info zxiiro could cover setting up maven sites and javadoc
17:59:09 <colindixon> #info we could talk about inventory vs. topology vs. new topology
17:59:37 <colindixon> #Info we could talk about fast release and/or phased release in anticipation of Carbon
17:59:57 <colindixon> #Info colindixon thinks that phased == semantic versioning and would be part of that, but it woudl be a really good topic
18:00:34 <colindixon> #link https://www.youtube.com/watch?v=TEC31OUG9HA skitt's talk from the DDF on semantic versioning
18:01:23 <colindixon> #endmeeting