creativecommons/quantifying

[Meta] Ways to Contribute

Open

#39 aperta il 3 mar 2023

Vedi su GitHub
 (14 commenti) (1 reazione) (1 assegnatario)Python (73 fork)auto 404
good first issuehelp wanted✨ goal: improvement🌟 goal: addition🏷 status: label work required💬 talk: discussion💻 aspect: code🟨 priority: medium🤖 aspect: dx

Metriche repository

Star
 (48 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

Overview

⚠️ This meta-issue should not be worked on itself. Instead it is a place for me (@TimidRobot) to document ways to engage with this project.

First

Ways to Contribute

  • Pull Requests (PRs)
  • Issues
    • Create a new issue recommending a data source that should be included. Include information like:
      • quantity of records
      • types of metadata available
      • API documentation link
      • API requirements and limitations
      • Also see
    • Create a new issue related to a single script or data source:
      • Scripts should be using .env (theskumar/python-dotenv) and not query_secrets.py or similar
      • Scripts mustn't be monolithic--they should be limited to a single phase (ex. query, process, report. See #22)
      • Scripts must be designed to be run from the repository root via pipenv (ex. pipenv run PATH/SCRIPT.PY)
        • Script should determine its own path and set appropriate global variables (ex. DIR_ROOT, DIR_SCRIPT)
      • Scripts have a lot of duplication between them. Begin a shared library (remember to keep issues as small and descrete as possible--limit each issue/PR to a single script or data source).
      • Scripts should be using retries with exponential backoff (ex. #2)

Tips

Conventions and best practices

Plot process data

Any plots in phase 3-report should graph data without significantly modifying it. This means that development of phase 2-process and phase 3-report usually needs to be done at the same time.

Put another way, there should be a 1:1 relationship between phase 3-report plots and phase 2-process CSV files.

Guida contributor