On Tue, May 05, 2020 at 03:28:25PM -0400, Ben Cotton wrote:
> churchyard suggested we add a "Feedback" section to the Change
> proposal template[1]. I see two benefits to this:
>
> 1. It provides FESCo a useful summary of the community feedback (and
> in particular the r
On Wed, May 06, 2020 at 04:53:58PM +0200, Miro Hrončok wrote:
> On 06. 05. 20 16:31, Ben Cotton wrote:
> >On Wed, May 6, 2020 at 4:03 AM Vít Ondruch wrote:
> >>I don't know, I am somewhat ambivalent on this. I am not sure who is
> >>going to collect the feedback there. Will it be the owner of the
On 06. 05. 20 16:31, Ben Cotton wrote:
On Wed, May 6, 2020 at 4:03 AM Vít Ondruch wrote:
I don't know, I am somewhat ambivalent on this. I am not sure who is
going to collect the feedback there. Will it be the owner of the change
or somebody else?
The owner of the change would be responsible
On Wed, May 6, 2020 at 4:03 AM Vít Ondruch wrote:
>
> I don't know, I am somewhat ambivalent on this. I am not sure who is
> going to collect the feedback there. Will it be the owner of the change
> or somebody else?
The owner of the change would be responsible for it, but they may
delegate that
I'm not the author of the proposal, but my take on this:
On Wed, May 06, 2020 at 10:02:19AM +0200, Vít Ondruch wrote:
> I don't know, I am somewhat ambivalent on this. I am not sure who is
> going to collect the feedback there. Will it be the owner of the change
> or somebody else? What will be
" tab/feature of the
wiki instead?
Or wouldn't it be better to include the devel ML reference?
Vít
Dne 05. 05. 20 v 21:28 Ben Cotton napsal(a):
> churchyard suggested we add a "Feedback" section to the Change
> proposal template[1]. I see two benefits to this:
>
> 1. It
On Tue, May 05, 2020 at 03:28:25PM -0400, Ben Cotton wrote:
> churchyard suggested we add a "Feedback" section to the Change
> proposal template[1]. I see two benefits to this:
>
> 1. It provides FESCo a useful summary of the community feedback (and
> in particular the r
churchyard suggested we add a "Feedback" section to the Change
proposal template[1]. I see two benefits to this:
1. It provides FESCo a useful summary of the community feedback (and
in particular the reasoning behind rejecting alternatives) to simplify
the voting process
2. I
churchyard suggested we add a "Feedback" section to the Change
proposal template[1]. I see two benefits to this:
1. It provides FESCo a useful summary of the community feedback (and
in particular the reasoning behind rejecting alternatives) to simplify
the voting process
2. I
