@stevenyholm
, great question. I answered that on the panel, but in case you missed, my answer is "Yes"! Projects are being open sourced for a reason: people want to get the community involved, regardless if it's an obscure project or a big one.
There are advantages on each:
for the obscure/smaller ones you're more likely to see the impact of your work and also to connect with people at a deeper level, as it's a small community. There the requirements might be lower for accepting and merging PRs.
for the big ones you'll probably have an easier time finding people to help you out, have more resources available to read (such as contributing guidelines and wikis) and contact with potentially big continuous integration and deployment infrastructures, but also the number of good issues to start with might always be low, as people run to get them.
@stevenyholm , great question. I answered that on the panel, but in case you missed, my answer is "Yes"! Projects are being open sourced for a reason: people want to get the community involved, regardless if it's an obscure project or a big one.
There are advantages on each:
for the obscure/smaller ones you're more likely to see the impact of your work and also to connect with people at a deeper level, as it's a small community. There the requirements might be lower for accepting and merging PRs.
for the big ones you'll probably have an easier time finding people to help you out, have more resources available to read (such as contributing guidelines and wikis) and contact with potentially big continuous integration and deployment infrastructures, but also the number of good issues to start with might always be low, as people run to get them.
Very helpful information. Thank you for taking the time to answer my questions, both during the live-streaming speaker discussion and in writing.