18:05:10 <dfarrell07> #startmeeting TWS
18:05:10 <odl_meetbot> Meeting started Mon Dec 18 18:05:10 2017 UTC.  The chair is dfarrell07. Information about MeetBot at http://ci.openstack.org/meetbot.html.
18:05:10 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:05:10 <odl_meetbot> The meeting name has been set to 'tws'
18:05:17 <dfarrell07> #chair CaseyODL
18:05:17 <odl_meetbot> Current chairs: CaseyODL dfarrell07
18:15:09 <lori> hi everyone, sorry for the long name and inability to be heard, it's the first time that I join from a Linux laptop, and it looks like I have to figure out some issues
18:43:14 <dfarrell07> #chair anipbu
18:43:14 <odl_meetbot> Current chairs: CaseyODL anipbu dfarrell07
18:45:02 <anipbu> #action TSC Chair will lead a discussion and proposal for how to work with unresponsive/struggling core projects
18:52:26 <dfarrell07> #info we need to tease out any differences between features and projects, make clear in slides
18:53:12 <bjohnson> #info some core project features may not be considered "core"
18:57:00 <anipbu> https://wiki.opendaylight.org/view/Release/Checkpoint/Proposal
18:57:57 <bjohnson> +1 to automation
19:01:17 <dfarrell07> #info vishnoianil_  points out existing offsets are about API layering, and if we put lots of projects with deps on each other in the same new offset that could be bad
19:02:31 <bjohnson> it could be bad, but it could just require more coordination between the projects
19:12:17 <bjohnson> Could we name the new offset 1 projects: [offset1.0, offset1.1, offset1.2]?
19:15:16 <abhijitkumbhare> bjohnson: vishnoianil_  LuisGomez : I think we should just use a different term to not confuse folks used to the current term: offset 0/1/2.
19:15:42 <bjohnson> abhijitkumbhare: agreed
19:16:06 <dfarrell07> #info offset 2 projects will not report milestones, only produce artifacts, need to make clear in slides
19:20:22 <bjohnson> #info we need to highlight and socialize that its not such a drastic thing for a project to not enter in the core distribution
19:21:00 <bjohnson> #info new projects should be able to decide if they want to try to be a core project or not, although its not such a big deal if they are non-core for their first release
19:24:16 <dfarrell07> #info possible req for core: have public weekly meetings
19:31:59 <bjohnson> +1 again to automating this process!!!
19:32:35 <abhijitkumbhare> I will need to go soon - have a lunch appointment with someone
19:33:39 <dfarrell07> #info dfarrell07 thinks all requirements should be automated, and if can't be automated should be a clear reporting process (send yaml patch: "I tried to contribute but couldn't get review, sent patch on X date, verify passing Y, pinged email/added reviewers by Q, no review by Z)
19:49:33 <abhijitkumbhare> anipbu: can you end meeting?
19:49:49 <anipbu> #endmeeting