Could you please show us example of such change proposal? I somehow cannot imagine the real benefit. V. Dne 23.8.2018 v 22:43 Ben Cotton napsal(a): > 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. > > Because we're already moving with changes for Fedora 30 and because a > few Pagure features would make it smoother (primarily allowing issue > submitters to edit metadata), I'd like to implement this for Fedora > 31. Before that, I'd like the community's feedback. > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/IVURLPA523CQJSONM5MOW2U7KCSWAKNY/
