#opendaylight-meeting: TWS

Meeting summary

1. 1. ACTION: TSC Chair will lead a discussion and proposal for how to work with unresponsive/struggling core projects (anipbu, 18:45:02)
   2. we need to tease out any differences between features and projects, make clear in slides (dfarrell07, 18:52:26)
   3. some core project features may not be considered "core" (bjohnson, 18:53:12)
   4. https://wiki.opendaylight.org/view/Release/Checkpoint/Proposal (anipbu, 18:57:00)
   5. 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 (dfarrell07, 19:01:17)
   6. offset 2 projects will not report milestones, only produce artifacts, need to make clear in slides (dfarrell07, 19:16:06)
   7. we need to highlight and socialize that its not such a drastic thing for a project to not enter in the core distribution (bjohnson, 19:20:22)
   8. 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 (bjohnson, 19:21:00)
   9. possible req for core: have public weekly meetings (dfarrell07, 19:24:16)
   10. 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) (dfarrell07, 19:33:39)

Action items

1. TSC Chair will lead a discussion and proposal for how to work with unresponsive/struggling core projects

People present (lines said)

1. bjohnson (8)
2. dfarrell07 (8)
3. odl_meetbot (5)
4. abhijitkumbhare (3)
5. anipbu (3)
6. lori (1)
7. CaseyODL (0)