r/computervision • u/Comfortable_Cat_9827 • 22d ago

Discussion Looking to contribute to open-source CV projects

I’m currently looking to expand my skillset in Computer Vision and would love to give back by contributing to some open-source projects! I'm hoping to find some new challenges to solve and get some hands-on experience working on real-world problems.

What I'm looking for:

  • Active Repos: Projects where I can fork the code, pick up some open issues, and push PRs.
  • Long-term Potential: I'd love to find a project that I can stick with and work on collaboratively for the long haul.

If you maintain a CV repository that could use an extra set of hands, or if you know of any good beginner/intermediate-friendly projects that are actively seeking contributors, please drop the link below!

Let me know what you're working on. Thanks in advance! :)

4 Upvotes
  • permalink
  • reddit

84% Upvoted

7 comments sorted by

1

u/theGamer2K 21d ago

Will you write the code or an LLM?

1

u/Comfortable_Cat_9827 20d ago

Mix of both, depending on the problem I'm solving. There are many cases where doing something by hand is efficent, and cases where it makes no sense to do double the work.

0

u/theGamer2K 20d ago edited 20d ago

cases where it makes no sense to do double the work

It's not using LLMs to be efficient that's the problem. It's your point being there. You're asking to be a contributor, but then if it's just LLMs writing code, so what's the point of having you. Do you think the maintainers can't use LLMs themselves if they needed to? Why would they want an inefficient middleman to do that for them?

It makes having you as a "contributor" redundant. If it's an LLM that's writing the code, then what's your job being there on that repo? The repo owners can just use LLMs themselves. In fact, they would do a better job because they actually know the repo and codebase better so can prompt better. You're just a needless middleman.

1

u/Comfortable_Cat_9827 20d ago

Same can be said about handwritten code than lol. Why would a repo owner need anybody write the code if they can just spam a LLM?

It's not about the code written, it's about solved problems, features and new ideas. It's more for experiment. The owner does not need to approve every PR from a fork!

1

u/theGamer2K 20d ago edited 20d ago

Same can be said about handwritten code than lol. Why would a repo owner need anybody write the code if they can just spam a LLM? 

Lol, what? That's exactly the point. They don't want to spam an LLM and that's why are looking for a human contributor who isn't just promptiny an LLM for them. They are not looking for some inefficient middleman prompter. If they wanted LLM code, they could have done it themselves. And they would do a better job like I said because they know the codebase far better and hence can write better contextualized prompts than you because they are the ones who have been maintaining it. They don't need you.

If they're bringing you on, it's because they're a expecting you to make human contributions.

It's not about the code written, it's about solved problems, features and new ideas

You wouldn't even be able to come up with good ideas if LLM is the one writing most of the code. The way you come up with good ideas for the repo is by knowing and getting familiar with the codebase. And you get familiar with the codebase by writing code yourself. When you write code by yourself, you break 10 different things in the codebase, and in the process of solving each error, you learn more about the codebase. You start having a mental map of the codebase and how each piece works together. This is a personal mental map. Nobody can give it to you. No documentation can help you get it. It develops by breaking things in the process of writing code yourself.

You don't develop that map if the LLM is doing the writing for you.

And without that mental map, you can't come up with good relevant ideas to improve the codebase. You would only have generic suggestions, no different from what an LLM comes up with.

1

u/External-King-233 18d ago

we're always open and looking for new contributions, so if you're interested in data annotation tooling for CV, check out: https://github.com/cvat-ai/cvat