coding conventions : getUrl vs getURL

[Cantor, Scott]

On 3/11/13 1:31 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>> suggest we adopt the methods most of the Apache projects use, which is
>> mostly a "3 yes votes, 0 no votes" approach to most resolutions, and any
>> no votes are worked through by requiring a justification and then
>> discussing it.
>
>I am not familiar with the apache way, but sounds worth trying.

There actually isn't one defined project management ruleset, Apache leaves
that to the PMC, which is the liason to the Apache Board. The PMC is left
to define its own rules for decision making, but it is a de facto standard
to call for votes on releases and other project decisions.

Seems to work well for a project in a healthy state (healthy meaning
developers not at each others' throats).

I was going to circulate that at some point for a thumbs up and submit it
to the board as the process by which the committers would make decisions
related to team membership and so forth. Unlike Apache, I would prefer
that all committers retain votes on such issues and the PMC (if we had
one) would reserve to itself structural decisions, such as changes to
those rules of the road.

-- Scott

---
When coordination is required, decisions are taken with a lazy consensus
approach: a few positive votes with no negative vote is enough to get
going.
Voting is done with numbers:

* +1 -- a positive vote

* 0 -- abstain, have no opinion

* -1 -- a negative vote


The rules require that a negative vote includes an alternative proposal or
a detailed explanation of the reasons for the negative vote.
The community then tries to gather consensus on an alternative proposal
that resolves the issue. In the great majority of cases, the concerns
leading to the negative vote can be addressed.