How to pick a project - new developer perspective.

zo0o0ot commented 2 years ago

Nice set of tweets here.

https://twitter.com/ujjwalscript/status/1532174600775225345

It would be nice to add a developer-centric section with these directions in it.

yashkhandelwal2203 commented 1 year ago

Please explain what task we have to perform.

zo0o0ot commented 1 year ago

The link above is a twitter thread with a lot of good advice.

This page should probably have an intro about how this was originally a thread on twitter, by DM Ujjwal Chadha, and give the link to the thread.

In case you're not able to see it, I'll paste it below:

Contributing to open source can open doors to your next programming job, but 90% people don't do it correctly.

Here's how to do it right

1. Choose a project

- It's a good idea to select one that you use yourself and want to see something improved

- Make sure it uses technology you understand and can build on

- Make sure it has active maintainers & a healthy community

2. Decide on a bug or a feature 

- The next step is to decide what you want to improve

- Fixing a spelling mistake in a repository is ok to get started, but not enough to impress a job interviewer

- Find an interesting problem that also impacts a lot of the project users

3. Understand the project code flow

- It's important to understand the project code, at least the part you will be making an impact in

- Clone the project, use debuggers and understand how the data is flowing and what different functions/classes are doing

4. Code a prototype

- Now that you understand the code, you are ready to start coding the problem you want to solve

- Write simple, short code as a proof of concept that what you are thinking works and wire everything up

5. Code with proper conventions

- Now follow proper project & language guidelines and convert your prototype code into quality code

- Make sure you read the contributions guide if present in the project readme

6. Create a PR & address feedback

- Next step is to create a PR and wait for feedback from the project maintainers

- If you receive any feedback, make sure to address it and communicate well with the reviewers

- Wait for the approval & finally merge it in!

Congrats! Now you are an open-source contributor!

- Understand the process of actually doing this on GitHub by reading this amazing guide by [@sumitsaurabh927](https://twitter.com/sumitsaurabh927)
 [https://resourcify.me/#/guides/open-source-contributions](https://t.co/T8ePgZ1fMT)

[resourcify.me](https://t.co/f9wD4RcExy) is [Ujjwal Chadha's](https://twitter.com/ujjwalscript) open-source project which aims providing guides and roadmaps to learn programming & technology for free and is now accepting your contributions. 

DM [Ujjwal Chadha](https://twitter.com/ujjwalscript) if you are interested in contributing to this project :)

The HOWTO page is probably already too long as it is, so I think I'm going to to a little reorganization(Defined in #31 ), and make a page dedicated to this thread that I'll link from the developer's page. I'll do an update to this issue when I've done the change.

zo0o0ot commented 1 year ago

I've created the file that will contain these posts:

https://github.com/hacktoberfesthowto/howto-blog/blob/ef414ea27db2b06b816740ca04e4629108b34d34/content/howto-picking-a-project.md?plain=1#L1-L7

Right now, it's a small file in draft mode, but it's the place where the content should go.

Once we're sure the content is good enough to publish, we'll change the frontmatter to say draft: false

hacktoberfesthowto / howto-blog

How to pick a project - new developer perspective. #19