Hi,
On 4/21/23 10:47, Daniel P. Berrangé wrote:
I agree with most of your points, but I wanted to comment on the Change
process.
(...skipped a lot...)
First, I’d like to move the Changes discussion. They will still be
posted to devel-announce, but responses directed to Project Discussion
in a new #changes tag. Ben tells me that this is a FESCo decision,
which seems reasonable.
Early you mentioned that lots of teams have moved discussions into
tickets in Pagure/GitHub/etc. I think that is an entirely natural
thing to do for task oriented discussions.
I think that Change proposals are precisely that - a task oriented
discussion, and thus would naturally fit into issue tracker model.
You then have the associated tools for tracking, tagging the changes,
linking between related tickets, and more, all in one place. The
way we use wiki categories to tag Change proposal pages, and then
have to have discussions somewhere else entirely, is effectively
reinventing a poor-mans' issue tracker. Just use a real issue tracker
here and stop splitting the process around multiple tools.
I think the issue with the Change process is that while the change
itself is a task, its discussion has a property of generating
sub-threads and sidetracks going in all directions, which shape the rest
of the fedora-devel discourse.
So while from the execution point of view having it in the issue tracker
makes a lot of sense, from the communication point of view Change
discussion is a seed, which when planted on a forum can create a whole
forest.
The hope is that forum tooling can be used to split the subthreads and
to let them live on their own. So instead of strict moderation of the
conversation in the issue tracker, which would be required to keep it on
point, we will allow conversations to spread out but in a way that you
have a possibility to choose your track.
P.S. It is funny how even though I consider myself a "seasoned" Fedora
Contributor, every time I send a mail to a mailing list, I still go to a
Hyper-Kitty interface to verify that I did everything correctly.
--
Aleksandra Fedorova
bookwar
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
