#opendaylight-meeting: tsc

Meeting started by vishnoianil at 17:01:25 UTC (full logs).

Meeting summary

    1. mohnish anumala (mohnish__, 17:01:47)
    2. vishnoianil (vishnoianil, 17:01:53)
    3. edwarnicke (edwarnicke, 17:01:55)
    4. gkaempfer (gkaempfer, 17:01:56)
    5. abhijitkumbhare (abhijitkumbhare, 17:02:00)
    6. Daniel Farrell (dfarrell07, 17:02:31)
    7. colindixon (colindixon, 17:02:58)
    8. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-06-09-17.03.html last week's meeting minutes (colindixon, 17:02:59)
    9. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47102#Agenda the agenda in it's usual place (colindixon, 17:03:05)
    10. Chris Price (ChrisPriceAB, 17:03:17)
    11. Tony Tkacik (ttkacik, 17:03:27)
    12. ACTION: phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (colindixon, 17:04:05)
    13. ACTION: phrobb and/or colindixon to start the mail thread to discuss fast and phased approach and carbon release planning (colindixon, 17:05:06)
    14. 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 (that is to figure out what projects might be related to what you want to do) (colindixon, 17:06:13)
    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 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. (colindixon, 17:06:38)
    16. ACTION: vishnoianil to schedule a meeting to discussion the project categorization (colindixon, 17:06:58)
    17. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:07:03)
    18. 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 (colindixon, 17:07:08)
    19. rovarga for jmedved (rovarga, 17:07:57)
    20. ACTION: colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place (colindixon, 17:08:04)

  2. TSC mailing list votes and discussions (colindixon, 17:09:34)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005396.html Giuseppe Petralia as NetIDE committer (colindixon, 17:09:46)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-June/005394.html Danian Shi and Yaozi Yang as committers on FaaS (colindixon, 17:10:02)
    3. https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html Additional questions in the Project Proposal Template (colindixon, 17:10:27)

  3. events (colindixon, 17:10:53)
    1. https://www.opendaylight.org/global-events (colindixon, 17:11:01)
    2. OPNFV summit in Berlin next week with an OpenDaylight mini summit (colindixon, 17:11:22)
    3. hackfest two weeks from now in San Jose (colindixon, 17:11:46)
    4. preliminary acceptances should have been sent out for the OpenDaylight summit, please register if you got one, some more may be coming (colindixon, 17:12:30)
    5. CaseyODL asks for anyone who might want to do do a demo or presentation at the ODL booth at OPNFV summit, please contact him TODAY (colindixon, 17:13:28)
    6. CaseyODL would also like for volunteers to man the booth if you're around (colindixon, 17:13:43)

  4. boron (colindixon, 17:14:03)
    1. We have merged the removal of YangParserImpl class (old YANG parser) in ODL projects (MD-SAL, etc) (anipbu, 17:14:15)
    2. https://lists.opendaylight.org/pipermail/release/2016-June/006840.html <--- Status email regarding removal of YangParserImpl (anipbu, 17:14:17)
    3. The patch series for Neutron Yang Model Revision will be merged soon in one week or two after blocker bugs are resolved. (anipbu, 17:14:31)
    4. https://lists.opendaylight.org/pipermail/release/2016-June/006744.html <--- Status email regarding Neutron Yang Model Revision (anipbu, 17:14:36)
    5. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=1458306352 <--- Google Spreadsheet tracking impacted projects (anipbu, 17:14:41)
    6. The OpenFlowPlugin project will be changing the default design on the master branch from the old –he design to the new –li design on Tuesday. (anipbu, 17:15:00)
    7. https://lists.opendaylight.org/pipermail/release/2016-June/006858.html <--- Status email regarding OpenFlowPlugin Li Design (anipbu, 17:15:05)
    8. odlparent team upgraded netty to 4.0.37 to resolve possible security issues that can lead to a DOS. (anipbu, 17:15:22)
    9. http://netty.io/news/2016/06/07/4-0-37-Final.html <--- security bug-fix filled as CVE-2016-4970 (anipbu, 17:15:26)
    10. https://git.opendaylight.org/gerrit/#/c/39978/ <--- Patch upgrading Netty (anipbu, 17:15:30)
    11. Boron M4 Offset 1 are due today 6/16/2016. Projects should take a moment to send their status. (anipbu, 17:15:45)
    12. https://lists.opendaylight.org/pipermail/release/2016-June/006855.html <--- Status Email Template (anipbu, 17:15:51)
    13. The Boron Autorelease job was failing to build vtnmanager-vsemprovider. The VTN team has fixed the issue with patch 40319 and we are awaiting the results of a new build. (anipbu, 17:16:13)
    14. https://git.opendaylight.org/gerrit/#/c/40319/ <--- Patch fixing autorelease (anipbu, 17:16:18)
    15. Atrium and Eman are still not in autorelease. Reminder that projects should build successfully in autorelease by M4. (anipbu, 17:16:30)
    16. Reminder that M5 is coming up and that is the suggested “line in the sand” for Boron Stable Distribution. (anipbu, 17:16:45)
    17. autorelease submodule timeout during cloning bumped to 60 minutes due to slow network (zxiiro, 17:17:21)
    18. we're expecting this to go away when jenkins and nexus move to the private cloud (colindixon, 17:19:01)
    19. rovarga says that Nexus has been causing merge failures, recently, presumably for the same reasons (colindixon, 17:19:59)
    20. colindixon asks if we can move production jenkins sooner than 6/25 (currently scheduled), but tykeal says no because we'd need to move 2.5 TB of information, which is hard (colindixon, 17:21:09)

  5. stable/beryllium (colindixon, 17:21:26)
    1. nothing this week (colindixon, 17:21:31)

  6. system integration and test (colindixon, 17:21:47)
    1. it seems pretty unlikely at this point it seems unlikely that there will be a stable feature in Boron because it needs to be done by 6/30 (offset 0 M5) (colindixon, 17:23:12)
    2. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-05-12-17.00.html (anipbu, 17:23:30)
    3. colindixon asks why that's happening, jamoluhrsen comments that it's because we don't have stable features, colindixon asks why that's true (colindixon, 17:23:58)
    4. jamoluhrsen says nobody's made the effort to become stable yet, dfarrell07 says he feels like we just need one project to pioneeer it (colindixon, 17:24:59)
    5. vina_ermagan says that she feels like lispflowmapping would be there save dependencies (colindixon, 17:25:24)
    6. rovarga says it pretty much has to be odlparent (colindixon, 17:25:31)
    7. ACTION: colindixon to reach out to skitt about making odlparent stable (colindixon, 17:25:48)
    8. vrpolak_ says that other things blocking are peformance and stablity tests for config subsystem as a well as experimental features in restconf (colindixon, 17:26:28)

  7. autorelease stability (colindixon, 17:27:37)
    1. we expect boron and beryllium will be fixed, we'll find out sometime tomorrow (colindixon, 17:27:59)

  8. infrastructure (colindixon, 17:28:13)
    1. we made modifications to timeouts for gerrit with autorelease to fix intermittent faliures (colindixon, 17:28:35)
    2. no major system-level changes, yet (colindixon, 17:28:47)
    3. we're now working to make sure the private cloud sandbox works right to make sure things go smoothly when we move jenkins into the private cloud on 6/25 (colindixon, 17:29:30)
    4. tykeal says that they're working on making the public cloud available for bursting as well (colindixon, 17:30:03)
    5. CaseyODL says they're looking at maybe moving toward something on stackoverflow instead of our own ask.opendaylight.org, so bring up questions if you have them (colindixon, 17:30:54)

  9. user groups (colindixon, 17:31:04)
    1. if you run a user group, CaseyODL should have reached out to you about moving to some new kind of meetup system (colindixon, 17:31:32)
    2. w.r.t. stack overflow/ask.odl, the key new feature we seem to be seeking is basically e-mail to bulletin board portal (colindixon, 17:32:25)
    3. ACTION: CaseyODL to add a TWS on ask/stack overflow (colindixon, 17:32:40)

  10. OpenDaylight wiki indexing (colindixon, 17:33:02)
    1. abhijitkumbhare asks how we can make more of the wiki searchable via search engines (colindixon, 17:33:18)
    2. CaseyODL says they can enable specific pages manually if you would like, for now all links from the main page and the project lists should be searchable now (colindixon, 17:33:56)
    3. colindixon asks if there's a way we can manage the robot.txt more easily, e.g., as a file in a git repo somewhere that we could modify easily (colindixon, 17:36:01)
    4. rovarga asks if there is some what to make that a tag in the wiki itself, colindixon says that we haven't found a way to make it a whitelist instead a blacklist tag (colindixon, 17:38:23)
    5. ACTION: CaseyODL to start a thread on how to better manage the list of whitelisted pages (colindixon, 17:38:41)

  11. project lifecycle states (colindixon, 17:40:45)
    1. https://www.opendaylight.org/project-lifecycle-releases vishnoianil asks if offest 0, 1 and 2 projects can all be core (colindixon, 17:41:11)
    2. https://www.opendaylight.org/tsc-policy (vishnoianil, 17:41:45)
    3. colindixon says that offsets technically can't impact the lifecycle state since offsets aren't mentioned in the lifecycle states, but as edwarnicke points out to be central to OpenDaylight, it's more likely that you'll be offset 0 than others (colindixon, 17:42:22)
    4. https://www.opendaylight.org/tsc-policy vishnoianil also asks how we plan do deal the signularity clause (colindixon, 17:43:15)
    5. rovarga says it will be dealt with on projects moving to core, edwarnicke instead suggests that the singularity clause is harmful (colindixon, 17:43:46)
    6. ACTION: edwarnicke and/or colindixon to add a discussion of the singularity clause as a TSC mailing list thread or future topic (colindixon, 17:44:30)
    7. http://www.merriam-webster.com/dictionary/singularity colindixon also notes that the definition of singularity doesn't really match the meaning we want (colindixon, 17:49:14)

  12. TSC elections progress (colindixon, 17:49:52)
    1. http://www.oed.com/view/Entry/180179?redirectedFrom=singularity#eid <- a dictionary that actually believes words mean things ;) (edwarnicke, 17:50:20)
    2. phrobb and dfarrell07 met to discuss how we can run the condorcet elections we'd like to run (colindixon, 17:51:40)
    3. we're exploring tooling, but right now we've realized that web-based ones don't provie what we need (colindixon, 17:52:19)
    4. implementing the framework should be pretty easy with libraries for voting (colindixon, 17:52:49)
    5. we need a user-guide for voting, rather than our current developer guide (colindixon, 17:53:00)
    6. we also need to figure out the settings of the knobs in our framework, e.g., the represented groups and their sizes (colindixon, 17:53:33)

  13. cookies (colindixon, 17:54:43)


