> On 31 Jul 2019, at 12:52, Julien Grall <julien.gr...@arm.com> wrote: > >> To move forward: >> * There should be a policy discussion > > How should I raise it? Do you want a patch again contribution-guidelines?
I think we should start with an e-mail thread with an appropriate title on xen-devel@ (CCing committers@) outlining * What the proposal is and why it is important - How we document it is secondary and I am happy to pick this up after there is agreement * How it would be implemented - e.g. if the proposal was to reject e-mails with a disclaimer, we need to have a mechanism that does this reliably and also informs senders why a mail was not posted. We wouldn't want xen-devel@ to become a black hole, where stuff from some people gets lost without It then would have to go through a vote as normal. You may want to have a chat to Ian Jackson on IRC: he has some opinions and experience that is applicable I just agreed with Ian, that there will be a similar discussion related to the 2 step process to change maintainers via unsupported status, which also was highlighted in this thread. Although this can probably just be a patch to MAINTAINERS Regards Lars _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
