[
https://issues.apache.org/jira/browse/QUARKS-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cazen Lee updated QUARKS-23:
----------------------------
Comment: was deleted
(was: Hi
Sure, I agree announce to forks is required.
I think It seems better to go directly to the next weekend because changes will
be further increase as time goes by. I can participate in next week with exact
GMT time provided.
And providing the formatter was used on IBM seems to be helpful to determind
Quarks formmater.
(Or we can choose one from famous other apache project without the
time-consuming))
> 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)
