Yeah, I think this has the intractable problem of effectively useless commits.
One might argue that initially those problems would fix themselves as people would grab for the lowly hanging fruit, and that's fine, but I could see someone refactoring segments of code for no realistic reason, but "selling" it as an improvement, for the explicit goal of collecting the money.
Having a gatekeeper prevents this somewhat, but this company seems more interested in some kind of idealistic anarchy.
Although to be honest, after the first few changes to readme/documentation[.] there really isn't much more left to update. And the actual maintainer of the repo has the final say on deciding what will and will not be pulled in. If you are just sending me lines upon lines of refactored code that literally does nothing but just move stuff around, I'm not going to merge it. Simple as that.
[.] Finally! We'll be having people fighting each other for a more up-to-date documentation!
Comments
Yeah, I think this has the intractable problem of effectively useless commits.
One might argue that initially those problems would fix themselves as people would grab for the lowly hanging fruit, and that's fine, but I could see someone refactoring segments of code for no realistic reason, but "selling" it as an improvement, for the explicit goal of collecting the money.
Having a gatekeeper prevents this somewhat, but this company seems more interested in some kind of idealistic anarchy.
Although to be honest, after the first few changes to readme/documentation[.] there really isn't much more left to update. And the actual maintainer of the repo has the final say on deciding what will and will not be pulled in. If you are just sending me lines upon lines of refactored code that literally does nothing but just move stuff around, I'm not going to merge it. Simple as that.
[.] Finally! We'll be having people fighting each other for a more up-to-date documentation!