There is an asymetry anyway as the company is probably contributing more than 90% of the code, maintain the infrastructure for the CI and website, do the promotion of the software, and more.
Depending of the motivation for your contribution, you get what you want, eg, the feeling of contributing to an open source project presumably used by many people, or having that entity to maintain your patch "for free".
You can keep your change in a fork if you like, but the likelihood that your fork is getting used is not that big, and mean more work from your side to rebase the change.
Depending of the motivation for your contribution, you get what you want, eg, the feeling of contributing to an open source project presumably used by many people, or having that entity to maintain your patch "for free".
You can keep your change in a fork if you like, but the likelihood that your fork is getting used is not that big, and mean more work from your side to rebase the change.