#opendaylight-meeting: tsc

Meeting started by colindixon at 17:02:24 UTC (full logs).

Meeting summary

  1. roll call/agenda bashing (colindixon, 17:02:30)
    1. alagalah (Keith) proxy for Ed Warnicke (alagalah, 17:02:33)
    2. dmm (dmm, 17:02:43)
    3. jmedved (jmedved, 17:02:47)
    4. Youcef Laribi (Youcef, 17:02:50)
    5. Chris Price (ChrisPriceAB, 17:02:52)
    6. colindixon (colindixon, 17:02:56)
    7. Kent Watsen (kwatsen, 17:03:01)
    8. regXboi (regXboi, 17:03:02)
    9. https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda as usual (colindixon, 17:03:15)
    10. jmedved asks for sonar to be added to the agenda (colindixon, 17:03:41)
    11. colindixon asks if there are any Microsoft reps around to cover last week’s action item (tbachman, 17:04:13)
    12. colindixon says there are 3 action items held over from last week (tbachman, 17:04:30)
    13. phrobb changing meeting to 2 hrs (done) (tbachman, 17:04:41)
    14. zxiiro to remove OpFlex from Helium projects list (done) (tbachman, 17:04:56)
    15. ACTION: testing of Helium on windows still assigned to LuisGomez phrobb and IvanWood (tbachman, 17:05:29)
    16. LuisGomez says that he doesn’t think there’s a problem with running on windows (with karaf help from icbts) (tbachman, 17:06:20)
    17. Dave Lenrow (dlenrow, 17:06:34)
    18. LuisGomez says they’re working with LF to get more VMs for RackSpace for testing (tbachman, 17:06:58)
    19. jmedved points out Mac testing has also been requested (ChrisPriceAB, 17:07:21)

  2. Updates (tbachman, 17:07:50)
    1. phrobb says there’s an application that he needs folks to sign to be a committer member, which is an extra process step (tbachman, 17:09:06)
    2. phrobb says there’s also a nomination committee for this (tbachman, 17:09:33)
    3. phrobb says there are two folks who’ve already self-nominated (tbachman, 17:09:58)
    4. just to note, the nomination committee is just to formally bless the self-nominations in the normal process (colindixon, 17:10:38)
    5. voters have to fill out the committer member form in order to be able to vote for the Committer Board election. (tbachman, 17:11:25)
    6. phrobb says that ChrisPriceAB ran a very successful HackFest on Monday (tbachman, 17:11:44)
    7. phrobb says the ODL mini-summit was very well attended on Tuesday (tbachman, 17:11:56)
    8. phrobb says that pretty much all the booths are showing ODL in their booths (tbachman, 17:12:15)
    9. ~160 attendees at the ODL mini-summit in Dusseldorf (tbachman, 17:12:28)
    10. next event is mini-summit in Tokyo (tbachman, 17:12:41)
    11. http://www.opendaylight.org/news/events (colindixon, 17:13:51)

  3. Stable Helium (tbachman, 17:14:08)
    1. gzhao says that all the projects have been moved to stable/helium except defense4all (tbachman, 17:14:23)
    2. defense4all will do this after their holiday (tbachman, 17:14:34)
    3. auto-build scripts have been modified to give defense4all special treatment, and auto-release is back to daily builds (tbachman, 17:14:56)
    4. colindixon asks if integration has cut yet b/c of dependency on defense4all (tbachman, 17:15:46)
    5. LuisGomez says that there’s no dependency/blocker there (tbachman, 17:15:59)
    6. colindixon asks if the master branches have all been bumped on the projects to get ready for Li release (tbachman, 17:16:27)
    7. ACTION: gzhao to check on master branch version bumps (tbachman, 17:16:35)
    8. LuisGomez reports that the community needs to decide what to do with the legacy distributions (tbachman, 17:17:12)
    9. colindixon says he believes this falls under the purview of the TSC (tbachman, 17:17:25)
    10. rovarga says that we haven’t announced yet that we’re removing the build artifacts, so we should probably make an announcement to the mailing lists with some grace period before removing them. (tbachman, 17:18:31)

  4. Committer Nominations (tbachman, 17:19:28)
    1. https://lists.opendaylight.org/pipermail/bgpcep-dev/2014-October/000121.html email for committer nomination of milos fabian on bgpcep (tbachman, 17:20:13)
    2. http://spectrometer.opendaylight.org/?module=bgpcep&metric=loc (colindixon, 17:21:07)
    3. colindixon asks if there’s a different name that he commits under (tbachman, 17:21:10)
    4. http://spectrometer.opendaylight.org/?module=bgpcep&metric=loc spectrometer fro bgpcep (tbachman, 17:21:37)
    5. VOTE: Voted on "Shall the TSC approve the promotion of Milos Fabian on the bgpcep project?" Results are, +1: 8 (phrobb, 17:22:44)

  5. Sonar Issues (tbachman, 17:23:14)
    1. AGREED: Milos Fabian is promoted to Committer on the BGPCEP project (phrobb, 17:23:18)

  6. Sonar (ChrisPriceAB, 17:23:33)
    1. jmedved says that sonar is not properly picking up the stats on the controller project (tbachman, 17:23:40)
    2. jmedved says that escalation hasn’t resulted in this getting fixed yet (tbachman, 17:24:07)
    3. and requires some fixing (ChrisPriceAB, 17:24:11)
    4. colindixon says that we need someone who understands the controller project and LF IT (tykeal or zxiiro) to work this out (tbachman, 17:24:37)
    5. tykeal says we get timeout issues b/c the controller is so large, so we had to increased the timeout (tbachman, 17:25:59)
    6. tykeal says it might also be going over the heap size (tbachman, 17:26:06)
    7. tykeal the timeout and heap sizes have grown so much that he’s not even sure we can run it through sonar any more (tbachman, 17:26:24)
    8. jmedved indicates that adjusting the controller project may be the required approach to solving the issues (ChrisPriceAB, 17:27:21)
    9. ACTION: tykeal and ttkacik to work out what the next steps are to resolve this (tbachman, 17:28:10)
    10. colindixon indicates this should be discussed in the lists and on IRC and the results of those discussions brought back to the TSC for information or decision (ChrisPriceAB, 17:28:10)
    11. colindixon asks that jmedved, tykeal, and ttkacik all reach out to him if there are any problems (tbachman, 17:28:32)

  7. hydrogen/helium release distributions (tbachman, 17:28:42)
    1. ACTION: tykeal, zxiiro, and Tony T. to work off line on the Controller sonar issue (phrobb, 17:28:53)
    2. LuisGomez noted that we still have the hydrogen artifacts built as part of helium b/c no one has bothered to remove them (tbachman, 17:29:17)
    3. regXboi says that if we’re talking about removing the jobs from integration, that’s one thing, but if we’re removing the artifacts from nexus, that’s another thing (tbachman, 17:29:43)
    4. colindixon asks if we can stop building the projects as part of the integration project (tbachman, 17:30:15)
    5. regXboi says that we agreed last week that we’d end of support for Hydrogen (tbachman, 17:31:05)
    6. rovarga says we should announce that we’re going to remove the release artifacts and provide a grace period before they are removed (tbachman, 17:31:43)
    7. question as to how this will work — will things be discontinued at the project level, release level, both? (tbachman, 17:32:14)
    8. dbainbri asks why should we remove the code from the Helium release (tbachman, 17:36:46)
    9. LuisGomez says that these builds are still available in the hydrogen source tree, so it doesn’t make sense ot keep building it as part of the Helium release (tbachman, 17:37:12)
    10. VOTE: Voted on "Shall the TSC allow the integration project to remove the code in the integration repositories to build the Hydrogen distributions as part of the master branch? Nothing will be removed from Nexus?" Results are, +1: 6 (phrobb, 17:39:57)
    11. the Integration project is urged to send a "warning" email at least 30 days before the above referenced code is removed (phrobb, 17:40:48)
    12. ACTION: LuisGomez to coordinate with dbainbri and shague about also removing the docker and rpm images from Helium since they’re only related to Hydrogen (tbachman, 17:42:14)

  8. DELL is new platinum member (tbachman, 17:42:33)
    1. mohnish is the new representative from DELL (tbachman, 17:42:43)

  9. Lithium schedule and timeline + Debt Reduction (tbachman, 17:44:22)
    1. https://wiki.opendaylight.org/view/File:Debt-reduction-ideas.TSC-meeting.2014.10.09.pptx link to power point on debt-reduction ideas (tbachman, 17:44:42)
    2. https://lists.opendaylight.org/pipermail/tsc/2014-September/001777.html email describing Li timeline (tbachman, 17:45:45)
    3. regXboi asks if there are TSC members who have not already expressed their opinions on this (tbachman, 17:46:04)
    4. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Lessons_from_Hydrogen.2FHelium_that_Should_be_Applied wiki page archiving lessions that should be learned from Hydrogen/Helium (tbachman, 17:46:45)
    5. ChrisPriceAB states that as the TSC has not yet voted on the decision to begin the simultaneous release, we have room now to address our technical debt in handling releases. (ChrisPriceAB, 17:48:30)
    6. jmedved points out there are some projects that may not have any dependencies on such technical debt, and therefore should be able to proceed (tbachman, 17:48:37)
    7. regXboi says that we could work on the Lithium release plan, while paying down the debt can happen at the same time (tbachman, 17:50:57)
    8. colindixon asks if we should have someone email all of the projects to provide their various debt items, so that we can prioritize the list? (tbachman, 17:55:35)
    9. colindixon identifies that cross project debt is the key focus area for the TSC. project specific information should handled therein (ChrisPriceAB, 17:55:36)
    10. Monday’s TWS call is dedicated to prioritize lessons learned from Helium and could also address technical debt (tbachman, 17:56:26)
    11. ACTION: gzhao to email projects to request their technical debt (tbachman, 17:57:26)
    12. https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas Upcoming TWS meeting on lessons learned (tbachman, 18:00:03)
    13. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Lessons_from_Hydrogen.2FHelium_that_Should_be_Applied wiki page describing lessons learned from Helium/Hydrogen (tbachman, 18:00:22)
    14. https://wiki.opendaylight.org/view/Project_Proposals:Release_Engineering_-_Builder Release engineering builder proposal wiki page (tbachman, 18:01:00)
    15. https://docs.google.com/spreadsheets/d/1tOcLOrcab3tlYiIkewQ9dIxTDTcQaGFWmTQZ5kkMNuI/edit?usp=sharing Google doc/spreadsheet containing lessons learned (itemized) (tbachman, 18:03:40)
    16. colindixon says there’s a discussion that’s been on the ML as to whether we should have a continuous delivery model (tbachman, 18:06:25)
    17. colindixon wonders if we should prove this first in a smaller scale (i.e. single project?) (tbachman, 18:08:02)
    18. https://wiki.opendaylight.org/view/CrossProject:HouseKeeping_Best_Practices_Group:Main has been left pretty much untouched since HJydrogen release and lists the most painful problems we have (rovarga, 18:08:21)
    19. rovarga says that we need 3 participating projects: odlparent, yangtools, and some downstream project from yangtools other than controller (b/c of its size) (tbachman, 18:10:07)
    20. rovarga asks if there’s a downstream project from yangtools that’s not dependent on controller (tbachman, 18:10:46)
    21. ACTION: rovarga to pursue trying to find a project that’s downstream from yangtools and not dependent on controller to prove the continuous release process (tbachman, 18:11:32)
    22. rovarga says that there’s still the version promotion issue/question (tbachman, 18:12:15)
    23. dlenrow asks where are we on the concept of refactoring controller into discrete smaller projects? Is this Lithium? Is this tech debt? (tbachman, 18:13:52)
    24. ACTION: colindixon and phrobb to produce a strawman release plan for Lithium for next week (tbachman, 18:14:38)

  10. controller refactoring (ChrisPriceAB, 18:15:17)
    1. dmm points out that edwarnicke should probably be present for such a discussion (tbachman, 18:16:02)
    2. rovarga says that some of the action items were agreed on at the design summit (tbachman, 18:17:28)
    3. there is some pruning we can do right now — all the OF stuff into openflowplugin, etc. — devinavery may have this list (?) (tbachman, 18:17:55)
    4. rovarga says we could probably start executing on the ideas that we agreed to in the design summit, and save the rest of the discussion until edwarnicke returns (tbachman, 18:18:53)
    5. colindixon says there another proposal not to break it up, but to at least divide it into logical groups (tbachman, 18:19:40)
    6. colindixon asks if we can have a list on the wiki to have the logical sub-components to try to figure out which bundles go into which place (i.e. an exercise in documentation) (tbachman, 18:21:39)
    7. ACTION: rovarga to provide a prelim list of the logical sub-components and document what bundles would go into what sub-component (phrobb, 18:21:57)
    8. http://www.opendaylight.org/project/tsc/charter (colindixon, 18:23:34)

  11. project leads (tbachman, 18:23:34)
    1. preliminary candidates are opendaylight/netconf, opendaylight/config (tbachman, 18:23:52)
    2. http://www.opendaylight.org/project/tsc/charter TSC charter, which includes description on project leads and their responsibilities (tbachman, 18:24:22)
    3. ChrisPriceAB says that we can ask for a project lead at the start of the project, but we shouldn’t demand to much from them until they participate in the simultaneous release (tbachman, 18:26:21)
    4. rovarga says that project leaders need to emerge, rather than being brought upfront (tbachman, 18:26:34)
    5. colindixon says maybe we just make this a requirement for participation in the simultaneous release (tbachman, 18:27:01)
    6. rovarga says that committer quorom can be sufficient until a leader emerges (tbachman, 18:27:56)
    7. colindixon says that would require a change in the current charter (tbachman, 18:28:12)
    8. dlenrow asks if the project lead has any special privileges or status, or are they truly just a contact for the project (tbachman, 18:29:05)
    9. colindixon says there are 3 things: if a project becomes core, the lead becomes a member of the TSC; they are supposed to be a “single throat to choke”; and the project lead is the only one approved to remove committers from a project (tbachman, 18:29:56)
    10. alagalah asks how can/do projects change their project lead (tbachman, 18:30:20)
    11. phrobb says we end up with defacto leads by having project contacts (tbachman, 18:30:42)
    12. colindixon says that project leads are elected by the committers of that project (tbachman, 18:31:11)
    13. colindixon says that condorcet voting should take place by the committers of the project to elect the project lead (tbachman, 18:32:15)
    14. phrobb notes that projects get to decide when they want to have their elections (tbachman, 18:32:23)
    15. VOTE: Voted on "Shall the TSC mandate Project Leads be identified for each project to participate in a simultaneous release?" Results are, +1: 9 (phrobb, 18:34:37)
    16. jmedved votes +1 on allowing the integration project to remove the code in the integration repositories to build the Hydrogen distributions as part of the master branch (jmedved, 18:36:44)
    17. alagalah votes +1 on allowing the integration project to remove the code in the integration repositories to build the Hydrogen distributions as part of the master branch (tbachman, 18:37:34)
    18. ACTION: TSC members please read Lithium Rel Plans and provide comments to colindixon and phrobb. Also please identify tech debt and document that on the wiki. (phrobb, 18:38:35)
    19. dlenrow asks if it make sense to exclude "leaf projects" ( those with no dependents) from SR to reduce complexity of convergence? This is also moot if we get all the way to full CI. (tbachman, 18:39:11)
    20. colindixon says there are 3 notiions of maturity for a project (tbachman, 18:39:58)
    21. one is the project’s stage in the life cycle (e.g. core) (tbachman, 18:40:51)
    22. colindixon notes we have 3 indicators of maturity - 1 project lifecycle, 2 how dependent a project is, 3 how vibrant a given project is, and responsive to requests, 4) code maturity. (phrobb, 18:41:01)
    23. ACTION: phrobb to produce a complete list of our governing documents (tbachman, 18:43:23)
    24. colindixon asks that folks please review the release engineering project (tbachman, 18:44:17)


