Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Meta] Ways to Contribute #39

Open
TimidRobot opened this issue Mar 3, 2023 · 6 comments
Open

[Meta] Ways to Contribute #39

TimidRobot opened this issue Mar 3, 2023 · 6 comments
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟨 priority: medium Not blocking but should be fixed soon 🏷 status: label work required Needs proper labelling before it can be worked on 💬 talk: discussion Open for discussions and feedback

Comments

@TimidRobot
Copy link
Member

TimidRobot commented Mar 3, 2023

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.

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 sources.md)
    • 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 [Feature] Automate Data Gathering and Analysis/Rendering #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. [Feature] Use requests included exponential backoff #2)
@TimidRobot TimidRobot added good first issue New-contributor friendly help wanted Open to participation from the community 🟨 priority: medium Not blocking but should be fixed soon 🏁 status: ready for work Ready for work 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase Hacktoberfest labels Mar 3, 2023
@TimidRobot TimidRobot self-assigned this Mar 3, 2023
@man0045

This comment was marked as outdated.

@man0045

This comment was marked as outdated.

@sumanbalayar08
Copy link

@TimidRobot, I'm interested in contributing to this project. Could you please provide more details on #39 or guide me on how to get started? Thanks!

@TimidRobot
Copy link
Member Author

Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and PRs (we generally don't assign issues prior to resolution, and this issue is [Meta] and will not be assigned).

@akshansh-modi
Copy link

hey i wish to contribute to this repo but don't see any open issues that I can work on

@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work and removed good first issue New-contributor friendly help wanted Open to participation from the community 🏁 status: ready for work Ready for work Hacktoberfest labels Jun 20, 2024
@TimidRobot
Copy link
Member Author

TimidRobot commented Jun 20, 2024

@akshansh-modi this project is currently in flux as it is reorganized as part of GSoC. It should be easier to contribute after 2024 Summer.

@TimidRobot TimidRobot moved this to Backlog in TimidRobot Sep 10, 2024
@TimidRobot TimidRobot added help wanted Open to participation from the community 💬 talk: discussion Open for discussions and feedback and removed 🚧 status: blocked Blocked & therefore, not ready for work labels Sep 26, 2024
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟨 priority: medium Not blocking but should be fixed soon 🏷 status: label work required Needs proper labelling before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

5 participants