15:00:55 <ChrisPriceAB> #startmeeting OPNFV Brahmaputra project meeting
15:00:55 <collabot> Meeting started Tue Sep  8 15:00:55 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:55 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:55 <collabot> The meeting name has been set to 'opnfv_brahmaputra_project_meeting'
15:02:12 <[2]JonasB> #info Jonas Bjurel (Fuel)
15:02:25 <morgan_orange> #info Morgan Richomme
15:02:37 <anac1> #info Ana Cunha (Yardstick)
15:02:37 <zhipeng> #info zhipeng huang
15:02:39 <ashyoung> #info Ashlee Young (ONOSFW)
15:02:47 <zhipeng> #info zhipeng huang (Parser)
15:02:59 <hongbotian> #info hongbo(bottlenecks)
15:03:12 <VikramDham> #info Vikram Dham (QTIP)
15:03:54 <fdegir> #info Fatih Degirmenci (Releng)
15:03:55 <trozet> #info Tim Rozet
15:04:00 <[2]JonasB> My GOTO meeting client is waiting for the organizer, is there a new goto meeting Id?
15:04:01 <lmcdasm> #info Daniel Smith
15:04:20 <trozet> #info Tim Rozet (Apex)
15:04:22 <fdegir> [2]JonasB: we use tsc gtm
15:04:30 <[2]JonasB> Ahh
15:04:44 <chenshuai> #info chenshuai (Compass)
15:04:45 <fdegir> https://global.gotomeeting.com/join/798898261
15:05:06 <mdgray> #info mdgray
15:05:15 <fdegir> please join release planning meeting using https://global.gotomeeting.com/join/798898261
15:05:35 <julien_ZTE> #info Julien
15:05:36 <maryamtahhan> is this the Brahmaputra release meeting?
15:05:42 <fdegir> maryamtahhan: yes
15:06:11 <uli-k> #info Uli Kleber Octopus
15:06:45 <ChrisPriceAB> #info Chris Price (opnfvdocs / dovetail)
15:06:48 * ChrisPriceAB cringes
15:07:02 <lmcdasm> #info Daniel Smith (fuel/bgs/pharos?)
15:07:17 <maryamtahhan_> the calendar invite had a different GTM
15:07:37 <ChrisPriceAB> yes we swapped out at the last minute to make this as difficult as possible.
15:07:44 <fdegir> :)
15:07:54 * ChrisPriceAB wonders if he types that out loud :D
15:08:06 <fdegir> tried to save 10 minutes but it seems it didn't help
15:08:14 <maryamtahhan_> :)
15:08:17 <maryamtahhan_> cool
15:08:23 <ChrisPriceAB> hehe, not this time.  Will not be repeated.
15:08:53 <fdegir> uli-k: :)
15:09:29 <dku> at least it gave me enough time to fix my GotoMeeting connection :-)
15:10:52 <dneary> Chair me
15:11:02 <ChrisPriceAB> #chair debrascott
15:11:02 <collabot> Warning: Nick not in channel: debrascott
15:11:02 <collabot> Current chairs: ChrisPriceAB debrascott
15:11:07 <ChrisPriceAB> #chair dneary
15:11:07 <collabot> Current chairs: ChrisPriceAB debrascott dneary
15:11:14 <ChrisPriceAB> #chair uli-k
15:11:14 <collabot> Current chairs: ChrisPriceAB debrascott dneary uli-k
15:11:39 <ChrisPriceAB> #chair debra
15:11:39 <collabot> Current chairs: ChrisPriceAB debra debrascott dneary uli-k
15:11:41 <ChrisPriceAB> #chair rpaik
15:11:41 <collabot> Current chairs: ChrisPriceAB debra debrascott dneary rpaik uli-k
15:12:40 <bryan_att> #info Bryan Sullivan, copper
15:12:51 <maryamtahhan_> #info VSPERF, SFQM Maryam Tahhan
15:13:10 <ChrisPriceAB> #chair debrascott
15:13:10 <collabot> Current chairs: ChrisPriceAB debra debrascott dneary rpaik uli-k
15:13:27 <ChrisPriceAB> #topic Status gathering
15:13:45 <ChrisPriceAB> #info opnfvdocs - building the backlog, not yet updated in Jira
15:13:58 <ChrisPriceAB> #info dovetail - awaiting Jira and repository
15:14:01 <ChrisPriceAB> :D
15:14:13 <uli-k> #info octopus - building the backlog, not yet updated in Jira
15:14:15 <hongbotian> #info bottleneck is building the test case
15:14:16 <fdegir> #info releng - backlog has been created in JIRA and Brahmaputra items have been labelled with R2 for easier query
15:14:16 <KLuehrs> #info Kevin Luehrs - Connectivity Services LSO project
15:14:23 <bryan_att> #info Copper - B release issues defined in Jira
15:14:27 <maryamtahhan_> #info VSPERF - continuing to implement testcases for release B - On Track
15:14:34 <ashyoung> #info ONOSFW
15:14:53 <zhipeng> #info parser working on define issues in Jira for release B
15:14:56 <VikramDham> #info QTIP working on creating JIRA stories & tasks
15:14:59 <maryamtahhan_> #info SFQM - continuing to extended DPDK NIC stats upstream and define a suitable API for this - On Track
15:14:59 <bin_> #info Bin Hu (IPv6)
15:15:06 <anac1> #info yardstick - implementation on-going for release B - on track; jira done
15:15:08 <chenshuai> #info COMPASS continue to implement for release B
15:15:08 <KLuehrs> #info LSOAPI - continuing to implement APIs
15:15:14 <[2]JonasB> #info Fuel-Status. All focus right now is on SR1. Known Backlog for B-release is set. Waiting for integration requests from other B-release projects.
15:15:15 <mdgray> #info mdgray (OVSNFV) - Building backlog
15:15:16 <morgan_orange> #info functest Jira created for B-Release
15:15:24 <bin_> #info IPv6 has defined all tasks and assignments in JIRA
15:16:30 <trozet> #info Apex - nothing in JIRA yet, will do it this week
15:16:38 <RayNugent> #info Ray Nugent
15:16:43 <bin_> #info IPv6 is working on those tasks and assignments. Some have been resolved and closed. Some are work in progress
15:16:44 <ashyoung> #info ONOSFW - Jira task breakdowns nearing completion for milestone C. Coding continues. With date change to Feb, we've now added ML3 plug-in to features.
15:17:14 <KLuehrs> #info LSOAPI - Not in Jira yet
15:17:26 <ChrisPriceAB> #info Task lists are not set up and labelled for opnfvdocs
15:17:27 <uli-k> #info Debra asks projects to notify if not in Jira yet
15:17:32 <dneary> I don't think I have done tasks in Jira yet
15:17:38 <maryamtahhan_> #info SFQM not in JIRA yet
15:17:40 <mdgray> #info OVSNFV - Not it Jira yet
15:17:48 <StuartMackie> #info OpenContrail - Not in Jira yet
15:18:12 <maryamtahhan_> #info VSPERF stories not labelled for Rel B
15:18:20 <ChrisPriceAB> #topic Jira
15:19:58 <ChrisPriceAB> #link https://wiki.opnfv.org/developers/project_proposal_creation_review_checklist Project creation process, including Jira establishment
15:21:25 <dneary> As a contributor to a project, how can I keep track of new Jira tickets reported against a project?
15:21:53 <fdegir> please submit ticket to rt-helpdesk if you're having permission issues with JIRA for the project you-re committer of
15:22:03 <ChrisPriceAB> for issues regarding Jira and roles, please send requests to opnfv-helpdesk@rt.linuxfoundation.org
15:25:44 <dneary> Do I need to do something special to be able to create issues?
15:26:59 <ildikov> dneary: probably you don't have rights if you cannot find the option where it should be
15:27:12 <fdegir> dneary: about your first question
15:27:18 <ildikov> dneary: I mean you need access rights
15:27:36 <fdegir> jira admins need to create JIRA notification scheme
15:27:44 <dneary> ask and you shall receive :-)
15:27:52 <VikramDham> #info what is url to the recording of OPNFV tools training?
15:28:26 * dneary would like to be sure that any project demos/documentation are from the point of view of the first connection - a normal, unprivileged user
15:29:59 <fdegir> maryamtahhan_: please follow this to apply bulk change
15:30:29 <fdegir> open your project page on jira
15:30:48 <ChrisPriceAB> hey VikramDham, we are putting together some guides and training.  I don't think we have anything yet to point to.
15:30:59 <fdegir> open list of all the issues
15:31:06 <fdegir> assuming your project is vswitchperf
15:31:11 <fdegir> this is the list I mean
15:31:13 <fdegir> https://jira.opnfv.org/issues/?jql=project%20%3D%20VSPERF
15:31:27 <fdegir> click tools on upper right corner
15:31:35 <fdegir> and you should see bulk change there
15:31:46 <fdegir> and follow the instructions on screen
15:33:39 <maryamtahhan_> fdegir thanks
15:33:51 <fdegir> np
15:34:32 <mdgray> What was the difference between closed and resolved? I missed that part.
15:35:06 <maryamtahhan_> resolved means you've implemented the story or bug fixes
15:35:21 <maryamtahhan_> closed means the team/tester has accepted the fix
15:35:37 <mdgray> maryamtahhan_ Thanks Maryam :)
15:36:39 <maryamtahhan_> no problem
15:37:13 <fdegir> it would be good to align on 3 things to start with
15:37:24 <fdegir> do the planning in JIRA
15:37:29 <fdegir> use issue type Story for planning the work
15:37:33 <fdegir> label the stories using R2
15:37:45 <bryan_att> The key question is what is "done", I.e. Just issues entered (are these the same as tasks?), or "stories", "tasks", etc. not all may be familiar with these concepts and why they are important
15:38:13 * ChrisPriceAB has to drop off. sorry everyone, my situation here has become untenable.
15:38:23 <ChrisPriceAB> Scribe!!!
15:38:55 <fdegir> bryan_att: story is the main work item type you use for planning purposes in scrum/agile
15:39:04 <fdegir> stories are weighted
15:39:18 <fdegir> and you can see tasks is child items under stories
15:39:27 <debrascott> could use tags on a group of stories for a sprint
15:39:28 <fdegir> dealing with specifics of a story
15:39:53 <bryan_att> I have issues entered and progressing on work toward resolving them. Is it mandated that the issues be further described in stories?
15:40:51 <bryan_att> E.g. If we are not using scrum/agile in a project, but leveraging Jira primarily as a high-level planning tool, do we need to go beyond issues.
15:40:59 <maryamtahhan_> is the recommendation here to add in weights and estimates to the stories we add?
15:41:52 <debrascott> stories are not mandated but a best practice depending on the number of tasks that a project has
15:42:02 <mdgray> The amount of work described by a story, task and epic is kind of arbitrary and will differ between projects. I think different projects will use them in different ways.
15:43:29 <fdegir> bryan_att: if you want people to understand what that work item means
15:43:39 <fdegir> it is better to put description and definition of dones there
15:43:55 <fdegir> if you're a one man project or all the people in your project know what that item means
15:44:00 <fdegir> you can perhaps skip the description
15:44:11 <anac1> it would be good to see the dependencies
15:44:12 <fdegir> but again this will block others to understand what that work item brings
15:46:11 <fdegir> if you want to create links between different work items
15:46:12 <bryan_att> IMO a Jira issue can represent the task description itself. That's how I have been using Jira. I'm not sure of the value of further breaking activity down into tasks or sub-tasks. Again where a project needs that level of coordination it's fine, but I have not intended to spend that much time on the tools, rather just get the work done.
15:46:24 <fdegir> you need to open the issue click the more button and then click the link from options
15:46:33 <fdegir> choose the link type on opening screen
15:46:44 <fdegir> and then type issue no into the box
15:47:05 <mdgray> bryan_att "Just get the work done" +1
15:48:27 <debrascott> Epics can be viewed as container for stories
15:49:29 <hongbotian> usually epic is used to cover more than a week.  a story is used for one week.
15:49:41 <debrascott> Epics contain stories- usually related
15:49:49 <fdegir> usually stories are the work items that fit into sprting
15:49:51 <fdegir> sprint
15:50:02 <fdegir> and sprints can be 1, 2, or 3 weeks long
15:50:05 <morgan_orange> tasks ⊂ stories ⊂ epics
15:50:11 <fdegir> morgan_orange: +1
15:50:17 <fdegir> and epics can span multiple sprints
15:50:35 <fdegir> but stories must be completed in a single sprint
15:50:41 <fdegir> or broken down further
15:50:44 <fdegir> or converted to epics
15:51:34 <debrascott> call helpdesk if you need to get permissions corrected for your project
15:52:25 <uli-k> #info uli-k asks how to progress with the dependencies
15:53:16 <uli-k> #info Debra clarifies that projects should document the dependencies in Jira
15:53:44 <fdegir> bryan_att: breaking tasks further can help others to take some items over
15:54:00 <fdegir> if it can't be broken down, then no need to break it down
15:54:20 <fdegir> again, the items in backlog should potentially be taken over by any team member
15:54:33 <fdegir> and getting things done requires more people's involvement sometimes
15:54:49 <debrascott> contact project lead if there is no task yet to connect a dependency to.
15:55:10 <fdegir> #endmeeting
15:55:15 <uli-k> #endmeeting