explore VS CodeTriage

There isn't a lot going on there, but I like the way he added the little language and tech-stack icons to his GitHub profile using the images served by the GitHub Explore page as well.

Checking the GitHub explore page for fun projects and inspiration

Uh? How is this AI thingie different from Github Explore?

https://github.com/explore

What is the real URL for Github Feed?

The Before I Die Code project’s front end is built with React, JavaScript, HTML, and CSS, and it’s currently deployed on Vercel. However, the technology will change with the deployment as I am planning on applying for this open-source project to be featured on the GitHub explore page. For this, the project will need to be using GitHub pages.

New users finding a project is much more likely on GitHub. I'm not necessarily talking about search. I would expect that experience to be about the same on both, though generally, I see a lot more empty projects showing up in results on GitLab for some reason, at least for things I've searched for there. Github seems to do reasonably well with search ranking. I'm more concerned about the poor experience with https://gitlab.com/explore compared to https://github.com/explore where people are going to be discovering new libraries when they don't know what they are looking for and are either browsing topically or just browsing for fun and learning. GitLab seems to do particularly poorly in their curation and selection of what they show you. GitHub on the other hand, has connected me with countless extremely high quality projects through this feature. Finally, the discoverability advantage of GitHub over gitlab is also simply because more people use GitHub. You don't need to primarily use GitHub to use it to point to GitLab If you want to work there, but you're certainly going to have more users finding your project if you have presence on GitHub.

You can also star projects you find interesting and github will use that for the EXPLORE tab to show you other cool projects.

Subscribe to atom/rss feed of https://github.com/explore (you prolly want to have a gihub account) or https://github.com/trending and be sure to at least 'follow' any projects that may interest you. No need to install everything.

Otherwise search for "good first issue" or similar, there are some sites that curate them. Or see GitHub Explore

Sauce: https://github.com/explore

3. Open Source Contribution

I wrote a book with a chapter on how to write docs for other people’s code https://howtoopensource.dev

I also wrote an open source tool for writing and testing tutorials https://github.com/zombocom/rundoc and another that will email you undocumented methods of open source code so you can practice writing documentation https://www.codetriage.com/.

CodeTriage helps you contribute to open source by “picking a handful of open issues and delivering them directly to your inbox”. (Source: CodeTriage)

Here are open source projects listed https://www.codetriage.com/ You can filter for "C".

The biggest untaped potential (IMHO) is not one company funding 1 full time maintainer, but EVERY company allowing and encouraging EVERY developer to help and work with open source. This was the basis of my web app https://www.codetriage.com/. I have a chapter on it in my book How to Open Source (https://howtoopensource.dev/), and I talked to Yehuda about it for about an hour after my last talk at Philly ETE.

You can also use websites like up-for-grabs, goodfirstissue, or CodeTriage to find projects with open issues. Find one that looks easy or interesting to you and comment on it, asking if you can take a shot at it.

I recommend these resources to help you contribute https://www.codetriage.com/ (free) and https://howtoopensource.dev/ (paid). DM if you can’t afford a copy.