Perhaps could be good to hide by default those projects without any issue open, there are plenty with 0 issues.
Also I see some variation in the reported number of issues, for example chamilo/chamilo-lms in PHP shows 3 issues but the GitHub repo has 8 'Good first issue' issues.
> I'm still not unsure if I should include it as part of my answer when asked if I contributed to open source projects
I woud say yes, as long as you make sure you indicate the level clearly.
It's not landing a great new feature, but it shows you understand how Open Source works, you understand the value of the non-code parts of these projects, you can use the tools (I assume Git PR's), you can communicate well and work with others.
This is an awesome idea, and it's cool to see it broken down by language so you can quickly find things you could actually help on (instead of slowing down a project as a newbie in any specific technologies). In the back of my mind it's hard to connect how these applications or tools help. Reading a few titles unfortunately gives me the vaguest of ideas of who or what I'm helping though (even if the second drop down lets you select "solving hunger" etc etc, I still don't see how or why or where this project is used without digging in. Even then, I randomly picked one and this was the best summary I got /from inside the git rep/ - "CREDEBL SSI Platform
This repository host codebase for CREDEBL SSI Platform backend." I really wish everyone spent a little more time actually writing titles and descriptions that gave even the smallest amount of additional context. I feel like most of us programmers have our heads in the technology so quickly that even as an empassioned technologist with 30 years of experience I have not even the slightest clue what that project does or the problem it solves. This is so true for things as simple as git commit messages to readmes to whatever. The project meta-data is important. Fill those little text boxes in with a bit of substance. The AI overlords will thank you as well as your future self in a few years when you don't have the context front-and-center like you did when you threw this project together.
> drupal / drupal
> Verbatim mirror of the git.drupal.org repository for Drupal core. Please see the https://github.com/drupal/drupal#contributing. PRs are not accepted on GitHub.
> Issues: 0
Does not seem very curated …
Great initiative! Note Re-Decentralise from 10 years ago with few hundred projects:
https://github.com/redecentralize/alternative-internet/blob/...
This specific format includes details to see which projects are really active. Number of commits, lines of code, unique developers, and age.
This is very cool. I hope it gets uptick.
I made a similar project a few years ago for non-code projects people could volunteer for online and it hasn't had very many merge requests :(
https://volunteer.onl/
Perhaps could be good to hide by default those projects without any issue open, there are plenty with 0 issues. Also I see some variation in the reported number of issues, for example chamilo/chamilo-lms in PHP shows 3 issues but the GitHub repo has 8 'Good first issue' issues.
Edit: typo.
I started with fixing typos in documentation.
I'm still not unsure if I should include it as part of my answer when asked if I contributed to open source projects or I should only mention bugfix.
> I'm still not unsure if I should include it as part of my answer when asked if I contributed to open source projects
I woud say yes, as long as you make sure you indicate the level clearly.
It's not landing a great new feature, but it shows you understand how Open Source works, you understand the value of the non-code parts of these projects, you can use the tools (I assume Git PR's), you can communicate well and work with others.
Typo fixes are appreciated but generally not something you’d put in a CV
This is an awesome idea, and it's cool to see it broken down by language so you can quickly find things you could actually help on (instead of slowing down a project as a newbie in any specific technologies). In the back of my mind it's hard to connect how these applications or tools help. Reading a few titles unfortunately gives me the vaguest of ideas of who or what I'm helping though (even if the second drop down lets you select "solving hunger" etc etc, I still don't see how or why or where this project is used without digging in. Even then, I randomly picked one and this was the best summary I got /from inside the git rep/ - "CREDEBL SSI Platform This repository host codebase for CREDEBL SSI Platform backend." I really wish everyone spent a little more time actually writing titles and descriptions that gave even the smallest amount of additional context. I feel like most of us programmers have our heads in the technology so quickly that even as an empassioned technologist with 30 years of experience I have not even the slightest clue what that project does or the problem it solves. This is so true for things as simple as git commit messages to readmes to whatever. The project meta-data is important. Fill those little text boxes in with a bit of substance. The AI overlords will thank you as well as your future self in a few years when you don't have the context front-and-center like you did when you threw this project together.