================================== #opnfv-meeting: Arno retrospective ================================== Meeting started by ChrisPriceAB at 13:01:09 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-06-11-13.01.log.html . Meeting summary --------------- * sound off (ChrisPriceAB, 13:02:39) * Chris Price (ChrisPriceAB, 13:02:44) * Heather Kirksey (HKirksey, 13:03:21) * Uli Kleber (uli-k, 13:03:28) * LINK: https://etherpad.opnfv.org/p/Arno_retrospective the etherpad currently capturing items (ChrisPriceAB, 13:04:11) * Malla (Docomo) (Malla, 13:04:12) * Jose Lausuch (jose_lausuch, 13:04:21) * Trevor Cooper (trevor_intel, 13:04:40) * introductions (ChrisPriceAB, 13:05:26) * ground rules, be productive, don't blame, bring ideas for improvements (ChrisPriceAB, 13:05:45) * what went welll (ChrisPriceAB, 13:06:31) * #Wenjing CHu (Wenjing, 13:06:55) * heather describes a lot of good feedback from the industry based on being able to ship Arno within 8 months (ChrisPriceAB, 13:07:00) * hujie (hujie, 13:07:04) * Mark Gray (mdgray, 13:07:28) * Heather asks form the teams involved, what went well? (ChrisPriceAB, 13:07:31) * good cross collaboration amongst 4 project teams over the past few months (rpaik, 13:08:10) * Chris highlights the cross team collaboration as a highlight (ChrisPriceAB, 13:08:22) * Jonas adds there was cross project contribution as well, not staying within our "project borders" when contributing (ChrisPriceAB, 13:08:45) * heather asks how we can nuture and promote the good areas (ChrisPriceAB, 13:09:21) * Jose says we should retain the good attitude that we developed to help each other out (ChrisPriceAB, 13:09:55) * LINK: https://global.gotomeeting.com/join/939959397 (uli-k, 13:10:55) * Fatih states that we should continue to contribute to other projects to help drive the project forward. If there are dependencies across projects a contribution to overcome them is the best way to keep moving forward. (ChrisPriceAB, 13:11:15) * Jonas adds that when we set stuctures in the future they continue to helpbuild community rather than building walls/competition (ChrisPriceAB, 13:12:13) * Jose outlines that the functest leader did an excellent job during the project with clear goals and direction. morgan_orange - just to be clear :D (ChrisPriceAB, 13:13:23) * Ray adds that he has seen a lot of good feedback from the industry, and that our start has been very positive when compared to other communities. (ChrisPriceAB, 13:15:28) * ChrisPriceAB added that functest team did a great job of dealing with transitions (rpaik, 13:15:36) * dneary outlines the impact we have had at the recent openstack summit and how we are engaging with upstream communities has been a positive. (ChrisPriceAB, 13:16:04) * Ildikov says the support we have seen on IRC to help bring people onboard has been excellent, well received, and is a value we have in our community to be maintained. (ChrisPriceAB, 13:17:02) * dsmith outlines an "onboarding package" to help get people started in the community would be beneficial (ChrisPriceAB, 13:17:40) * sharing across muitplie projects (integration, requirements, etc.) is another positive (rpaik, 13:19:18) * The Arno release is well publicised on the social media and internet search engines. (ChrisPriceAB, 13:19:18) * etherpad topics around improvements (ChrisPriceAB, 13:20:28) * LINK: https://etherpad.opnfv.org/p/Arno_retrospective etherpad (ChrisPriceAB, 13:20:33) * the burden on a small number of SME' during Arno was highlighted as an issue for our community (ChrisPriceAB, 13:21:00) * some e-mail threads have additionally raised concerns around this area. (ChrisPriceAB, 13:21:25) * consideration: it may not have been clear what skill-sets would be required in OPNFV to engage from our members. (ChrisPriceAB, 13:21:54) * actions: being clear on the areas where we need to increase will help our members and the broader community find the right people to have involved (ChrisPriceAB, 13:22:43) * dsmith notes that resource needs are dependent on goals/targets that community sets (rpaik, 13:23:57) * dsmith agrees there is a need for ODL SME's to help in the community (ChrisPriceAB, 13:24:17) * IP, VLAN & network topology competence is also required (ChrisPriceAB, 13:24:30) * dneary adds that we need people who are in telco operations who are actively deploying applications today and can provide feedback (ChrisPriceAB, 13:25:33) * dsmith adds operational and practical skills are required with the above competences. (ChrisPriceAB, 13:25:55) * Jose adds additional testing competence is required, with broad experience in testing for application deployment scenarios would be valuable. (ChrisPriceAB, 13:26:36) * dsmith adds collaboration with SDO members will continue to be valuable and is something we should promote moving forward. (ChrisPriceAB, 13:27:21) * Debra adds that training and onboarding resources would be helpful (ChrisPriceAB, 13:28:51) * icbts adds that perhaps some OSGI/Karaf people to help with platform issues you see on ODL/ONOS (ie when features/repos/commands/monitoring is required on controllers?) (ChrisPriceAB, 13:29:09) * How do we support Arno? (ChrisPriceAB, 13:29:25) * two onboarding areas: new developers plus new users (rpaik, 13:30:44) * Currently a mailing list exists that shall be used to address support issues, no plan is yet in place to establish a concrete structure (ChrisPriceAB, 13:31:12) * heather asks for additional input as available. (ChrisPriceAB, 13:31:26) * Investigation is ongoing into establishing a spectrometer/stackalytics like solution for project visibility. (ChrisPriceAB, 13:32:37) * Ildikov added that project information to engage in projects and understand them is required to help onboarding new people. (ChrisPriceAB, 13:33:19) * dsmith agrees, more available and clear scope and documents would help as our community fluxes through the year for consistency. (ChrisPriceAB, 13:34:05) * have a look at https://trello.com - used on ODL integration team (icbts, 13:34:26) * any last issues on community (ChrisPriceAB, 13:34:27) * improvements in the requirement projects and handling would be valuable (ChrisPriceAB, 13:35:34) * Project management and handling (ChrisPriceAB, 13:35:57) * Debra asks what went well in project and scope mgmt (ChrisPriceAB, 13:37:03) * dneary outlines that scope definition was something that went rather well. Within 2 months we had a relatively clear idea of our Arno scope. (ChrisPriceAB, 13:37:30) * the scope reduction was contributing factor in being able to deliver (ChrisPriceAB, 13:38:21) * ChrisPriceAB adds that communication on reduced scope could have gone better (rpaik, 13:40:04) * dsmith adds that we did not have an effective change management process for decision making during Arno (ChrisPriceAB, 13:41:11) * and adds that better communication will help reduce friction (ChrisPriceAB, 13:42:03) * dneary adds that in some cases people came away from discussions with different understandings of the outcome of those discussions (ChrisPriceAB, 13:42:50) * ChrisPriceAB thinks this can also be attributed to our backgrounds and not having yet established a common language/understanding (ChrisPriceAB, 13:43:16) * Debra asks if there is a need for change management process (rpaik, 13:44:59) * dneary/ChrisPriceAB then asks what change we are trying to govern. preference is not to be too rigid (rpaik, 13:46:31) * Debra suggests that decision makers on change management could be the project leads (rpaik, 13:47:51) * dneary flags the need to be wary of imposing too much top-down control/benediction of project leaders vs allowing leaders to arise organically as we grow as a community. (dneary, 13:51:23) * Jira is used by most Apache projects, allowing the community to co-ordinate (icbts, 13:51:53) * ChrisPriceAB adds that a structured approach to using Jira may be helpful (rpaik, 13:52:24) * Debra and Jose outline some additional effort is needed to addres risk mitigation when making our plans (ChrisPriceAB, 13:54:35) * Jonas adds that as we did not have a clear idea of the resources available it was very difficult to manage the risk of the scope (ChrisPriceAB, 13:55:06) * Jose outlines that we need to be aware of the active contributors when making plans, the numbers on the wiki may not reflect the activity in the project (ChrisPriceAB, 13:55:50) * Jonas adds that better prioritization also would have been helpful (rpaik, 13:58:00) * dneary adds that successful time based projects manage a release time-ruch by gating early on feature readiness and gating early. (ChrisPriceAB, 13:59:50) * ChrisPriceAB adds that establishing clear milestones and being concise on the meaning of those milestones and qualitifcations will be important (ChrisPriceAB, 14:03:36) * dsmith adds that projects will ahve their own timeline that may or may not coincide with a time based release activity. We need to be clear on the correlation between releasing and content (ChrisPriceAB, 14:04:35) * Ildikov states she thinks it is acceptable to set our release date based on upstream dependencies rather than trying to stay to a completely time based release cycle. (ChrisPriceAB, 14:07:16) * Julien (julien_ZTE, 14:08:04) * zhifeng (zhifeng, 14:11:31) * project resources (ChrisPriceAB, 14:15:44) * Debra asks what went well in Arno and where we can get improvement moving forward (ChrisPriceAB, 14:16:28) * zhipeng (zhipeng, 14:16:51) * dsmith states due to the various timezones effective communications are needed and how each team can relate to each other (ChrisPriceAB, 14:17:09) * more analysis/process needs to be done to make decisions on our release process moving forward (wrapping up the project schedule topic…) (rpaik, 14:17:25) * fdegir adds that Octopus resource was an issue and had to borrow poeple from other projects (rpaik, 14:20:09) * Rajeev Koodli (rajeev, 14:22:16) * dsmith to send email on what additional support may be necessary for the LF labs (rpaik, 14:26:32) * Iben ask if there is a way to automate a lot of activities on the LF hardware (rpaik, 14:28:47) * There was a discussion about release cadence, and how features will make it from upstream into a release (dneary, 14:29:48) * dneary made the point that there is not a shared understanding of what a "release" means, what release artifacts the project will create, or even what it means to be in a release (dneary, 14:30:24) * ray wraps up, this will be updated on the wiki (ChrisPriceAB, 14:30:30) * There are many installer projects, multiple SDN related projects, not all with the same functionality, and in that context, there is not a shared understanding of what an OPNFV release *is* (dneary, 14:31:10) Meeting ended at 14:31:16 UTC. People present (lines said) --------------------------- * ChrisPriceAB (78) * rpaik (20) * dneary (12) * collabot (9) * uli-k (4) * icbts (3) * mhaugh (2) * trevor_intel (1) * julien_ZTE (1) * mdgray (1) * Malla (1) * hujie (1) * rajeev (1) * zhipeng (1) * HKirksey (1) * jose_lausuch (1) * zhifeng (1) * Wenjing (1) * Debra (0) Generated by `MeetBot`_ 0.1.4