[jira] [Commented] (QUARKS-23) Provide a formatter for Quarks coding convention

["Kathey Marsden (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QUARKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191243#comment-15191243 ] 

Kathey Marsden commented on QUARKS-23:
--------------------------------------

Nice to meet you Cazen and thank you for your interest in Quarks.

I personally am in favor of at least a standard indentation with spaces.  I don't have a strong preference otherwise but would want to avoid changing things besides whitespace which would make history hard to diff and discern. Changing the licenses as early as possible would be good too.

> 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)