#opendaylight-meeting: tsc

Meeting started by vishnoianil at 17:03:14 UTC (full logs).

Meeting summary

    1. Daniel Farrell (dfarrell07, 17:03:23)
    2. vishnoianil (vishnoianil, 17:03:23)
    3. edwarnicke (edwarnicke, 17:03:25)
    4. mohnish anumala (mohnish__, 17:03:26)
    5. abhijitkumbhare (abhijitkumbhare, 17:03:29)
    6. ttkacik (ttkacik, 17:04:37)
    7. Chris Price (ChrisPriceAB, 17:04:54)
    8. rovarga for jmedved (rovarga, 17:05:22)
    9. gkaempfer (gkaempfer, 17:05:50)

  2. agenda (vishnoianil, 17:06:09)
    1. https://wiki.opendaylight.org/view/TSC:Main (vishnoianil, 17:06:11)
    2. vishnoianil to talk about the additional questions in project creation template (vishnoianil, 17:07:36)

  3. additional questions in project creation template (vishnoianil, 17:08:05)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005361.html (abhijitkumbhare, 17:09:33)
    2. rgoulding proxying for Colin Dixon (rgoulding, 17:09:51)
    3. dfarrell07 thinks adding the questions to clarify overlap in creation template is good, thinks vishnoianil's suggested questions are broadly good, suggests adding "we don't reject projects for overlap" reassurance (dfarrell07, 17:10:28)
    4. edwarnicke, dfarrell07, vishnoianil and others don't think overlap would prevent project approval, vishnoianil clarifies that these questions are to document overlap, make that more clear, basically help describe the project (dfarrell07, 17:13:39)
    5. phrobb points suggests this may be more relevant to a release plan, overlap of projects in a release (conflicting ports and such), maybe not as much relevant to project creation (dfarrell07, 17:14:55)
    6. abhijitkumbhare points out that this could also help projects decide if they want to work with existing projects, at least have them look at that as an option, edwarnicke, dfarrell07, phrobb and others agree (dfarrell07, 17:15:45)
    7. edwarnicke points out that questions like ports, as phrobb pointed out, would be good to ID during releases (disjoint from this TODO I think) (dfarrell07, 17:16:37)
    8. timeboxing this, moving to mailing list (dfarrell07, 17:20:35)
    9. ACTION: vishnoianil to bring these points to mailing list, drive discussion there (dfarrell07, 17:21:29)
    10. ACTION: phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (vishnoianil, 17:23:21)
    11. daniel and phil has a meeting schedule tomorrow to start discussion on it (vishnoianil, 17:23:44)
    12. phrobb and dfarrell07 have meeting for TSC elections planning tomorrow, dfarrell07 has started on simple, user-facing version of election docs, dfarrell07 has a bit of tooling code POC (dfarrell07, 17:24:48)
    13. ACTION: phrobb to start the mail thread to discuss fast and phased approach and carbon release planning (vishnoianil, 17:25:11)
    14. ACTION: vishnoianil to add short versions of those questions here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Instructions_for_Submitting_Creation_Review and/or the template here: https://wiki.opendaylight.org/view/Project_Proposals:ABC_Plugin (vishnoianil, 17:25:25)
    15. ACTION: vishnoianil, phrobb and abhijitkumbhare Need to think of better approach on how projects can be categorize in a better way, so that it can be (vishnoianil, 17:25:37)
    16. ACTION: (2/2) helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope. This will be useful in broadly categorizing the projects, that can be used as a reference for next TSC elections. (dfarrell07, 17:26:14)
    17. ACTION: vishnoianil to schedule a meeting to discussion the project categorization (vishnoianil, 17:26:25)
    18. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=1529202298 (anipbu, 17:27:06)
    19. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (vishnoianil, 17:27:13)
    20. ACTION: colindixon to send e-mail about possibly moving our documentation toolchain to ReStructured Text => Sphinx => Read The Docs, as opposed to using AsciiDoc => Asciidoctor, which has caused us some pain (vishnoianil, 17:27:25)

  4. Events (Phil) (vishnoianil, 17:28:29)
    1. https://www.opendaylight.org/global-events (vishnoianil, 17:28:38)
    2. https://www.opendaylight.org/events/opendaylight-june-hackfest-2016 <--- Hackfest (anipbu, 17:29:53)
    3. Prem__ will stand in for ChrisPriceAB for the remainder of the call. (ChrisPriceAB, 17:29:55)
    4. ODL Summit CFP acceptance notification will be start from next week (vishnoianil, 17:31:18)

  5. Boron (An/Thanh) (vishnoianil, 17:31:50)
    1. distribution-karaf which provides the karaf distribution for ODL releases will be changed to inherit from karaf-parent. Possible breakages limited to CSIT tests and downstream usage of .zip files. (anipbu, 17:32:15)
    2. https://wiki.opendaylight.org/view/Weather#distribution-karaf_to_inherit_from_karaf-parent <--- Weather item for distribution-karaf (anipbu, 17:32:19)
    3. The VPNService project will migrate some code out to NetVirt and Genius. Because NetVirt and VPNService have some overlap in functionality we will adopt the VPNService code as the new NetVirt re-architecture. (anipbu, 17:33:07)
    4. We are in the progress of planning a TWS Session to discuss the NetVirt/VPNService Migration in more details. (anipbu, 17:33:11)
    5. https://wiki.opendaylight.org/view/CrossProject:NetVirt_VPNService_Migration <--- Wiki page for NetVirt VPNService Migration (anipbu, 17:33:16)
    6. https://wiki.opendaylight.org/view/CrossProject:NetVirt_VPNService_Migration <--- Wiki page for NetVirt VPNService Migration (anipbu, 17:33:22)
    7. Boron Autorelease is building successfully (job #147). Many thanks to Vratko Polak, Releng, and various projects for the effort. (anipbu, 17:34:17)
    8. Atrium and didm are still removed from boron autorelease and eman and vbd have not yet been added to boron autorelease. (anipbu, 17:34:20)
    9. There are test failures in boron autorelease job related to bgpcep, mdsal, netconf, openflowjava, openflowplugin. (anipbu, 17:34:49)
    10. https://jenkins.opendaylight.org/autorelease/job/autorelease-release-boron/147/testReport/ <--- Boron Autorelease Test Failures (anipbu, 17:35:01)
    11. Thanh has updated autorelease such that every autorelease nightly build will become a Release Candidate build. (anipbu, 17:35:28)
    12. https://lists.opendaylight.org/pipermail/release/2016-June/006771.html <--- Email thread discussion the autorelease job changes (anipbu, 17:35:30)

  6. Stable/Beryllium (An/Thanh) (vishnoianil, 17:39:17)
  7. System Integration and Testing (Jamo) (vishnoianil, 17:39:32)
  8. Infrastructure (Andrew/Thanh) (vishnoianil, 17:40:17)
    1. testing on sandbox and resolving the issues (vishnoianil, 17:40:36)
    2. final migration of release engineering migration on June 25 (vishnoianil, 17:40:58)

  9. Sai MarapaReddy as committer on L2Switch project (vishnoianil, 17:42:18)
    1. https://lists.opendaylight.org/pipermail/l2switch-dev/2016-May/001191.html (vishnoianil, 17:42:25)
    2. https://git.opendaylight.org/gerrit/#/q/owner:%22Sai+MarapaReddy+%253Csai.marapareddy%2540gmail.com%253E%22+status:merged+project:l2switch (vishnoianil, 17:42:37)
    3. VOTE: Voted on "shall the TSC approve Sai MarapaReddy as a committer on l2switch?" Results are, +1: 9 (vishnoianil, 17:44:17)
    4. AGREED: Sai MarapaReddy in now a committer on l2switch (vishnoianil, 17:44:25)

  10. Subhash Sing as a committer on DIDM project (vishnoianil, 17:45:04)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005359.html (vishnoianil, 17:45:11)
    2. https://lists.opendaylight.org/pipermail/didm-dev/2016-June/000412.html (vishnoianil, 17:45:25)
    3. https://git.opendaylight.org/gerrit/#/q/project:didm+owner:%22subhash+kumar+singh+%253Csubh.singh007%2540gmail.com%253E%22 (vishnoianil, 17:45:36)
    4. https://git.opendaylight.org/gerrit/#/q/project:didm+reviewer:%22subhash+kumar+singh+%253Csubh.singh007%2540gmail.com%253E%22 (vishnoianil, 17:45:45)
    5. https://wiki.opendaylight.org/view/DIDM:Main (hideyuki, 17:50:42)
    6. concerns about only having 1/4 votes, about PTL not being committer, tabled and taking to list (dfarrell07, 17:52:40)

  11. Donald Hunter as a committer on Unimgr project (vishnoianil, 17:54:08)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005358.html (vishnoianil, 17:54:14)
    2. https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000148.html (vishnoianil, 17:54:20)
    3. https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000150.html (vishnoianil, 17:54:28)
    4. https://git.opendaylight.org/gerrit/#/q/owner:%22Donald+Hunter%22+project:unimgr (vishnoianil, 17:54:36)
    5. VOTE: Voted on "shall the TSC approve Donald Hunter as a committer on unimgr?" Results are, +1: 10 (vishnoianil, 17:55:25)
    6. AGREED: Donald Hunte in now a committer on unimgr (vishnoianil, 17:55:27)

  12. David Goldberg as a committer on Unimgr project (vishnoianil, 17:57:05)
    1. ACTION: phrobb add documentation for the process of project PTL election (vishnoianil, 17:59:23)

  13. Bartosz Michalik as a committer on Unimgr project (vishnoianil, 17:59:41)
    1. https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000148.html (vishnoianil, 18:00:25)
    2. "The project lead is a Committer selected by vote from the Committers in the project." <- the relevant line in governance docs about these PTL as committer questions. I think it implies "committer to same project", but it doesn't say that explicitly. (dfarrell07, 18:00:34)
    3. https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000150.html (vishnoianil, 18:00:35)
    4. https://www.opendaylight.org/tsc-charter PTL as committer docs, see bottom (dfarrell07, 18:00:57)
    5. this committer nominee doesn't have public Gerrits, need to reach out and ask for more contribution history (dfarrell07, 18:02:31)
    6. ACTION: vishnoianil notify Bartosz and David about the tsc comments (vishnoianil, 18:02:38)

  14. Archive Reviews: (vishnoianil, 18:03:01)
    1. https://wiki.opendaylight.org/view/Archive_Proposals/Affinity_Metadata_Service (vishnoianil, 18:03:09)
    2. https://git.opendaylight.org/gerrit/#/q/project:affinity+status:merged (vishnoianil, 18:03:20)
    3. https://lists.opendaylight.org/pipermail/affinity-dev/2016-May/000157.html (vishnoianil, 18:03:27)
    4. VOTE: Voted on "shall the TSC move the Affinity Metadata project to archived?" Results are, +1: 9 (vishnoianil, 18:04:00)
    5. AGREED: the Affinity Metadata project is now archived (vishnoianil, 18:04:20)

  15. Defense4Aall Archive Proposal (Posted 5/26/2016) (vishnoianil, 18:05:29)
    1. Defense4Aall Archive Proposal (Posted 5/26/2016) (vishnoianil, 18:05:39)
    2. https://git.opendaylight.org/gerrit/#/q/project:defense4all+status:merged (vishnoianil, 18:06:00)
    3. https://lists.opendaylight.org/pipermail/defense4all-dev/2016-May/000156.html (vishnoianil, 18:06:12)
    4. VOTE: Voted on "shall the TSC move the Defense4Aall project to archived?" Results are, +1: 9 (vishnoianil, 18:06:37)
    5. AGREED: the Defense4Aall project is now archived (vishnoianil, 18:06:45)

  16. cookies and beer (vishnoianil, 18:07:15)


Meeting ended at 18:07:20 UTC (full logs).

Action items

  1. vishnoianil to bring these points to mailing list, drive discussion there
  2. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  3. phrobb to start the mail thread to discuss fast and phased approach and carbon release planning
  4. vishnoianil to add short versions of those questions here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Instructions_for_Submitting_Creation_Review and/or the template here: https://wiki.opendaylight.org/view/Project_Proposals:ABC_Plugin
  5. vishnoianil, phrobb and abhijitkumbhare Need to think of better approach on how projects can be categorize in a better way, so that it can be
  6. (2/2) helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope. This will be useful in broadly categorizing the projects, that can be used as a reference for next TSC elections.
  7. vishnoianil to schedule a meeting to discussion the project categorization
  8. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  9. colindixon to send e-mail about possibly moving our documentation toolchain to ReStructured Text => Sphinx => Read The Docs, as opposed to using AsciiDoc => Asciidoctor, which has caused us some pain
  10. phrobb add documentation for the process of project PTL election
  11. vishnoianil notify Bartosz and David about the tsc comments


Action items, by person

  1. abhijitkumbhare
    1. vishnoianil, phrobb and abhijitkumbhare Need to think of better approach on how projects can be categorize in a better way, so that it can be
  2. dfarrell07
    1. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  3. vishnoianil
    1. vishnoianil to bring these points to mailing list, drive discussion there
    2. vishnoianil to add short versions of those questions here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Instructions_for_Submitting_Creation_Review and/or the template here: https://wiki.opendaylight.org/view/Project_Proposals:ABC_Plugin
    3. vishnoianil, phrobb and abhijitkumbhare Need to think of better approach on how projects can be categorize in a better way, so that it can be
    4. vishnoianil to schedule a meeting to discussion the project categorization
    5. vishnoianil notify Bartosz and David about the tsc comments
  4. UNASSIGNED
    1. phrobb to start the mail thread to discuss fast and phased approach and carbon release planning
    2. (2/2) helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope. This will be useful in broadly categorizing the projects, that can be used as a reference for next TSC elections.
    3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    4. colindixon to send e-mail about possibly moving our documentation toolchain to ReStructured Text => Sphinx => Read The Docs, as opposed to using AsciiDoc => Asciidoctor, which has caused us some pain
    5. phrobb add documentation for the process of project PTL election


People present (lines said)

  1. vishnoianil (74)
  2. dfarrell07 (20)
  3. odl_meetbot (20)
  4. anipbu (14)
  5. abhijitkumbhare (11)
  6. gkaempfer (8)
  7. mohnish__ (7)
  8. rovarga (6)
  9. rgoulding (6)
  10. edwarnicke (6)
  11. tykeal (5)
  12. Prem__ (4)
  13. ChrisPriceAB (4)
  14. ttkacik (2)
  15. LuisGomez (1)
  16. vina_ermagan (1)
  17. hideyuki (1)


Generated by MeetBot 0.1.4.