On 23/08/18 22:43, Ben Cotton wrote:
Hi community,
We've traditionally used the wiki for Change proposals because it's
the tool we had. But, it's not necessarily well-suited to the purpose.
But now we have Pagure, which can help address some of the
shortcomings of using the wiki: poor scriptability, no reporting, and
a lot of copy/paste.
So I've come up with a plan that would use Pagure instead:
https://fedoraproject.org/wiki/User:Bcotton/UsePagureForChanges
You can read the full details on the wiki page above, but the general
idea is that we won't change the policy for Changes, just how we store
and manipulate them. My intent is to make it nearly seamless for the
community while giving us a platform for building on the process in
the future. Note that this would run parallel to Bugzilla for a
release or two and then replace Bugzilla for Changes tracking.
Even though I'm not as active here as I would like to be, I generally like
this idea.
A few things which would be good to sort out are:
* Still requires changes be represented in three different Pagure repos
* We lose edit history if a change proposal is updated based on feedback
From my point of view, those are the most critical ones. The history is good
when you want to see if/how things changed - to learn from specific changes
which went well or really bad. Not having a history to base it on makes this
learning somewhat more difficult - as you don't know exactly how a change
proposal did develop, just the final result.
Also having changes represented in three different repos sounds a bit too
bureaucratic to me. Processes are good to have, but in the moment they get
too complicated people will generally try to avoid them. If it is really
needed to involve three repos, then a decent tooling on top of it is needed at
launch time; to hide this bureaucratic process a bit.
Other than that, I think this idea makes perfect sense. The first time I did
a change proposal (not even system-wide), it felt like an odd process ("Is
this the right template? In a wiki? Have I filled out all the proper fields
correctly? How is this proposal picked up and distributed properly?" are some
of the thousands questions which popped up).
--
kind regards,
David Sommerseth