Difference between revisions of "Meetings/product-team"
< Meetings
(→Jun 12th, 2017 (Monday @ 2100 UTC) Product Team Meeting Agenda) |
|||
Line 1: | Line 1: | ||
− | = Jun | + | = Jun 19th, 2017 (Monday @ 2100 UTC) Product Team Meeting Agenda = |
* Review of action items | * Review of action items | ||
− | ** Arkady_Kanevsky and AndyU to | + | ** Arkady_Kanevsky and AndyU to schedule a web meeting for AR1 |
− | ** mrhillsman and AndyU | + | ** Leong to email if anyone from PWG is attending PTG and if a WG meeting is needed |
− | ** all to review existing+wip proposals and decide which one is ready to move forward with wider participation from PTL/core | + | ** Leong to ask PWG if need to organize midcycle, colocated with Ops Midcycle at Mexico |
+ | ** all to review Moderator Guide and provide feedback to mrhillsman and AndyU | ||
+ | |||
+ | * Development Proposals review | ||
+ | ** [Action] all to review existing+wip proposals and decide which one is ready to move forward with wider participation from PTL/core | ||
+ | ** https://review.openstack.org/#/q/project:openstack/development-proposals+status:open | ||
+ | |||
+ | * OpenStack Boston Forum | ||
+ | ** [Action] All please look at the hashtag results and sign up for the data-mining | ||
+ | ** https://etherpad.openstack.org/p/PWG-forum-analysis | ||
+ | ** https://github.com/openstack/development-proposals/tree/master/forum/201705-bos | ||
+ | |||
* Action Plan | * Action Plan | ||
+ | ** PWG Review | ||
+ | *** Given the limited resource we have, how can we make the Development Proposal process easier to be consumed/executed by other WG. | ||
+ | *** What's the next step to get more engagement/support from TC/PTL/Core | ||
** Value 1: Properly documenting ideas, getting a structured workflow, and integration into development workflow | ** Value 1: Properly documenting ideas, getting a structured workflow, and integration into development workflow | ||
** Value 2: Periodic coordination/collaboration across WGs/Product Managers | ** Value 2: Periodic coordination/collaboration across WGs/Product Managers | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Open | * Open | ||
Revision as of 16:18, 19 June 2017
Jun 19th, 2017 (Monday @ 2100 UTC) Product Team Meeting Agenda
- Review of action items
- Arkady_Kanevsky and AndyU to schedule a web meeting for AR1
- Leong to email if anyone from PWG is attending PTG and if a WG meeting is needed
- Leong to ask PWG if need to organize midcycle, colocated with Ops Midcycle at Mexico
- all to review Moderator Guide and provide feedback to mrhillsman and AndyU
- Development Proposals review
- [Action] all to review existing+wip proposals and decide which one is ready to move forward with wider participation from PTL/core
- https://review.openstack.org/#/q/project:openstack/development-proposals+status:open
- OpenStack Boston Forum
- [Action] All please look at the hashtag results and sign up for the data-mining
- https://etherpad.openstack.org/p/PWG-forum-analysis
- https://github.com/openstack/development-proposals/tree/master/forum/201705-bos
- Action Plan
- PWG Review
- Given the limited resource we have, how can we make the Development Proposal process easier to be consumed/executed by other WG.
- What's the next step to get more engagement/support from TC/PTL/Core
- Value 1: Properly documenting ideas, getting a structured workflow, and integration into development workflow
- Value 2: Periodic coordination/collaboration across WGs/Product Managers
- PWG Review
- Open
Information on previous agendas: https://etherpad.openstack.org/p/pwg_previous_agendas