Skip to content

Latest commit

 

History

History
39 lines (21 loc) · 3.03 KB

CONTRIBUTING.md

File metadata and controls

39 lines (21 loc) · 3.03 KB

Contributing to the 990 Scraper a.k.a. Nonprofit Info Collector

Thanks for helping to build the 990 Scraper a.k.a. Nonprofit Info Collector!

This project is a way to quickly and easily aggregate information on a bunch of nonprofits, all in one easy to navigate, and easy to visualize (if you so choose) place. The tool is going to be used to gather information on organizations that make, use, or engage with technology for social justice (as found in this list), but could be used on any list of United States Nonprofits you have.

These are some guidelines on how you can help.

Participation guidelines

This project adheres to a code of conduct. Don't be garbage, and don't bring your macho geek bro vibes in here. No one needs that, and no one wants that. Treat everyone with respect. Please report unacceptable behavior to [email protected], and she will try to respectfully handle the situation.

What we're working on

This project is being started at the Mozilla Sprint (June 1-2, 2017), so as of this writing, there is not much more than a README.

However, take a look at the issues, or post your own issues you think should be addressed.

How to submit changes

Once you've identified one of the issues above that you feel you can contribute to, you're ready to make a change to the project repository!

  1. Fork this repository. This makes your own version of this project you can edit and use.
  2. Make your changes! You can do this in the GitHub interface on your own local machine. Once you're happy with your changes...
  3. Submit a pull request. This opens a discussion around your project and lets the project lead know you are proposing changes.

First time contributing to open source? Check out this free series, How to Contribute to an Open Source Project on GitHub.

(instructions on how to contribute taken from Node.js's instructions. Hey, it's my first time srsly doing an open source project too.)

How to report bugs

Stay on the lookout for can any potential issue that might cause problems for our project. These could be problems in code, content omissions or copy errors, or any issues with the functionality or design of this project.

Notice a mistake? Please file any bugs, requests, or questions in our issue tracker!

Communication channels

We should have one, right? This will be updated when I get to the Moz Sprint site in Worcester, but in the meantime, email [email protected] to get in contact.