threads / discuss / 56886

Anything I can contribute?

Subject: Anything I can contribute?

## tl;dr

3 messages between Nov 13, 2021 and Nov 14, 2021.

replies: 2people: 3as markdown or json

Deng Kaisheng· Nov 13, 2021, 08:33 UTC · lore
Hi,
My name is Deng Kaisheng, a graduate student in National University of Sinapore (NUS) now major in computer science. I've read the introduction of your organization and I'm quite interested in what you're doing.
I want to do something and contribute to the community, and I wonder if there is something I can do. I major in computer science since undergraduate with a solid foundation in CS, and I'm also confident in my fast-learning skills. I have programming skills in C++, Python, Java, Objective-C, etc., and database skills in MySQL and Cassandra. 
I wonder if your organization is going to take part in the GSoC 2022, if possible, I would like to contribute to your project in GSOC 2022.
I am looking forward to your reply!
Best regards,
Kaisheng
Saksham Mittal· Nov 13, 2021, 10:41 UTC · re: Deng Kaisheng · lore

Re: Anything I can contribute?

Hello,

My name is Saksham Mittal, and I am about to enter university. I have experience with Linux, MySQL, Python and have learnt C as well. I would also like to contribute to git as well. I have spent the past week trying to look through the source code and am going over the documentation as well.

I am also quite eager to pick up some bugs and try my hand at fixing them. However, I am finding it difficult to find bugs people have reported.

Most searches of the mailing list for "[BUG]", "bug" etc. yield scores of results for patches other people have already submitted, which are likely being looked over by experienced maintainers anyway. How do we find issues in the mailing list, especially ones that are better suited to a beginner?

Cheers, Saksham

Bagas Sanjaya· Nov 14, 2021, 07:17 UTC · re: Saksham Mittal · lore

Suggested Project Ideas (was Re: Anything I can contribute?)

On 13/11/21 17.41, Saksham Mittal wrote:
Show 5 quoted lines
> Most searches of the mailing list for "[BUG]", "bug" etc. yield scores
> of results for patches other people have already submitted, which are
> likely being looked over by experienced maintainers anyway. How do we
> find issues in the mailing list, especially ones that are better suited
> to a beginner?
Breaking the thread.

I think you should check for open bugs against Git package for your distribution first, then come up here with bugfixes.

For project ideas, you can try converting/rewriting git-request-pull.sh in C. When converting, you can also add `-o/--output` option to write PR message to a file instead of stdout. You may want to mark PR message strings for i18n if you want.

-- 
An old man doll... just what I always wanted! - Clara

← back to recent threads