[openstack-dev] [tc][goals] tracking status of old goals for new projects

[Doug Hellmann]

There is a patch to update the Python 3.5 goal for Kolla [1]. While
I'm glad to see the work happening, the change adds a new deliverable
to an old goal, and it isn’t clear whether we want to use that
approach for tracking goal work indefinitely. I see a few options.

1. We could update the existing document.

2. We could set up stories in storyboard like we are doing for newer
goals.

3. We could do nothing to record the work related to the goal.

I like option 2, because it means we will be consistent with future
tracking data and we end up with fewer changes in the governance repo
(which was the reason for moving to storyboard in the first place).

What do others think?

Doug

[1] https://review.openstack.org/#/c/557863/

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.opens

[Jeremy Stanley]

On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote:
[...]

Post by Doug Hellmann
3. We could do nothing to record the work related to the goal.

[...]

For situations like 557863 I think I'd prefer either the status quo
(the kolla deliverable _was_ already listed so it could make
sense to update it in that document) or option #3 (the cycle for
that goal is already well in the past, and certainly adding new
deliverables like kolla-kubernetes to a past goal sets unrealistic
expectations for future goals regardless of where we track them).

I really do, though, think we should simply accept that these goals
don't always (or even usually?) reach 100% coverage and that at some
point we need to be able to consider better means of keeping track
of, e.g., which deliverables work on which Python versions. The
goals process is excellent for reaching critical mass on such
efforts, but should not be considered a source of long-term support
documentation.

[Thierry Carrez]

Post by Doug Hellmann
There is a patch to update the Python 3.5 goal for Kolla [1]. While
I'm glad to see the work happening, the change adds a new deliverable
to an old goal, and it isn’t clear whether we want to use that
approach for tracking goal work indefinitely. I see a few options.
1. We could update the existing document.
2. We could set up stories in storyboard like we are doing for newer
goals.
3. We could do nothing to record the work related to the goal.
I like option 2, because it means we will be consistent with future
tracking data and we end up with fewer changes in the governance repo
(which was the reason for moving to storyboard in the first place).
What do others think?

I don't have a strong opinion, small preference for (2). At the end of
the cycle, the goal becomes just another story with leftover tasks.