You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Martin Bukatovic (JIRA)" <ji...@apache.org> on 2014/07/11 08:14:06 UTC
[jira] [Commented] (BIGTOP-1240) Formatting Guidelines
[ https://issues.apache.org/jira/browse/BIGTOP-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058449#comment-14058449 ]
Martin Bukatovic commented on BIGTOP-1240:
------------------------------------------
Maybe a stupid note, but I noticed that mentioned page refers to Sun coding conventions, but the link is broken. The document has been moved to: http://www.oracle.com/technetwork/java/codeconvtoc-136057.html
> Formatting Guidelines
> ---------------------
>
> Key: BIGTOP-1240
> URL: https://issues.apache.org/jira/browse/BIGTOP-1240
> Project: Bigtop
> Issue Type: Task
> Components: General
> Affects Versions: 0.7.0
> Reporter: jay vyas
> Fix For: 0.8.0
>
> Attachments: ssht.jpg
>
>
> We need to expand https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute with
> - formatting guidelines for groovy . groovy seems tricky to format, not sure what guidelines to follow.
> - Also bigtop has many other file types (bash, puppet, etc...) so probably good to outline expectations for those to, or at least link to references.
> - patch submission guidelines : if we want to use reviewboard or other review tools how we will use them, and in what cases.
> This will make minor nits easier : just reference the code formatting guidelines.
--
This message was sent by Atlassian JIRA
(v6.2#6252)