The danger of what is happening now is that it will become grandfathered in with no proper workflow in place, no proper criteria for processing changes, and no clear documentation that helps committers or the public to contribute.
We have to decline any attempt to include an test framework code until requirements are in place. People must understand that any they are working on now will not be permitted to enter the repositories until we can verify it against an agreed to set of requirements.
I don't know what the extent of the risk is. There is one pending change with regard to workflow logic. I think that this particular change is reasonable and not a hostile takeover. But it leaves you to wonder what else could come???? I definitely have a lack of trust.
What do we have to do? A PMC vote to put a halt and finish the workflow?
I don't think we have the authority force anyone to stop work. But we can prohibit anything from entering the repositories prior to the requirements definition and without approval.
I could finish the the document in a day by simply combining the existing materials, resolving conflicts, and filling some missing logic. But I need to have the confidence of the PPMC. I am not the kind of person who would push ahead without concurrence.
I am persistent (if no one has noticed), but I do not take liberties. Greg
