github.com/robryk/drone@v0.2.1-0.20140602202253-40fe4305815d/CONTRIBUTING.md (about)

     1  # Contributing to Drone
     2  
     3  Want to hack on Drone? Awesome! Here are instructions to get you
     4  started. They are probably not perfect, please let us know if anything
     5  feels wrong or incomplete.
     6  
     7  ## Contribution guidelines
     8  
     9  ### Pull requests are always welcome
    10  
    11  We are always thrilled to receive pull requests, and do our best to
    12  process them as fast as possible. Not sure if that typo is worth a pull
    13  request? Do it! We will appreciate it.
    14  
    15  If your pull request is not accepted on the first try, don't be
    16  discouraged! If there's a problem with the implementation, hopefully you
    17  received feedback on what to improve.
    18  
    19  We're trying very hard to keep Drone lean and focused. We don't want it
    20  to do everything for everybody. This means that we might decide against
    21  incorporating a new feature.
    22  
    23  ### Discuss your design on the mailing list
    24  
    25  We recommend discussing your plans [on the mailing
    26  list](https://groups.google.com/forum/?fromgroups#!forum/drone-dev)
    27  before starting to code - especially for more ambitious contributions.
    28  This gives other contributors a chance to point you in the right
    29  direction, give feedback on your design, and maybe point out if someone
    30  else is working on the same thing.
    31  
    32  We may close your pull request if not first discussed on the mailing
    33  list. We aren't doing this to be jerks. We are doing this to prevent
    34  people from spending large amounts of time on changes that may need
    35  to be designed or architected in a specific way, or may not align with
    36  the vision of the project.
    37  
    38  ### Create issues...
    39  
    40  Any significant improvement should be documented as [a GitHub
    41  issue](https://github.com/drone/drone/issues) before anybody
    42  starts working on it.
    43  
    44  ### ...but check for existing issues first!
    45  
    46  Please take a moment to check that an issue doesn't already exist
    47  documenting your bug report or improvement proposal. If it does, it
    48  never hurts to add a quick "+1" or "I have this problem too". This will
    49  help prioritize the most common problems and requests.