Open Stack

 ---- On Thu, 24 Sep 2020 03:45:38 -0500 Lajos Katona <katonalala at gmail.com> wrote ----
 > Hi,I would like to selectively respond to the number of goals per cycle question.
 > A possible direction could be to forget the "one cycle goal" thing and allow to finish the goals in a longer time frame. From "management" perspective the important is to have a fix number of goals per cycle to avoid overallocation of people.
 > Another approach could be to attach a number, a difficulty feeling or similar to the proposed goals to make it easier to select them, and avoid to choose 2 hard-to-do goal for one cycle.This numbering can be done by project teams/PTLs whoever has the insight for the projects.Example: zuulv3 migration can be a hard to do goal as affects the whole gating of a project with hard coordination between projects.Add healthcheck API is much simpler as can be done without affecting the life of a whole project, or the community.

+1 on these feedback. 

 > A possible direction could be to forget the "one cycle goal" thing
This is much needed for complex goal or need more work like OSC one, we have
not done yet but we discussed the possibility of multi-cycle goal in last cycle.
We can add the framwork/guidance for multi-cycle goal like it has to be devided
by work to be done or by projects(like target set of projects per cycle).

-gmann

 > RegardsLajos Katona (lajoskatona) 
 > 
 > Graham Hayes <gr at ham.ie> ezt írta (időpont: 2020. szept. 21., H, 19:54):
 > Hi All
 > 
 > It is that time of year / release again - and we need to choose the
 > community goals for Wallaby.
 > 
 > Myself and Nate looked over the list of goals [1][2][3], and we are
 > suggesting one of the following:
 > 
 > 
 >   - Finish moving legacy python-*client CLIs to python-openstackclient
 >   - Move from oslo.rootwrap to oslo.privsep
 >   - Implement the API reference guide changes
 >   - All API to provide a /healthcheck URL like Keystone (and others) provide
 > 
 > Some of these goals have champions signed up already, but we need to
 > make sure they are still available to do them. If you are interested in
 > helping drive any of the goals, please speak up!
 > 
 > We need to select goals in time for the new release cycle - so please
 > reply if there is goals you think should be included in this list, or
 > not included.
 > 
 > Next steps after this will be helping people write a proposed goal
 > and then the TC selecting the ones we will pursue during Wallaby.
 > 
 > Additionally, we have traditionally selected 2 goals per cycle -
 > however with the people available to do the work across projects
 > Nate and I briefly discussed reducing that to one for this cycle.
 > 
 > What does the community think about this?
 > 
 > Thanks,
 > 
 > Graham
 > 
 > 1 - https://etherpad.opendev.org/p/community-goals
 > 2 - https://governance.openstack.org/tc/goals/proposed/index.html
 > 3 - https://etherpad.opendev.org/p/community-w-series-goals
 > 4 - 
 > https://governance.openstack.org/tc/goals/index.html#goal-selection-schedule
 > 
 >