So I link to a document and say it contains the list of immutable items, acknowledge it is merely a signpost, and request contributions.
Your response "that's not good enough", hmmmm.... Marvin you undertook to do the release requirements doc. You did huge amounts of work on it. All that is needed is to make it official. You do that back getting VP Legal to approve it. VP Legal might ask the board for input, but he doesn't need to. He has the authority to just approve it. There can be no dissenting voices, he is the deadlock breaker. If the membership don't like the decision they petition the board to remove him. If the board don't do so the membership calls a members meeting to replace the board. Like I said elsethread there is no hierarchy here unless a big stick is needed. But don't expect the one with the stick to wield it without there being an identified need. That would be overstepping the cultural objective of no leaders. I use your work only as an example. I'm not picking on you, I'm actually acknowledging your contribution to the intended process - thank you. Maybe someone will finalize the doc and ask VP Legal to approve it. Sent from my Windows Phone ________________________________ From: Marvin Humphrey<mailto:mar...@rectangular.com> Sent: 1/10/2015 12:05 PM To: general@incubator.apache.org<mailto:general@incubator.apache.org> Subject: Re: What is "The Apache Way"? On Fri, Jan 9, 2015 at 12:01 PM, Rich Bowen <rbo...@rcbowen.com> wrote: > On 01/09/2015 02:03 PM, Jim Jagielski wrote: >> >> Another way to look at the Apache Way is as a musical composition. >> Sure, it was written for a specific arrangement, but sometimes >> it's played as a jazz piece, other-times as a classical, or maybe >> with a blues flavor. But it is always (or*should be*) recognizable. >> If you*don't* recognize it, then you've taken the "interpretation" >> too far, if you get my meaning. > > What a delightful analogy. > > Of course, you're always going to get people who say that a disco > rendition is fine, and others who say it's blasphemous. >From my perspective, that explanation of The Apache Way was fine, but completely unhelpful. Similarly, a "signpost" document collecting links is no more useful in establishing the boundaries of Apache's project requirements than countless other incomplete, unofficial resources. The willingness of a Board member or other authority to provide answers to specific questions is marginally helpful -- until contradictory answers are provided by a competing authority. Somewhere out there in the vast wasteland of Apache's websites and mailing list archives, there exist requirements that Apache projects *must* fulfill or face sanction by the Board. Theoretically there are not many absolute requirements, but learning all of them is literally impossible: there is no authoritative document setting limits on what Apache expects of its projects. Determining what you can get away with at Apache entails digging through huge scrap heaps of documentation and picking the brains of various unreliable oracles. It's maddeningly laborious and slow, and ultimately you can never have much confidence in the answers you unearth. I don't place much value on giving the Board so much flexibility. My sympathies lie with the poor slobs trying to figure out where Apache's rules begin and end -- and with those who build strong communities according to their own good faith interpretation of The Apache Way, only to face censure because their interpretation turned out to be "wrong". Maintaining the Board's flexibility to pass judgment while denying those it oversees the rule of law is a poor tradeoff. It is incredibly inefficient, and it makes the Incubator's mission untenable. Even if the Board makes good calls every once in a while, the rest of us should not have to live in perpetual uncertainty. Marvin Humphrey --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
