This sounds interesting but as a community user[1] my biggest complaint is not knowing 1) when an issue will be worked on, and 2) how to influence the priority.
As an example, take the story 2602[2]: As a user, I want docker repos to have "mirror on sync". It's difficult for me, not being in all the meetings and plannings, to know if this issue will ever be addressed. Will a roadmap be tied to specific issues for the plugins? Will there be a way for casual consumers of the plugin to influence priority? An example of a roadmap that I've found useful is openshift's[3]. It doesn't necessarily help me with all the issues, or if an issue will ever be worked on, but is a nice quick overview. Looking forward to hearing more! [1] To be fair, a dev on foreman/Sat-6 with a vested interest in container images [2] https://pulp.plan.io/issues/2602 [3] https://ci.openshift.redhat.com/roadmap_overview.html On Mon, Oct 16, 2017 at 4:17 PM, Robin Chan <[email protected]> wrote: > Hello, > > During our internal Pulp meeting this year, we discussed creating a > roadmap for plugins. I would like to capture our discussion and ask for > feedback so that we can start working on our first few roadmaps for > plugins. We hope that this will be an iterative approach to planning and > creating roadmaps, extending it to other plugins or core if they are > helpful. > > *Why? - What will a roadmap help do?* > Communicate relative priority of work for a plugin > Determine MVP (for Pulp 3) for a plugin > Help identify dependencies on work outside of the plugin > Capture architectural decisions especially when departing from past Pulp 2 > implementations (was this implied in conversation? writing this out is > good.) > Provide direction with the understanding that work planned farther in > future is subject to change. > > > *What* > EPIC level descriptions of work - so not user stories, not tasks, not use > cases. > Describe major functionality delivered in an order > Use y release descriptions for EPICs > > What did I forget to add? What else would be helpful to add to a roadmap, > take away, or state that it would be described/accounted for elsewhere? > > Thanks, > Robin > > > _______________________________________________ > Pulp-dev mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
