Open Stack

Hello Everyone,

We discussed Ussuri goals in Forum as well as in PTG. I would like to summarize the discussions here.

* Forum[1]:
Three goals were discussed in details:
1.  Drop Python 2.7 Support
We discussed keeping the CI/CD support for Swift which is the only project keeping the py2 support.
Swift needs the devstack to keep installing on py2 env with the rest of the services on py3 (same as old jobs when Swift
was on py2 by default on devstack). There is no oslo dependency from swift and all the other dependency will be capped
for py2 version. 

Requirements check job currently checks that if openstack/requirements list two entries for a requirement
(one for <=2.7 and one for >) that the repo under test also has both entries.  smcginnis already pushed the changes[2] to
handle dual python version requirements. 

Everything else will go as discussed in ML[3] and this is already accepted as Ussuri goal[4]. 

2. Project Specific New Contributor & PTL Docs
- As per feedback in Forum sessions, this is a good goal which will make documentation more consistent. All the
projects should edit their contributor.rst to follow a more complete template and adjust/add PTL documentation.
- This is accepted as a pre-approved as Ussuri goal
- Kim Hindhart is working on getting EU funding for people to work on OpenStack and they like consistent documentation.
- diablo_rojo already updated the goal proposal patch and it is up to get wider feedback. 

3. Switch remaining legacy jobs to Zuul v3 and drop legacy support
- Grenade job is not yet on zuulv3 which is required to finish first.
- Few projects waiting for big projects finishing the zuulv3 migration first.
- This needs more work and can be a "pre-approved" thing for V, and this would be split to focus on
the Grenade work in U. 

Other than above 3 goals, there were few more ideas for goal candidate and good to go in goal backlogs etherpad:

- cdent: stop using paste, pastedeploy and WSME
Note from Chris: This does not need to be a community goal as such but requires the common solution from TC
WSME is still used, has contributions, and at least a core or two

- cmurphy: Consistent and secure default policies
https://etherpad.openstack.org/p/PVG-keystone-forum-policy
Going with pop-up team first

- support matrix documentation to be consistent across projects.
going with pop-up team (fungi can propose the pop-up team in governance) first
Richard Pioso (rpioso) to help fungi on this
once consistent framework is identified, the pop-up team can expire with the approval of a related cycle goal
for implementing it across remaining projects

* PTG[5]:
We all agreed to select the Ussuri goal asap because the Ussuri cycle already started and projects are waiting for
the final goals. TC discussed this further in PTG and agreed on below two goals to be selected as the Ussuri goal.
1.  Drop Python 2.7 Support - Already Accepted. 
2. Project Specific New Contributor & PTL Docs - Under Review

Goal "Switch remaining legacy jobs to Zuul v3 and drop legacy support" will be pre-selected for V cycle, that does
not mean to stop the review on proposed goal or any ongoing work. All ongoing efforts will continue on this.  

[1] https://etherpad.openstack.org/p/PVG-ussuri-goal-forum
[2] https://review.opendev.org/#/c/693631/
[3] http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010371.html
[4] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html
[5] L76 https://etherpad.openstack.org/p/PVG-TC-PTG

-gmann