Looking at Hadoop's bylaws https://hadoop.apache.org/bylaws.html
They have this: Significant, pervasive features are often developed in a speculative branch of the repository. The PMC may grant commit rights on the branch to its consistent contributors, while the initiative is active. Branch committers are responsible for shepherding their feature into an active release and do not cast binding votes or vetoes in the project. I would like to have something similar in our bylaws where we can have feature branches with their own set of committers. We may have prototype-grade features that need to be rapidly evolved with the feedback from the community. So we would need a lighter process to evolve these features rapidly, while still keeping the community involved. A more rigorous review process can then be applied when the feature is more mature and is ready to be committed into master. What do you think? ------------------- Thank you, James Sirota PPMC- Apache Metron (Incubating) jsirota AT apache DOT org
