I agree with Ina regarding some form of deadline to keep issues from
falling by the wayside. I know we're not *really* doing Agile, but both
Kanban and Scrum have points or "pull from the top of the stack" features
to ensure that less appealing issues are not passed up repeatedly. I see
it kind o
W/r to stakeholders needs. We have dedicated people on our team who closely
work with the stakeholders, therefore both of the parties are in agreement
on:
1) what needs to get done
2) by when #1 needs to get done
In my understanding if there are some uncertainties about some work then 1)
it was n
From a tooling perspective:
we have had good success in the past with fully defining and designing a
feature in a Redmine Story. The story (description) provides a good way
to capture (and edit) the overall design and (comments) support a
discussion history. Then, the implementation can be b
Brian,
To bring this back to your original question, here are some comments in
line.
Agree w/#1 - I have observed a few different ways that this problems has
been solved by developers. The requirement here is "I need a way to
understand all the work and deliverables associated with a feature." Th
I'd also like to propose formal Project Technical Lead and a formal
Project Community Lead roles to be able to decide in case of competing
(technical) ideas or planning priorities.
These would have to be time-boxed (half a year) and folks would elect
the leader for a period based on leader's progra
I agree the decision process for core itself needs discussion. For now, I'm
only able to offer facilitating a convo that focuses on the communication
aspects not the decision process. I would like to improve the transparency
into the features that will and won't be in any given release for our
stak
I agree with the problems that Brian listed, but I hope we can focus on the
decision making process itself in addition to how those decisions are
communicated.
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
Brian,
thanks for the proposal!
I've been considering a similar one for some time.
On Thu, Mar 29, 2018 at 9:13 PM, Brian Bouterse wrote:
> I want to start a discussion around how Pulp does roadmap planning and some
> of our current challenges. This is the pre-discussion part of a future PUP.
>
