"There will be somebody that will contribute code actually, but most of the times this code will be about features you don't want to implement, or will not look like sane enough to be merged without a profound review, or will solve a good problem in a way that is not general enough, or simply the coder does not understand enough of the Redis internals or about your future plans to provide an implementation that is acceptable."When this happens should the maintainer write back to the contributor and explain to them how they would like to code to be written instead (can be very difficult to explain). Or if the maintainer has time should they fix the code up themselves and merge it in?
No comments yet.