Re: Guile & Fesco requiring package maintenance work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kevin Fenzi <kevin@xxxxxxxxx> writes:

> https://fedoraproject.org/wiki/FESCo_meeting_process
>
> "Make sure to check with and invite stakeholders who may not be CC'd in
> the issue. Consider deferring issue if stakeholders have not had
> adequate notice and are not available for discussion."
>
> Perhaps it should be more explicit in how to "check with and invite"?

Not sure about that cc:-on-the-issue condition.  There appears to be no
systematic notification *in the issue* that the topic is on the next
agenda, so people on the cc: list are not automatically invited.
There's also no notification in the wiki Change page, so those watching
that don't know either.  Can this get fixed?  Those two bits of extra
process might be enough to ensure that change proponents feel invited.

- FChE
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux