Branko, I am confident that the existing project with bylaws, policies and/or standing rules formalised has had its share of discussions regarding applicability of elements therein.. And have resolved those. I guess that when such an element is either to vague or to restrictive so that the situation becomes untenable to move things forward, the community will find ways to resolve it.
This thread is about: - why does the Board tasks projects to create a set of bylaws for some graduating podlings (when so many seem to feel that it doesn't add value); - and when it does, why doesn't it follow up on the task or request the VP of the project to report on its progress until the task is completed. It has to come from somewhere. It seems to come to light during the incubation phase. Don't mentors advice properly? 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 Tue, Jul 7, 2015 at 3:11 PM, Branko Čibej <br...@apache.org> wrote: > Pierre, I could find any number of euphemisms to say the same thing, but > I prefer to say what I mean and not beat about the bush. > > To give you an idea where my disgust comes from: Every project here that > I know of that has bylaws about decision-making has some kind of > fundamental problem and constant tensions in the community. Now some > people may think that extra rules serve to keep problems in check, but > IMO they just make things worse. > > -- Brane > > > On 06.07.2015 23:40, Konstantin Boudnik wrote: > > That's called 'difference of opinions'. Nobody is entitled to like > others' > > viewpoints. In fact, there are certain viewpoints that hardly can cause > > anything but regurgitation in a sane human being. On the hand, no one can > > denied anyone a right to express their opinions. > > > > Cos > > > > On Mon, Jul 06, 2015 at 12:10PM, Pierre Smits wrote: > >> Thank you, Branko. I feel (somewhat) sorry for you, when I read your > >> statement of being disgusted by the viewpoint of others on the matter. I > >> hope you recover from it soon. > >> > >> 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 10:51 AM, Branko Čibej <br...@apache.org> wrote: > >> > >>> On 04.07.2015 18:34, Pierre Smits wrote: > >>>> Having done a cursory review of the incubator reports to the board for > >>>> this year (January till May/June 2015), I found that only the SAMOA > >>>> podling reported working on a project set of bylaws, which without > >>>> knowing details could encompass and/or incorporate the code of > conduct. > >>> I find myself disgusted by this widespread assumption that each project > >>> needs its own bylaws. WTF for? Are not ASF policies and practices > enough > >>> for everyone? What sort of bylaws could you possibly invent that are > >>> both a useful extension of these policies and practices /and/ are not > >>> applicable to other projects? > >>> > >>> Per-project bylaws are just a tool for fragmenting the ASF community, > in > >>> other words, they're a bad idea; paper-shuffling at its most useless. > >>> > >>> -- Brane > >>> > >
