17:02:38 <tbachman> #startmeeting tws
17:02:38 <odl_meetbot> Meeting started Mon Oct 20 17:02:38 2014 UTC.  The chair is tbachman. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:02:38 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:02:38 <odl_meetbot> The meeting name has been set to 'tws'
17:02:47 <tbachman> #chair alagalah colindixon
17:02:47 <odl_meetbot> Current chairs: alagalah colindixon tbachman
17:03:14 <alagalah> #topic Agenda
17:03:31 <alagalah> #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas
17:03:59 <tbachman> #undo
17:03:59 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Link object at 0x2513850>
17:04:06 <tbachman> #link https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas agenda for today’s TWS
17:04:30 <tbachman> #topic Changes in Karaf 3.0.2
17:06:26 <tbachman> #info icbts says there were a lot of changes requested for the next iteration of karaf by ODL community
17:06:51 <tbachman> sorry ! :)
17:07:07 <tbachman> #info new features in 3.0.2: ability to use !$ to recall last argument in console
17:07:44 <tbachman> #inof new feature in 3.0.2: command to display the bundle id (i.e. bundle:id <arg>)
17:07:53 <tbachman> #info new feature in 3.0.2: command to display the bundle id (i.e. bundle:id <arg>)
17:08:31 <tbachman> #info new feature in 3.0.2: when a feature is generated from a bundle project, include that bundle in the feature
17:09:07 <tbachman> #info colindixon asks what bundles are automatically included
17:09:19 <tbachman> #info icbts says that it will get the dependencies, but not the bundle that was created locally
17:10:25 <tbachman> #info new feature in 3.0.2: add baclomg emgome service for org.apagache.karaf.jaas.modules.publickey.PublickeyLoginModule
17:10:39 <tbachman> #info new feature in 3.0.2: add a flag to bin/client so that it can read private key from a specified location
17:11:52 <tbachman> #info Bug fix for JDK 1.8 support
17:12:26 <tbachman> #info Windows support fixes (3 issues discovered with JVMs on windows systems, where JVM options were ignored on windows)
17:16:43 <tbachman> #info feature improvements: features-maven-plugin cannot resolve a feature without an explicit descriptor; features deployer is useless for dynamic updates; karaf-maven-plugin ignores dependent feature repositories when building an assembly; whitespace in feature file bundle element value causes NumberFormatException; Concurrency issues in FeatureService related to add/remove/list operations; Using features to extend existing
17:16:43 <tbachman> configuration
17:17:25 * tbachman notes his inconsistency in listing “new features”, “bug fixe, and feature improvements :p
17:18:51 <tbachman> #info icbts asks that folks come to Apache Karaf if there are other feature requests, bugs, etc.
17:19:12 <tbachman> #info colindixon points out that icbts is “I Code By The Sea” :)
17:20:14 <tbachman> #info colindixon says for help in where we can simplify our feature files and making sure that our feature specifications are “correct"
17:20:59 <icbts> Which email address to send a PDF of the Karaf 3.0.2 changes too?
17:21:45 <flaviof> https://bugs.opendaylight.org/show_bug.cgi?id=2002
17:22:44 <tbachman> #link https://bugs.opendaylight.org/show_bug.cgi?id=2002 flaviof asks if any of the known karaf bugs could be related to this bug
17:23:38 <tbachman> #info icbts says you can type “exports” to see what classes are currently installed in karaf
17:24:13 <tbachman> #info LuisGomez asks what the process is to update the projects to the newest version of karaf?
17:25:04 <tbachman> #info gzhao asks if it requires every project to move to 3.0.2, or whether this can be done on a per-project basis
17:25:25 <tbachman> #info icbts says that it’s just the controller project that builds the opendaylight-karaf distribution
17:27:36 <tbachman> fwiw, I did see this in my project’s features/pom.xml, in teh properties:     <karaf.version>3.0.1</karaf.version>
17:28:12 <tbachman> s/my project’s/groupbasedpolicy/
17:28:43 <tbachman> #topic Lessons Learned from Helium
17:29:09 <tbachman> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Lessons_from_Hydrogen.2FHelium_that_Should_be_Applied Wiki page capturing the lessons learned from Hydrogen/Helium
17:29:48 <tbachman> #link https://docs.google.com/spreadsheets/d/1tOcLOrcab3tlYiIkewQ9dIxTDTcQaGFWmTQZ5kkMNuI/edit#gid=0 Google spreadsheet form of this link
17:30:06 <icbts> phrobb: Which email address do i send the PDF of the karaf talk to?
17:31:05 <tbachman> #info alagalah  asks if we were to pick 5 things on the list, what would we choose?
17:31:16 <tbachman> #undo
17:31:16 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2739cd0>
17:31:27 <tbachman> #info alagalah  asks if we were to pick 5 things on the list, what would we choose to do for Lithium?
17:33:00 <tbachman> #info colindixon says there are some items on the list that don’t require much effort (e.g. providing primary contacts for projects)
17:37:08 <tbachman> #info colindixon says that if a project wants/needs to elect their project lead, they should contact phrobb to set up the condorcet election
17:37:44 <tbachman> #info colindixon says that we didn’t use offsets for projects in Helium, as we did in Hydrogen
17:38:13 <tbachman> #info colindixon asks if some projects weren’t able to meet deadlines  because of dependencies on other projects
17:39:09 <tbachman> #info colindixon says that the project lead should be the default point of contact, and if they’re not going to be, they need to appoint someone to be the point of contact
17:40:52 <icbts> Karaf slides: https://www.dropbox.com/s/oaipjreyvhcib3w/Apache-Karaf-3.0.2-Summary.pdf?dl=0
17:41:15 <tbachman> #link https://www.dropbox.com/s/oaipjreyvhcib3w/Apache-Karaf-3.0.2-Summary.pdf?dl=0 slides for icbts’s karaf presentation
17:41:18 <tbachman> icbts: thx!
17:41:26 <icbts> tbachman: no problem
17:41:43 * tbachman notes it will be a little non-sequitor b/c of topics, but at least it’s in the minutes :)
17:43:56 <tbachman> #info colindixon would like to see definitions that can be verified for things like “started documentation”
17:46:04 <tbachman> phrobb: hard to hear you
17:46:42 * tbachman wonders what the best way is to capture this here
17:50:30 <tbachman> #info colindixon says that his goals for the list were visibility and awareness
17:51:46 <tbachman> #info colindixon would love to see folks jump in and help drive the items on the list
17:54:05 <tbachman> colindixon: alagalah: if we want folks to pick things from the list and run with them, should we formalize it a bit? (e.g. send email to ML, telling project leads to attend, and work on going through the items on the list)
17:54:15 <alagalah> tbachman: Agreed
17:55:03 <tbachman> #info jmedved would like to see earlier integration points for the release
17:55:14 * icbts sorry about that :(  We’re trying to fix our release schedule to be more timely
17:55:41 <tbachman> time check: 5 mins
17:58:41 <tbachman> #info colindixon would like to see different requirements for leaf projects and core projects
17:59:57 <tbachman> #info dlenrow says that creating a project is a right, and joining the simultaneous release is a privilege, and therefore projects need to meet different standards for those events.
18:01:21 <tbachman> crumbs — what was that action?
18:02:39 * tbachman would like to see major features introduced at some time earlier than the last 3-4 weeks
18:03:21 <phrobb> icbts:  Just send the pdf to me (probb@linuxfoundation.org) and I'll put them on the wiki and point to them from the meeting from the TWS page.
18:03:29 <tbachman> #endmeeting