Like expressed earlier, that loosely way of interpreting ASF guidelines has led to the situation that the board charges newly established projects to define its bylaws. Charges that are then disregarded by the project and not followed up on by the board and or the appointed VP of the project.
It is such that makes the determination of 'doing the right thing, doing it the right way' less credible in stead of more. The show flake falling down at the top of the mountain creates the avalanche in the valley. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Jul 6, 2015 at 1:25 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Mon, Jul 6, 2015 at 11:38 AM, Pierre Smits <pierre.sm...@gmail.com> > wrote: > > ...The latest posting by Jan proves the point of the necessity of good > > per-project bylaws when it comes to deviating from the generic guidelines > > of the ASF... > > But as others have said, the best is to stick to those guidelines and > use the default bylaws, unless it's absolutely necessary to do things > differently. > > -Bertrand >
