RE: ACNA Presentation Template - Crunch

I have extracted the three background images from the ACEU14 presentation. They are not possible to morph. They are JPEGs and there is no reasonable way to extract pieces and morph the logo and conference name. My plan is to produce three new ones of these and slide them into the ODP in pla

Re: Veto! Veto?

On Sat, Mar 21, 2015 at 8:50 AM, Pierre Smits wrote: > I am not talking about the consensus aspect in the principles of the ASF. > Everybody agrees that it is (one of) the first and foremost principle(s) of > the ASF. And I expect, like everybody else, that every contributor works > towards that

Re: Veto! Veto?

On Sat, Mar 21, 2015 at 11:59 AM, Pierre Smits wrote: > It is sometimes the case that the individual, with power in the community, > can't work with another 'in his eyes difficult' person. > > If his contributions are beneficial to the project, if others in the > project can work with that second

Re: Veto! Veto?

If person A ‘can’t work’ with person B, in the nomination discussion, if person A is a reasonable person and sees overwhelming support for person B, person A should simply vote +0 and try to avoid person B. It isn’t like you all work in the same physical office. Once a group of people gets large

Re: commit rights to ComDev non-community.a.o site resources

On Mon, Mar 16, 2015 at 1:21 AM, Ulrich Stärk wrote: > One doesn't exclude the other. I'd first like us to establish whether > committership > to the ComDev code is by invitation only or open to all existing Apache > committers > (which I'd prefer). +1

Re: ACNA Presentation Template - Crunch

Thank you so much for your assistance, Dennis! Can you guys please respond to his questions?! Thank you so much! ~M From: Dennis E. Hamilton To: dev@community.apache.org Cc: 'Melissa Warnkin' ; 'Nick Burch' Sent: Saturday, March 21, 2015 3:11 PM Subject: RE: ACNA Presentation Template

Re: Veto! Veto?

It seems resolution 7.G is a result of the rule of no -1 votes leading to irreconcilable difference. And the rule of no -1 votes seems to be the result of the rule to grant the power to veto. In stead of making it simpler it has added layers. >From the reports of the various projects that I have r

RE: ACNA Presentation Template - Crunch

I am having a problem. Because the background image in the ACEU14 set is all JPEG with no way to take it apart, I looked at the others on SourceForge. They each have problem, especially with the name and location of the conference being bolted into the feather images as combined raster/JPEG im

Re: Veto! Veto?

It is sometimes the case that the individual, with power in the community, can't work with another 'in his eyes difficult' person. If his contributions are beneficial to the project, if others in the project can work with that second person in the collegia/civil manner that is expected in a commun

RE: ACNA Presentation Template

I assume that is what I am working on. I am adapting ACEU 2014 for ACNA 2015 as easily as possible. I assume that any IP issue is solved when the image is replaced. I'm also assuming, based on silence, that this template was used and none had a problem with it. If there is a particular place

Re: ApacheCon Twitter account

On Thu, Mar 19, 2015 at 6:46 AM, Rich Bowen wrote: > Twitter just posted the following blog post: > https://blog.twitter.com/2015/introducing-tweetdeck-teams Interesting! On a related subject: should we promote the usage of this for managing all of our project @ASFxxx accounts? Thanks, Roman.

Re: Veto! Veto?

On Sat, Mar 21, 2015 at 9:34 AM, Dennis E. Hamilton wrote: > Can someone please link to any place where invitation of committers and of > PMC members is subject to a veto (as opposed to a need to see if -1 > objections can be cured in discussion of the objection) as a matter of > policy? See reso

Re: ACNA Presentation Template

Sorry for jumping into the discussion late, but is there a chance for [semi-]official templates to be available for ACNA15? Thanks, Roman. On Fri, Mar 20, 2015 at 12:46 PM, Andrea Pescetti wrote: > On 19/03/2015 Rich Bowen wrote: >> >> >> http://templates.openoffice.org/en/search?search_api_view

Re: Veto! Veto?

On Sat, Mar 21, 2015 at 8:29 AM, Benson Margulies wrote: > And I emphasize 'range'. There was a talk at Apache Con some years > back about the idea that civility goes in two directions: we all want > to express ourselves in collegial and civil ways, and we also have to > be prepared to accept com

RE: Veto! Veto?

Can someone please link to any place where invitation of committers and of PMC members is subject to a veto (as opposed to a need to see if -1 objections can be cured in discussion of the objection) as a matter of policy? [One case is that PMC invitations are subject to Board lazy consensus, but

Re: Veto! Veto?

On Sat, Mar 21, 2015, at 11:50 AM, Pierre Smits wrote: > When a (greater) number of people within a project can collaborate with > the 'difficult' newcomer, why should it then be possible that the one (or the > few) with veto power - who don't/doesn't seem to be able to collaborate > with the 'diff

Re: Veto! Veto?

In a healthy community, in my experience: 1: someone starts a DISCUSS thread to propose adding a person. 2: if someone else had serious reservations, they state those reservations 3a: remarks from others cause the person with the reservations to withdraw them, and the group proceeds to a VOTE. 3

Re: Veto! Veto?

I am not talking about the consensus aspect in the principles of the ASF. Everybody agrees that it is (one of) the first and foremost principle(s) of the ASF. And I expect, like everybody else, that every contributor works towards that in any of the projects (and podlings) in any kind of situation.

Re: Veto! Veto?

Majority voting, regarding on and offboarding of people, is less subject of abuse - when it comes to get to a resolution - than the veto mechanism. Pierre Smits *ORRTIZ.COM * Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http

Re: Veto! Veto?

I'd like to suggest backing up from the point where Alex was commenting. It is an Apache goal to build broad communities, not to build homogeneous groups. That includes PMC as well as committers. To me, this suggests that the community-building starts when the person shows up. Hypothetical: a new

Re: Veto! Veto?

On 21 March 2015 at 15:24, Pierre Smits wrote: > Again, this is not about the veto mechanism for the technical works of the > project. This is about onboarding of new people, this is about community > development. > > Voting is not a technicality or formality when it comes to people. It is > the

Re: Veto! Veto?

Sorry, I wasn’t clear. It isn’t whether the nominee is perceived as an obstructionist, it is whether one or two of the voters is perceived as an obstructions. There are communities where everyone gets along, and there are communities where there is a person one can construe as a ‘difficult person

Re: Veto! Veto?

Again, this is not about the veto mechanism for the technical works of the project. This is about onboarding of new people, this is about community development. Voting is not a technicality or formality when it comes to people. It is the ultimate means to get to a resolution. We can discuss all we

Re: Veto! Veto?

Have you read https://www.apache.org/foundation/voting.html? As others have said, the idea is always to build consensus rather than force a result. I guess I've been fortunate in that the projects in which I've been most active have always been more interested in consensus than individuals forci

Re: Veto! Veto?

On 21 March 2015 at 12:00, Pierre Smits wrote: > If the majority perceives that a nominee is an obstructionist then it will > be reflected in the voting result. But if the minority - or even only one > voter - perceives that and others don't, then a veto would be a show > stopper for innovation,

Re: Veto! Veto?

If the majority perceives that a nominee is an obstructionist then it will be reflected in the voting result. But if the minority - or even only one voter - perceives that and others don't, then a veto would be a show stopper for innovation, expansion and merit recognition c.q. privilege awarding.