Skip to content

Latest commit

 

History

History
132 lines (94 loc) · 7.81 KB

CONTRIBUTING.md

File metadata and controls

132 lines (94 loc) · 7.81 KB
Raw

Contribute to an important restoration and education effort in NYC!

The Billion Oyster Project is an ecosystem restoration and education project designed to restore one billion live oysters to New York Harbor by 2035 while educating all one million of NYC's public school students. But if we're going to restore one billion oysters to New York Harbor, we need lots of New Yorkers' help with all the work that goes into restoration, including software development! Environmental restoration includes activities like data analysis and scientific communication, and the BOP Digital Platform is a key tool for these aspects of our work.

One thing that sets Billion Oyster Project apart from other environmental organizations is that we are equal parts restoration AND education. So we believe that open source software projects are the perfect opportunity for people of a wide range of ages and ability levels to use their technical skills for good while learning new skills and building community. Whether you're a developer, DBA, UX designer, QA tester, or just a passionate user, we'd love for you to join us as a contributor!

Take a look through the information below to get started!

  • Quick Guide. Check out the BOP Digital Platform Quick Guide. This is a doc you can quickly scroll through to get a sense of the platform's core features, and it includes links to all the help documentation in our wiki.

  • Sign-up. Sign up for an account on the BOP Digital Platform if you'd like to get a sense of the user experience- make sure to choose the "team lead" role.

  • Code of Conduct. Read our code of conduct. Since our project engages community members of all abilities, especially NYC school students, it's crucial that everyone in the Digital Platform community is kind, assumes a good faith effort/best intentions on the part of other participants, and goes out of their way to be welcoming to people who are new to coding and technology. (One negative social interaction can be really discouraging for students/people who are just getting involved with open source, so we ask you to really go out of your way to be patient and friendly!)

  • API and data model documentation. We want to more fully flesh out our API documentation, but this is our current API and data model documentation. The front end makes extensive use of the API.

  • MEAN.JS. The platform was originally built by contractors based off the MEAN.JS stack (MongoDB, Express, Angular, Node.js). They forked it from the MEAN.JS project in Github in February 2016. We've reviewed every MEAN.JS commit since 2/2016, and there are two features we're likely to implement (sign-on with email address, and forgot password with email address). Other than that, we're not expecting to add anything newer from the project, but if you know of a cool MEAN.JS implementation let us know!

  • Github issues. Check out our list of Github issues. At the moment, we're using Github issues to showcase the project's most pressing software development requests. (We have a much larger internal backlog, but the Github issues are our way of highlighting issues that we've learned are important to our community members through site feedback and user testing.)

If you think there's something interesting you could do, or a bug you could fix, and it's not an existing issue in Github, open up an issue. We've included specific guidelines for creating issues and pull requests below. And please let us know if you have any questions or ideas you'd like to discuss! You can get in touch with Heather Flanagan, the BOP Digital Platform's product owner, at bop.digital.platform@nyharbor.org

Creating an Issue

Before you create a new issue:

  • Check the issues in Github to ensure a similar issue doesn't already exist.

In your issue request:

  • Clearly describe the issue.
    • If it's a bug, include the steps you took to reproduce the issue.
    • If it's a new feature, enhancement, or restructure, explain why you think it should be added.
  • Include your BOP Digital Platform username.
  • Include the type and scope.
    • Issue types:
      • feat - features, enhancements, and overall improvements
      • fix - fixes, bugs, HotFixs, etc...
      • doc - changes to the documentation that don't touch any code.
    • Issue scopes:
      • The scope should be where proposed changes will take place.
      • Examples: Expeditions, Data, Curriculum, Events
  • Label your issue with the site feature it relates to:
    • Expeditions
    • Data
    • Curriculum
    • Research
    • Events

Issue format guidelines:

Header
Blank Line
Body
Blank Line
BOP Digital Platform username

The header should look like this:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the issue (described above).

So a commit should look like:
feat(Expeditions): Include wild oyster recruitment data in Protocol 2: Oyster Measurements.

We'd like a way to collect information about potential wild oyster recruitment at an ORS site.

UN: bop-admin

Someone from BOP will get back to you within a week with feedback on your issue!

Making Changes

  • Create a topic branch from the master branch.
  • Check for unnecessary whitespace / changes with git diff --check before committing.
  • Also check that your code is formatted properly with spaces (hint: Use .editorconfig)
  • Keep git commit messages clear and appropriate.
  • Follow the commit message guidelines below.
  • Make sure you have added any tests necessary to test your code.
    • Run all the tests to ensure nothing else was accidently broken.
    • Don't rely on the existing tests to see if you've broken code elsewhere; test the changes you made in a browser too!

Commit Message Guidelines

Header
Blank Line
Body
Blank Line
BOP Digital Platform username
Footer

The header should look like this:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the commit:
An example, references as to where this idea came from, etc.

The footer should have all the issues tagged:
Fixes #123, Fixes #456

So a commit should look like:
feat(Expeditions): Add new checkbox to Protocol 2: Oyster Measurements form.

This feature adds a checkbox to indicate wild oyster recruitment at the site.  Idea proposed by @haflanagan

UN: bop-admin

Fixes #82
  • Types:
    • feat - features, enhancements, and overall improvements
    • fix - fixes, bugs, HotFixs, etc...
    • doc - changes to the documentation that don't actually touch any code.
  • Scope:
    • The scope should be where the change took place.
    • Examples: Expeditions, Data, Curriculum, Events
  • Subject:
    • The subject line should be clear and concise as to what is being accomplished in the commit.
  • General Rules:
    • No line in the commit message can be longer than 80 characters.

Submitting the Pull Request

  • Push your changes to your topic branch on your fork of the repo.
  • Submit a pull request from your topic branch to the master branch on the Digital-Platform repository.
  • Be sure to tag any issues your pull request is taking care of / contributing to.
  • Someone from BOP will get in touch within a week to discuss your pull request!