Maybe I'm missing the point of your argument here, but doesn't the maintainer of a project has an intrinsic right to manage the project in his or her own way? They are the gatekeepers to their own projects contributions.
And while I completely agree with your point that the project code can be seen as everyone's, how does some third party have the right to define how someone manages his or her own gate?
I'm looking at it more as, it's the maintainer's right to manage the project and it's issues as he or she sees fit. I can see how the maintainer doesn't have the right to manage the code outside of the repo, but telling someone how to manage their own repo...
I do have to agree to your point on the use of 'independent contractor' here. It'd be interesting to see what they are basing that on.
My state provides some 'tips' for small businesses. One is employee types, and this sort of a relationship is not an independent contractor. They make a point to say that simply calling someone an independent contractor has no baring on their status, exactly as you have said.
For those stating this would cause candidates to work for free:
"During this time, all Wonoloers would be considered as independent contractors and get paid for the job performed. Wonolo would take care of payroll as well as other administrative HR burdens involved."
This could also clear the air of expected compensation from the start.
Regardless, I do think the idea behind this approach has merit, but it could also use some realistic iteration itself.
I really don't enjoy seeing a single sentence with this many unnecessary commas or two em dashs. This is a 'grammar smell' just as obviously as when we see blatant code smells.
Thanks for sharing this. I may have missed this answer between all of the threads related to 2048, but has anyone found if there is a limit for the 4x4 tile size?
And while I completely agree with your point that the project code can be seen as everyone's, how does some third party have the right to define how someone manages his or her own gate?
I'm looking at it more as, it's the maintainer's right to manage the project and it's issues as he or she sees fit. I can see how the maintainer doesn't have the right to manage the code outside of the repo, but telling someone how to manage their own repo...