You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/09/06 16:06:29 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=14124488#comment-14124488 ] 

jay vyas commented on BIGTOP-1240:
----------------------------------

we can close it.  For now, got to https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute#HowtoContribute-REVIEWINGPATCHES To review, update, and refresh guidelines.

> 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
>            Assignee: 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.3.4#6332)