#opendaylight-meeting: tsc

Meeting started by colindixon at 17:00:20 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:36)
    1. colindixon (colindixon, 17:00:42)
    2. mohnish anumala (mohnish__, 17:00:45)
    3. edwarnicke (edwarnicke, 17:00:55)
    4. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47211 the agenda (colindixon, 17:00:59)
    5. abhijitkumbhare (abhijitkumbhare, 17:01:04)
    6. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-06-16-17.01.html last week's meeting minutes (colindixon, 17:01:22)
    7. jamoluhrsen (jamoluhrsen, 17:01:22)
    8. gkaempfer (gkaempfer, 17:01:24)
    9. vishnoianil (vishnoianil, 17:02:08)
    10. ttkacik tony tkacik (ttkacik, 17:02:14)
    11. https://lists.opendaylight.org/pipermail/release/2016-June/006933.html thread on possible migration from AsciiDoc/Asciidoctor to ReStructuredText/Sphinx (colindixon, 17:02:21)
    12. Prem_ (for Chris Price) (Prem_, 17:02:36)
    13. https://lists.opendaylight.org/pipermail/odlparent-dev/2016-June/000398.html thread on trying to get stable features from odlparent (looking to carbon to have an actual stable distrubiton) (colindixon, 17:02:50)
    14. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:03:32)
    15. 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:03:33)
    16. ACTION: CaseyODL to add a TWS on ask/stack overflow (colindixon, 17:03:52)
    17. ACTION: CaseyODL to start a thread on how to better manage the list of whitelisted pages (colindixon, 17:03:52)
    18. ACTION: anipbu to follow up on removing the ancient org.eclipse dependencies in controller (and elsewhere?) (colindixon, 17:05:03)
    19. 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:10)
    20. ACTION: vishnoianil to schedule a meeting to discussion the project categorization (colindixon, 17:06:11)
    21. ACTION: phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (colindixon, 17:06:17)

  2. TSC maling list votes and discussions (colindixon, 17:07:59)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005377.html Addition questions in the Project Proposal Template (colindixon, 17:08:16)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-June/005428.html Fast and/or Phased Planning for the Carbon Release (colindixon, 17:08:30)
    3. https://lists.opendaylight.org/pipermail/tsc/2016-June/005407.html Asking the Board to Remove the Singularity Principle (colindixon, 17:08:40)
    4. https://lists.opendaylight.org/pipermail/tsc/2016-June/005420.html [VOTE] Ryan Vail as a committer on Packetcable (colindixon, 17:09:10)

  3. events (colindixon, 17:09:47)
    1. we have the ODL hackfest next week on WTh (6/29-6/30) (colindixon, 17:10:20)
    2. https://www.opendaylight.org/global-events events in the usual place (colindixon, 17:10:48)
    3. colindixon asks if we wnat to have a TSC meeting next week on 6/30 (colindixon, 17:11:07)
    4. colindixon says that his take is agendas have been light and and the key issues we would like to resolve, e.g., carbon planning, might be better resolved with in-person work than a TSC meeting (colindixon, 17:11:52)
    5. vishnoianil, edwarnicke, and abhijitkumbhare all say they wouldn't mind canceling it (colindixon, 17:12:13)
    6. AGREED: there will be no TSC meeting next week on 6/30/2016 (colindixon, 17:12:39)
    7. the OPNFV summit and ODL mini-summit in Berlin is just wrapping up (colindixon, 17:13:22)
    8. edwarnicke says that it was really good, he was mostly focused on fd.io and fast data stack, but there were lots of people with lots of diverse areas (colindixon, 17:14:02)
    9. upcoming evnets include LinuxCon Japan (7/13) and LinuxCon North America (8/22) (colindixon, 17:15:16)

  4. boron (colindixon, 17:16:34)
    1. https://git.opendaylight.org/gerrit/#/c/35505/ <--- Neutron Yang Model Revision has been merged. (anipbu, 17:16:47)
    2. https://git.opendaylight.org/gerrit/#/c/35892/ <--- OpenFlowPlugin Migration to Li Design Default has been merged. (anipbu, 17:16:54)
    3. https://wiki.opendaylight.org/view/Weather#NetVirt_VPNService_Migration <--- NetVirt/VPNService has scheduled a TWS session to discuss. (anipbu, 17:17:01)
    4. There are plans to upgrade ietf-inet-types@2010-09-24 and ietf-yang-types@2010-09-24 (RFC 6021) to ietf-inet-types-2013-07-15 and ietf-yang-types@2013-07-15 (RFC 6991) in the Boron release, with impact to lispflowmapping, sfc, topoprocessing, openflowjava, restconf, neutron, ovsdb, gbp, netvirt (anipbu, 17:17:18)
    5. https://wiki.opendaylight.org/view/Weather#Upgrade_ietf-.7Binet.2Cyang.7D-types_to_2013-07-15 <--- Weather item for upgrade of ietf-{inet,yang}-types (anipbu, 17:17:50)
    6. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=778533050 <--- Google Spreadsheet Tracking dependency and impact to ietf-{inet,yang}-types upgrade (anipbu, 17:17:55)
    7. The Boron Autorelease job is currently failing to build intent-listeners. The NIC team has fixed the issue with patch 40259 and we are awaiting the results of a new build. (anipbu, 17:18:29)
    8. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/160/org.opendaylight.nic$intent-listeners/ (anipbu, 17:18:34)
    9. For M4 Offset 2, we are hosting an IRC meeting on Wednesday June 29th at 10:00AM Pacific Time Zone for new projects to ask questions about their M4 requirements. (anipbu, 17:18:56)
    10. https://lists.opendaylight.org/pipermail/release/2016-June/006936.html <--- M4 IRC Working Session (anipbu, 17:19:01)

  5. stable/beryllium (colindixon, 17:20:18)
    1. Beryllium SR3 is scheduled for 7/28/2016 with a cutoff on 7/24/2016 11:59 UTC. (anipbu, 17:20:31)
    2. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-beryllium/198/testReport/ <--- Beryllium autorelease test failures in bgpcep and controller. (anipbu, 17:20:45)

  6. system integration and test (colindixon, 17:21:14)
    1. jamoluhrsen says nothing this week (colindixon, 17:21:21)

  7. infrastructure (colindixon, 17:21:26)
    1. https://lists.opendaylight.org/pipermail/release/2016-June/006937.html outage for this weekend to move the last things to the private cloud (colindixon, 17:22:09)
    2. When: Saturday, June 25, 2016 @ 08:00 - 17:00 PDT (15:00 - 00:00 UTC) (colindixon, 17:22:19)
    3. while gerrit will be up, jenkins will be offline, so jobs won't trigger (colindixon, 17:22:54)
    4. colindixon asks if we should block merges, tykeal and others note that the next job will pick it up, so it's low risk (colindixon, 17:24:33)
    5. also the fact that veriy jobs won't run, will likely gate things, so that it's not a real risk (colindixon, 17:25:01)
    6. tykeal says that we have a new APAC time zone joining as a release engineer, who we will likely see at events sometime soon (colindixon, 17:25:21)

  8. David Goldber as a committer on UNI manager (colindixon, 17:25:45)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005429.html (colindixon, 17:25:51)
    2. https://git.opendaylight.org/gerrit/#/q/owner:%22David+Goldberg%22+project:unimgr commits (colindixon, 17:26:04)
    3. https://lists.opendaylight.org/pipermail/unimgr-dev/2016-June/000148.html 4 +1 votes (colindixon, 17:26:19)
    4. that's unanimous +1s from all current committers (colindixon, 17:27:11)
    5. VOTE: Voted on "shall the TSC approve David Goldber as a comitter on the UNImgr project?" Results are, +1: 9 (colindixon, 17:29:16)
    6. AGREED: David Goldber is now a committer on UNImgr (colindixon, 17:30:30)
    7. mohnish__ notes that UNImgr is seemingly a PoC project and do we have a way to do that, should it be in ODL forge (colindixon, 17:31:06)
    8. people note that ODL forge doens't exist yet, and we've generally erred on the side of giving people projects if they want them (colindixon, 17:31:35)
    9. gkaempfer also notes that it's moving past being just a PoC in this case toward tigher integration with vCPE use cases (colindixon, 17:31:53)

  9. removing "draft" status from committer promotion process (colindixon, 17:34:46)
    1. https://wiki.opendaylight.org/view/TSC:Main#TSC_Procedures_and_Processes (colindixon, 17:34:58)
    2. https://wiki.opendaylight.org/view/TSC:Main#Committer_promotion_process_for_contributors_.28Draft.29 this is a draft at the moment (colindixon, 17:35:10)
    3. ACTION: colindixon to start a thread to remove the "draft" status from committer promotion process (colindixon, 17:35:21)
    4. vishnoianil and colindixon talked earlier about making sure that the community is aware that nominations are also a call for public comment and not just comment/votes from existing comments (colindixon, 17:38:04)
    5. edwarnicke says to be careful with tone, by saying it's a public comment period than asking for concerns (colindixon, 17:38:31)
    6. colindixon also notes our governance generally as a way of escalation from conversation within the community, to comitters/PTLs mediating it at the project level, to TSC mediating it when there are disputes within or across projects, to the board resolving things involving the TSC (colindixon, 17:43:31)
    7. we don't communincate this well, and it's not explicitly stated anywhere (colindixon, 17:43:49)
    8. ACTION: colindixon to start a therad on language and ways to communicate escalation processes for disputes (colindixon, 17:45:09)

  10. attendance of the developer design forum (colindixon, 17:45:21)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005419.html (colindixon, 17:45:54)
    2. phrobb said the intent was that anyone who is registered to attend the ODL summit, can also attend the design forum, and the commit was only required if you wanted to only attend the free design forum (colindixon, 17:47:10)
    3. in essence the goal was not to exclude people that actually wanted to participate, but to make sure we didn't get accidental registrations for what happened to be free (which happend in the past) (colindixon, 17:48:40)
    4. phrobb said: the intent is "have a gerrit id, get in straight away. Don't have one, then tell us why you'd like to attend." (colindixon, 17:49:24)
    5. ACTION: phrobb or colindixon to figure out how to communicate this better as the registration site stays up (colindixon, 17:49:40)
    6. colindixon notes that part of the problem is that this was surprising and happend without community involvment, establishing a clear policy for how registration is handled in the future with community involvement seems importnat (colindixon, 17:50:49)
    7. ACTION: phrobb to work on having a policy for how attendence to desing forums works going forward with community involvement (colindixon, 17:51:07)

  11. cookies (colindixon, 17:51:15)


