We are already WAY past that line, just because people don't fork
> and just because someone has the time to write a patch doesn't mean they have the desire or time to run a project.
So DON'T run a project. Fork it, fix your problems and be done with it.
This seems to be at the core of the disagreements in this thread, one argument being that you shouldn't be expected to maintain a community project just because you put code on the internet.
Expecting that will lead to less open sourced code, which is bad IMHO.
Lastly, your last argument argument reads a little bit as "Not everybody has the desire or time to run a project, so what they want is somebody else to do it"
I might be reading in to much into it though. This thread has a fair amount of pronounced entitlement.
We are already WAY past that line, just because people don't fork
> and just because someone has the time to write a patch doesn't mean they have the desire or time to run a project.
So DON'T run a project. Fork it, fix your problems and be done with it.
This seems to be at the core of the disagreements in this thread, one argument being that you shouldn't be expected to maintain a community project just because you put code on the internet.
Expecting that will lead to less open sourced code, which is bad IMHO.
Lastly, your last argument argument reads a little bit as "Not everybody has the desire or time to run a project, so what they want is somebody else to do it"
I might be reading in to much into it though. This thread has a fair amount of pronounced entitlement.