#opendaylight-meeting Meeting

Meeting started by regXboi at 16:55:48 UTC (full logs).

Meeting summary

    1. dmm (paris) (dmm, 16:57:39)
    2. https://wiki.opendaylight.org/view/TSC:Main#Meeting_Agenda (dmm, 16:57:55)
    3. vijoy (vijoy, 17:00:06)
    4. Ryan Moats (regXboi) (regXboi, 17:00:21)
    5. Ed Warnicke :) (edwarnicke___, 17:00:25)
    6. Chris Wright (cdub, 17:02:58)
    7. Colin Dixon (colindixon, 17:04:53)
    8. Chris Price joined the meeting (chrisprice___, 17:05:16)
    9. Madhu  (Madhu, 17:05:19)
    10. Brent (networkstatic, 17:05:53)

  2. remove minutes from meeting agent (regXboi, 17:06:19)
    1. ACTION: acceptance of minutes will now be auto-on (regXboi, 17:06:35)
    2. RobDolin proxy for Rajeev Nagar (Microsoft) (RobDolin, 17:07:20)
    3. skipping event updates (phil is not on the call) (regXboi, 17:07:20)
    4. skipping system integration/testing update (luis is not on the call) (regXboi, 17:07:35)
    5. skipping creation reviews(s) ... nothing on the list (regXboi, 17:07:51)

  3. creation review(s) (regXboi, 17:10:25)
    1. discussion of the two week requirement for project reviews (regXboi, 17:10:38)
    2. ACTION: Madhu to schedule review of acceleration project to dmm (regXboi, 17:11:38)

  4. committers (regXboi, 17:11:45)
    1. consideration of Michal Polkorab as new committer on OpenFlowJava (regXboi, 17:12:17)
    2. https://lists.opendaylight.org/pipermail/openflowjava-dev/2014-March/000154.html - request to add Michal Polkrab as a committer to openflowjava (edwarnicke___, 17:12:54)
    3. https://lists.opendaylight.org/pipermail/openflowjava-dev/2014-March/000151.html - to the call for a vote on the openflowjava-dev mailer (edwarnicke___, 17:13:24)
    4. Paul Zimmerman (paulz, 17:13:55)
    5. AGREED: Michal Polkorab will be added as a committer (regXboi, 17:15:59)
    6. David Meyer is asking the TSC to vote on approving Michal P. to committer (RobDolin, 17:16:06)
    7. this is to the openflowjava project (colindixon, 17:17:21)
    8. ... committer on OpenFlowJava project (RobDolin, 17:17:43)
    9. Madhu is sharing screen for demo (RobDolin, 17:18:58)
    10. https://wiki.opendaylight.org/view/Project_Proposals:OpenDaylight_Toolkit the project proposal (which was e-mailed to TSC and project proposals lists) (colindixon, 17:19:23)
    11. https://maven.apache.org/guides/introduction/introduction-to-archetypes.html maven documentation about archetypes (colindixon, 17:20:02)
    12. the general idea of the project is to provide skeletons for OpenDaylight applications which can be quickly spun up (and customized) by leveraging maven archetypes (colindixon, 17:21:34)
    13. it is informed by the rough edges found while Madhu, networkstatic and others were helping out running hackfests (colindixon, 17:21:57)
    14. this is very cool (dmm, 17:31:02)
    15. archetypes (dmm, 17:31:35)
    16. archetypes can be generated from existing code (regXboi, 17:35:20)
    17. http://maven.apache.org/archetype/maven-archetype-plugin/create-from-project-mojo.html (GiovanniMeo, 17:36:17)
    18. the archetype can also be extracted from an existing project (GiovanniMeo, 17:36:37)
    19. colindixon stresses...eclipse built app w/ _no build errors_ (answers some large percentage of email questions via automation) (cdub, 17:41:44)
    20. there is a no brainer (dmm, 17:41:57)
    21. s/there/this (dmm, 17:42:13)
    22. regXboi suggests this looks like a fundamental architectural shift (fundamental change to how we build ODL and its apps) (cdub, 17:43:15)
    23. edwarnicke___ notes that they're really good for simple things, but they have more warts when you get to doing complicated things, so this is unlikely to extend to factoring out all modules in the current ODL codebase (colindixon, 17:44:16)
    24. even regXboi agrees that this is hugely useful for bringing new people into the project whether it's in hackfests or with new developers (colindixon, 17:48:10)
    25. question from luis: can archetypes be used for apps on top of MD-SAL (regXboi, 17:50:00)
    26. answer from Madhu: this is independent of MD-SAL/AD-SAL (regXboi, 17:50:21)
    27. there is already an archetype for model driven apps (GiovanniMeo, 17:50:31)
    28. so this is a good topic for MD-SAL (regXboi, 17:50:33)

  5. stable release (draft 1) (regXboi, 17:54:13)
    1. plea from cdub for review of the high level process for stable releases (regXboi, 17:56:57)
    2. Ed Warnicke suggests we should get some wiki pages listing bugs that are good candidates for stable branch fixes (RobDolin, 17:57:41)
    3. Ed Warnicke suggests we need a way to handle artifact versioning (RobDolin, 17:58:40)
    4. stable release process...agree we want this, per-project stable branch, per-project committers to manage those branches, guidelines for what goes into that, releasing this (cdub, 17:59:06)
    5. Chris Wright suggests it will be helpful to have a document that helps committers say no to changes to a stable branch (RobDolin, 17:59:57)
    6. regXboi notes that we need to work on our ability to build snapshots of non-jar stuff so that we don't lose it as we release things. For example documentation and source code. (colindixon, 18:00:16)
    7. the git tag of the release (GiovanniMeo, 18:02:39)

  6. stability, scalability, performance Hyrdogen releases (regXboi, 18:05:52)
    1. open question on candence (regXboi, 18:07:31)
    2. https://wiki.opendaylight.org/view/CrossProject:Stable_Release (cdub, 18:07:53)
    3. release cadence discussion...3 dimensions: critical bugfix forces release, time based, queue length based (cdub, 18:11:03)
    4. one request for time based to make it predictable for users (and developers -- know when the train is leaving the station) (cdub, 18:11:47)
    5. discussion on what is a stable release seems to converge on "it's only stability/bugfix no new features" (cdub, 18:21:49)
    6. RobDolin reporting (regXboi, 18:22:57)
    7. the criteria are guidelines for describing for what goes into the stable release, there are shades of grey here, judgement call needs to be made, we will make mistakes (chances are good at some point we'll introduce regression in stable release)...mitigation for this is transparency (cdub, 18:23:38)
    8. a small group of folks are discussing documentation and are thinking of creating a documentation project for providing a clearing house of best practices for documentation as well as documentation tool chain (regXboi, 18:23:55)
    9. stable release patch proposal transparency can be done by literally posting the patch queue to the list (lkml style) or gerrit based mechanism for proposing patches to stable branches w/in a project (cdub, 18:24:43)
    10. http://docs.inocybe.com/install-guide/install-guide-20140316.pdf (colindixon, 18:24:58)
    11. http://docs.inocybe.com/install-guide/content/ch_install.html (colindixon, 18:25:01)
    12. we are gerrit based and more likely to adopt the latter model (cdub, 18:25:03)
    13. mlemay (of inocybe) has been working on some documentation efforts (colindixon, 18:27:02)
    14. http://docs.inocybe.com/install-guide/content/ch_install.html html docs that are the current output (colindixon, 18:27:15)
    15. http://docs.inocybe.com/install-guide/install-guide-20140316.pdf pdf versions of the same (colindixon, 18:27:29)
    16. https://wiki.opendaylight.org/view/GettingStarted:Developer_Main - master list of IRC channels is here (edwarnicke___, 18:27:47)
    17. https://wiki.opendaylight.org/view/CrossProject:Documentation_Group <- Cross-project documentation group as mentioned (RobDolin, 18:27:49)
    18. https://wiki.opendaylight.org/view/IRC <- List of IRC channels (RobDolin, 18:28:30)
    19. https://wiki.opendaylight.org/view/Meetings (cdub, 18:29:32)
    20. colindixon suggests RSS feed w/ ical to put all meetings in one (cdub, 18:31:10)
    21. colindixon suggests that we write code for a living (cdub, 18:35:49)
    22. ACTION: colindixon to look into how to coordinate meetings (regXboi, 18:36:13)
    23. colindixon to look into this (regXboi, 18:37:00)

  7. open election status by phrobb (regXboi, 18:37:43)
    1. https://meetings.opendaylight.org/opendaylight-meeting/2014/opendaylight-meeting.2014-03-13-16.59.html bullet #15 (colindixon, 18:39:53)
    2. regXboi asked why only committers? (regXboi_, 18:40:25)
    3. answer was to keep things sane (regXboi_, 18:40:42)
    4. question is how to remove oneself from the nomination list (regXboi_, 18:41:43)
    5. ACTION: phrobb will send email to nominees to get confirmation that they want to run (regXboi_, 18:42:13)
    6. question on what is the term being elected for (regXboi_, 18:42:26)
    7. answer is one year (regXboi_, 18:42:33)

  8. call for new topics (regXboi, 18:43:51)
    1. question if there will be a meeting next week (regXboi, 18:44:02)
    2. ACTION: dmm will propose to cancel next weeks meeting (regXboi, 18:44:15)


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

Action items

  1. acceptance of minutes will now be auto-on
  2. Madhu to schedule review of acceleration project to dmm
  3. colindixon to look into how to coordinate meetings
  4. phrobb will send email to nominees to get confirmation that they want to run
  5. dmm will propose to cancel next weeks meeting


Action items, by person

  1. colindixon
    1. colindixon to look into how to coordinate meetings
  2. dmm
    1. Madhu to schedule review of acceleration project to dmm
    2. dmm will propose to cancel next weeks meeting
  3. Madhu
    1. Madhu to schedule review of acceleration project to dmm
  4. phrobb
    1. phrobb will send email to nominees to get confirmation that they want to run


People present (lines said)

  1. cdub (46)
  2. regXboi (40)
  3. colindixon (28)
  4. alagalah (18)
  5. edwarnicke___ (12)
  6. GiovanniMeo (12)
  7. dmm (12)
  8. RobDolin (11)
  9. Madhu (10)
  10. regXboi_ (10)
  11. vijoy (4)
  12. phrobb (2)
  13. odl_meetbot (2)
  14. paulz (1)
  15. chrisprice___ (1)
  16. networkstatic (1)


Generated by MeetBot 0.1.4.