Meeting ended at 17:51:18 UTC (full logs).

Action items

  1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  2. colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place
  3. CaseyODL to add a TWS on ask/stack overflow
  4. CaseyODL to start a thread on how to better manage the list of whitelisted pages
  5. anipbu to follow up on removing the ancient org.eclipse dependencies in controller (and elsewhere?)
  6. 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.
  7. vishnoianil to schedule a meeting to discussion the project categorization
  8. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  9. colindixon to start a thread to remove the "draft" status from committer promotion process
  10. colindixon to start a therad on language and ways to communicate escalation processes for disputes
  11. phrobb or colindixon to figure out how to communicate this better as the registration site stays up
  12. phrobb to work on having a policy for how attendence to desing forums works going forward with community involvement


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 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. anipbu
    1. anipbu to follow up on removing the ancient org.eclipse dependencies in controller (and elsewhere?)
  3. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    2. colindixon to clean up documentation for the process of project PTL election and post it on the TSC page in the normal place
    3. colindixon to start a thread to remove the "draft" status from committer promotion process
    4. colindixon to start a therad on language and ways to communicate escalation processes for disputes
    5. phrobb or colindixon to figure out how to communicate this better as the registration site stays up
  4. dfarrell07
    1. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election
  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 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. 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
    3. phrobb to work on having a policy for how attendence to desing forums works going forward with community involvement


People present (lines said)

  1. colindixon (85)
  2. anipbu (12)
  3. odl_meetbot (10)
  4. dfarrell07 (5)
  5. jamoluhrsen (3)
  6. abhijitkumbhare (3)
  7. mohnish__ (2)
  8. gkaempfer (2)
  9. edwarnicke (2)
  10. ttkacik (2)
  11. Prem_ (2)
  12. vishnoianil (2)


Generated by MeetBot 0.1.4.