Running to the board every time there is a lack of consensus about a candidate
is not appropriate governance at Apache. The fact that PMC members are
afforded certain RIGHTS, including the right to stop the train on a personnel
promotion, is an important aspect of maintaining proper checks and
+1 Ted. While I have never personally felt the need to issue a veto regarding
a personnel promotion, I have seen others use it, and have on balance agreed
with those decisions, including for the exact situation I mentioned.
Sent from my iPhone
> On Apr 4, 2017, at 8:18 PM, Ted Dunning wrote:
Niclas,
I never presented an argument in favor of *using* a veto. I presented an
argument in favor of *having* a veto to potentially use.
The possibility of a veto encourages consensus building before the decision
is recorded.
I personally think that vetoes should almost never happen because an
That's reassuring, but how does that relate to defaulting to vetoes for
personnel?
Your statement about Board intervening could be said for Joe's/Ted's claim
about "letting the minority be heard" as well... and doesn't support or
undermine the use of vetoes for personnel.
Cheers
On Apr 5, 2017
On Tue, Apr 4, 2017 at 4:26 PM, Niclas Hedhman wrote:
> Vetoes can become very contentious, and I don't really buy the arguments
> presented in favor of using it. To me a negative use is a BDFL-type
> leader/founder preventing active contributors from getting a say in a
> project.
If a personnel
But Ted, how does the minority regain the "minority's voice heard" simply
by veto of new members? If they place unreasonable vetoes and hope that
over time the majority will "evaporate" seems unproductive as well.
Vetoes can become very contentious, and I don't really buy the arguments
presented i
Hi Christine
Thanks for reporting this. Infra tell me that we need to file a Jira to
get it fixed - so I can take care of it.
Thanks
Sharan
On 04/04/17 21:30, Christine Poerschke (BLOOMBERG/ LONDON) wrote:
Hello,
Not sure if this is the most suitable place to report it but I noticed that at
Hello,
Not sure if this is the most suitable place to report it but I noticed that at
the top of https://blogs.apache.org/ some of the links e.g. the "Get Involved"
link appear to be broken links.
Interestingly though if you start out at (say)
https://blogs.apache.org/foundation/entry/the-apac
> On 2017-04-04, at 02:44, Bertrand Delacretaz wrote:
>
> On Fri, Mar 31, 2017 at 3:07 PM, Rich Bowen wrote:
>> ...As a small way to address this, my desire is to send a newsletter to
>> committers every two months..
>
> I like the idea (especially if you're doing the work ;-) and suggest
> pu