Meeting ended at 18:44:21 UTC (full logs).

Action items

  1. testing of Helium on windows still assigned to LuisGomez phrobb and IvanWood
  2. gzhao to check on master branch version bumps
  3. tykeal and ttkacik to work out what the next steps are to resolve this
  4. tykeal, zxiiro, and Tony T. to work off line on the Controller sonar issue
  5. LuisGomez to coordinate with dbainbri and shague about also removing the docker and rpm images from Helium since they’re only related to Hydrogen
  6. gzhao to email projects to request their technical debt
  7. rovarga to pursue trying to find a project that’s downstream from yangtools and not dependent on controller to prove the continuous release process
  8. colindixon and phrobb to produce a strawman release plan for Lithium for next week
  9. rovarga to provide a prelim list of the logical sub-components and document what bundles would go into what sub-component
  10. TSC members please read Lithium Rel Plans and provide comments to colindixon and phrobb. Also please identify tech debt and document that on the wiki.
  11. phrobb to produce a complete list of our governing documents


Action items, by person

  1. colindixon
    1. colindixon and phrobb to produce a strawman release plan for Lithium for next week
    2. TSC members please read Lithium Rel Plans and provide comments to colindixon and phrobb. Also please identify tech debt and document that on the wiki.
  2. dbainbri
    1. LuisGomez to coordinate with dbainbri and shague about also removing the docker and rpm images from Helium since they’re only related to Hydrogen
  3. gzhao
    1. gzhao to check on master branch version bumps
    2. gzhao to email projects to request their technical debt
  4. phrobb
    1. testing of Helium on windows still assigned to LuisGomez phrobb and IvanWood
    2. colindixon and phrobb to produce a strawman release plan for Lithium for next week
    3. TSC members please read Lithium Rel Plans and provide comments to colindixon and phrobb. Also please identify tech debt and document that on the wiki.
    4. phrobb to produce a complete list of our governing documents
  5. rovarga
    1. rovarga to pursue trying to find a project that’s downstream from yangtools and not dependent on controller to prove the continuous release process
    2. rovarga to provide a prelim list of the logical sub-components and document what bundles would go into what sub-component
  6. tykeal
    1. tykeal and ttkacik to work out what the next steps are to resolve this
    2. tykeal, zxiiro, and Tony T. to work off line on the Controller sonar issue


People present (lines said)

  1. tbachman (154)
  2. ChrisPriceAB (31)
  3. odl_meetbot (24)
  4. colindixon (21)
  5. rovarga (19)
  6. alagalah (19)
  7. phrobb (17)
  8. regXboi (14)
  9. dlenrow (11)
  10. tykeal (7)
  11. dmm (6)
  12. jmedved (4)
  13. abhijitkumbhare (4)
  14. Youcef (3)
  15. kwatsen (3)
  16. dfarrell07 (2)
  17. mohnish (2)
  18. hideyuki (2)
  19. icbts (1)
  20. dbainbri (1)
  21. gzhao (1)


Generated by MeetBot 0.1.4.