[
https://issues.apache.org/jira/browse/HDFS-9328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Clampffer updated HDFS-9328:
----------------------------------
Attachment: HDFS-9328.HDFS-8707.000.patch
I've put together basic coding requirements based on the google style guide and
additions to that that I've seen so far from code review feedback.
[~bobhansen] and [~wheat9], could you let me know if I'm missing anything. My
goal is that all rules we ever intend to have are included so there won't be
any surprise rejections on patch submissions.
I wouldn't be surprised if I have some elementary grammar mistakes. Please
point those out as well.
> Formalize coding standards for libhdfs++ and put them in a README.txt
> ---------------------------------------------------------------------
>
> Key: HDFS-9328
> URL: https://issues.apache.org/jira/browse/HDFS-9328
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Priority: Blocker
> Attachments: HDFS-9328.HDFS-8707.000.patch
>
>
> We have 2-3 people working on this project full time and hopefully more
> people will start contributing. In order to efficiently scale we need a
> single, easy to find, place where developers can check to make sure they are
> following the coding standards of this project to both save their time and
> save the time of people doing code reviews.
> The most practical place to do this seems like a README file in libhdfspp/.
> The foundation of the standards is google's C++ guide found here:
> https://google-styleguide.googlecode.com/svn/trunk/cppguide.html
> Any exceptions to google's standards or additional restrictions need to be
> explicitly enumerated so there is one single point of reference for all
> libhdfs++ code standards.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
