Skip to content

Instantly share code, notes, and snippets.

@darthgera123
Forked from briandk/CONTRIBUTING.md
Last active May 15, 2020 14:18
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save darthgera123/941e080ec8dd0cc6953d776160745b2c to your computer and use it in GitHub Desktop.
Save darthgera123/941e080ec8dd0cc6953d776160745b2c to your computer and use it in GitHub Desktop.
A basic template

Contributing to Educational Challenges πŸ”¨

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

  • Reporting a bug πŸ›
  • Discussing the current state of the code πŸ”¬
  • Submitting a fix πŸ”§
  • Proposing new features πŸ”†
  • Submitting a new baseline πŸ“œ
  • Becoming a maintainer πŸ“ˆ

We Use GitLab Flow, So All Code Changes Happen Through Merge Requests

Merge requests are the best way to propose changes to the codebase (we use GitLab Flow). We actively welcome your merge requests:

  1. Fork the repo and create your branch from master.
  2. If you've added code that should be tested, add tests.
  3. If you've changed APIs, update the documentation πŸ“ .
  4. Ensure the test suite passes:heavy_check_mark: .
  5. Make sure your code lints:chart:.
  6. Issue that merge request!

Any contributions you make will be under the MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Report bugs using Gitlab's issues πŸ›

If you see any typos anywhere you can simply raise an issue

Write bug reports with detail, background, and sample code πŸ“‘

The bug report should be in a way so that its easy to comprehend for anyone so they can fix it. Include all information

Great Bug ReportsπŸ“‹ tend to have:

  • A quick summary and/or background
  • Steps to reproduce
    • Be specific!
  • What you expected would happen
  • What actually happens:bomb:
  • Notes (possibly including why you think this might be happening, or stuff you tried that didn't work):memo: Screenshots are a great way to explain any errors so dont be hesitant.
    People love ❀️ thorough bug reports. I'm not even kidding.

Submitting new notebooks πŸ“œ

As a datascience community we love new insights regarding data and its applications, thus any new submissions regarding notebooks are encouraged. However there are some guidelines that need to followed which are as follows -

  • Notebooks should be in .ipynb format or colab format only
  • It must have the following section as follows-
    • Name of the challenge and Name of the author
    • Data Download:memo:
    • Importing Packages:clipboard:
    • EDA (if required):bar_chart:
    • Training Phase(not required if only EDA):chart:
    • Testing Phase(not required if only EDA):chart_with_upwards_trend:
  • Raise a merge request to add your notebook in the baseline folder of the challenge. πŸ“

The challenge author will review your notebook and if all goes well, we will feature it soon with our set of notebooks. Also a post with your notebook will be made on discourse form under the discussion tab.

License

By contributing, you agree that your contributions will be licensed under its MIT License.

References

This document was adapted from the open-source contribution guidelines for Facebook's Draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment