16:00:06 <phrobb> #startmeeting Karaf Meeting #1
16:00:06 <odl_meetbot> Meeting started Wed Jul 23 16:00:06 2014 UTC.  The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:00:06 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:06 <odl_meetbot> The meeting name has been set to 'karaf_meeting__1'
16:00:35 <phrobb> #topic Each Project Contact please #info in with the project you are representing
16:01:07 <tbachman> #info tbachman for Group Based Policy
16:01:24 <oflibMichal> #info oflibMichal for openflowjava
16:01:47 <xsited> #info Thomas Kee for packetcable
16:01:53 <hideyuki> #info Hideyuki for VTN
16:02:07 <lori> #info Lori Jakab for lispflowmapping
16:02:14 <Madhu> #info Madhu for OVSDB
16:02:23 <liemmn> #info Liem Nguyen for AAA
16:02:26 <paulz> #info Paul Zimmerman for ODL Docs
16:03:30 <tykeal> #info Andrew Grimberg for infrastructure (just in case...)
16:03:32 <phrobb> #chair Madhu
16:03:32 <odl_meetbot> Current chairs: Madhu phrobb
16:04:33 <tbachman> phrobb: I can help Madhu take notes if you want
16:04:51 <ttkacik> #info ttkacik for YANGTools
16:04:52 <ChrisPriceAB> I'm not finding the webex.
16:05:00 <Madhu> ChrisPriceAB: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M3JACWYDE6BJDHVHY0YV877WO7-9VIB&rnd=111712.22940
16:05:47 * ChrisPriceAB ty madhu
16:05:47 <phrobb> #chair tbachman
16:05:47 <odl_meetbot> Current chairs: Madhu phrobb tbachman
16:05:53 <tbachman> :)
16:07:00 <abhijitkumbhare> #info abhijitkumbhare  for OpenFlow plugin
16:08:29 <phrobb> #topic Introduction to what is needed to support Karaf - Docs, tests, pkging, etc
16:08:46 <Madhu> #link https://lists.opendaylight.org/pipermail/release/2014-July/000078.html it all starts here
16:09:17 <phrobb> luis, could you get the wiki page up?
16:10:26 <Madhu> #info edwarnicke suggests us to move the wording of requirement -> recommendation in https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan
16:11:39 <edwarnicke> #link https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines
16:12:21 <Madhu> #link https://wiki.opendaylight.org/view/CrossProject:Helium_Release_Vehicle_Brainstorming:Pure_Karaf
16:12:55 <tbachman> #info mlemay asks projects to either indicate whether or not they’d like his help in “karaf-ing” their project
16:13:52 <Madhu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Helium_Release_Plan#Proposed_Release_Vehicles to indicate if the project will support Karaf for Helium
16:18:14 <Madhu> #info edwarnicke suggests to provide both the feature dependency and the repo reference and it will help a great deal when the dependency tree grows .
16:18:18 <edwarnicke> #action edwarnicke will update the guidelines to describe how to properly setup features.xml in a way that transitive feature depenencies are handled easily :)
16:18:20 <Madhu> edwarnicke: i hope I captured that :)
16:18:29 <edwarnicke> Madhu: You did better than I did :)
16:19:10 <edwarnicke> Question: Do we want in the guidelines to suggest a format for the artifactIds for the features/ directory?
16:19:21 <edwarnicke> Question: Do we want to talk about avoiding overinclusion in features.xml?
16:19:45 <edwarnicke> Question: Do we want to talk about avoiding cycles between features.xml files when possible?
16:21:07 <Madhu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Project_Expectations Project Expectations
16:21:27 <edwarnicke> Question: What guidance (if any) do we want to provide to projects with non-Java components like VTN, OpenDove, Opflex etc?
16:21:32 <hideyuki> Madhu: Thank you!
16:21:35 <Madhu> edwarnicke: lets push these questions to the stack for now till folks are all upto speed :)
16:21:59 <edwarnicke> Madhu: That's why I am IRCing them instead of interupting the audio :)
16:22:07 * edwarnicke can evidently learn not to interupt ;)
16:22:08 <Madhu> edwarnicke: yep. thanks for that
16:25:26 <Madhu> #info in order to understand what a project provides for the release (such as Features, documentation, etc...) project should provide a metafile as defined under https://wiki.opendaylight.org/view/Simultaneous_Release:Project_Expectations
16:28:55 <tbachman> #info edwarnicke asks why we don’t specify conflicts and dependencies at the project level
16:29:17 <edwarnicke> tbachman: Actually the opposite :)
16:29:21 <tbachman> lol
16:29:21 <tbachman> k
16:30:48 <tbachman> #info Madhu asks if this is a project level dependency or component level dependency
16:30:57 <tbachman> #info mlemay says it’s really a maven dependency
16:31:32 <tbachman> #info Madhu asks if this is purely for documentation, or also for packaging
16:31:45 <tbachman> #info mlemay says it’s mainly for testing and documentation purpose
16:32:14 <Madhu> #info mlemay confirms it is not a maven dependency :) this just negates tbachman assertion above
16:32:21 <tbachman> lol
16:32:25 <Madhu> lol
16:32:28 * tbachman should stop doing #info’s
16:32:29 <tbachman> lol
16:32:38 <Madhu> tbachman: u have 1 more strike
16:32:41 <tbachman> lol
16:32:54 <tykeal> and then he gets a cookie?
16:33:06 <tbachman> Is there an unchair?
16:33:08 <tbachman> lol
16:33:14 <tbachman> demote-chair
16:34:02 <Madhu> tykeal: and milk
16:37:32 <edwarnicke> tbachman: You are just trying to avoid being chaired ;)
16:37:40 <tbachman> edwarnicke: you’re on to me
16:37:48 <edwarnicke> ;)
16:37:52 <tbachman> lol
16:37:54 <Madhu> edwarnicke: he asked for it.
16:37:56 <Madhu> :)
16:37:58 * edwarnicke is just jealous he didn't think of it first ;)
16:38:37 <tbachman> edwarnicke: Madhu: it’s the way I learn — assert the exact opposite of what was said
16:43:02 <Madhu> #info in summary <component> is a level of abstraction to uniformly obtain (programatically) what a project has to offer at a component level which can be used for uniform Documentation, Integration testing and for GUI
16:43:45 <edwarnicke> I do a poor GiovanniMeo imitation... but I do try when he's not around to represent him on the meager things I understand :)
16:45:04 <Madhu> #link https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines Guidelines for creating and maintaining Apache Karaf feature files in each project
16:49:47 <phrobb> #info mlemay asks that each project create a karaf feature.xml file.  He can provide a skeleton that each project can start from, or mlemay offers to help build each project's feature file if need be.
16:51:51 <phrobb> #info questions on standards for feature names… foo-features vs features-foo  … we need a guideline so that everyone is consistent in their naming
16:54:58 <Madhu> #info mlemay controller/features can be used as an example for others to follow
16:57:36 <edwarnicke> #link https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines#Feature_Best_Practices - updated with some additional guidelines
17:01:42 <phrobb> #action mlemay to provide a good example of a POM file for this Karaf work
17:07:49 <Madhu> #question LuisGomez : where do we put the project component files ?
17:08:07 <edwarnicke> #link https://wiki.opendaylight.org/view/Runtime:Karaf_Features_Guidelines#Atomicity - updated to include advice on atomicity
17:08:12 <Madhu> #info mlemay it is preferred to place it in projects root
17:09:20 <Madhu> #endmeeting