[
https://issues.apache.org/jira/browse/QUARKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191450#comment-15191450
]
Daniel John Debrunner commented on QUARKS-23:
---------------------------------------------
+1 on a standard formatter with spaces.
Thanks for volunteering to to this, the only item I would request that you
provide a heads up when the code will be reformatted with enough warning to try
and avoid merge conflicts for anyone with changes in progress. At least 72
hours warning and maybe try for it to be a Friday afternoon or a Monday morning.
The formatter can be added ahead of reformatting all the code.
> Provide a formatter for Quarks coding convention
> ------------------------------------------------
>
> Key: QUARKS-23
> URL: https://issues.apache.org/jira/browse/QUARKS-23
> Project: Quarks
> Issue Type: Task
> Components: Documentation
> Reporter: Cazen Lee
> Priority: Minor
>
> Nice to meet you. This is Cazen.
> Seems that people who contribute to quarks use their own formatter.
> It may be confusing and can be helpful if the formatter specified explicitly.
> Something like this:
> According to Sun's convention with two space per level and 100 characters of
> line length
> (http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html)
> or provide eclipse-formatter to repository. It can be used by both eclipse
> and intellij.
> (e.g
> https://github.com/apache/hive/blob/master/dev-support/eclipse-styles.xml)
> I can participate in following cases if permitted.
> - Provide formatter according to existing apache project and modify
> DEVELOPMENT.md
> - Reformatting all code in repository
> - Change IBM licence pharase to apache 2.0 in all source code
> Thank you very much
> BR
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
