commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: Should a vote about a commons wide checkstyle config be submitted to the PMC (was Re: Common checkstyle)
Date Wed, 29 Feb 2012 14:41:04 GMT
Nah. It just means that when someone actually decides to do it we will review it then.  I don't
really see the point in voting on something and then no one following through to implement


On Feb 29, 2012, at 5:27 AM, Benedikt Ritter <> wrote:

> Hi,
> for the record: since more than 72h have passed with no response, I guess we can drop
this topic and leave everything the way it is.
> Regards,
> Benedikt
> Am 25.02.2012 17:33, schrieb Benedikt Ritter:
>> Hi,
>> for some reason this discussion ended without a result. Maybe it is time
>> to summarize what has been discussed so far.
>> This all goes back to a commit by Gary, that fixed several check style
>> issues in VFS [1]. The following discussion between Gary and Ralph and
>> others [2] showed, that there are several thinks unclear regarding the
>> check style configurations in commons:
>> - which configuration to use when starting a new project
>> - if the check style configuration of a project can be changed
>> - if there is a commons wide check style configuration, that all
>> projects could agree on
>> It was then suggested to call a vote on whether there should be a
>> commons wide check style configuration. This question is still unanswered.
>> Arguments for a commons wide configuration:
>> - it is easier for people to swap between projects and for new
>> contributers to get started
>> - Commons is one subproject of the ASF, so it should have only one style
>> - all source code would be formated the same way (making it "common" )
>> Arguments against a commons wide configuration:
>> - several projects have evolved their configuration in different ways,
>> making it hard to find a commons wide style
>> - Reformatting will be a lot of work
>> - teams should be able to choose their own style
>> - most people only develop a few components, so that the swapping is not
>> that much of an issue
>> - Technical restrictions (where to place such a commons wide check style
>> file?)
>> As a solution to those arguments it was proposed to have a default check
>> style configuration, that can be used for new projects. This
>> configuration may be overwritten by the different components if they
>> feel the need.
>> So now we have to answer the question: Should a vote be submitted to the
>> PMC?
>> Regards,
>> Benedikt
>> [1]
>> [2]
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message