|Re: [ee4j-community] EE4J code conventions?|
On 2018-04-09 9:11 AM, arjan tijms wrote:
On Mon, Apr 9, 2018 at 1:58 PM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:
+1, Dmitry. Coding conventions should be a project-specific requirement, not an EE4J requirement. EE4J could possibly recommend some coding conventions, but the requirements should be left up to each individual project.
While the goal is to have code conventions, and having them at the project level is definitely better than having none at all, I do wonder why we would even want different conventions per project?
Because Eclipse Foundation open source projects are self-governing meritocracies, and we don't tell them what to do. Ultimately, it is the committers who would need to do the work, and I don't think any of us get to tell them how to spend their time.
I'm not saying that this is an unreasonable idea. But generally speaking open source projects don't respond well to being ordered about. Ivar has already said that he'll raise it with the PMC. Let's wait and see how that plays out.
ee4j-community mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top