Meeting ended at 17:54:47 UTC (full logs).

Action items

  1. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  2. phrobb and/or colindixon to start the mail thread to discuss fast and phased approach and carbon release planning
  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 (that is to figure out what projects might be related to what you want to do)
  4. 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 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.
  5. vishnoianil to schedule a meeting to discussion the project categorization
  6. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  7. 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
  8. colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place
  9. colindixon to reach out to skitt about making odlparent stable
  10. CaseyODL to add a TWS on ask/stack overflow
  11. CaseyODL to start a thread on how to better manage the list of whitelisted pages
  12. edwarnicke and/or colindixon to add a discussion of the singularity clause as a TSC mailing list thread or future topic


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 (that is to figure out what projects might be related to what you want to do)
    2. 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 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.
  2. colindixon
    1. phrobb and/or colindixon to start the mail thread to discuss fast and phased approach and carbon release planning
    2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    3. 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
    4. colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place
    5. colindixon to reach out to skitt about making odlparent stable
    6. edwarnicke and/or colindixon to add a discussion of the singularity clause as a TSC mailing list thread or future topic
  3. dfarrell07
    1. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  4. edwarnicke
    1. edwarnicke and/or colindixon to add a discussion of the singularity clause as a TSC mailing list thread or future topic
  5. vishnoianil
    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 (that is to figure out what projects might be related to what you want to do)
    2. 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 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. vishnoianil to schedule a meeting to discussion the project categorization
  6. UNASSIGNED
    1. CaseyODL to add a TWS on ask/stack overflow
    2. CaseyODL to start a thread on how to better manage the list of whitelisted pages


People present (lines said)

  1. colindixon (74)
  2. anipbu (17)
  3. odl_meetbot (6)
  4. vishnoianil (6)
  5. rovarga (3)
  6. edwarnicke (3)
  7. ChrisPriceAB (2)
  8. mohnish__ (1)
  9. gkaempfer (1)
  10. tykeal (1)
  11. zxiiro (1)
  12. dfarrell07 (1)
  13. ttkacik (1)
  14. abhijitkumbhare (1)
  15. jamoluhrsen (1)


Generated by MeetBot 0.1.4.