Skip to content

Latest commit

 

History

History
144 lines (90 loc) · 7.44 KB

CONTRIBUTING.md

File metadata and controls

144 lines (90 loc) · 7.44 KB

Contributing to Our Projects, Version 1.5

NOTE: This CONTRIBUTING.md is for software contributions. You do not need to follow the Developer's Certificate of Origin (DCO) process for commenting on the Code.mil repository documentation, such as CONTRIBUTING.md, INTENT.md, etc. or for submitting issues.

Thanks for thinking about using or contributing to this software ("Project") and its documentation!

Policy

1. Introduction

The project maintainer for this Project will only accept contributions using the Developer's Certificate of Origin 1.1 located at developercertificate.org ("DCO"). The DCO is a legally binding statement asserting that you are the creator of your contribution, or that you otherwise have the authority to distribute the contribution, and that you are intentionally making the contribution available under the license associated with the Project ("License").

2. Developer Certificate of Origin Process

Before submitting contributing code to this repository for the first time, you'll need to sign a Developer Certificate of Origin (DCO) (see below). To agree to the DCO, add your name and email address to the CONTRIBUTORS.md file. At a high level, adding your information to this file tells us that you have the right to submit the work you're contributing and indicates that you consent to our treating the contribution in a way consistent with the license associated with this software (as described in LICENSE.md) and its documentation ("Project").

3. Important Points

Pseudonymous or anonymous contributions are permissible, but you must be reachable at the email address provided in the Signed-off-by line.

If your contribution is significant, you are also welcome to add your name and copyright date to the source file header.

U.S. Federal law prevents the government from accepting gratuitous services unless certain conditions are met. By submitting a pull request, you acknowledge that your services are offered without expectation of payment and that you expressly waive any future pay claims against the U.S. Federal government related to your contribution.

If you are a U.S. Federal government employee and use a *.mil or *.gov email address, we interpret your Signed-off-by to mean that the contribution was created in whole or in part by you and that your contribution is not subject to copyright protections.

4. DCO Text

The full text of the DCO is included below and is available online at developercertificate.org:

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Getting Started

This project is intended to replace what is currently hosted at https://cwms-data.usace.army.mil/cwms-data/

Due to the current limits on releasing about database source we don't expect much random contribution. However, we will be moving more of the logic into this repository and any help on the formatting code and such will be greatly appreciated.

Making Changes

Now you're ready to clone the repository and start looking at things. If you are going to submit any changes you make, please read the Submitting changes section below.

Code Style

If you are editing an existing file please be consistent with the style in the file.

Otherwise use the defined checkstyle format for new code.

SQL Coding

  1. Use the JOOQ wrapper. Generally the wrapper provides sufficiently reasonable query generation. However, DO NOT be afraid to say, "that looks terrible", and tweak it until it generates something better. a. If the query you're making has nested queries name the queries. Example
    sql select a.* from (select col1,col2 from a_table) a; Otherwise JOOQ creates a new name each time the query is run which can starved the shared memory.

  2. Joins are your friend. They are a much better friend IF you let the database do them for you. Do not pull data into java just to do a join. Write the appropriate SQL.

Submitting an Issue

You should feel free to [submit an issue](https://github.com/) on our GitHub repository for anything you find that needs attention on the website. That includes content, functionality, design, or anything else!

Submitting a Bug Report

When submitting a bug report, please be sure to include accurate and thorough information about the problem you're observing. Be sure to include:

  • Steps to reproduce the problem,
  • What you expected to happen,
  • What actually happened (or didn't happen), and
  • Technical details including the specific version number of OpenDCS you are using
  • Sanitized logs, if possible.

Submitting Code

Please fork the repository on github and create a branch in Git if you are making changes to existing code.

Once you have made your changes submit a pull request. Please submit all PRs to the develop branch.

Barring nothing working at all or the code not being related to CWMS Data API your contributions will be accepted.

Releases an branching

If you have write access to the repository you can create release. All release should be put in a release/X.Y branch.

Check Your Changes

Before submitting your pull request, you should run the build process locally first to ensure things are working as expected.

The project is setup as a gradle project and using either the command line or any IDE should work to build the project.

./gradlew build

Due to the use of the CWMS Oracle Database is it difficult to provide an easy mechanism to fully test locally without having additional access to source that hasn't been made public. This may change in the future.