Hi David, I appreciate your concerns, and I agree that the community like any other open source project has room for improvement. It's great to hear that you want to contribute and we're trying to make this easier for all within the project. As such, we are in the process of setting up a TAB to help address these concerns and minimise bikeshedding where possible. I hope that once we have a full TAB, problems such as these will be quickly resolved so that everyone can move forward. Please rest assured that this is a top priority but will take some time to set up, as with any other major change.
I will be speaking to the conduct team this week to fast-track this process, and as soon as I have details to share I will let everyone know. It's important to note that we are continuously making improvements to help Xen become healthy, such as refreshing governance policies and implementing informal voting procedures. These are just a snippet of a few initiatives being run in the community and I would like to ask that you give the community a chance to show the incremental progress we are making. Many thanks, Kelly Choi Community Manager Xen Project On Mon, Dec 11, 2023 at 5:12 PM David Woodhouse <dw...@infradead.org> wrote: > On Fri, 2023-12-01 at 10:27 +0000, George Dunlap wrote: > > > > FWIW I think a "five-point survey" would probably have been somewhat > better: > > > > Regarding the review insisting that the word "broken" be removed from > > the updated documentation to the old hypercall: > > (✔) I think this sort of enforcement is unreasonable and is harming the > community > > Honestly, this latest example just epitomises the reason I've dedicated > the last two years of my life to hosting Xen guests on something > *other* than Xen itself. > > I *want* to contribute, to help make Xen better. We have code we'd love > to give back. I'd love to see Xen upstream supporting live update and > guest transparent live migration (oops, even that term got gratuitously > bikeshedded, didn't it?) > > But I cannot, and will not, subject my engineers to this. > > I've even got long-time Xen contributors on my team saying that they're > done with it. I certainly can't ask junior engineers to operate in this > environment. > > I don't say this to be combative. I genuinely want the Xen community to > improve and to become as welcoming and productive as it can be. > > Perhaps we do need a TAB to help keep things working smoothly, and help > stamp out the problematic behaviour? This isn't healthy. >
