I would recommend not making one, an interesting and active GitHub account (warts and all) is a much better way for employers to get an idea of your capabilities
How do i start contributing to OSS most of the time it seems overwhelming don't know where to start. I have contributed in some issue fixes with PR but those projects are not much active(PR were not reviewed). I want to participate in contributing OSS do you have any advice?
An active GitHub account is not always a good indicator. In my case, the majority of the projects I've worked on over the past few years are confidential, hence absent from my public Github. Therefore, in my case, a portfolio is more than necessary.
I would recommend not making one, an interesting and active GitHub account (warts and all) is a much better way for employers to get an idea of your capabilities
How do i start contributing to OSS most of the time it seems overwhelming don't know where to start. I have contributed in some issue fixes with PR but those projects are not much active(PR were not reviewed). I want to participate in contributing OSS do you have any advice?
Look for "good first issues". It's the best way I know to start contributing to OSS.
Thankyou
An active GitHub account is not always a good indicator. In my case, the majority of the projects I've worked on over the past few years are confidential, hence absent from my public Github. Therefore, in my case, a portfolio is more than necessary.
What's in the portfolio if the majority of projects are confidential?
Unfortunately, I cannot display them in my portfolio neither.
Never hurts to have one!
Actually not true. A poorly constructed portfolio has been a key reason for me not hiring a good few developers