> No, Chris. You have this entirely wrong, so you can just stop with the > nonsense. There is no rule "as soon as they graduate". The rule is "they > can operate according to standard Apache governance". YOU are swooping in, > and trying to impose your perceptions of rules and governance. You are not > a PMC member, and have no basis to impose your thinking upon this > community. Point out things to correct, but your commentary is unwarranted, > uninvited, and unwelcome.
It was my expectation that the first Petri graduate out of the gate would have some growing pains - not because Petri does things "wrong", but because the Incubator has years of process/playbooks/crank-turning and so some things get caught earlier just due to that. I'm, of course, an outsider both to BuildStream and to Petri, so my commentary might also be unwelcome. But I see Chris' comments as an important part of honing that process to ensure that projects that come out of this parallel workstream are as well prepared for life at the ASF as projects that come out of the Incubator. Chris' eye for detail is something that I have appreciated over the years. Meanwhile, what's important here, IMHO, is that both BuildStream and Petri be open to criticism, and to correcting missteps - and that's certainly what I'm seeing in this thread so far. This is an important part of us all coming to trust the new Petri process. I expect that BuildStream is going to get scrutiny that other projects don't have to endure, and I, for one, appreciate Tristan's willingness, so far, to take this constructive criticism and act on it.
