15:03:06 <ChrisPriceAB> #startmeeting Brahmaputra project meeting
15:03:06 <collabot> Meeting started Tue Sep 15 15:03:06 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:06 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:03:06 <collabot> The meeting name has been set to 'brahmaputra_project_meeting'
15:03:10 <ChrisPriceAB> #topic roll call
15:03:15 <ChrisPriceAB> #info Chris Price
15:03:17 <lmcdasm> #info Daniel Smith
15:03:22 <lmcdasm> are we using same GTM again?
15:03:30 <hujie> #info Jie Hu
15:03:35 <lmcdasm> or the one in the  meeting invite?
15:03:37 <anac1> #info Ana Cunha (Yardstick)
15:03:48 <zhipeng> #info Zhipeng (Parser)
15:03:48 <debrascott> lmcdasm: no my go to meetin is now updated to accomodate >100 people
15:03:49 <fdegir> #info Fatih Degirmenci (Releng/Octopus)
15:04:01 <debrascott> use the one in the meeting invite
15:04:02 <chenshuai> #info chenshuai (Compass4nfv)
15:04:28 <hujie> #info Jie Hu (escalator)
15:04:40 <frankbrockners> #info Frank Brockners
15:04:42 <morgan_orange> #info Morgan Richomme
15:04:43 <iben> would someone paste the g2m link here please?
15:04:53 <frankbrockners> https://global.gotomeeting.com/join/341956909
15:05:36 <iben> thanks
15:05:36 <mdgray> #info Mark Gray
15:05:52 <debrascott> #info Agenda
15:06:01 <debrascott> #info https://wiki.opnfv.org/releases/brahmaputra/minutes
15:06:55 <bin_> #info Bin Hu (IPv6)
15:07:35 <ashyoung> #info Ashlee Young (ONOSFW)
15:07:46 * ChrisPriceAB is interested to know who can help scribe
15:07:58 * ChrisPriceAB as I am trying to wrap up my last meeting
15:08:01 <debrascott> #topic jira training
15:08:03 <ChrisPriceAB> #chair debrascott
15:08:03 <collabot> Current chairs: ChrisPriceAB debrascott
15:08:22 <debrascott> #topic jira training
15:08:53 <StuartMackie> #info Stuart Mackie
15:09:27 <debrascott> #info raw material is done but not published yet
15:09:40 <debrascott> #info plan to publish by end of week
15:10:19 <debrascott> #info if anyone is unclear on what to do in jira please reach out to community, don’t wait for formal training
15:11:27 <debrascott> #info question is do we have default permissions correct so UI is common?
15:12:04 <debrascott> #info do we need to have template and workflows?
15:13:12 <dneary> My main concern is that an authorized user on Jira can create a ticket, modify their own tickets, and add a comment with no additional hoops to jump through
15:13:39 <debrascott> #info every project has different needs, and use of jira so not all will be uniform
15:13:49 <lmcdasm> dneary: - indeed, this was (for me) a small typo that Aric fixed..  my concern ni that last week was that doing it 1 ticket at a time to fix each commiter is heavy work
15:14:05 <dneary> s/authorized/authenticated
15:14:23 <fdegir> people should be able to create stuff
15:14:35 <fdegir> but only project committers should have the right to remove them
15:14:35 <debrascott> #info Chris clarifies that we provide general guidelines not detailed template
15:14:40 <lmcdasm> creates were ok - they needed Editing and workflows to be set up
15:15:23 <debrascott> #info permissions, and workflow need to consistent so everyone see same interface
15:15:25 <ChrisPriceAB> #info franckbrockners describes and issue with authorities to open them up for all contributors to be able to raise tickets.
15:16:05 <dneary> #info lmcdasm raises the point that there is no clear agreement on default permissions.
15:17:04 <dneary> #info dneary points out that in the absence of aricg on the call, we should ensure that there is a clear request for default permissions sent to him.
15:17:49 <dneary> #info Iben asks the question whether there's a need to have multiple levels of authorization
15:21:06 * dneary would like to move on - this can all be done by email
15:21:24 <ashyoung> yep
15:23:05 <debrascott> #info need to write a proposal on what to present to Aric to change the implementation on Jira
15:23:14 <dneary> #info Iben points out we need to define groups per project to allow people who are core contributors to close tickets
15:23:31 <dneary> debrascott, Yes - Etherpad is great
15:23:38 <ashyoung> dneary: great point
15:24:05 <[1]JonasB> #info Jonas Bjurel (Fuel)
15:24:07 <debrascott> #info Debra to start an etherpad to continue this discussion
15:24:30 <ChrisPriceAB> #action debrascott to establish an etherpad on, and have a dialog with aricg on, the needed roles and permissions in Jira.
15:25:31 <debrascott> #topic weekly reports
15:26:57 <ChrisPriceAB> #link https://etherpad.opnfv.org/p/Brahmaputra_Release_Weekly_Project_Status reporting etherpad
15:28:05 <bryan_att> have we been specifically asked by the board to provide this info weekly? can we generate any of this automatically? I am concerned about the overhead
15:28:14 <fdegir> we already have this info in jira
15:28:28 <fdegir> and have yet another page to report the status
15:29:01 <fdegir> what happens if anyone doesn't put the status there?
15:29:08 <fdegir> and keeps the status solely in JIRA?
15:32:33 <[1]JonasB> fdegir: link to Jira?
15:33:00 <fdegir> [1]JonasB: link to Jira?
15:33:05 <fdegir> what you mean?
15:33:15 <ashyoung> It takes about a minute. Even I can spare that :)
15:33:25 <fdegir> it is not about sparing a minute
15:33:39 <fdegir> it's about adding more and more stuff to control what's happening
15:33:53 <fdegir> but it's perhaps only me and can be neglected
15:34:13 <ashyoung> Jira should be primarily used by the projects to police themselves
15:34:34 <ashyoung> I cannot comment on another project's jira tickets to determine that they've addressed all tasks
15:34:38 <fdegir> Jira can be used by others to follow the progress of the projects
15:34:50 <ashyoung> this is a way to keep the communities in sync
15:34:53 <debrascott> #info lets work toward highlighting the projects that are doing well using jira dashboards
15:34:54 <lmcdasm> how does the Gensis tickets come into play in that scenario? Since Genesis wont produce anything, you ahve a three way matrix you have now created between projets / genesis and isntallers
15:35:00 <[1]JonasB> fdegir: What if you out the link to the Jira dashboard in the status report?
15:35:15 <fdegir> [1]JonasB: that can be done
15:36:24 <ChrisPriceAB> #topic Genesis proposal for sharing cross project requirements
15:36:42 * ChrisPriceAB is waiting for frank to pound in the link
15:36:43 <frankbrockners> #link https://wiki.opnfv.org/genesis/integration_guidelines
15:36:45 <ChrisPriceAB> :)
15:38:07 <debrascott> #info Frank esplains Genesis proposal, 1st entry point is to create a Jira ticket to Genesis
15:38:58 <debrascott> #info Jira enables a focused discussion, discussion tracking
15:40:36 <mdgray> Is there a link to this procedure on the wiki? I cant find it on the Genesis page.
15:41:13 <debrascott> mdgray, frankbrockners entered the link above
15:41:40 <mdgray> debrascott: thanks
15:42:45 <lmcdasm> suggestion - in the CREATION phase
15:42:54 <lmcdasm> there should be a indication of the local project JIRA ticket (their own requirment)
15:43:07 <lmcdasm> as well as (once approved) the JIRA tickets for the installers that are going to pick it up
15:43:15 <lmcdasm> otherwise you dont have a maaping from project to JIRA to installer
15:44:51 <debrascott> #info dneary asks definition of requirement in Genesis. Frank clarifies the requirements are for the installers, and is a “proposal” until approved
15:44:57 <bryan_att> are we talking about https://jira.opnfv.org/browse/BGS?
15:46:08 <bryan_att> or https://jira.opnfv.org/browse/GENESIS?
15:46:43 <fdegir> https://jira.opnfv.org/browse/GENESIS
15:48:11 <bryan_att> have the current emailed requirements been added as tickets? I don't see any specifically.
15:48:46 <debrascott> bryan_att, he said they are working on that
15:50:42 <bryan_att> it is my understanding that in some cases we will never get all installers to support a specific feature, e.g. heat. in those cases can we ever get this feature as part of OPNFV?
15:51:21 <bryan_att> why should we gate participating in genesis on support by all installers?
15:51:52 <debrascott> bryan_att: you can still work with the individual installers. Genesis is specifically for “common” requirements across all installers
15:52:08 <bryan_att> IMO there should be a minimum of 2 installers perhaps, but a higher bar is unecessarily exclusive
15:52:45 <bryan_att> not seeing the benefit of engaging with genesis then - have to still engage with every installer
15:53:38 <bryan_att> there will be a small set of features supported by every installer - thus the scope of genesis will be small if support by all installers is the gate
15:54:49 <mdgray> Do we need to enable a feature across all installers to be considered part of a release?
15:55:30 <debrascott> mdgray: no
15:57:10 <mdgray> I agree with dneary that it seems the overhead of having to try and implement the feature into each installer project is significant.
15:57:19 <bryan_att> just to be included in genesis apparently
15:57:36 <mdgray> I suspect projects will just pick their favorite installers and work with them directly
15:57:54 <dneary> mdgray, Interests have to align
15:58:15 <mdgray> dneary, interests between installers and feature projects?
15:58:43 <dneary> mdgray, Yes - and users
15:59:33 <dneary> mdgray, "I want to make feature X available to my users" + "I want my work to be available on platform X" + "I want to get my hands on that feature in my preferred environment" = sweet spot
16:00:47 <ChrisPriceAB> thanks for the update on genesis and good discussion frankbrockners
16:00:53 <dneary> Yes, thank you frankbrockners
16:00:57 <ChrisPriceAB> #topic AoB
16:01:00 <mdgray> Perhaps genesis can help generalize the requirements. For example, in ovsnfv, we want to allow installation of a "different" version ovs but for genesis this means installers need to have the ability to install alternate packages
16:01:12 <ChrisPriceAB> #info debrascott asks for additional agenda items to be proosed to her during the week
16:01:13 <fdegir> anyone who has labs to offer to jump to pharos and make their labs useful for the CI and developers
16:01:18 * dneary would appreciate detailed minutes going to the list to document consensus and concerns from this call
16:01:54 <ChrisPriceAB> ack fdegir let's work on getting the labs in place ASAP
16:02:00 <ChrisPriceAB> #endmeeting